Privacy Policy

Effective date: November 17, 2026

This policy explains what narrador collects and why, for the narrador browser extensions narrador X and Web narrador, and for the narrador account they use. narrador turns text into audio (and, in narrador X, into videos) with natural-sounding voices.

Questions: support@narrador.io.

Summary

  • The extensions do nothing on a page until you press a narrador button, open the narrador side panel, or use a narrador shortcut or menu item.
  • To create audio or video we send the post ID (narrador X) or the text you chose (Web narrador) to our servers. Our servers generate the audio with a voice provider.
  • You need a narrador account. Narration and videos require a monthly plan and use credits.
  • We do not sell your data, show ads, or use third-party analytics or tracking in the extensions.

What we collect and how we use it

Your account

You sign in on narrador.io with Google or with a sign-in link sent to your email. We store your name, email address, and profile picture (if your sign-in provider gives one), plus account details such as your language, role, and the date you joined. We use them to run your account, to show who is signed in, and to email you about sign-in.

The extensions do not ask for your password. They use the narrador.io session your browser already has, the same way the website does. For up to 60 seconds they keep a copy of your user ID, name, email, and profile picture in the browser's session storage, which the browser clears when it closes, so the panel does not have to ask our server on every click.

narrador X (posts on x.com)

  • On x.com pages, the extension reads the posts on the page in your browser so it can show its buttons, show the post you picked in the side panel, and highlight words while they are read. That page content stays in your browser until you act.
  • When you pick a post (press Narrate, the queue button, or open it in the panel), the extension sends its post ID to our server. The server looks the post up (see below) to find the recommended voice and to check whether audio already exists.
  • When you press Narrate or Make video, the extension sends the post ID, the voice, and the accent. If X is showing its own translation of the post, the extension sends that translated text instead, so you hear what you see.
  • When you play a thread or "Narrate from here", the extension reads the next posts on the page and requests audio for them, one ahead of the post that is playing.
  • On our servers, we fetch the public post (its text, author name, handle and profile picture, media, and public counts such as likes and views) from FxTwitter or the official X API, using only the post ID. We store this public post data, and we send the post text to a voice provider to generate the audio. Generated audio, word timings, and videos are stored so the same post and voice can be replayed without generating again. We link the audio and videos you create to your account. That is how we show what you already own and avoid charging you twice.
  • Make video renders the video on our servers and gives you a download link that expires after a few minutes.

Web narrador (any web page)

  • The extension can run on the pages you visit so its narrate controls are available. It reads the page only to find the text you select or the block you point at.
  • When you start a narration, the extension sends the text you chose, with the voice and accent, to our server. We send that text to a voice provider and store the resulting audio and word timings. They are stored under a fingerprint of the text, voice, and accent, so the same text is not generated and charged twice. We keep a record that your account already paid for that fingerprint.

Plans, credits, and payments

Checkout, subscriptions, and billing are handled by Polar on narrador.io. We do not receive your full card details. We keep your credit balance and a ledger of credit charges (for example, a narration or a video) to bill correctly and to show your balance.

Settings stored in your browser

The extensions save your choices in your browser's extension storage. That covers the voice and accent, video style (for narrador X, together with your user ID so another account on the same browser does not reuse them), auto-scroll and highlight options, the interface language, and whether you have seen the first-run tour. Some of these, such as voice, accent, and language, use Chrome sync storage. If you have Chrome sync on, Chrome syncs them across your browsers. They are not sent to narrador except as part of a request you make (for example, the voice you pick for a narration).

Error reports

If one of the extensions hits an unexpected error, or audio generation fails, it can send our server a short technical report. The report contains the extension name and version, where the error happened, an error code, the error message, and code locations. Before sending, the extension removes web addresses' query strings, email addresses, and long token-like strings, and shortens the text. Reports never include post or page text, cookies, or your account ID. They are sent without your login cookies, and each extension sends at most a few per session. We write them to our server logs to fix bugs; we do not store them in your account.

Service providers

We share data only with providers that help us run narrador, and only what each one needs:

  • Voice generation: Inworld and other text-to-speech providers we use (Fish Audio, and self-hosted models). They receive the text to read, and the voice.
  • Post lookup (narrador X): FxTwitter and the X API receive the post ID.
  • Storage and database: Our database and stored files (Postgres and Storage, self-hosted Supabase) run on our own server, a VPS hosted by Hostinger.
  • Sign-in and email: Google (if you sign in with Google) and Resend (sign-in emails).
  • Payments: Polar.

We do not sell personal data. We do not use it for advertising or to decide creditworthiness. We do not share it with anyone else, except when the law requires us to.

How long we keep data

  • Your account: until you delete it. When you ask to delete your account, it is blocked right away and deleted after 30 days. That also deletes your credit balance and the links between your account and the audio and videos you created.
  • Cached content: Public post data, generated audio, word timings and videos are kept as long as the service needs them, with no fixed period. They are not tied to your account and can remain after you delete it.
  • Payments: Your credit balance is deleted with your account. Credit and purchase history is kept with no fixed period, for accounting and refunds. Polar, our payment processor (merchant of record), keeps transactions for at least 5 years for legal and tax obligations.
  • Server logs: Application logs, including extension error reports, are kept only for a short time: they are limited in size and replaced on each deploy. Mobile app error reports are deleted after 30 days. We do not keep a per-request access log. Server system logs are kept up to 7 days.
  • Data in your browser: until you sign out, clear it, or remove the extension. Session data is cleared when the browser closes.

Your choices

  • Sign out from the extension panel or on narrador.io.
  • Remove the extension at any time from Chrome's extensions page. Its local data is removed with it.
  • Delete your narrador account at narrador.io/stoic-locker/delete-account (same narrador account; deletion happens 30 days after the request), or write to support@narrador.io.
  • Ask us for a copy of your data or to correct it at support@narrador.io.

Chrome Web Store User Data Policy

How the narrador extensions use information complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. We use data only to provide and improve the narration features described here.

Children

narrador is not directed at children under 16.

Changes

If we change this policy, we will update the date above. For important changes, we will tell you in the extension or by email.