Privacy
Eyekit is a hosted-transcription beta. The extension runs in your browser and writes the session it creates to your computer.
What this site does
This site provides Eyekit account creation and a small account dashboard. Supabase Auth processes account credentials and Google sign-in, and the Eyekit API stores only the account and usage information needed to provide the service. The site host may process ordinary request metadata such as an IP address, user agent, and time of request.
The site code has no analytics, advertising trackers, or nonessential cookies. Links to Groq, GitHub, or another service take you to that service, whose own policies apply.
What the extension does
When you record, Eyekit captures audio from the microphone after you grant the browser’s permission. Audio chunks are sent to the Eyekit API and forwarded to Groq for transcription. Eyekit stores usage metadata so it can enforce the free allowance and paid access; it does not retain audio after transcription completes.
Your extension token is stored in Chrome’s local extension storage. The server stores only a hash of that token and can revoke it from your account page. Review Groq’s current privacy policy and terms for how Groq handles transcription requests.
Page context and screenshots
To help an agent understand what you pointed at, Eyekit records page URLs, selected DOM details, text snippets, element selectors, and limited style information. The extension does not intentionally read input values and skips text extraction when the sampled element is a form control or editable region. Text elsewhere on the page, including parent elements, can still contain sensitive information. Do not treat that filtering as a guarantee that sensitive information cannot appear in a page context or image.
Optional screenshots can be captured while recording. A screenshot is a view of the visible content in the recorded browser tab and may show sensitive information, even when an input value was not extracted. Eyekit does not promise complete redaction. Session files, including the transcript, page context, and any screenshots, are exported locally to your Downloads folder.
Removing local data
Stop any recording first, then disconnect your device in extension settings. Uninstall the extension to remove its local settings according to Chrome’s uninstall behavior, and remove downloaded session folders from your computer separately. Data already sent to Groq or handled by Supabase is subject to those services’ policies.
If you give a downloaded session to a coding agent, that agent and its provider may process the files under their own policies.
Questions
For troubleshooting and support contact details, see Support. This page describes the current beta behavior and may change as Eyekit develops.