read-it-aloud

Privacy Policy — Read It Aloud

Last updated: June 12, 2026 Effective: When you install or update to v1.3.0 or later

Summary in plain English

What data the extension handles

Data Where it lives Where it’s sent Why
Your ElevenLabs API key storage.local on your device only api.elevenlabs.io as the xi-api-key HTTP header Required to authenticate TTS requests
Selected text on a web page RAM (transient) and the extension’s offscreen audio document api.elevenlabs.io in the TTS request body Required to generate the audio you asked for
Your voice & playback settings (voice ID, model, speed, stability, etc.) storage.local on your device only api.elevenlabs.io as part of TTS request body Required so generation matches your preferences
Generated audio bytes RAM and the offscreen audio document; discarded when you stop or close the tab Stays on your device Played back to you, optionally downloadable

Nothing is sent to any other party. The extension makes no network calls to any host except api.elevenlabs.io.

What we do NOT collect

Third-party services

The selected text and your voice settings are sent to ElevenLabs, the TTS provider. ElevenLabs is governed by their own privacy policy: https://elevenlabs.io/privacy. You hold an account directly with ElevenLabs (this extension uses your API key) and your relationship with them is between you and ElevenLabs.

Permissions and what they’re for

The exact set of permissions may vary slightly by browser due to platform differences (Chrome / Edge / Firefox / Safari implement extension APIs slightly differently). The underlying data practices above are identical across all versions.

Your rights

Changes to this policy

We’ll update this document if the data practices change. The “Last updated” date at the top reflects the current version. Material changes will be noted in CHANGELOG.md.

Contact

For questions about this policy, open an issue at https://github.com/JPF1111/read-it-aloud/issues.