Reed
Support Privacy Terms

Privacy Policy

Last updated: 17 August 2026

Reed is Mac dictation. You sign in with Apple in the app. There is no website account.

Summary

We store an Apple user id, a session, and usage counts, so we can transcribe and enforce your plan. By default, speech is turned into words on your Mac. That text is sent to Reed, then to Google, to clean up. The recording stays on your Mac on that path. If you choose Cloud in Settings, or Apple heard nothing usable, the audio is sent instead. We do not keep your audio, and we keep no copy of your transcripts. Reed does keep your recent transcripts on your own Mac so you can copy them again — that history never leaves your computer and you can switch it off or delete it. We do not sell personal information, and there is no analytics or tracking in the app.

Who we are

Reed is operated by Fuse Link Inc. (fuselink.app). Bundle id app.fuselink.reed. App Store id 6801225937. Questions: support@fuselink.app.

What we collect

You provide

  • Sign in with Apple. We store Apple’s sub identifier. We never receive a password, and we do not ask for your name or email.
  • Audio you record while the dictation key is held. It is captured in memory, never written to a file on your Mac. By default it does not leave your Mac. Apple Speech Recognition turns it into words there. Those words are sent to Reed’s server, which passes them to Google’s Gemini model to clean up punctuation and wording. If you choose Cloud in Settings, or Apple returned nothing usable, the audio itself is sent to Reed and then to Google for transcription. In every case we never write audio to a database or a log.
  • The name of the app you are dictating into, on every plan. Just the name and its bundle identifier — “Slack”, com.tinyspeck.slackmacgap — sent with the request so the text can be written the way that app is written. Not the window title, not the page you are on, not what is in it. It is used to build the request and is never stored or logged.
  • On-screen text, on Pro+ only. See the section below. Pro+ is not currently offered for sale; this still applies if your account already has it.
  • Support mail, if you write to us.

We create

  • A session: a short-lived access token and a refresh token. The server keeps only a one-way hash of the refresh token.
  • Usage counters: how many words you have transcribed in the current period, and your plan.
  • Diagnostics: how long a clip was, how many bytes, how long the request took, whether it succeeded. No transcript text and no audio ever goes into a log.

Screen text on Pro+

If you have Pro+ and use “Read text from screen”, Reed captures the region you select, reads the text from it on your Mac using Apple’s Vision framework, and discards the image. The image never leaves your Mac.

The text it read does leave your Mac. Up to 8,000 characters are sent with your next dictation so the model can fit what you say to what you are filling in. It goes to Reed’s server and then to Google, exactly like hop-1 text, and like that text it is not stored by us.

Only select regions you are willing to send. Do not use it on a password manager, someone else’s message, or anything you would not paste into a cloud service.

Who we share it with

WhoWhyWhat they get
Apple Sign in, App Store subscriptions, and on-device speech recognition when Apple hearing is on Purchase data; speech audio processed on your Mac under Apple’s speech APIs
Google Cloud Runs our server, database, and the Gemini model that transcribes or cleans up Hop-1 text (default), audio (Cloud path or empty hop-1 fallback), any Pro+ screen text, your Apple sub, usage counters
RevenueCat Subscription and entitlement handling Your Apple sub, purchase state

That is the complete list. There is no advertising, attribution, or analytics SDK in Reed. RevenueCat’s privacy information is at revenuecat.com/privacy.

What Google does with it

Google does not use your data to train its models. That is contractual, not a promise we are making on their behalf — see Google’s Service Specific Terms.

Google may hold inputs briefly to operate the service: up to 24 hours of caching, and up to 90 days of logging for abuse monitoring. We do not store your audio or transcripts; our processor may hold them for those short periods. We are working to reduce this to zero retention, and this policy will be updated when that is in force.

Where it goes

Our server and database run in Belgium (europe-west1). The cleanup and Cloud-transcription model is served from Google’s global endpoint, so that step may happen outside the EEA. Those transfers are covered by Google’s Cloud Data Processing Addendum and the Standard Contractual Clauses. On-device Apple speech stays on your Mac.

How long we keep it

  • Audio: not kept by us. Discarded as soon as the transcript comes back. On the default Apple path it was never uploaded.
  • Transcripts: not kept by us. The text is returned to your Mac and pasted. Our server never writes it down. Your Mac keeps the most recent ones locally — see History below.
  • Apple sub, plan, usage counters: until you delete your account.
  • Refresh tokens: as a hash, until used or expired. They are single-use.
  • Diagnostic logs: standard retention, and they contain no content.

History, on your Mac

Reed keeps your most recent transcripts so you can copy something again after it has been pasted. This is on by default, because the moment you need it is usually after the text has already gone somewhere you did not want.

  • It is stored only on your Mac, at ~/Library/Application Support/Reed/history. It is never uploaded, never backed up to us, and we cannot read it.
  • The file is encrypted, with a key held in your Mac’s Keychain.
  • Text only. No audio, and no Pro+ screen text.
  • It keeps the most recent 50 by default. You can set 10, 25, 50, or 100 in Settings.
  • Reed skips a transcript while macOS reports a password field has focus.
  • Switch it off in Settings → History at any time. “Clear history” deletes everything kept, and deleting your account deletes it too.

Because it never leaves your machine, this history is yours rather than ours: there is nothing here for us to hand over, and nothing for us to lose.

Voice and biometrics

We do not create a voiceprint. We do not identify you by your voice, do not match your voice against anyone else’s, do not use voice for authentication, and do not analyse your voice for emotion, health, or any other characteristic. Your audio is used for one thing: turning it into text and giving the text back to you.

Your rights

If you are in the EEA or UK, you have rights of access, rectification, erasure, restriction, objection, and portability.

The practical answer for most of these is that we hold very little: an identifier, a plan, and a word count. There is no transcript archive to request, because we never built one.

To delete everything: Settings → Delete account. This removes your user record and all your sessions from our database immediately. To cancel a subscription, use System Settings → Apple ID → Subscriptions.

For anything else, write to support@fuselink.app.

Children

Reed is not directed at children and we do not knowingly collect data from anyone under 16.

Security

Audio is never written to disk on your Mac. Tokens are held in the macOS Keychain. The server verifies Apple identity tokens against Apple’s public keys, stores refresh tokens only as hashes, and is the only thing permitted to call the transcription model — there are no model credentials in the app.

Changes

We will update this page and change the date above. Material changes will be flagged in the app.

Contact

Questions or privacy requests: support@fuselink.app.

For product help, see Reed Support. License terms: Terms of Use.

© 2026 Fuse Link Inc.
Support Privacy Terms Contact All apps