Privacy Policy

Folio is a personal book-formatting and reader tool built by Jacob Siler. This page explains, in plain English, what data Folio handles and what happens to it. No legalese, no dark patterns.

What Folio stores

When you use Folio signed in with a Google account, the following is stored in Google Firebase (operated by Google LLC under Google's privacy policy):

• Your manuscript content — chapter text, titles, and formatting settings you've chosen.
• Your Firebase user id and the email address associated with your Google sign-in.
• Audio files you've generated via the TTS feature, cached in your own browser's IndexedDB (never uploaded to Folio's servers).
• If you enable a paid release, your Gumroad product id is stored as part of the release metadata. Buyer license keys are never stored on Folio's side — each reader's key stays in their own browser.

What Folio does not do

• No analytics. No tracking pixels. No behavioural profiling.
• No advertising. Folio will never serve ads and will never let third parties do so on its behalf.
• No selling of data. Ever. Your manuscript is your manuscript.
• No email marketing or newsletter lists built from your account. If Folio ever needs to email you, it'll be because you asked it to.

Third-party services Folio relies on

Folio is a thin client built on top of a few well-known platforms. Each has its own privacy policy, linked below:

• Google Firebase — authentication and Firestore storage for your account and manuscripts. Firebase privacy.
• Google Cloud Text-to-Speech — optional, opt-in. Only used if you generate audio and supply your own API key. Text you submit is sent to Google under their standard terms. Google Cloud DPA.
• ElevenLabs — optional, opt-in. Same deal: only used if you turn it on and supply your own API key. ElevenLabs privacy.
• Gumroad — only if you publish a paid release. Readers pay on Gumroad; Folio never sees card details or full contact info. Gumroad privacy.
• Cloudflare Workers — used as a stateless proxy for the TTS and paywall APIs. Folio's workers do not log or persist request bodies.

Your rights

• Delete any folio at any time from the sidebar — the Firestore document is removed immediately.
• Sign out to return to a guest/anonymous state.
• Request full account deletion by emailing the address below. All your Firestore data will be deleted within 14 days.
• Request a copy of your data in JSON. Same email, same timeline.

Cookies and local storage

Folio uses your browser's localStorage and IndexedDB for app settings, bookmarks, annotations, and cached audio. These stay in your browser and are not transmitted to Folio. Firebase uses cookies for authentication state; that's a Google-managed concern and you can clear them at any time via your browser settings.

Children

Folio isn't intended for children under 13. If you're younger than that, please don't create an account. If you're a parent or guardian and believe a child has set up an account, contact me and I'll delete it promptly.

Changes to this policy

If any of the above changes materially, this page will be updated and the “last updated” date above will reflect the change. For significant changes that affect existing users, I'll email the address on your Google account.

Contact

Questions, requests, or concerns: folio@jacobsiler.com. I read every message personally.