Privacy Policy

What keel collects

keel collects limited account, product and analytics data to provide its services, run optional features such as leaderboards, and improve the product.

• Account data: email-based account/session from Supabase authentication.
• Profile/settings data: display name, username, extension preferences.
• Product usage events (see Product usage analytics below): high-level signals sent to keel servers to improve reliability and product experience. These events do not include prompts, page text, or full URLs.
• Gameplay analytics events: game_played and brain_answer with game/topic metrics, timestamps, and your user ID when you are signed in and choose to sync.
• Extension install/connect pings used to confirm extension setup (including extension version and browser user-agent).
• If you use an ambassador or referral invite (see Ambassador and referral links below): the email you submit on that page, plus related technical identifiers used to deliver the invite and measure whether the referral led to keel usage.

Product usage analytics

keel may collect internal product analytics: limited usage events sent to keel servers to improve reliability and product experience. This telemetry is not used for advertising.

The extension may create a randomly generated pseudonymous identifier and keep it in local extension storage. That ID helps group usage events from the same install over time. It is not your name. It is not treated as a public account handle. In ordinary use it is not linked to your email unless you sign in for sync, or unless a referral/ambassador invite operationally connects that install to an email you submitted (see below). Uninstalling the extension removes local extension storage, including that identifier and queued events that have not yet been delivered.

Examples of what those events can include:

• Session started, completed, or dismissed (high-level lifecycle signals).
• Selected mode: Play, Brain, Focus, or Auto (when Auto is the effective preference).
• Game started (Play mode) and session or play-related completion signals.
• Which supported AI site keel is paired with: ChatGPT, Claude, or Gemini (category only).
• Approximate session duration.
• Extension version.
• Basic settings changes (for example that preferences changed, without copying your settings values).

keel uses this information only to improve product reliability, understand feature usage, and prioritize future work. It is not a medical or clinical tool, and this data is not used to assess or label your health. If sending or storing analytics fails for any reason, the extension continues to work normally; analytics never blocks core functionality.

keel does not collect or store the following for this product analytics (or for analytics in general):

• AI prompts you write.
• AI responses or model output.
• Page content from websites you visit.
• Your full browsing history.
• Complete URLs of pages you visit.
• Health, diagnosis, or clinical data.
• Mouse movement tracking.
• Gameplay frame-by-frame recordings or equivalent high-frequency motion logs.

Ambassador and referral links

If you open an ambassador or referral page (for example /a/A01) and submit your email, keel collects that email so we can:

• Send you a keel link to open or install keel on your computer.
• Send one follow-up email about a week later. The content may differ depending on whether you have already started using keel.
• Measure whether the referral led to actual keel usage (for example install and activation).

This is not a newsletter signup. There is no automatic marketing email sequence beyond the immediate keel email and that single follow-up.

The referral flow may use technical identifiers such as an ambassador/referral source, a handoff identifier on the invite link, and the extension's pseudonymous install identifier. These may be connected operationally so keel can tell whether a referred person activated and returned. That means referral email is not always fully separate from extension usage identifiers.

Ambassador reporting is aggregated (for example counts of leads, installs, and activations). Ambassadors do not receive your email address, individual usage history, extension anonymous IDs, or handoff tokens.

What keel does not collect

• keel does not collect full browsing history.
• keel does not capture screenshots.
• keel does not log keystrokes as user typing telemetry.
• keel does not sell personal data.
• keel does not use data for personalized advertising.

Why data is collected

• To authenticate users and sync settings between web app and extension.
• To power Play and Brain leaderboards.
• To monitor reliability and debug event delivery issues.
• To understand product usage and plan improvements (see Product usage analytics).
• To deliver ambassador/referral invites and measure referral outcomes in aggregate.

Where data is stored and processed

• Supabase is used for authentication and database storage.
• Vercel is used to host the web application and API routes.
• Resend is used to deliver transactional and referral/invite emails (including the immediate keel link email and the single follow-up).
• keel uses Vercel Web Analytics to understand aggregated website traffic (page views and visitor counts, not individual user profiles).
• Some extension preferences and short-lived queues are stored locally in Chrome storage.

Contact

For privacy questions, contact the keel project maintainer via the support channel listed in the Chrome Web Store listing.