Skip to content

Privacy

Unread is built so that it needs very little about you, and so that what it does hold is yours to export or delete at any time. No analytics, no advertising, no third-party trackers.

What is stored

DataWhereWhyHow long
Your position in a title (a beat index, the tier, whether you finished)Store (local JSON or Supabase)So recaps and the companion stop at the right placeUntil you delete it
Reading ledger (one row per day: date, beats advanced)StoreFor the pace forecast and the Markdown ledger exportUntil you delete it
Predictions (your text, the position it was written at, the score once you finish)StoreThe prediction journalUntil you delete it
Clubs you created or joined, and messages you posted (text, your display name, your position at the time)StoreThe spoiler-safe clubUntil you delete your data; the club itself stays for other members
"That spoiled me" reports and corrections you submitStoreTo fix ladders for everyoneKept with the ladder, without your identity once you delete your account
Display nameA cookie in your browserShown in clubsUntil you clear it
Anonymous id (local mode only)An httpOnly cookieTo tell your browser apart from another oneA year, or until you clear it
Email address (Supabase mode only)Supabase AuthMagic-link sign inUntil you delete your account
Ladders (story beats for a title)Store, sharedBuilt once for everyone; contain no user dataIndefinitely
Tripwire log (work, tier, position, the spans removed)Store, server onlyTo catch spoiler leaks; contains no user idRolling, last 1000 entries
Readers on your account (a name each)StoreHousehold mode: separate positions per personUntil you remove the reader or delete your data
Shared recap links (the recap text, the position, your reader id)Store, public by linkSo a friend can read a spoiler-safe recapUntil you delete your data
Digest subscription (on/off, an unsubscribe token)Supabase onlyThe weekly counts-only emailUntil you turn it off or delete your account
Subtitle timings (seconds per beat, which episodes are timed)Store, shared ladderThe TV Exact tierWith the ladder; the subtitle text itself is not stored

Imports from Kindle, Kobo and Audible are parsed in your browser; only titles and a percentage, page or location are sent to propose a position, and highlights, notes and listening history stay in the file. Subtitle files are parsed in your browser too; cue text is sent once for alignment and discarded.

Your uploaded EPUB is parsed in your browser. Only the plain chapter text is sent once, to build the Exact ladder, and the file itself is not stored unless you explicitly choose Supabase Storage in a future version. Unread keeps a short hash of the text to label the ladder's provenance.

What is sent to the model

Every generation (recap, cast list, open threads, companion answer, prep brief, parent guide) sends:

Nothing else: no email, no id, no reading history, no other titles. Prompts are versioned so you can see exactly which text produced a result. With the Stub provider, nothing leaves the server at all.

Metadata lookups

Searching sends your query to Open Library (books) and TMDB (TV and film), or to Google Books when a key is configured. These services see the query and your IP address. With UNREAD_METADATA=fixtures nothing is sent.

How to export or delete

Open Account. "Export JSON" downloads everything above that is tied to you. "Delete everything" removes it immediately and signs you out. In local mode this also clears the cookie, so you become a new reader. Ladders are not deleted because they contain no user data; corrections you contributed stay attached to the ladder but lose their link to you.

Cookies

Unread sets at most three cookies: the anonymous id (local mode), the display name, and the Supabase session (Supabase mode). None are used for tracking.