Privacy Policy

Newsletter signups. When you subscribe from the newsletter page or any subscribe form on the site, we store the email address you give us in our subscribers list. We send the daily briefing to that address via Resend, a transactional email provider; replies go to hello@tokentimes.world.

Comments. Posting a comment requires signing in, and sign-in is a one-time email link — there's no password to set or store. The first time you comment, we ask for a display name; that name is saved to your account and shown publicly next to every comment you post, so choose it knowing that.

Likes. Liking an article doesn't require an account. It's tied to a random id we generate and store in your browser (in localStorage, not a cookie) the first time you like anything. That id isn't an identity — it exists only so the same browser can't like an article twice, which is also why a like can't be undone once it's counted.

Comment reports. Reporting a comment uses that same anonymous browser id. Reporting is deliberately quiet: you get an acknowledgement, and we don't show you what happens to the comment next.

Article view analytics. As you read, we record which article you viewed or clicked, its category, the type of event, a randomly generated per-browser id, the page that referred you, and any utm_source / utm_medium / utm_campaign parameters on the link you followed. If you arrived from a link in one of our newsletter emails — those links carry your email address so we can measure opens — that address is saved in your browser and attached to further view events on that browser.

Site analytics. Vercel Analytics runs on every page of this site.

Every comment is screened automatically before it's shown, and marked visible, hidden, or flagged based on that screening. If the screening step itself fails for any reason, the comment is left visible rather than silently blocked — a moderation outage is never allowed to swallow what you wrote.

Comments are public the moment they're posted — the body text and the display name you chose are visible to anyone who opens that article page, including search engines that index it. Don't put anything in a comment you wouldn't want to see indexed. Likes are not shown individually; only the total count on an article is public.

Subscriber emails, comments, accounts, likes, and analytics events are stored in Supabase (a hosted Postgres database with built-in authentication). The site itself — the pages you're reading — is hosted on Vercel.

We use a small number of outside services to run the site: Supabase (data storage and sign-in), Resend (delivers the daily newsletter email), Vercel (hosting and Vercel Analytics), and Google Fonts (the two typefaces on this page are loaded directly from Google's servers).

A few small values are kept in your browser's local storage, not cookies:

tt_client_id — a random id used only for anonymous likes and comment reports.

tt_liked_<article> — records that this browser already liked a given article.

tt_email — the email address from the most recent newsletter link you followed, if any, so view analytics can be tied to your subscription.

tt_session — holds your signed-in session token if you've signed in to comment; on a page you haven't signed in on, the view tracker uses the same key to hold a random per-browser id instead.

Email hello@tokentimes.world with a link to the comment or the email address on your account, and we'll remove it. Unsubscribing from the newsletter — via the link in any email or from the newsletter page — stops future sends but keeps your address on file marked inactive rather than deleting it; email us if you'd rather it were deleted outright.

If what we collect or how we use it changes, we'll update this page and the date at the top.