Upsurge turns your voice into clean text. This page explains, in plain language, what we collect, why, and the control you have over it.
The short version
Upsurge does not sell your content or use it to train Upsurge models.
Your dictation is sent to the service providers needed to transcribe and clean it. Upsurge does not create its own server-side archive of your recordings or dictation history.
Your saved dictation history stays on your device and syncs through your personal iCloud when you enable it. Where shared plan and usage are available, your Upsurge account carries your subscription, trial and word allowance across devices.
App versions with mandatory sign-in require an Upsurge account before use. Auth0 handles sign-in using the Apple, Google or email option available in the app. Older versions may work without an account. Feedback and support are optional.
What we collect
Account information — in app versions with mandatory sign-in, Auth0 processes the sign-in information provided through your chosen method. Upsurge uses a verified account identifier and, when available, a verified email address to sign you in and select your personal data. Email sign-in also uses your email address to deliver a one-time code. Your selected identity provider processes information under its own privacy policy.
Voice recordings — when you dictate, the audio is sent through our service to a speech-recognition provider. Upsurge does not intentionally write the recording to persistent storage or create a server-side recording archive. Provider processing and retention are described below.
Raw and cleaned text — the transcript is processed to produce your finished text, which is returned to the app and saved to your history on your device (and synced through your own iCloud if you enable sync). Upsurge does not create a server-side message-history database. Provider processing and retention are described below.
Words Upsurge learns — so it spells the names and terms you actually use the right way, Upsurge notes proper nouns it spots in your dictations (a colleague's name, a product, a place) and keeps them on our servers. In signed-in iOS versions, vocabulary is linked to your selected account; older versions link it to a pseudonymous device token. Only the individual words are kept — never the message they came from — and a word is used to help transcription only once it has recurred a few times. You can see the list, remove any word, or clear it entirely in the app.
A pseudonymous device identifier — on first launch the app creates a random token so your requests can be authenticated and linked to your usage and entitlement. The installation token remains separate from the account sign-in described above; deleting or signing into an account does not reset its usage counter.
Pseudonymous usage and diagnostic signals — events such as registration, feature use, dictation length and timing, app version, platform and error outcomes. We use the installation identifier for device-based allowances, reliability and product analytics. Where shared usage is available, our servers link word counts and the allowance period to your Upsurge account to calculate the remaining allowance across devices. Signed-in requests also carry an account identifier for personal-data access. Pseudonymous identifiers do not make these records anonymous. Usage signals do not include message text or audio.
Subscription and trial status — we use subscription status and trial eligibility to determine your access to paid features. Where shared access is available, we link verified subscription and trial status to your Upsurge account so access follows that account across devices. Versions using device-based access link subscription status to a pseudonymous device token. Apple handles billing and payment information for App Store subscriptions. We do not receive your card details for those purchases.
Feedback and support information — if you send in-app feedback, we receive the topic, your message, an optional reply email, your pseudonymous identifier and basic diagnostics such as app version, device, operating system, language and subscription status. For the signed-in iOS flow, message content, reply email and diagnostics are kept in the account-scoped support record; email and owner notifications contain only a fixed category and ticket reference. Older app versions and messages you send directly to support can also leave content copies in our support inbox or notification systems.
How your voice is processed
To turn your speech into clean text, Upsurge uses three AI providers acting on our behalf. ElevenLabs receives your recording and produces a raw transcript. OpenAI may receive that transcript to clean it. Anthropic handles cleanup for older app versions and when OpenAI is unavailable; it also handles personal writing styles, requested translations, writing feedback and recaps from messages you select. These providers process content under their commercial API terms and may retain request data for service operation, security, abuse prevention, troubleshooting and legal compliance. Upsurge does not sell, rent or share your recordings or messages with advertisers or data brokers.
OpenAI and Anthropic state that their commercial API inputs and outputs are not used to train their models by default unless the customer opts in; content submitted as feedback to a provider may be handled differently. Upsurge does not opt your API content into that training. ElevenLabs processing is governed by its current service terms, privacy policy and our account settings.
Storage and retention
Upsurge application servers: we do not add recordings or dictations to a persistent server-side message history.
ElevenLabs: our current speech-to-text requests use its standard API retention and are not covered by Zero Retention Mode. ElevenLabs may retain recordings, transcripts and related logs under its policies. See ElevenLabs' retention documentation.
Anthropic: under its standard commercial API policy, inputs and outputs are normally deleted from its backend within 30 days, subject to its stated safety and legal exceptions. See Anthropic's retention documentation.
OpenAI: standard API abuse-monitoring logs may contain prompts and responses and are normally retained for up to 30 days, with stated exceptions. See OpenAI's API data controls.
Accounts and sign-in: Auth0 maintains the account profile used for sign-in. Account deletion requests remove the selected account through Auth0; the app reports incomplete requests as pending. Authentication-service logs and other provider records may follow separate retention rules, which are not a promise of immediate deletion from every provider system.
Your saved history: stored on your device and in your personal iCloud account if sync is on. In iPhone and Mac versions with account-separated history, your verified Upsurge profile controls which history and related statistics you can see. To restore synced history on another iPhone or Mac, use the same Upsurge profile and iCloud account and enable sync. Signing in to Upsurge alone cannot restore history that was stored only on a previous device or synced to a different iCloud account.
History from earlier versions: where transfer is available, we offer it after confirming your right to the archive. If you choose to transfer, the app copies the history into your selected Upsurge profile on the device and syncs it through your iCloud if enabled. A completed transfer links the archive to that profile. If you decline, the original archive stays in place outside the current profile.
Words Upsurge learns: kept for about four months after your last dictation (about a year for words you add yourself), then deleted automatically. Removing or clearing them in the app deletes them straight away.
Feedback from the signed-in iOS flow: our service keeps up to 20 recent submissions per account. That list expires 180 days after its latest submission unless removed earlier with account deletion. Older-version feedback uses a separate list of up to 500 recent submissions. Direct support messages and older content copies in our support inbox and notification systems are kept until no longer needed for support or until you ask us to delete them.
Usage and operational metrics: retained as needed to operate the service and understand product usage. Some records remain linked to a pseudonymous device identifier before they are aggregated. Account deletion preserves the original installation usage counter and Apple-managed purchases.
Deletion records: After account deletion completes, we retain limited pseudonymous deletion records to help prevent old credentials or old data copies from restoring deleted personal data through our account services, and to check the deletion outcome. These records contain account and source hashes, request references, a hashed status-recovery check, relevant times and completion status. Our current service does not automatically expire these records. The completed deletion job no longer contains the original authentication-provider or installation identifiers. These retained records contain no audio, dictated text, vocabulary words or feedback messages. Temporary confirmation records expire separately; an unfinished request may retain the original identifiers needed to finish deletion and remains pending until completion.
Website and download analytics
These website preferences are separate from data processed by the Upsurge apps.
Necessary settings: browser storage remembers your chosen language, whether you dismissed the Mac download reminder, and your website privacy choice. These preferences stay in this browser until you change them or clear the site's stored data.
Optional analytics: site analytics and download counters are off until you explicitly enable them. If enabled, Vercel Web Analytics measures visits and events, including the page, referrer, approximate location, browser and device type. Our own counters record the download platform and any campaign or referral tags supplied with the visit. Vercel describes its data handling in its Web Analytics privacy documentation.
Your control: use the cookie illustration to open Cookie settings, turn Site analytics on or off, and save your choice. Withdrawing consent stops subsequent analytics events and clears campaign and referral tags stored by this website; it does not erase statistics already collected. You can browse and download Upsurge with analytics off.
We do not use advertising cookies or cross-site advertising trackers. Changing a website preference does not change microphone permissions, app diagnostics or the processing needed for dictation.
Your choices
Delete individual messages or your whole history in the app at any time.
Turn iCloud sync off in Settings.
Move your history to another device: on a supported iPhone or Mac, open Back up & restore in Settings and choose Export backup. Save the file somewhere you can reach from the new device. In versions that require an account, sign in to the same Upsurge account, then choose Restore from file and select your backup. The file contains readable dictation text and includes the history available at the time of export. Keep it in a location you trust. Upsurge does not upload the backup file to its servers. If iCloud sync is enabled, imported entries can sync through your personal iCloud.
In iOS versions with accounts, open Settings → Delete account & data to initiate deletion of the selected Upsurge login and its personal data. You may need to verify that login again. The app shows pending or unconfirmed work rather than treating it as completed. Previously imported data sources that changed may need another explicit review.
In those updated account-separated versions, a new confirmed account-deletion request covers the selected profile's working history and other private account data, including its server vocabulary and feedback. Original and unassigned history archives are kept and managed separately; they are not silently assigned by email or treated as another profile's working data. Requests accepted under the earlier shared-history policy keep that policy. Account deletion does not promise to erase independent old app copies or all historical iCloud archives on other devices. Review the scope and any pending work shown in the app.
Deleting an Upsurge account does not cancel an Apple subscription or reset the original installation word counter. Manage billing separately at Apple Subscriptions. If you used Sign in with Apple, the app also links to Apple's instructions for checking and removing remaining sign-in access; an account-deletion confirmation is not a claim that every Apple grant was independently verified as revoked.
Remove learned words in the app. For older-version server data or feedback tied to a device token, or for direct support copies, contact support@useupsurge.com. This support path does not replace the in-app account-deletion option in versions with accounts.
Deleting local history does not automatically delete request data that an API provider may retain under its own policy. Contact us if you need help with a provider-related deletion request.
Permissions
Upsurge asks for microphone access to record when you choose to. You can start a recording with the app's microphone button, a configured shortcut, the Action Button on supported iPhones, or the Upsurge keyboard flow. Recording ends when you stop it or release a shortcut configured for hold-to-record. On Mac, Accessibility access is needed to insert finished text into supported text fields. The optional iPhone keyboard needs Full Access for its voice-input flow.
In app versions that highlight spoken words during onboarding, Apple speech recognition runs on the device when a local model is available. This helper does not send your recording to Apple. The recording is still sent to the service providers described above to produce your finished text.
Changes
Features and this policy may change as the product evolves. We'll update the date above when we make material changes.