Privacy policy
How orkai handles your data — local-first by design.
orkai is local-first software. Your indexed code, documents, standards, sessions, and other knowledge-graph entities stay on your machine unless you explicitly export them.
1. Data stored locally
When you run orkai, structured data, embeddings, and raw content are stored under
~/.orkai/ on your device (SQLite databases and local files).
We do not operate a hosted copy of your knowledge graph and do not receive your indexed
entities, prompts, or source code as part of normal product operation.
2. License activation and validation
To activate and validate a license, orkai communicates with Polar's customer-portal API. Over the wire we send:
- Your license key (required to activate and validate)
- Public product and benefit identifiers embedded in the binary
- Your activation ID after the first activation on a device
- A SHA-256 hex digest of a machine fingerprint derived from OS username, a hostname fallback label, and a platform machine identifier
The raw machine identifier is not sent to Polar — only the hash is used to bind a license to a device. Hostname and raw machine ID are not transmitted as part of the license API contract.
More on device binding and offline grace: see our Terms. Questions: [email protected].
3. Payments
Checkout and receipts are handled by Polar (merchant of record). Payment card data is processed by Polar and its payment partners — not by orkai on your machine. See Polar's privacy policy at checkout for how they handle billing data.
4. Embedding providers (optional)
If you configure OpenAI, Anthropic, Mistral, Ollama, or another embedding provider for indexing, orkai sends text to that provider per your configuration so embeddings can be generated. That traffic goes directly from your machine to the provider you chose — not through orkai-operated cloud infrastructure.
5. Product telemetry
orkai does not include product analytics or usage telemetry. License validation heartbeats go to Polar only as required for activation enforcement. This applies to the orkai software itself; the getorkai.com marketing website uses analytics with consent as described in section 6.
6. Website analytics
getorkai.com uses PostHog for pageviews and usage events (for example CTA clicks and the workflow explorer). A consent banner asks you to Accept or Reject before analytics cookies are stored.
- Accept: PostHog may set first-party cookies and use local or session storage for a stable visitor id, sessions, and analytics. Data may include page URLs, referrer, approximate location (GeoIP), browser and OS details, and CTA events.
- Reject: no analytics cookies. PostHog may still count visits with a privacy-preserving server-side hash (limited detail, no stable multi-day identity).
The site analytics path does not collect names, emails, or payment data. Payments are handled by Polar (see section 3). For how PostHog processes data, see PostHog's privacy policy. Related browsing terms: Terms.
7. Local secrets
~/.orkai/license.json and API keys in
~/.orkai/config.yaml are stored with restrictive file permissions.
Treat them like secrets.
8. Contact
Privacy questions: [email protected]