Data handling

Encryption

In transit. TLS everywhere. Internal service-to-service traffic is encrypted, including the path from the control plane to the build workers and from the build to the trial environment. Certificates are issued automatically and renewed before expiry; an expired certificate takes the service down rather than silently downgrading.

At rest. Database volumes, object storage, and backups are encrypted at rest. Where the storage layer supports customer-managed keys, those are available on the Self-Hosted plan and by arrangement on the Team plan.

Secrets

The rule is that a secret is never written anywhere it could be read by someone who should not have it.

  • Secrets are injected into the running process as environment variables or as files mounted read-only into the container. They are not baked into images, not written to disk in the workspace, and not passed as command-line arguments, which are visible in the process table.
  • Build logs never contain secret values. Where a step uses a secret, the log records the secret’s name and a masked fingerprint, so you can correlate two occurrences without either being readable.
  • Trial environment credentials are issued once, at provisioning, and can be re-issued but not read back. A credential that was issued is not retrievable later; it can only be rotated.
  • Secrets are never returned by the API. There is no endpoint that reads a secret’s value, because the platform stores only the encrypted reference, not the value.

What leaves our systems

Destination What is sent Retention at the destination
Model provider The prompt, the specification context, the relevant repository content Not retained beyond the request; not used for training
Source control Commits, branches, pull requests — in your repository Governed by your repository settings
Object storage Build logs, artifacts, recordings, seed data Until the retention window expires
Payment processor Token, amount, currency, customer reference Per the processor’s policy; card data never reaches us
Email provider Addresses, message content Per the provider’s policy

The model-provider line is the one worth reading twice. Your specification and the repository context needed to act on it are sent to the provider to produce a response. That is inherent to the product. What we contract for is that the provider does not retain it and does not use it for training, and the same contract covers every provider we use.

If your requirements forbid sending content to a model provider, the Self-Hosted plan exists for that case: bring your own inference, including a fully offline one.

Retention

Category Retention
Specifications and clauses Life of the account
Approval and audit history Life of the account
Verification results and findings Life of the account, or your configured window
Build logs 30 days by default, configurable to 90
Trial environment data Destroyed with the environment
Build artifacts 30 days, configurable
Seed data Regenerated on demand; not retained after teardown
Account data Life of the account, then 90 days to export, then deleted

Backups

The control plane database, the object storage metadata, and the platform configuration are backed up on a daily schedule, encrypted, and retained for 14 days. Backups are restore-tested, not merely written.

One thing worth stating explicitly, because it is the kind of gap that documentation usually papers over: backups of the control plane do not contain your source code. Your specifications and generated code live in your repository, under your retention, under your control. If you lose it, that is a repository problem, not ours — and we will not have a copy.

International transfers

The control plane runs in Southeast Asia. Trial environments run in the region closest to you, which may be elsewhere. Some subprocessors are located in the United States and elsewhere.

Transfers out of the EEA and UK are covered by Standard Contractual Clauses or an applicable adequacy decision. A current list of subprocessors, with locations and the data each handles, is available on request and is reviewed quarterly.

Deletion

A deletion request removes your personal data from the control plane database, the audit store, object storage, and any regional environment. The audit history is retained in a reduced form where retention is legally required — the record that an approval happened, without the content that was approved.

Your repository is yours. We commit to it; we do not administer it. We will tell you exactly where to look.

This site

The marketing site carries no third-party analytics, no advertising pixels, and no tracking cookies. Server logs are retained for 30 days for security and capacity planning. There is no cookie banner, because there is nothing to consent to.

See the Privacy Policy for the commitments this site makes directly.

Next