Data Processing Addendum

For repository content and portfolio data processed on your behalf, you are the controller and we are the processor. For account and billing data about your own users, we are the controller.

We process data on your documented instructions, which are the configuration of your account: the connected organisations, the Blueprints, the policies, the approval gates and the autonomy level.

We do not process it for any other purpose, and we do not use it to train models made available outside your account.

Encryption in transit and at rest. Credentials held only by the services that require them. Access to production restricted, logged and reviewed.

Every autonomous action is recorded with its actor, its authorising policy, its inputs and its validation result.

We use the sub-processors listed on the subprocessors page. We give notice before adding one, and each is engaged under terms no weaker than these.

We assist with data subject requests, impact assessments and incident notification within the timelines your agreement sets.

Because every change carries provenance, an audit request about a specific shipped change can usually be answered from the audit trail rather than by inspection.

On termination, data is returned or deleted at your election within the period your agreement sets. Your code is already in your repositories and is unaffected either way.