Skip to content

Does use.fo store your audio?

Short answer

No. use.fo does not store audio recordings, transcripts, rewrite input, or rewrite output. use.fo does not use your voice or text data for model training. Data handling depends on which route you choose: Subscription, BYOK, or Local AI / Local STT.

Evidence and updates

Facts checked on July 24, 2026

Reviewed by use.fo product team. Sources below identify whether a fact comes from an official product page, a first-party test, customer evidence, or an independent source.

Update log: July 24, 2026 — Published the no-subscription product fact registry and clarified BYOK, Local AI, and Windows support boundaries.

Steps

  1. Subscription route

    When you use the Subscription route, your audio is sent to the selected API endpoint — currently mainly Groq — for speech-to-text processing. The resulting text is then sent to the rewrite endpoint. use.fo does not store audio, does not store transcripts, does not store rewrite input, and does not store rewrite output on its servers. Provider-side retention depends on that provider's own privacy policy. Groq's data retention policy is available on the Groq website.

  2. BYOK route

    When you use BYOK (Bring Your Own Key), content goes directly from your device to the API endpoint you configured — Groq, OpenRouter, Google AI Studio, or another supported provider. The content does not route through use.fo servers. use.fo servers are only contacted for license verification, sync, and downloading optimised rewrite prompts. Provider-side retention depends on your provider's policy.

  3. Local AI / Local STT route

    When you use Local AI / Local STT, speech recognition and AI rewriting both run on your device. After the initial license verification and model download, user content — audio, transcript, rewrite input, and output — does not leave the device. Only device and license information is sent to use.fo servers for license binding and verification.

  4. Provider keys

    Your API keys are encrypted and stored locally on your device. use.fo does not use the system Keychain for API keys. Keys are not transmitted to use.fo servers.

  5. Google Drive Sync

    If you use Google Drive Sync for snippets, use.fo uses the Google App Data scope. This means use.fo reads and writes only to its own app-specific data area in your Google Drive. use.fo cannot access the rest of your Google Drive files.

  6. What use.fo does NOT do

    use.fo does not: store audio recordings, store transcripts, store rewrite input or output, use your audio or text data for model training, sell your data to third parties, or share your data with third parties beyond what is required for the selected processing route (Subscription: your chosen API provider; BYOK: your chosen provider; Local AI: no third party after setup).

Troubleshooting

Problem: I'm concerned about what my provider does with my data

Solution: For Subscription, the current main provider is Groq. Review Groq's privacy policy at groq.com. For BYOK, check the privacy policy of the provider whose key you configured. use.fo does not control provider-side data handling.

FAQ

No. use.fo does not use your audio, transcripts, rewrite input, or rewrite output for model training.

Subscription: at the selected API endpoint (mainly Groq). BYOK: at your chosen provider's endpoint directly. Local AI: on your device — audio never leaves your machine after setup.

use.fo does not store user voice or text content. For specific GDPR compliance questions, refer to the Privacy Policy at use.fo/privacy-policy.

Yes. API keys are encrypted and stored locally on your device. They are not transmitted to use.fo servers.

You can delete your account and associated data. See the Privacy Policy for the account deletion process.

Related