Privacy policy.
Storyflo is in private alpha. This policy describes what we collect, why we collect it, and how to get rid of it. It will get more formal once we exit alpha — until then, the short version below is the actual implementation.
What we collect
- Email address — when you join the alpha waitlist or forward an article to story@storyflo.com. Stored in a single database row keyed by your email.
- Forwarded article URLs and contents — when you forward newsletters / links, we fetch the URL, extract the article body via a readability extractor, render it to audio, and cache the audio. We do not store your full email or its metadata beyond the sender address and the URLs we extracted.
- Listening events — when you play audio, we log the article id and listened seconds. Used only to surface what stayed in your queue and to honor publisher revenue shares.
- IP address (hashed) — to rate-limit endpoints against abuse. We store a SHA-256 of your IP, never the IP itself.
What we do not collect
- Cookies for ad tracking or third-party analytics.
- Your full email body or attachments.
- Your contact list or anything in your inbox other than messages you forward to us.
- Payment details — there's nothing to pay yet.
Where it lives
Application data: a Postgres-compatible store hosted on Fly.io in the United States.
Audio cache: Cloudflare R2, replicated across Cloudflare's global network for delivery.
Inbound email: routed via Postmark Inbound and Microsoft 365 (story@storyflo.com mailbox).
Sharing
We don't sell or trade your data. The only third parties that see anything are the operational vendors above (Fly, Cloudflare, Postmark, Microsoft 365). Each handles only the slice they need: hosting, audio delivery, inbound email, mailbox.
Publishers we partner with see aggregate listening counts for their own articles — never your email or any identifier that could re-link plays to a person.
Deleting your data
Email legal@storyflo.com from the address we have on file and we'll wipe everything tied to your account within 7 days. Audio cache keys are hashed by text content, not by user, so other listeners' plays of the same article are unaffected.
Changes
We'll update this page when the surface changes — the Last updated stamp at the top is authoritative. Material changes will also be sent to anyone on the alpha waitlist.
Contact
Questions, requests, takedowns: legal@storyflo.com.