What the Brief stores, why, and who handles it. Last changed 1 December 2026.
The Griffin Brief is published by Darius Griffin, called “we” on this page.
Reading the Brief needs no account. The site sets no cookie for readers and gives them no lasting reader ID. Vercel, which runs the site, sees each request (below).
The browser keeps a few display settings for the site in its own storage, such as the day or night theme and which story pictures have already been shown. They are never sent to us.
To draw the globe, the browser loads map code from jsDelivr, or from unpkg if jsDelivr does not answer. Pictures and audio load from the Brief’s storage at Supabase.
Signing up for the issue by email stores the email address, whether it has been confirmed, which form on the site it came from, and when. Each issue sent to the address is recorded. The email is sent through Resend.
The address is used to send the confirmation and the issue. Only an address confirmed by the link in the confirmation email is sent the issue, and the record of what was sent keeps an issue from going to the same address twice.
When an address leaves the email list, it stays on record, marked as having left, so it is never mailed again. An address that Resend reports as unable or unwilling to receive the email is marked the same way.
The email list is not linked to accounts or keys.
Buying the $29 plan needs an account. The account is kept by Supabase’s sign-in service: the email address used to sign in, when the account was made and last signed in, and Supabase’s own record of sign-ins. Signing in with Google also gives the account the name and profile picture link that Google shares.
Signing in puts a cookie in the browser that keeps the account signed in. Only the sign-in and account pages, and the payment and key steps, read it. Signing out removes it.
For a buyer the Brief also stores Stripe’s customer id for the account, the plan’s state and dates, and, for each key, a one-way hash and whether it still works. The key itself is shown once and never stored.
The account ties the plan and its keys to one buyer, and the plan’s state decides whether a key works.
Payment details are entered on Stripe’s page and never reach the Brief. Stripe is given the account’s email address and keeps the payment details under its own privacy policy.
Requests made with a key are logged with that key, as below, so they can be tied to the account that made it.
The Brief measures how the site is used with its own counter, not another company’s: which pages are opened and for how long, how far a page is scrolled, which controls are used, whether audio is played, how far a signup gets, the country or region, and the kind of device. Reads by programs and AI agents are counted apart from people.
The counter sets no cookie and stores no IP address. It tells one visitor from another only by a code that changes every day and cannot be turned back into a person, so it cannot follow a reader from one day to the next. The counts are used to see what is read and what breaks, and for nothing else.
Until the counter is switched on, nothing is counted.
The addresses built for programs and AI agents (/v1, the feed, llms.txt, the markdown files, the event pages and the MCP server) and the email signup form, with the links in its emails, count requests per minute from each IP address, to apply their limits. The count is kept under a shortened one-way hash of the IP address, a scrambled form that cannot be turned back into it, never the address itself. Counts older than an hour are cleared as new requests come in.
Each request to /v1 is logged: which /v1 address was asked for, with its query, the answer’s status, how many results it held and how long it took, the time, and a rough kind of caller, such as a browser, a bot or an AI agent. A request made with a key is logged with that key. No IP address is logged.
The log shows how the data is used and where it fails.
Nothing is deleted on a schedule today, apart from the per-minute counts.
This page changes when what the Brief stores changes, and the date at the top changes with it.
Questions about this page, or about what is stored, go to the contact details at dariusgriffin.com.