Privacy
Owner review draft: Add the operating entity, a monitored privacy contact, and confirmed provider retention details before treating this page as final.
Last updated: October 4, 2026.
ReadFlow turns documents and public web pages into a reading view with optional browser or Google narration. This page describes the data the current app handles.
Information ReadFlow handles
- Account: When you sign in, Supabase Auth stores your account and authentication information. Google sign-in shares the profile details Google provides to the sign-in flow. A display name you edit in Account management is saved with your Supabase Auth profile. If Google supplies an avatar, your browser loads that image from Google.
- Documents and progress: Without an account, imported documents, original PDF files, reading positions, and preferences are kept in this browser. When signed in, ReadFlow syncs documents, original PDF files, and reading positions to a private Supabase account. Unsynced browser copies remain on the device until synced or deleted.
- Google Drive imports: If you choose a Drive file, ReadFlow requests access to the selected file, downloads it to import, and stores the resulting document with your ReadFlow account. The Drive access token is held in memory for the import flow and is not stored with the document.
- Web imports: When you submit a public URL while signed in, the ReadFlow server fetches the page and returns readable HTML for import. The resulting document is saved to your account when cloud sync succeeds.
- Preferences: Voice, playback, highlighting, and display preferences are stored in this browser.
Listening and error reports
Scanned PDF OCR runs in your browser. ReadFlow downloads OCR worker and language-model files from its configured asset host when OCR is first used. The source PDF image is processed locally by the browser; recognized document text is then saved according to your browser-only or signed-in cloud-sync choice described above.
Bookmarks, sentence highlights, notes, and document tags are stored with the document. Signed-in documents sync these items to your private account. Selecting “Available offline” saves an additional account-scoped document and source-file copy in this browser. Removing the offline copy or deleting the account removes it from this browser. Signing out removes the offline copies for that account from this device.
Browser voices use the browser or operating system speech engine under that provider’s settings and privacy practices. Signed-in readers can optionally choose Google Neural2 narration. Before the first request in an open document, ReadFlow asks permission to send the played passages through its server to Google Cloud Text-to-Speech. The original document file is not sent to Google. Google states that Cloud Text-to-Speech does not log customer text or audio; see Google’s data-handling notice.
For reliability, the app can report a fixed error category and timestamp to ReadFlow's Cloudflare endpoint. It does not send the error message, stack trace, page URL, account ID, document title, or document text. Cloudflare processes the network request and may handle technical request data under its own policies. Reports are limited in the browser and at the endpoint.
For Google narration, ReadFlow saves generated audio, exact word timings, a content hash, voice selection, document identifier, and creation time in your private Supabase account. This prevents repeat synthesis of unchanged passages with the same voice. Cached audio is retained until you delete the document or account; it is included in account export. A small temporary audio cache in the open reader is cleared on close, sign-out, or revoking Google narration permission. ReadFlow also keeps daily character and request counters for usage limits. It does not log narration text or audio in error reports. Switching to a browser voice stops further Google requests; it does not erase already saved audio.
Service providers
Supabase provides authentication, database, and private file storage. Cloudflare hosts the website and runs its web-link and monitoring endpoints. Google provides sign-in, the user-selected Drive import flow, and optional cloud narration. These providers process data as needed to provide their services and under their own terms and privacy notices.
Security and retention
Account documents and PDF files are stored in a private bucket with account-scoped access policies. ReadFlow uses account-scoped database policies for documents and reading progress. No system can promise perfect security; protect your sign-in account and devices.
You can export account documents, progress, saved narration audio, timings, and usage counters from Account management. Its activity dashboard summarizes documents and reading positions already in your library; ReadFlow does not collect a separate listening-time or browsing-history record. Deleting your account removes its active database rows, private Storage files, and ReadFlow browser copies on the current device. Supabase provider backups may retain copies until their applicable backup retention period ends. The project plan and configured retention window have not yet been confirmed for this draft.
Your choices
You can use ReadFlow without signing in and keep documents only in the browser. Sign in to sync. Open Account management from your avatar to export data, sign out, or delete your account. “Delete account” permanently removes the account and its cloud data and clears pending or duplicate copies associated with the account in this browser. Local-only documents that were never added to the account remain in the browser and can be removed individually.
Contact and owner details
Operating entity: [Owner to add]. Privacy contact: [Owner to add a monitored email address]. Support: see the support page.