Listen is a Chrome extension that reads web pages, documents, and photos aloud using AI text-to-speech, with synchronized word highlighting. This policy explains what data Listen handles and where it goes.

Listen works in one of two modes: Listen service mode (default — free trial or Listen Pro subscription, requests go through Listen's server) and own-key mode (you supply your own OpenAI API key and requests go directly from your browser to OpenAI; Listen's server is not involved).

The short version

• Text is only processed when you actively start a reading or use a feature (recap, quiz, word explanations, photo transcription, voice preview). Listen never reads or transmits pages you merely visit.
• In service mode, your text is sent to Listen's server, which forwards it to OpenAI to generate speech, and keeps a count of characters used — that's how the free trial and fair-use limits work.
• Free-trial devices are identified only by a random ID. If you subscribe, Stripe shares your email with us so we can manage your subscription.
• Card details are handled entirely by Stripe and never touch Listen's server.
• No analytics or advertising trackers. No selling, renting, or sharing of data — ever.

Listen service mode (trial and Listen Pro)

Device identity. On first use, the extension generates a random device ID (UUID) and registers it with Listen's server, which issues an access token. This ID contains no personal information and is not linked to your identity unless you subscribe.

Text and photos. Content you choose to read is sent to Listen's server (listen-backend.listenhq.workers.dev, hosted on Cloudflare Workers), forwarded to OpenAI to generate speech, timings, transcriptions, or summaries, and returned to your browser. Listen's server does not store the text you read or the audio generated — it passes through to fulfill your request.

Usage metering. The server records, per device: characters processed and requests per day, and plan status. This operates the free trial, fair-use limits, and abuse monitoring.

Subscriptions. Checkout and billing are handled by Stripe. Card details go directly to Stripe. After checkout, Stripe shares your email and a customer reference with Listen so we can recognize your subscription and let you manage billing.

Own-key mode

With your own OpenAI API key in settings, the extension talks directly to api.openai.com — no device registration, no metering, nothing sent to the developer. Your key is stored via chrome.storage.sync and only transmitted to OpenAI. Treat it like a password.

Stored on your device

Settings, access token/device ID, a local audio cache (IndexedDB) so re-reads are free, and library/positions/stats. Uninstalling removes all of it.

Retention and deletion

Usage and device records are retained to operate the service; subscriber email and Stripe reference for as long as you have an account relationship. Request deletion anytime at the contact below. Cancel anytime via the extension's Manage subscription button (Stripe billing portal).

Third parties

• OpenAI — receives text/images needed to fulfill readings and features.
• Cloudflare — hosts Listen's server and database.
• Stripe — processes all payments and stores payment details.
• Google — if you read a Google Doc, its text is fetched using your own Google session.

What Listen does NOT do

• No collection of browsing history
• No analytics or advertising trackers
• No storing of read text or generated audio on Listen's server
• No selling, renting, or sharing of data
• No reading of page content without an explicit action from you

Children

Listen is not directed at children under 13, and we do not knowingly collect personal information from them.