Legal

Privacy

What we collect, why, and how to get it back or delete it.

Last updated November 2026.

The short version

  • We collect what we need to run the site and personalize your feed, nothing more.
  • We don't sell your data. There's no ad tech on these pages.
  • You can export everything we have on you, or delete your account, from account settings.
  • We use a single first-party cookie for sign-in and a short-lived CSRF token. No third-party trackers.

What we collect

If you have an account, we store:

  • Your email address and a hashed password (bcrypt). Plain-text passwords are never stored.
  • If you use Sign in with Apple: the account identifier Apple gives us, and the name and email Apple shares (which may be a private relay address). No password is stored.
  • Optional display name and preferences (topics and regions you follow).
  • Your bookmarks, annotations, reactions, briefings, and reading history (used for “continue reading”).
  • If you enable two-factor authentication: an encrypted TOTP secret and hashed backup codes.
  • Sign-in audit log (IP address, user-agent, timestamp) for the most recent sign-ins.

Everyone who visits: for each page view we record the page, the page you came from, your browser and device type, how you arrived (for example a link tagged by a newsletter or video), any search you run on the site, a pseudonymous session ID kept in our session cookie, and a one-way hash of your IP address that can't be reversed to the address. If you choose “Accept all” in the cookie banner we also record your IP address and country. We use this to count real readers, separate them from automated traffic, and stop abuse. These records are deleted after 7 days.

If you subscribe to the daily briefing, we store your email address, the frequency you chose, where on the site you signed up, when you confirmed, and when we last sent you an issue. We email only to confirm the subscription and to send the briefing; every email has a one-tap unsubscribe link.

If you write to us through the support page, we store your message, the reply address you give (if any), and your browser's user-agent, so that we can answer you.

The iPhone app

The app shows this website, so everything above applies to it too. If you allow notifications, we also store the device's push token (an identifier Apple issues so alerts can reach the app on that device), the alerts you chose (breaking news, product updates, quiet hours), and your time-zone offset so that quiet hours follow your local time. If you are signed in, the token is linked to your account. We use these only to deliver the alerts you chose. Turning notifications off in iPhone Settings stops delivery, and deleting your account unlinks the device from you.

AI assistants (our MCP server)

AI assistants such as Claude can read Pure Report through our public MCP server at https://pure.report/mcp. It needs no account and asks for no personal data. For each request we log which tool was called, whether it succeeded, the client application's name and version as the client reports it, its user-agent string, and a one-way hash of the calling IP address. We use this for rate limiting and usage statistics and delete it after 7 days. We do not log search terms or any other tool arguments.

If an assistant files feedback with the submit_feedback tool, we store the text it sends, the article or event it refers to, and a hashed IP, so that we can read and answer it. Ask us through the support page to delete a ticket.

Why we collect it

  • Authentication and account security. Without an email and password, or Sign in with Apple, we can't sign you in.
  • Personalization. Topics and regions you follow weight your home feed and daily digest.
  • Social features. Bookmarks, annotations, reactions, and briefings need user-id linkage to function.
  • Abuse prevention. Rate limiting, MFA, and the sign-in audit log help us spot account takeovers.

Cookies

We set one essential cookie (the session cookie used for sign-in) and a short-lived CSRF token. We do not set advertising, analytics, or tracking cookies. There is no third-party tracker on this site.

Third parties

We use third-party services for hosting (Fly.io), for sending email (Resend), for crash and error reporting (Sentry — aggregated stack traces, no personal data), for the AI rewrite step (OpenAI), and Apple for Sign in with Apple and for the push notification service that delivers app alerts. Article text is sent to the AI provider as part of the debiasing pipeline; reader account data is never sent to the AI provider.

Your rights

You can, at any time:

  • Download an export of your data (JSON).
  • Delete your account. Deletion is permanent. Your email, name, sign-in details, notes, briefings, reading history and daily brief subscription are erased immediately. If you use Sign in with Apple, we also ask Apple to revoke Pure Report's access.
  • Contact us through the support page for any GDPR / CCPA request we don't already handle in-product.

Changes

Material changes to this policy are announced via a banner on the site and via the daily digest for subscribers, at least 30 days before they take effect. The “last updated” date at the top reflects the most recent revision.