Privacy
Plain language, because we read the data policy too.
Last updated: July 2026
This website
- No cookies. No analytics. No trackers. This site is a static page that loads nothing from anyone else.
- Standard infrastructure logs exist (IP address, requested page, timestamp) on our server and at Cloudflare, kept briefly for operations and abuse prevention. That's all.
The forefetch service (API users)
- What we store: the text your integration sends us via
remember()andobserve(), plus operational metadata (row ids, timestamps, the readiness scorecards). That's the product: it's a memory. - Hard isolation: your API key maps to your own tenant with its own memory engine and its own database file. Cross-tenant access has no code path.
- What we never do: we don't train models on your data, we don't sell or share it, and we don't read it except when you ask us to help debug something.
- Embeddings are computed on our server, not sent to any third-party AI service. Your content does not leave our infrastructure to be processed.
- Deletion: email us and we delete your tenant's data and revoke the key. Gone means gone.
Infrastructure we run on
- Amazon Web Services: servers and storage, EU (Stockholm) region.
- Cloudflare: DNS and the network tunnel that carries traffic to us.
These providers carry or hold data as part of hosting the service; neither is given access to your memory content beyond what transporting and storing it requires.
Contact
Yashvardhan Goel · [email protected]
forefetch is in its design-partner phase and is operated by an individual
developer. This policy is deliberately plain-language; it will be formalized (and reviewed
by an actual lawyer) before general availability. If anything here is unclear, ask. The
honest answer is the whole brand.