Privacy Policy

Your email and password. The password is hashed by our authentication provider; we never see the plaintext and we can't recover it for you.

The briefing configuration you enter: country, focus description, keyword list, and the recipient addresses you add.

The billing state that our payment provider sends us through webhooks — subscription ID, status, trial end date, cycle. Card details stay with the payment provider; we neither see nor store them.

A record of which stories went into which briefing, so the next morning doesn't repeat yesterday's news. That record keeps story identifiers and timestamps for 14 days, and is scoped to the briefing.

Standard server logs from the hosting layer: IP, user agent, request paths, timestamps.

When you add a person to your team, we store their address and a random unsubscribe token.

We don't fingerprint recipients, we don't track opens with a pixel, and we don't sell or share the list. Any recipient can unsubscribe from the link in any briefing's footer, without logging in and without going through you. Once they do, we switch their email off, record when they unsubscribed, and show that to the team owner, who has to confirm before turning it back on.

We fetch publicly available articles from the source list for each covered country. For each article we keep the URL, headline, publication date, and the full text for 60 days, then delete. Sent briefings follow the same 60-day limit.

The full text is stored to write the daily summaries and to power search. We never redistribute it. Connected AI apps (see below) receive short excerpts with a link to the original, not the article. Search is gated so that only subscribers with an active subscription in a country can search that country's archive.

You can authorize an AI app, such as Claude or ChatGPT, to read your news briefings. An authorized app receives your organization's briefings and excerpts (up to 1,500 characters, plus a link to the original) of the news articles we gathered for your country. Access is read-only: the app can't change your account, your briefings, or your recipients.

You can revoke an app at any time under Account → Connected apps. Revoking deletes the app's access, so it stops working from its next request.

We rely on a small set of processors to run the service:

• A database and authentication provider — holds almost everything in §01 except logs.
• A hosting provider — hosts the app and ingests server logs.
• A payment provider — billing and merchant of record. Card data stays with them under their own privacy policy.
• An email delivery service — sends the morning emails on our behalf.
• A rate-limiting service — we send a hashed session identifier, not account data.
• An LLM provider— generates the summaries. We send the article text and your focus and keyword configuration. We don't send account identifiers.
• A search provider— turns article text and your search questions into search fingerprints. We don't send account identifiers.

We do not run third-party analytics in the app. No Google Analytics, no Segment, no ad pixels, no marketing SDKs.

Raw news stories

60 days, then auto-pruned by a scheduled database job.

Sent briefings

60 days, then deleted by the same scheduled job.

Per-briefing delivery records

14 days.

Server logs

30 days at the hosting layer's default.

Account data

As long as the account exists. Delete the account and the row goes; briefings, recipient lists, and delivery records cascade with it.

Billing records at the payment provider

Retained under their policy, not ours.

You can export your data: email us and we return JSON within 30 days of the request.

You can delete your account from the account page once that page ships, or by email. A delete cascades across your briefings, recipients, and delivery records.

You can correct anything the dashboard exposes by editing it directly. For fields the dashboard doesn't yet surface, email us.

You can withdraw consent at any time: cancel the subscription, unsubscribe a recipient, or delete the account.

One session cookie, set by our authentication provider so you stay logged in between page loads. No analytics cookies. No ad trackers. No cross-site identifiers.

The database runs in an EU-West region. Our hosting, email, payment, and LLM providers operate globally; in the normal course of the service, data will be processed in the United States as well as the EU.

If your legal environment requires data residency inside a specific jurisdiction, this service isn't the right fit today.

privacy@briefer.media for privacy and data questions. hello@briefer.media for everything else. Expect a reply within 5 working days; regulator-backed requests get priority.