Effective date: 19 September 2026 · Last updated: 19 September 2026 · Data controller: Birdie Ltda., Santiago, Chile · Contact: support@birdie.cl
This policy explains how the Read My Page extension for Google Chrome and Microsoft Edge handles your information: what it can access, what leaves your device and when, what we store, what we deliberately do not store, and the measures that protect all of it.
Read My Page is one of several ways to use Read My Document. The add-ins for Microsoft Word and Outlook, the Google Docs add-on and the web app each have their own policy; the Google Docs add-on policy covers that surface.
1. What the extension does
Read My Page reads the web page you have open out loud. You ask it to read a page — by clicking its icon, using its keyboard shortcut, choosing an entry in the right-click menu, or pressing play in its side panel — and the text of the article is extracted in your browser, sent to our servers, converted to speech, and streamed back as audio. While it plays, the word being spoken is highlighted on the page itself.
Everything else the extension offers — reading a selection, reading from a chosen paragraph, MP3 export, AI summaries — is built on that same flow.
2. Permissions we request, and why
- activeTab — lets the extension read the page you invoked it on, and only that one. The access is granted by your gesture and expires when the tab navigates.
- scripting — inserts the reading helper into that page, on request. The helper is part of the extension package; no code is downloaded at runtime.
- sidePanel — the panel is the extension’s interface.
- storage — keeps your chosen voice, your settings, your session and your reading position on your own computer.
- identity — lets you sign in. The sign-in happens on our own website or with your browser profile account; the extension never sees a password.
- contextMenus — the three right-click entries.
- Access to readmydoc-api.birdie.cl — our own speech service. This is the only server the extension talks to.
- Optional: access to websites — requested only if you turn on “Read the tab I’m looking at”, and by default only for the site you are reading at that moment. Granting every site is a separate, explicit choice. This permission is not requested when you install the extension, it is granted from inside the extension, and turning the option off gives it back.
3. What leaves your device, and when
Nothing is sent anywhere because you visited a page. Text leaves your device only when you ask for it to be read, exported or summarised, and only the text you asked for: the article, or the passage you selected. It travels over HTTPS to our speech service so that it can be turned into audio.
That text is held in volatile memory for as long as producing the audio takes, and is then discarded. It is never written to disk, never analysed, never shared with anyone beyond the speech providers listed in section 6, and never used to train any model, ours or anyone else’s.
4. What we do not collect
- Your browsing history. We do not collect, receive or store the addresses of the pages you visit or read. So that reopening an article can resume where you left off, the extension keeps a reading position on your own computer, filed under a cryptographic hash of the page address rather than the address itself. It was built that way specifically so this answer needs no qualification.
- Pages you did not ask us to read. The extension has no access to a page until you grant it, and it never reads a page in the background.
- Passwords. Sign-in is delegated to Microsoft, Google or Apple, or to our own website. We never see your credentials.
- Payment card details. Checkout is hosted by our merchant of record (section 6). Card data never reaches us.
5. What we do store
- On your computer (browser storage, never sent to us): your voice and reading settings, your session token, and the reading positions described above.
- On our servers, only if you sign in: an account identifier from your identity provider, your email address and display name, your plan and its limits, and how many characters you have synthesised in the current period — a counter, not the text.
- Aggregate telemetry: which voice was used, how many characters, the detected language, latency and error rates. It never contains the text you read, nor the address of any page.
6. Who else receives data, and what for
- Microsoft Corporation — hosting, database, identity and telemetry (Azure), and billing for work and school accounts through the Commercial Marketplace.
- Speech providers — when you pick a premium or studio voice, the text being read is sent to Microsoft Azure Cognitive Services, ElevenLabs, OpenAI or Google Cloud for synthesis only, and is discarded by them afterwards. Free voices are synthesised on our own machine.
- Polar Software Inc. — merchant of record for personal accounts: it hosts the checkout, processes the payment and issues the invoice. We pass it your account identifier and email so the purchase can be matched to your account; your card details never reach us.
We do not share data with any third party beyond what is technically necessary to operate the service. We do not sell or rent your data, we do not use it for advertising or profiling, and we do not use the content you read to train models.
7. Remote code
The extension executes no remote code. Everything it runs ships inside the reviewed package: there is no script loaded from a CDN, no eval, and no identity SDK injected at runtime. Signing in opens our own website in a browser window rather than pulling third-party code into the extension.
8. Retention
- Page text and audio: not retained. Held in memory only while the audio is produced.
- Account, plan and usage counters: for as long as the account exists, and deleted on request.
- Telemetry: 90 days.
- Data on your own computer: until you clear it, remove the extension, or sign out.
9. Where your data is processed
Our servers run in the United States (Microsoft Azure, West US). Speech providers process text in their own regions. Birdie Ltda. is established in Chile.
10. Your rights
You may ask us for a copy of the data held about you, ask us to correct it, or ask us to delete your account and everything attached to it. Write to support@birdie.cl and we will answer within 30 days. You can also revoke the extension’s access to websites at any time from the extension itself or from your browser’s extensions page, and uninstalling it removes everything it kept on your computer.
11. Children
The extension is not directed at children under 13, and we do not knowingly collect their data.
12. Changes
We may update this policy. When we do, we update the “Last updated” date above. Material changes to how we process your data will be announced inside the extension and, for subscribers, by email.
13. Contact
Birdie Ltda. — Santiago, Chile — support@birdie.cl
This policy is provided for transparency and is not legal advice.