Data handling and isolation
Each ThriveOnDev run happens in its own short-lived job, in an environment reserved for your workspace. The job gets only the credentials that one run needs, for only the repositories you allowed, and it is deleted shortly after it finishes.
Where a run happens
- One job per run. Every stage of every task, whether implement, review, fix review or release, starts as a separate job with a fresh copy of the repository.
- A space per workspace. Your workspace's jobs run in their own Kubernetes namespace with resource limits. Jobs from other workspaces cannot reach them.
- Network rules. A job accepts connections only from the ThriveOnDev control plane. It can reach the internet, for example to install dependencies or call the AI provider, but not private or internal network ranges.
- Time limit. A run is stopped after 5 hours.
- Clean-up. The repository copy exists only inside the job. Finished jobs are deleted after about 30 seconds.
Credentials a run gets
| Credential | Scope and lifetime |
|---|---|
| GitHub | An app installation token limited to the repositories your workspace allows. It lasts one hour and is renewed during a long run only while the repository is still allowed. |
| AI access | The Claude key or Codex sign-in of the person who gave the task. Keys are stored encrypted (AES-GCM) and are never shown again after you save them. |
| Delivery | A one-time token that hands the job its credentials and expires within 15 minutes. |
Callbacks from a job to ThriveOnDev are signed with HMAC-SHA256.
What is kept
| Data | Kept for |
|---|---|
| Repository contents | The life of the job only |
| Linear issue and comment details the agent used | The service term |
| Run history: stages, outcomes and failure reasons | Workflow history 7 days, events 3 months, other records the service term |
| Agent session records: prompts, output and tool events | The service term. Pod logs only for the life of the job |
At the end of the service, a signed DPA provides return or deletion within 30 days. The managed cloud runs on DigitalOcean in London (LON1). See the subprocessor list.
Sign-in and access
People sign in to the workspace through ThriveOnDev's identity service with OIDC. Roles come from your workspace membership. See Team and roles. Each run is tied to the person who gave the task and their own AI access, so there is no shared agent account.
Assurance status
- A DPA draft is available for legal review.
- No penetration test has been carried out yet.
- ThriveOnDev is not SOC 2 certified, and no audit is in progress.
For the full overview, see the security page. Send security questions to security@thriveondev.com.