Privacy Policy

1. What the installed client sends

The publisher client (the thing that runs inside your terminal alongside your AI coding agent) can only emit five fields. The schema is public, versioned, and enforced on both the client and the server — a batch carrying any extra field is rejected in full, and the rejection raises a public audit alert.

• when your agent starts thinking (timestamp)
• when it stops thinking (timestamp)
• the duration, derived from the two above
• a local random UUID — rotatable, not tied to any hardware identifier
• a closed enum naming the CLI tool (claude-code, aider, cursor, …)

Never collected. Not anonymized — absent:

prompts, code, agent responses, file or project names, environment variables, shell history, hostname or username, persisted IP address, or any hardware identifier.

2. What account data we hold

Creating a publisher or advertiser account stores: your email address, a salted/hashed password (we never store the password itself), an optional display or company name, and the IP address you registered from. The registration IP is used only for anti-abuse rate limiting and, for admins, a best-effort country-level lookup (via a third-party IP geolocation API) to see roughly where signups and delivery are coming from — never city-level, never sold, never shown to anyone but the operator.

3. Payments

Advertiser topups and publisher payouts, where processed by a real payment provider (Stripe), are handled entirely by that provider — we never see or store full card numbers. Our database holds the resulting ledger entries (amounts, timestamps, status) but no raw payment instrument data.

4. Cookies and local storage

The dashboard stores your API key or session token in your browser's localStorage, sent only as a Bearer token to our own API — never to a third party, and never as a tracking cookie. There is no advertising or analytics tracker on this site.

5. Sub-processors

Depending on what your deployment has configured: Stripe (payments), SendGrid (transactional email — verification and password reset), and ip-api.com (best-effort IP → country lookups for admin visibility, never on a path that blocks or delays your requests). None of these receive telemetry data — only the account or payment fields each one strictly needs.

6. Retention and deletion

Ledger and audit records are kept for the lifetime of the account plus a reasonable period for financial and fraud recordkeeping. You can request account closure and deletion of personal data (email, name, IP) beyond what we're required to retain for those purposes — reach out through the contact details on our GitHub repository.

7. Changes

We may update this policy as the product evolves; material changes will be reflected here with an updated date.