Beacon AI — Privacy Policy
Last updated: August 2026
Beacon AI is a Chrome extension that lets you control and understand webpages by voice, using AI to read, summarize, translate, and answer questions about page content. This page explains, plainly, what data Beacon AI handles and where it goes.
In short: your voice is transcribed by Google's speech recognition service and never stored by Beacon AI. Page text you ask about is sent to Anthropic's Claude AI service to generate a response. Your personal preferences stay on your own device. Beacon AI does not require an account, does not collect personally identifiable information, and does not keep a permanent record of what you've asked or read.
What data is processed, and by whom
- Voice audio — when you use voice commands, your speech is sent to Google's speech recognition service (via the browser's built-in Web Speech API) to convert it to text. Beacon AI itself does not record, store, or have access to raw audio beyond this transcription step.
- Page content — when you ask Beacon AI to read, summarize, translate, simplify, or answer a question about a page, the visible text of that page is sent to Anthropic's Claude API to generate a response. Only content readable on the page is sent — never information you type into forms, passwords, or other private input fields, since Beacon AI does not read user-entered form data at all.
- Your spoken request text (the transcribed version of what you said) is sent alongside the page content to generate a relevant response.
What is stored, and where
- Preferences (speech rate, zoom level, color theme, onboarding status) are stored locally on your device via the browser's extension storage. They are never transmitted anywhere.
- Page extraction cache — to avoid re-processing the same page repeatedly, Beacon AI temporarily caches extracted page text in the browser's session storage. This is cleared automatically when you navigate away, refresh, or close the tab, and is never sent anywhere beyond the AI request described above.
- Beacon AI's own backend does not maintain a database. It is a stateless service — each request is processed and forgotten. Beacon AI does not keep logs of your questions, page content, or responses beyond what's operationally necessary to process the request in the moment.
Third-party services involved
- Google — speech-to-text transcription, via the browser's built-in Web Speech API. Subject to Google's own privacy practices for this service.
- Anthropic — page content and your request text are sent to Anthropic's Claude API to generate responses. Subject to Anthropic's API data handling terms.
- Railway — hosts Beacon AI's backend server, which relays requests to Anthropic. Railway does not receive your voice audio.
What Beacon AI does not do
- Does not require account creation, sign-in, or any personally identifiable information
- Does not sell or share data with advertisers
- Does not track browsing history beyond the single page you actively ask about
- Does not read form inputs, passwords, or other private page fields
- Does not listen continuously — voice input only activates when you explicitly start it
Children's privacy
Beacon AI is not directed at children and is not knowingly used to collect data from children.
Changes to this policy
If this policy changes, the "Last updated" date above will change accordingly. Material changes will also be reflected in the extension's in-app "Privacy & Data" explanation.
Contact
Questions about this policy or how Beacon AI handles data can be raised via the project's GitHub repository: github.com/Ponnusa/Plugin.ai.