Data facts

Privacy: what the software handles

This describes implemented data flows, not an approved legal privacy policy or a promise about every deployed service. Do not submit secrets or sensitive project content unless you are authorized to send it to the configured services.

Website account and sessions
Google sign-in supplies account identity. The website database schema stores a user ID, name, email, profile image, linked OAuth account fields (including provider tokens when supplied), and database-backed sessions. Authentication cookies identify browser sessions.
Desktop authorization
The website stores hashed desktop approval and device codes, the PKCE challenge, account association, and expiry/consumption timestamps. It stores credential hashes with owner, creation, expiry, and revocation metadata, not the raw issued desktop bearer token in those credential tables. The model gateway separately manages model credentials.
Caller abuse controls
Desktop API throttling uses the caller IP supplied by the configured trusted ingress. The rate-window database stores a keyed hash of the caller or credential identifier, scope, minute, and count. This is an abuse-control mechanism, not a claim that infrastructure logs never contain IP addresses.
Payments
Stripe hosts checkout and the billing portal. The application stores Stripe customer, subscription, checkout and receipt identifiers, payment-related status, and allowance/reconciliation records. Card entry occurs on Stripe's hosted pages, not a card form in this application.
Model requests and usage
Desktop model requests pass through a LiteLLM gateway to configured upstream model providers. Prompts and the context attached to a request leave the desktop; this can include project source or editor information needed for the task. The gateway stores those prompts and the model responses in a private S3 bucket for debugging and abuse investigation. Gateway usage reporting includes spend, request counts, and token counts. This is not an offline-only assistant. The privacy policy describes that log.
Hosted library
Catalog requests authenticate a desktop credential and restrict private catalog metadata to its owner. The currently hosted library serves metadata search and resolution; its HTTP download endpoint does not provide asset binary delivery.
On the desktop
The desktop saves its credential locally using Electron safeStorage and refuses sign-in when secure storage is unavailable. Local support diagnostics and project-operation records also exist. Encryption of a saved credential does not mean every project file or diagnostic is encrypted, or that a compromised signed-in device cannot use it.
What revocation changes
Usage lists both model and library-only credentials and allows the signed-in owner to revoke them. Revocation is an access control, not deletion of account, payment, project, or provider records. Website sign-out does not revoke desktop access. Already-started requests may complete.

Policy documents

The list above is the implementation record. The privacy policy and terms of service are the documents that apply to the website and the Windows app. This page does not add a retention period, a deletion deadline, or a refund right.