Privacy
Your words.
Your choice of voice.
Last updated November 5, 2026
This notice covers the Renarrator website, extension, and account service. For privacy questions or a request about your account records, contact the Renarrator publisher at support@renarrator.com.
The video you choose
When you open Renarrator on a video page, the extension reads the selected page’s address and title, identifies its video and available captions, and shows the title in the popup. It uses page addresses and video identifiers in memory to keep narration and prepared audio with the right video. It reads caption files, transcripts, subtitle tracks, or on-screen captions for narration, and observes video playback state, including pauses and seeks, to synchronize speech. It does not read Chrome’s browsing-history database or monitor all browsing activity.
Local narration and tab audio
Kokoro generates local AI speech inside Chrome. German narration uses computer voices or the optional cloud voices described below. Local transcription and translation also run on your computer. Renarrator’s account server does not receive captions, recordings, transcripts, or generated audio from those local features. Models download from their hosting services when needed.
When you choose Prepare next minute, Listen first & play, or Transcribe as you watch, Renarrator can capture audio from the selected tab to prepare a transcript locally. A caption-preparation action can also switch to local transcription when the site has no usable captions. Tab capture can include other sounds playing in that tab; it does not request microphone or camera input. Audio is held in memory and transcribed on your computer, rather than saved as a recording file or uploaded to Renarrator. Stop or Cancel ends capture.
Local storage and diagnostics
Downloaded voice, transcription, and translation model data is cached in this Chrome profile for reuse. Chrome manages its own translator language packs. Caption and transcript text, translations, captured audio, and generated narration are processed in memory. Prepared narration can remain ready for seeking after you press Stop. Changing the video, closing or reloading its tab, or reloading the extension clears its prepared narration cache.
The extension stores voice preferences, saved provider keys, the signed-in email and session token, trial and license status, and license activation information in this Chrome profile. Sign-out removes the locally stored email and session token. Provider keys stay until you remove them; removing a device activation removes its saved license information. Uninstalling removes local extension data and model caches.
Renarrator keeps up to 300 recent playback diagnostic events in local extension storage. They contain timestamps, playback and processing status, pause or seek events, and error information. They exclude caption text, audio, page titles, and page addresses. The oldest events are replaced as new events arrive; there is no automatic time-based expiry. These diagnostics are not automatically uploaded. You can choose Save playback log to download a copy and decide whether to share it with support. A downloaded or shared copy remains wherever you keep or send it.
Your account and trial
When you request a sign-in code, your email is sent to Renarrator’s server and its email delivery service, Resend. The account database keeps a keyed digest (HMAC-SHA-256) of the normalized email instead of the plain-text address. This digest is a persistent account identifier, not anonymous information.
The server stores your trial balance and playback allowances, session-token digests, verification records, and counters used to limit abuse. Network addresses are converted into keyed digests for account sign-in rate limits. Cloudflare also processes network addresses for hosting and license rate limiting; those operations do not use the account sign-in digest. We use these records to sign you in, maintain your trial across reinstallations, and protect the service. Trial playback requests contain an allowance identifier and listening duration, not the video’s address, captions, or audio.
Retention and deletion
Codes expire after ten minutes and sessions after thirty days. Expired authentication records and account rate-limit counters are removed during later successful sign-in-code requests. Trial eligibility, usage records, and license associations remain until the account is deleted; uninstalling does not delete them.
To delete your account, open the Renarrator iPhone app, go to Settings → Account → Delete Account, and confirm with a code sent to your email. Deletion is complete as soon as the app confirms it. If you don’t use the iPhone app or can’t sign in, or to request access to your records, email support@renarrator.com from the address used for the account. We may ask you to verify ownership.
Deletion removes your email digest, account ID, sessions, any pending sign-in code, the sign-in email counter for your address, your trial and usage records, and the links between your account and your licenses or App Store purchases. These things are kept:
- App Store transaction records. Apple’s transaction ID, the product, app and environment, and whether the purchase was revoked, with the link to your account cleared. This keeps a refunded purchase revoked if it is later restored to another account.
- License, credit and subscription records. The license-key digest, device activations, status, and any older credit balances or subscription IDs. These records name no account, and your license keeps working on your computers.
- A spent-trial record, if you used any trial time. An HMAC of your email digest and the seconds you spent. It lasts up to 12 months, or until that address signs in again, when the seconds move to the new account and the record is removed. Without it, deleting an account would refill its free minutes. Matching it requires both our secret key and your address.
- Rate-limit counters. Keyed digests of network addresses, not tied to your account. They expire within 2 hours and are removed during a later sign-in-code request.
- Records outside this deletion. Database backups until they age out; the delivery records Resend keeps of your sign-in emails, including your address; the order and customer records Lemon Squeezy keeps; and Apple’s purchase records. Those companies’ records follow their own policies and legal obligations.
Optional cloud voices
If you save your own Google Cloud, OpenAI, or ElevenLabs key, it stays in this Chrome profile and is sent only to that provider. Text you ask that voice to narrate goes directly to the provider, subject to its privacy policies and billing. Computer voices marked “online” may also send text to their provider.
Purchases and licenses
Lemon Squeezy handles checkout, billing details, and license keys for the one-time purchase. Your license key stays in the Chrome profile and is sent through Renarrator’s server to Lemon Squeezy for validation. The server stores the key’s digest, activation identifier, status, and an account association when you are signed in. Renarrator does not receive your payment-card details.
Website, support, and infrastructure
This website does not use advertising trackers, analytics scripts, or a marketing signup form. Cloudflare hosts the website and account service. Fonts are served from this website. The account service logs request methods, recognized routes, and response status without recording email addresses, session tokens, captions, or audio in those logs. Hosting, email, model downloads, payment, and voice providers process network information needed to provide their services, with retention governed by their policies.
Messages to support@renarrator.com are forwarded by Cloudflare to a Gmail inbox. Support emails include the address and information you choose to send and are kept as needed to resolve and follow up on your request. You can request deletion of support correspondence.
Provider policies: Cloudflare, Resend, Lemon Squeezy, and Google. Optional voice and model-hosting providers also apply their own policies.
Chrome Web Store Limited Use
Renarrator’s use and transfer of user data complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. We use data only to provide and support the narration, sign-in, trial, licensing, and reliability functions described here. We do not sell user data, use it for personalized advertising, or use it to determine creditworthiness or for lending. Transfers are limited to the service providers needed for these functions and the other exceptions permitted by that policy. Human access is limited to your consent for support, necessary security work, legal requirements, or aggregated and anonymous internal operations permitted by that policy.
Your controls
You can stop narration or capture, remove saved provider keys, sign out, or remove a device activation in the extension. Reloading the extension clears its in-memory narration; uninstalling removes local extension data, including diagnostics and model caches. Neither action refunds a purchase or deletes server-held account records. Copies of playback logs you downloaded or shared must be deleted separately.