Cookie Policy
How ScribeText uses authentication cookies, local preferences and browser storage.
Last updated: September 15, 2026
Scope
This policy explains cookies and similar browser storage used by ScribeText at scribetext.com. It should be read with our Privacy Policy. Visiting the site or reading this policy is not consent to optional tracking.
Storage used by the current service
| Type | Purpose | How long it remains |
|---|---|---|
| Authentication cookies | Keep you signed in, manage a session and support account security. | Sessions are currently configured to expire after seven days, with renewal during continued use. Signing out ends the session. Individual cookie lifetimes can differ. |
| Theme preferences | Remember your appearance choice in local storage. | Until you change the preference or clear the site's browser data. |
| Sample transcript edits | Keep changes you make to the illustrative transcript in this browser. | Until you reset the sample or clear this site's local storage. Signing out does not clear these edits. |
| Temporary audio preview | Let the browser play the file you selected from your device. This is a temporary file reference, not an uploaded recording or an advertising cookie. | While the preview holds the file. Removing it or closing the page releases that reference and does not delete the original recording. |
| Upload resume metadata | Session storage keeps an upload identifier, filename, size and modification time so reselecting the same file can resume confirmed parts. It does not contain the audio or provider access link. | Cleared after starting a task or removing the file; otherwise session storage lasts for the tab session and the resume record expires after 24 hours. |
Optional services
Google Analytics 4, our self-hosted Plausible instance at pla.panjin.dev, and our self-hosted Umami instance at umami.panjin.dev are optional and load only after you select Allow analytics. Choosing No thanks, or leaving the choice unanswered, prevents their analytics scripts and event requests from loading. We do not backfill actions taken before you allow analytics.
Analytics measures visits, file selection, sign-in during an upload, transcription starts, viewed results, exports and checkout progress. Google receives a cookie-based browser identifier and browser/device information. Our Plausible installation uses connection and browser information for aggregate statistics without setting analytics cookies; it runs on infrastructure we manage through Zeabur, not Plausible's managed cloud service. Umami also runs on our Zeabur infrastructure without analytics cookies or account identification. It respects the browser’s Do Not Track setting. Our event properties contain only the public tool type and export format. We remove query strings, fragments, filenames, account information and recording content, and aggregate private page addresses. Google and Plausible receive no referrer. Umami may receive only a recognized public search or AI service origin (for example, https://chatgpt.com), with no conversation path or search query; unrecognized referrers are discarded. Google page titles are reported as ScribeText. Automatic enhanced measurement, advertising personalization and Google signals are disabled.
Your analytics choice is stored locally for up to 180 days. If you allow analytics, Google Analytics uses first-party _ga cookies, configured here with a 90-day expiry and automatic expiry renewal disabled. Session-only keys prevent repeated conversion events for the same recording within a browser tab. This is separate from authentication and does not identify your account to analytics.
Use Cookie preferences in the footer to change your choice. Rejecting analytics stops further collection by all three trackers, discards pending Plausible and Umami events and removes this site's Google Analytics cookies without signing you out. It does not erase statistics already received by Google or our analytics installations. See Google's data-use information and Plausible's measurement approach; the latter's managed-hosting location commitments do not describe our own infrastructure. We do not use advertising, retargeting, session replay or the optional support chat widget.
If you later open Google sign-in or Stripe checkout, those services may use their own cookies for authentication, payments and security. Their notices apply to their own services. ScribeText's browser preferences do not automatically control cookies on a provider's separate site.
Your controls
You can change the theme through the website, reset sample edits in the sample workspace, or use your browser's settings to inspect, block or delete site data. Blocking authentication storage can prevent sign-in from working. Clearing local storage can remove unsaved sample edits; it does not remove files from your device's folders.
Updates and contact
We will update this page if these practices change. For questions about cookies or local storage, email hi@scribetext.com.