Privacy Policy
Last updated: August 2026
1. Who we are, and our promise
Forkcell is operated by Nicholas Muir. Our position is simple: your code is yours, we store as little as the product needs, and this page lists all of it. We do not sell personal data, we do not run advertising or third-party analytics, and we never use your code, tickets, or prompts to train models. Questions: info@forkcell.ai.
2. Exactly what we store
This is the complete inventory of what lives in Forkcell’s database:
| Category | What, precisely | Kept for |
|---|---|---|
| Account | Name, email, password (bcrypt hash — we never see the plaintext), role, email-verification state | Until you delete your account |
| Organization & billing | Org name, plan, seat count, Stripe customer/subscription identifiers, whether a card is on file. Card numbers never touch our systems — they live with Stripe | Life of the account + legal retention for invoices |
| Integration credentials | Agent tokens (Claude/OpenAI/local-model config), GitHub token or App installation id, Jira credentials, webhook secrets, license key — all encrypted at rest; disconnecting an integration deletes its credential | Until you disconnect or delete the account |
| Repository configuration | Clone URLs, setup/startup/test commands, ports, image choices, agent instructions you write | Until you remove the repository |
| Workspace run records | The ticket text you submit, run status and timestamps, opened PR links, a snapshot of the agent's output log, any demo credentials the agent left in its notes, test-gate result, agent cost and token counts | Until you delete the run; containers themselves are reaped automatically after their TTL |
| Runner records | Runner name, a hash of its token (the token itself is shown once and never stored), advertised host, mesh IP if enrolled, last-seen time | Until you remove the runner |
| Activity log | Who did what, when — workspace, settings, and team changes | Life of the organization |
| Push tokens | Device tokens for mobile notifications, if you enable them | Until you sign out the device |
| Review approvals | The name a stakeholder enters when approving a workspace via a review link, and the timestamp | With the run record |
We also keep aggregate, non-personal operational metrics (run counts, spend totals) to operate and improve the Service. Nightly database backups are retained for 14 days; deleted data leaves backups as they rotate out.
3. Where your code lives — and where it doesn’t
- Self-hosted runners (the recommended setup): your repositories are cloned onto yourmachines, inside disposable containers. Your source code never reaches our infrastructure — our control plane sees the ticket, the status, PR links, and the agent’s output log, not the codebase.
- Forkcell-hosted workspaces: code exists only inside the transient workspace container and is destroyed when the workspace is deleted or automatically reaped. We keep no copy.
- Model providers: the agent sends prompts — which include your ticket text and the parts of your code it reads — to the model provider you configure (e.g. Anthropic or OpenAI, under their terms), using your keys. Configure a self-hosted model (Ollama) and nothing leaves your network at all.
- Dependency caches: package-manager caches live on the machine that runs your workspaces, are scoped to your organization, and contain public packages, not your code.
4. Sub-processors
We share data only with the services that make Forkcell work: DigitalOcean (hosting), Stripe (billing), GitHub (repository access you authorize), Atlassian (Jira, if you connect it), Expo (mobile push, if you enable it), and the model provider your organization configures. Each receives only what its function requires. A current sub-processor list and a Data Processing Agreement are available on request.
5. Security
Credentials are encrypted at rest; runner tokens are stored only as hashes; secrets reach workspaces via files that are deleted after reading, never via inspectable environment variables; runners connect outbound-only with no listening ports; and every administrative action is recorded in the activity log your admins can read. No system is perfectly secure, but we will notify affected customers without undue delay if we become aware of a breach affecting their data.
6. Cookies
One session cookie, for signing you in. No advertising cookies, no cross-site trackers, no third-party analytics scripts.
7. Your rights
You can access, correct, export, or delete your personal data. Admins can delete runs, repositories, and integrations directly in-product; for account deletion or a data export, email info@forkcell.ai — we action deletion requests within 30 days (plus the 14-day backup rotation). Where GDPR or similar laws apply, Nicholas Muir acts as processor for the content your organization runs through the Service and as controller for account data; we honor the rights those laws grant, as implemented under Dutch law.
8. Changes
We may update this policy as the product evolves; the inventory above is kept in step with what the product actually stores. Material changes are announced in-product or by email before they take effect.