Skip to content

New: deep research, balance and auto-reload tools in the keyless MCP server. Install in one line

Legal

Privacy

ContextFetch is an API for AI agents. We keep as little as we need to run it and bill for it, and this page lists all of it.

Last updated 17 October 2026

In short

  • We store a SHA-256 hash of your API key, never the key itself (except for 24 hours after checkout so you can copy it).
  • We need no account, name or email to use ContextFetch. Stripe handles payment details; we never see your card number.
  • We keep no access logs of API requests and do not record which queries a key or IP address made.
  • We do not sell data, share it for advertising, or train models on your queries or results.

What we store

This is the complete list of data the API keeps about you or your requests.

DataWhyKept for
SHA-256 hash of your API keyTo recognise your key. The key itself is never stored.Until you ask us to delete it
Your plaintext API key, onceSo the checkout success page can show it to you.24 hours after checkout, then deleted
Credit balance, pack and creation timeTo bill requests.With the key
Stripe customer idStripe creates it at checkout; it links the key to its purchases.With the key
Saved payment method idOnly if you turn on auto-reload, so the saved card can be charged.With the key
Auto-reload settings and month-to-date reload spendTo apply your threshold and monthly cap.Settings with the key; spend records about 40 days
Credits used per day, per keyTo report your burn rate on /v1/balance.8 days
Keyless request count per IP address (IPv6: per /64)To enforce the free tier of 25 requests a day.Until the end of that UTC day
A search query and its resultsTo answer the same query again quickly. Not linked to who asked.15 minutes
Text of a fetched pageTo avoid fetching the same page twice.Up to 48 hours
Public pages found by web searchOur shared search index.Until removed from the index

URLs you send us

URLs you pass to /v1/contents, the Reader (/r/) or as the source of /v1/findSimilar are fetched for you and never added to the shared search index, because they may carry private tokens. URLs with a username or password in them are rejected. Only pages that our web search found on its own enter the index.

Who else sees your data

  • Search sources. To answer a search we send the query text to the sources we search: a SearXNG metasearch instance we run (which forwards it to public search engines), Wikipedia, Hacker News (Algolia), Stack Exchange, GitHub and arXiv. They see the query, not who sent it. Do not put secrets in queries.
  • Websites we fetch. We fetch result pages and the URLs you send from our server, identified as ContextFetchBot/1.0. Those sites see our server's address, not yours.
  • Stripe processes payments and receives the details you enter at checkout, under Stripe's privacy policy.
  • Vercel hosts this website and processes the request data needed to serve it, such as your IP address. The site sets no cookies of its own and runs no analytics or advertising scripts.
  • Hetzner provides the server in Helsinki, Finland, that runs the API, its database and caches.

Logs

The API keeps no access logs: neither our web server nor the application records requests, IP addresses or queries. Error logs can include the URL of a page that failed to load and, when an auto-reload payment fails, the hash of the key involved (never the key). They are capped at 30 MB per service and the oldest lines are overwritten.

Security

  • The API and this website are served over HTTPS only.
  • Your key is checked against its SHA-256 hash; the balance checker sends it in a header, never in a URL.
  • Every fetch goes through a guard that allows only public http(s) addresses and re-checks each redirect.
  • The server accepts SSH with keys only.

Your choices

You can use ContextFetch without a key, and buy credits without creating an account. To delete the data held for a key, turn off auto-reload, or ask what we hold, email support@contextfetch.dev from the address you used at checkout, or include your Stripe receipt. Deleting a key also deletes its remaining credits.

Changes

When what we store changes, we update this page and the date at the top. The current version always lives at contextfetch.dev/privacy.

Contact

Questions about privacy: support@contextfetch.dev.