Privacy Policy — Chrome Extension

Tiny Electrons LLC ("Vox Issue", "we", "us") makes the Vox Issue Chrome extension, which turns screenshots of a web page into GitHub issues. This policy explains what the extension processes, the small amount of data our licensing service holds when you buy a license, and the choices you have. Our guiding design: your content stays on your device and in the services you connect; the only data on our servers is what a one-time purchase requires.

Data the extension processes

Stays on your device

• Screenshots & captures of the web pages you point the extension at. The extension can operate on any site you visit (its <all_urls> host permission), but it captures only when you invoke it — nothing is captured in the background.
• Notes and dictation transcripts you record for each capture. (How the audio itself is recognised is under Dictation below.)
• Markup, tags, project settings, and your GitHub token, kept in the browser's local extension storage. Your GitHub token stays on your device and is never sent to us.
• Your Anthropic API key (if you use the AI agent), stored encrypted in local extension storage behind a passphrase.

Sent to services you connect (with your own credentials)

• GitHub. When you file or sync issues, screenshots, titles, descriptions, labels, and project-field values are sent to the GitHub repositories you choose, using your access token.
• Dictation (optional). When you press the microphone, your browser's speech recognition transcribes what you say. On Chrome 139 and later with the on-device language pack installed, recognition runs on your device and no audio leaves it. Otherwise your browser sends the audio to its own cloud speech service — Google's for Chrome, Microsoft's for Microsoft Edge — under that provider's privacy policy. The extension keeps only the transcript, on your device. Details under Dictation.
• AI coding agent (optional, your own key). If you connect your own Anthropic API key, running the agent sends the issue text and prompt — and your GitHub token so the agent can access the repo — to Anthropic. It does not send your screenshots or images to Anthropic. The agent is billed to your own Anthropic account. This feature is off until you add a key.

We do not collect

• The extension uses no cookies and contains no analytics, advertising, or tracking SDKs. We do not sell personal information.
• We do not receive your screenshots, notes, GitHub token, or AI key on our servers.

Auto-capture

The extension can capture a page (or a series of frames of a long page) when you invoke it. Any repeated or multi-frame capture runs only as part of an action you start — there is no background process that captures pages on its own. Captures go to the GitHub repository you have selected for the active project.

Dictation

Chrome does not allow the Web Speech API to run inside an extension, so the side panel embeds a small bridge page from voxissue.com/dictate.html that runs it on a normal web origin. That page is static: it runs entirely in your browser, relays the transcript to the extension, and sends nothing to us. We never receive, store, or listen to your audio or your transcripts.

The microphone is active only while the dictation button is on. Whether recognition happens on your device or in your browser's speech service depends on your browser: Chrome 139+ with the on-device language pack recognises locally (the extension asks Chrome to download the pack when it can); older Chrome, and Edge, send the audio to Google's or Microsoft's speech service respectively, and it is handled under Google's or Microsoft's privacy policy. The microphone-check page in the extension's settings tells you which mode your browser will use. If you would rather not use any speech service, type the note instead — dictation is never required.

Licensing & payments — the only data on our servers

Vox Issue is a one-time purchase. To sell and validate a license, our licensing service (hosted on Amazon Web Services) stores a small record:

• your email address (so we can deliver your license and support the purchase);
• a Stripe customer/transaction identifier (to tie the license to your payment); and
• a one-way hash of your license key — never the key itself — plus non-identifying validation data such as an anonymous install identifier and seat count.

Payment is handled by Stripe. We never see or store your card number; Stripe processes payment details under Stripe's privacy policy. When your extension checks that your license is valid, it sends your license key and an anonymous install identifier to our validation endpoint; we compare against the stored hash and return a signed, time-limited grant. We do not log the pages you visit or the contents of your captures.

Sharing & sub-processors

We use the following processors, each only for the purpose shown:

• GitHub — destination for your issues and screenshots, at your direction (privacy statement).
• Anthropic — only if you enable the AI agent with your own key; receives issue text and your GitHub token, not images (commercial terms; API inputs are not used to train their models).
• Google or Microsoft (browser speech service) — only while you dictate on a browser that does not recognise speech on-device; receives the audio of your dictation, handled under the browser vendor's own privacy policy. We receive neither the audio nor the transcript.
• Stripe — processes your payment and holds the payment details (privacy policy).
• Amazon Web Services — hosts our licensing service (email, payment id, license-key hash) in the United States.

We do not sell or share your data for advertising, and we do not use it for anything beyond delivering and validating your license and the features you invoke.

Chrome Web Store limited use

Our use of information received from Google APIs and from the extension's permissions adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements. We use the data only to provide and improve the extension's user-facing features, do not sell it, and do not use it for advertising or for any unrelated purpose.

Data retention & deletion

On-device data (captures, notes, tokens, keys) lives in your browser and is removed when you remove the extension or clear its storage. For the licensing record on our servers, we keep it for as long as your license is active so we can validate it. To request deletion of your licensing record (email, payment id, license-key hash), email privacy@voxissue.com from the address used at purchase and we will delete it; note that deleting it may deactivate your license, and that Stripe independently retains transaction records it is legally required to keep.

Your rights

Depending on where you live (for example under the GDPR or CCPA), you may have rights to access, correct, delete, or port your personal data, and to object to certain processing. Because the only personal data we hold is your licensing record, we can satisfy these requests directly — email privacy@voxissue.com. You may also delete on-device data yourself at any time by removing the extension.

Children

Vox Issue is a developer tool and is not directed to children under 13.

Changes

We'll update this page when our practices change and revise the "last updated" date above.

Contact

Questions about privacy? Email privacy@voxissue.com or use our contact page.