Your reading,
your business.

The core action of HearFlow is simple: you highlight text, and we turn it into audio. To do that, the text you select is passed through our voice engine. That text is processed in memory to produce the audio you hear, and is not retained after your session ends.

We do not build a record of what you have read, do not archive transcripts of your selections, and do not use your selected text to train voice models.

To run your account and your subscription, we keep:

• Account Your email address and any display name you set.
• Subscription Your subscription status — trialing, active, paused, or cancelled — and the plan you're on.
• Billing The last four digits of your payment method and the country of the issuing card, for receipts and tax. Full card data is held by our payment processor; we never see it.
• Device A device identifier for the Mac(s) on which HearFlow is installed, so we can honor your seat limit.
• Diagnostics Anonymous error reports, if you've left them enabled in Settings. These contain stack traces and a coarse OS version — no selected text, no document contents.

It's worth being explicit. We do not:

• Store text Keep, archive, or transcribe the text you select for reading.
• Record audio Save copies of the audio HearFlow synthesizes for you.
• Profile you Build a profile of your reading habits, topics, or sites.
• Listen in Use your microphone, watch your screen, or track activity outside the moment you ask HearFlow to read.
• Sell data Sell, rent, or share your personal data with advertisers or data brokers.

A small number of services help us run HearFlow. Each is scoped to a single, narrow job, and each is bound by their own privacy and security commitments.

• Payments Stripe. Handles your card details, receipts, and renewal billing. We receive only metadata (status, last four, country).
• Infrastructure A cloud hosting provider in the United States hosts our account database and authentication.
• Email Resend. Sends account, billing, and security messages on our behalf — never marketing without your opt-in.
• Diagnostics An error-monitoring service receives anonymous crash reports if you've left diagnostics on in Settings.

Whether you live in the EU, the UK, California, or anywhere else, the same principles apply: the data we hold about you is yours to inspect, correct, export, or remove.

• Access Request a copy of everything we store associated with your account.
• Correct Update or fix anything that's wrong — usually right from your account page.
• Delete Ask us to erase your account and associated data. We will, within 30 days.
• Export Take your data with you in a portable, human-readable format.
• Object Object to any processing you're uncomfortable with; we'll find a way to honor it or explain why we can't.

To exercise any of these, write to us at the address in section 10. We'll respond within 30 days.

• Account Held while your subscription is active. Deleted within 30 days of cancellation, unless you ask us to keep it for an eventual return.
• Billing Receipts and tax records are retained for 7 years, to meet legal and accounting obligations.
• Diagnostics Anonymous crash logs are rotated after 90 days.
• Selected text Held only as long as it takes to produce your audio. Then it's gone.

Data in transit between your Mac and HearFlow is protected with TLS. Data at rest is encrypted on disk. Access to production systems is limited to a small number of engineers, gated behind hardware security keys, and audited.

No system is perfect. If we ever discover a breach that affects your data, we'll notify you within 72 hours of confirming the scope, along with the specifics and our response.

HearFlow is not directed at, and is not knowingly used by, children under the age of 16. If we learn that a HearFlow account belongs to someone under 16, we will close it and remove any associated data.

We'll update this policy when our practices change, when the law changes, or when we find a way to say something more plainly. For material changes, we'll email you at least 30 days before the change takes effect, with a summary of what's different.

Older versions of this policy are kept on file. You can request a prior version from us at any time.

Questions about your data, requests to exercise your rights, or anything else covered above — we'd rather hear from you than have you wonder.