Privacy

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 uses browser storage to keep you signed in. Links to other services take you to those services, whose own policies apply.

With your consent, PostHog receives website page URLs and referrer sources, browser and device information, click interactions, page-exit timing, and session replay. Query strings and fragments are removed. Replay may reconstruct what appears on public pages, including pointer movement, scrolling, and navigation. Session replay is disabled on sign-in, sign-up, and account pages. PostHog may process your IP address to estimate your approximate location, and cookies or similar browser storage may recognize returning visits.

If you sign in, consented website activity may be linked to your account using its Supabase user ID. We do not send your email address or profile details to PostHog. The analytics code blocks sign-in form contents, account values, extension connection details, and the extension’s injected recording controls from capture.

You can decline analytics or withdraw consent through Cookie settings. Declining will not prevent you from using the site or your account. Necessary storage for sign-in and your consent preference will remain available.

Website analytics will not track how you use the extension or collect its recordings, transcripts, page context, screenshots, or exported session files. The service still processes the data needed to provide transcription and manage your account, as described below.

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.

Screenshots are captured automatically 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. Page URLs, DOM text/selectors/styles, cursor activity, clicks, scrolling, drawings, returned transcripts, voice amendments, notes, and screenshots are stored locally in Chrome extension storage and IndexedDB. No session archive is automatically uploaded and no hosted sharing or remote retrieval runs. Stopping copies a local-file prompt to your clipboard; the row Copy action copies it again. Download saves session.json and screenshots as a ZIP from Settings → Sessions; stopping does not automatically download files. You choose whether to give the prompt and files to an agent.

Stop any recording first. Disconnecting clears the local account connection; it does not remove saved sessions or downloaded files. Uninstall the extension to remove its local extension storage according to Chrome’s uninstall behavior, and remove downloaded session folders from your computer separately. Necessary account, usage, and billing records remain separate from local sessions. Data already sent to Groq or handled by Supabase or Polar 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.

Earlier Eyekit versions uploaded private session archives and used session read keys for remote agent access. This version removes that flow. Existing hosted archives and backups are not deleted automatically by an extension update, disconnect, or uninstall. They require a separate approved operator cleanup. Contact support to request removal of earlier hosted data; any files already given to an agent remain subject to that agent’s policies.