This policy explains what Cogenity processes when you use the website, the command-line tool, and Cogenity Pro. It also explains what stays on your device.
Who is responsible
Cogenity is provided by Kenneth Lynne AS, organization number 823 450 532, Toftes gate 43C, 0552 Oslo, Norway. The company is the data controller for the processing described here unless another provider acts as an independent controller.
What we process
Account profiles on your device
Provider account credentials stay on your device. Cogenity reads local Claude Code and Codex profile files to enroll an account, show its limits, and start the selected provider. It does not send provider credentials, prompts, project paths, or the email addresses of those accounts to the Cogenity service.
Cogenity Pro
You sign in to Cogenity to verify the subscription required to run agents. cogenity login signs you in through WorkOS, our sign-in provider. Your machine keeps that sign-in in the operating system keychain, next to a short signed proof of your plan.
The Cogenity service stores your WorkOS user ID and email address. It also stores one record for each machine you signed in from, your plan and the date it is paid through, your Creem customer and subscription IDs, and the IDs of the Creem events it has already handled. A machine record holds a keyed digest of the session instead of the session itself, so the stored value cannot sign anyone in. The dashboard at app.cogenity.sh lists your machines and lets you revoke any of them. A revoked machine loses agent access the next time you use it. One cookie keeps you signed in to the dashboard.
Payments
Creem collects checkout, billing, payment, tax, and invoice details as the merchant of record. Cogenity receives identifiers and subscription events from Creem. Cogenity does not receive or store your full payment card details.
Usage telemetry
The CLI creates a random telemetry ID. It is separate from your sign-in and from any machine record. When telemetry is on, the CLI reports which Cogenity command ran, its duration and exit status, and the operating system, CPU architecture, Bun version, and Cogenity version. It does not report arguments, paths, account names, email addresses, prompts, or tokens. The relay gives the caller IP address to OpenPanel to derive an approximate location. The IP address is not stored as an event property.
The website sends anonymous server events to OpenPanel to count page views and selected link clicks. The browser sends only the normalized route, event name, and an allowed destination name. It does not send a full URL, referrer, browser details, device identifier, profile identifier, session identifier, or browser timestamp. OpenPanel can derive a daily identifier for the server relay from its own request metadata. That identifier represents the relay, not a visitor. Session replay, advertising, cross-site profiles, visitor sessions, and user identification are not enabled.
Turn CLI telemetry off with cogenity telemetry off or COGENITY_TELEMETRY=0. Cogenity also honors DO_NOT_TRACK=1 and disables telemetry in continuous integration environments.
Why we process it
- To provide and verify Cogenity Pro under our contract with you.
- To operate, secure, diagnose, and improve Cogenity.
- To answer support requests.
- To meet accounting, tax, fraud-prevention, and legal duties.
The legal bases are contract performance, legal obligations, and our legitimate interests in operating and improving the service. Where the law requires consent, we ask for it before that processing.
Who receives it
- Cloudflare hosts the website, the API, and the Cogenity Pro records. It also processes network request data.
- WorkOS runs the sign-in. It holds your email address and your sign-in history.
- OpenPanel processes the website and CLI analytics described above.
- Creem handles checkout, billing, invoices, tax, fraud checks, and related customer service. Creem acts as the merchant of record and may act as an independent or joint controller for buyer data.
These providers may process data outside Norway. Their policies explain their locations and transfer safeguards. We may also disclose data when the law requires it or when professional advisers need it to protect a legal right. We do not sell personal data.
How long we keep it
Local profile and settings files remain until you remove them. We keep subscription, machine, checkout, and event records while needed to provide or recover Cogenity Pro, prevent fraud, resolve disputes, and meet legal and accounting duties. We keep analytics only while it is useful for operating and improving Cogenity. You can ask us to delete or restrict data when the law permits it.
Your rights
Depending on the law that applies, you can ask for access, correction, deletion, restriction, portability, or an objection to processing. You can withdraw consent where consent is the legal basis. You can also complain to the Norwegian Data Protection Authority or your local authority.
Changes
We update this page when the data flow or legal terms change. The date above shows when the current version took effect. We will give another notice when the law requires it.
Contact
Email hello@cogenity.sh with a privacy question or request. You can also write to Kenneth Lynne AS, Toftes gate 43C, 0552 Oslo, Norway.