Privacy policy
Last updated November 10, 2026.
This policy explains what Trace the Roots ("we", "us", "the site"), run by one person with help from AI agents, collects, why, who else handles it, how long we keep it, and how to ask us to delete it. If something is unclear, email hello@tracetheroots.com.
You can read the site without an account. We don't show ads. We don't sell personal information. We don't use advertising cookies.
Who is responsible
Trace the Roots ("we", "us", "the site"), run by one person with help from AI agents, decides how and why personal data on this site is used. Contact: hello@tracetheroots.com.
If you only read the site
You don't need an account, and we don't ask you for a name or an email address. The servers that deliver the pages, run by Cloudflare, see technical details of the request, including the IP address, the browser type, and the page asked for. Cloudflare uses that to deliver the site and to block attacks. We have not turned on Cloudflare's web analytics beacon. If we turn it on later, we will update this policy.
Your browser keeps a few settings on your own device, described under "Cookies and local storage". Those settings are not sent to our database.
Pictures on event pages are loaded by your browser from Wikimedia. That request goes to Wikimedia, not through us, so Wikimedia sees the IP address of the browser that asks for the picture.
Account, username, and Google sign-in
Accounts are created with Google sign-in, through Supabase. Email sign-in links are not offered. When you sign in, we receive and store:
- the email address on the Google account, and the account identifier Google and Supabase use for that sign-in;
- a public handle and display name, which start as a neutral reader id, not your Google name;
- a profile photo only if you upload one later. A new profile does not copy a Google photo. An older account may still show a photo or name that was copied from Google until that person changes it;
- sign-in records kept by the sign-in system, including when the account was created and the IP address used for sign-in.
Your email address is not shown on your public profile. The sign-in system may also hold the name or photo Google attaches to the sign-in, even when the public profile does not use them.
What you do while signed in
- Posts: notes, comments, sources, books, videos, and event proposals, including links and whether you marked something as your own work. Live posts are public and show your handle.
- Votes: up and down votes, and events you mark as mattering. Other people see totals, not your individual votes.
- Reading history: events you opened and roots you traced while signed in, and which days you were active. We use this for streaks, badges, challenges, and to avoid repeating events.
- Settings: theme, whether graphs start grouped, whether you want occasional emails, whether you appear on the Sponsors wall, and the time zone your device reports. We store that time zone as a setting. We do not turn it into a street address.
- Reports: what you flagged, the reason, and any detail you add. The person reported is not told who reported them.
- A short error report if the page itself fails, limited to a short message and the path of the page.
- Moderation notes from automatic screening and from a person reviewing a post.
Your public profile can show your handle, display name, photo, bio, join month, reputation, contribution counts, badges, streak, a calendar of active days, and your live posts. It does not show your email, your individual votes, or the list of events you opened.
Gifts and subscriptions
Card payments are handled by Stripe. The site never sees your card number, card expiry, or bank login. What we store is the amount, the currency, the date, the tier (Supporter, Sponsor, or Patron), the billing interval, and Stripe reference ids: a customer id, a checkout session id, a subscription id, an invoice id, and the event id for the notice Stripe sends us. We also store whether the badge is permanent and how many subscription months have been counted.
A crypto claim stores the chain you select, the transaction hash, the amount, the token or coin, and the sending wallet address when the public transaction shows one. Those details are already public on the blockchain. We do not take custody of a wallet and we do not ask for a seed phrase.
A supporter badge and, for a subscription, the month count, are shown on your public profile.
Waitlist and email you send us
If you join a supporter waitlist, we store that email address and the date, only so we can write once about supporting the site. If you email hello@tracetheroots.com, we keep the message and the address so we can reply.
Screening
Each note, source, comment, proposal, and profile text is checked by rules that run on our side. When an AI screening key is configured, the text of that submission, not your email address, is also sent to Anthropic's API so a model can flag spam, threats, and private personal information. If that service is not configured, or if it does not answer, the post waits for a person instead of going live unchecked.
The historical pages themselves were compiled and checked with the help of AI agents, from public sources. That work is described in the terms.
Who else handles data
We don't sell personal information, and we don't share it for advertising. The companies below process data only to provide their own service:
- Cloudflare delivers the site, protects it, and receives the technical details of each request, including the IP address. It may set a cookie that is needed to check that a visitor is not an automated attack. That cookie is not used to advertise to you.
- Supabase stores the database, sign-in records, uploaded photos, and the server functions that receive posts and gifts.
- Google confirms a Google sign-in and sends the email and account identifier described above. Google's own policy covers what Google does with that sign-in.
- Stripe processes card gifts and subscriptions and hosts the page where a subscriber cancels. We don't receive the card number.
- Anthropic, only when AI screening is switched on, receives the submission text described above.
- Wikimedia receives the browser request for an event picture, as described above.
- KLIPY, only if the GIF button is shown in a comment box. Your browser then asks KLIPY for GIFs, and this site stores a random id in local storage on your device for that picker. The GIF button is hidden when no key is configured.
- Blockchains used for a crypto gift. A transaction you broadcast is public on that network. We don't control the network.
We may also disclose information if the law requires it, or to protect someone's safety or to respond to a legal claim. If operation of the site is transferred, the data needed to run it would move with it under this policy, and we would tell account holders.
These companies may store data somewhere other than where you are. Ask us if you want the safeguards named in their contracts.
Cookies and local storage
We don't use advertising cookies or a cross-site advertising profile. The site uses local storage and session storage on your device:
- Sign-in session: Supabase keeps the session token in local storage so you stay signed in. Signing out removes it.
- Display: theme, whether graphs start grouped, whether the side list is collapsed, whether the era list is open, and whether you have dismissed the short intro or the tour.
- Saved events and up to 2,000 recently opened event ids, kept on this device so Surprise me and Discover can skip what you just saw. That device list is separate from the reading history stored with a signed-in account.
- After you choose Sign in: the page to return to, and a pending vote, kept in session storage for that tab and cleared after sign-in.
- A Discover trail in session storage so a refresh can restore it.
- A random id for the GIF picker, only if that picker is available.
Preview mode, used only on unpublished copies of the site, keeps a demo account in local storage on that browser. The live site does not use that store for real accounts.
Cloudflare may set a security cookie as described above. You can clear site data in your browser. You will be signed out, and the on-device choices will reset.
How long we keep it
- Account, profile, settings, votes, and reading history: until you delete the account. We don't automatically delete quiet accounts.
- Posts you delete, or posts removed for breaking the rules: removed posts and their moderation notes may be kept for up to 6 months so a decision can be reviewed, then deleted, unless we need them longer for a legal claim. Content the screen refuses outright is not saved as a live post.
- Reports: until they are resolved, and then for up to 12 months.
- Payment and crypto-claim records: for as long as the law that applies to the operator requires us to keep financial records, even after the account is deleted.
- Server and sign-in logs that include an IP address: no longer than 90 days, unless a specific log is needed to investigate abuse.
- Email you send us: up to 3 years after the last exchange, unless a legal claim requires longer.
- Waitlist email: until the one message is sent, then deleted, or sooner if you ask.
- On-device settings: until you clear them.
Deletion and other requests
You can delete your account from profile settings. That deletes the account, profile, uploaded photo, settings, votes, reading history, badges, notes, sources, comments, proposals, and reports tied to the account. It cannot be undone. Payment and crypto-claim records we must keep, and anything needed for a legal claim, can remain. If you cannot sign in, email us and we will delete the account.
You can also email hello@tracetheroots.com to ask for a copy of the personal data we hold, a correction, or deletion. Write from the email on the account, or tell us the handle so we can confirm it is you. We will answer within 30 days. We may refuse a request that is clearly unfounded or excessive, and we will say why. You can object to occasional emails at any time, and every such email has an unsubscribe link.
Children
Children under 13 are not allowed to create an account. We do not knowingly collect personal data from a child under 13. If you believe a child under 13 has an account, email us and we will delete it. Anyone can read the public pages without an account.
Security
Traffic to the site is encrypted. Database rules limit what each signed-in person can read or change. No system is perfectly secure. If a breach puts your data at serious risk, we will tell you as the law that applies to us requires.
Changes
If we change this policy, we will post the new version here and change the "Last updated" date. If a change materially expands how we use personal data, we will give account holders notice on the site or by email before it takes effect, when we reasonably can.
Contact
Email hello@tracetheroots.com.