Chorus

Privacy summary

What we upload, store, and never do.

The short version of how Chorus handles your audio and data. The complete policy lives on the full privacy policy and terms pages.

Your lessons live on your device first

Imported audio, subtitles, translations, and practice recordings are stored locally on your device. Deleting a lesson in the app removes that lesson's audio, subtitles, translations, and practice recordings. Settings → Clean Cache removes only your Echo practice recordings; deleting the app removes everything stored on the device.

Uploads exist only to make subtitles

To generate subtitles, the audio file is uploaded over HTTPS to our server. Speech-to-text is performed by the Groq API acting as our processing service provider — Groq processes your audio solely to produce the transcript. Your audio is not shared with any unrelated third parties.

Uploads are deleted on a fixed schedule

The uploaded file is deleted as soon as your subtitles are produced. Remaining audio segments are kept for at most 24 hours, and task results (transcripts and subtitle data) for at most 48 hours, after which they are removed automatically.

No training on your content

We do not sell your data, use advertising identifiers, or use your audio or transcripts for model training.

Sign-in receives the minimum

Sign in with Apple, Google, or a one-time email code is processed by Supabase, which receives only the provider identity, your email address where supplied, session tokens, and a stable account identifier. Email sign-in sends a one-time verification code to the address you enter.

Payments never touch us

Subscriptions are billed by Apple; payment details are processed by Apple and we never see them. Subscription status is verified through Apple's signed receipts (StoreKit 2). RevenueCat is used only as a fallback when restoring purchases.

Last reviewed 2026-11-07. If this summary and the full policy ever disagree, the full policy wins.