what Readr collects
When you sign in with Google, Readr receives your email address, name, and avatar URL from Google's OAuth response. These identify you across sessions.
When you upload an EPUB, the file is stored privately so that only you can read it. Reading state (which chapter you're on, your highlights, your chat threads with the AI companion) is saved so that it's there when you come back.
When you chat with the AI companion, the message you send — along with the relevant chapter context — is forwarded to a third-party language model provider so it can respond.
where it lives
- Account, reading state, highlights, and threads: Supabase Postgres (Supabase, Inc.).
- EPUB files and parsed assets: Vercel Blob (Vercel Inc.).
- Authentication and session cookies: Supabase Auth (Supabase, Inc.).
- AI companion responses: Anthropic, PBC and OpenAI, LLC are sent the prompt + relevant chapter excerpts when you chat. See their respective privacy policies for how they handle that data.
what Readr does not do
No analytics scripts, no advertising, no third-party trackers. Your reading data isn't sold or shared with anyone outside the sub-processors named above (which are required to run the app).
cookies
Readr only uses cookies that are necessary to keep you signed in. These are set by Supabase Auth and are removed when you sign out.
deletion
To delete your account and everything associated with it (uploads, highlights, threads, reading state), email srijakonjarla@gmail.com. Deletion is processed manually and usually completes within a few days.
changes
If this policy changes in a material way, you'll see a note on this page with a new "last updated" date.
contact
Questions, requests, or concerns: srijakonjarla@gmail.com.