How Kith handles your data.

1. Scope

This policy applies to the Kith website, account surface, backend API, and extension requests.

It covers information processed when you sign in, use text or visual analysis, save explanations to the Archive, or use billing-related features.

2. Information we collect

We collect account, session, usage, and saved-context data.

• Email address used for sign-in and account ownership.
• One-time sign-in code records and authenticated session records.
• Account settings such as private mode, sync state, weekly summary, and hotkey preferences when supported.
• Saved concepts and explanations you choose to store in the Archive.
• Limited landing-page analytics and usage events tied to product actions.
• Billing metadata such as Stripe customer and subscription identifiers when billing is configured.
• When the extension draws its on-page overlay, it may load typography assets from Google Fonts (similar to many websites) so the card UI matches the Kith design system; those requests follow Google’s policies for font delivery.

3. Analysis data

Text and visual explanations require the relevant slice of page context.

• Text requests may include selected text, page title, URL, headings, and surrounding text.
• Vision requests may include the marked image region, page title, URL, optional hint text, and surrounding text.
• Usage telemetry records limited metadata such as plan tier, private-mode flag, image size, or a redacted excerpt of selected text.

4. How we use information

We use data to authenticate accounts, operate analysis, enforce quotas, and support billing.

Kith uses the information above to sign users in, route model requests, return explanations, store saved concepts, measure daily quota usage, prevent abuse, and manage subscriptions where applicable.

5. Third-party processors

Kith relies on external providers for model and billing infrastructure.

• Google Gemini processes model requests that Kith sends through its backend.
• Stripe processes paid checkout and billing portal actions when billing is configured.

6. Storage and retention

Session and account data are retained to run the service until they expire or are removed.

• Sign-in codes expire after a short time window and are not stored in plain text.
• Authenticated sessions currently expire after 30 days in the service backend.
• The web account surface stores the active session token in local browser storage.
• The backend supports account deletion, which removes user records, sessions, usage events, and saved concepts from the application database.

7. Security and changes

We review this policy as the product surface changes.

Kith uses authenticated API routes for protected features and keeps billing outside the extension workflow. We may update this policy as the product evolves, and the date at the top of the page will reflect the latest revision.