Privacy Policy

Last updated July 19, 2026.

AgentRead ("we," "us") is a tool that fetches and distills web pages for AI agents. This page describes, plainly, what data we collect and why. We are an early-stage product — if anything here is unclear, email us and we'll clarify or fix it.

What we collect

  • Account info. If you sign in with Google or an email magic link, we store your email address and (for Google) the name/avatar Google provides. Sign-in itself is handled by Supabase Auth — we never see or store your Google password.
  • Read history.URLs you submit through the Read API, Playground, or MCP server, along with the resulting ReadScore, flags, and byte/token counts. If you're signed in, this is tied to your account so your dashboard can show it to you; if you use the anonymous public ReadScan tool, it is not tied to an account.
  • API keys. We store a one-way hash of any API key you generate, never the plaintext (which is shown to you once, at creation, and never again).
  • Waitlist emails. If you join the waitlist, we store the email address you provide.

What we don't do

We don't run third-party analytics, ad trackers, or session-replay scripts on this site as of this writing. We don't sell your data. We don't use the content of URLs you scan for anything other than returning you the result and (if you're signed in) showing it back to you in your own dashboard.

Where data lives

Account and application data is stored in Supabase (PostgreSQL), protected by row-level security so your data is only ever readable by you and by our service for operating the product. The underlying extraction engine makes a real HTTP request to whatever URL you submit — that request is visible to the target site's own server logs, the same as any other web request.

Your choices

You can revoke any API key at any time from your dashboard. You can delete your account and associated data by emailing us — we don't yet have a self-serve delete-account button, and we're telling you that plainly rather than pretending otherwise.

Contact

Questions about this policy or your data: reach out via the contact details on our GitHub repository.