Trust
Every statement on this page is rendered from a fact that a check or a configuration file produced. Nothing here is typed by hand except this copy, which is reviewed, and every section says when it was last verified and what produced it.
Where data is at rest
The region and zone every resource of this deployment is labelled with, by resource class, and whether the resource holds customer data.
| Resource | Region | Zone | Customer data |
|---|---|---|---|
| database | europe-west3 | europe-west3 | none |
| database volume | europe-west3 | europe-west3 | none |
| compute | europe-west3 | europe-west3 | none |
No second region is configured for this deployment: there is no copy of the data anywhere else.
What leaves the system
Every host the running service may reach, with the purpose and what leaves for it, from the reviewed allow-list.
| Host | Purpose | What leaves |
|---|---|---|
| api.github.com | The GitHub App's requests: the installation, the repositories it can see, their pull requests, and a review or comment a person writes in Regbuild | Repository names, pull request numbers and the words a person chose to post; never a key or a token of the workspace |
| github.com | Exchanging a person's authorisation code for their token; the installation and authorisation pages are GitHub's own, opened by the browser | The authorisation code and the App's client credentials, nothing else |
Who processes data
The organisations that process data on the operator's behalf, where, and what class of data, from the reviewed list.
| Name | Role | Location | Data | Notice | Since |
|---|---|---|---|---|---|
| Google Cloud | Build and staging infrastructure | europe-west3 (Frankfurt) | No customer data, ever; seed data only (DR-05) | 30 days | 2026-09-06 |
| OVHcloud | Production hosting, planned | eu-west-par (Paris) | Customer data, once production exists (DR-05, DR-14) | 30 days | 2026-09-06 |
A change to this list takes effect only after the notice period each entry states, counted from the date beside it, so a customer has time to object before a new processor is used.
How it is deployed
The environment, how the service is reached, how many copies of it run, and where the database lives.
| Environment | Reached through | Copies | Database |
|---|---|---|---|
| gcp | Ingress | 1 | PostgreSQL in the cluster, one StatefulSet with a persistent volume |
Where inference happens
The model providers configured for this deployment and the region each one reports.
No provider configured. Inference location is never assumed: it appears here when a provider adapter reports a region, and not before.
What is certified, and what is not
The certifications this deployment runs under, each with who holds it, what it covers and the region it is keyed to, from a reviewed file. A certification held by a supplier is the supplier's, not this service's, and the scope column says which.
| Scheme | Held by | Scope | Region | Evidence |
|---|---|---|---|---|
| ISO/IEC 27001 | OVHcloud, the hosting supplier | The supplier's own datacentres and platform operations, not this service running on them | eu-west-par | The supplier's published certificate, checked at the deployment's review |
| BSI C5 | OVHcloud, the hosting supplier | The supplier's German platform operations, not this service and not the region this deployment runs in | de1 | The supplier's published attestation report, checked at the deployment's review |
Not claimed
Stated as plainly as what is claimed, so nothing is inferred from silence. A scheme absent from the list above is not held for this deployment, whether or not it appears elsewhere in the industry or in another region of the same supplier.
- SecNumCloud: not held for this deployment. The qualification applies to specific supplier offerings and regions, and this deployment does not run on one of them.
- ISO/IEC 27001, SOC 2 and any other scheme for RegInspect Ltd itself: none is held. What is listed above is the hosting supplier's, for the supplier's platform.
- BSI C5 for the region this deployment runs in: the attestation above covers the supplier's German region, which this deployment does not use.
- Any certification of the model providers a workspace configures: those are the providers' own and are stated in the inference section as each provider reports them.
The documents
The terms, the data processing agreement and the notices this deployment publishes, with the version in force and the date it took effect.
No document is published for this deployment yet.
Security posture
The penetration test this deployment has closed, its scope and who ran it, with the findings open and closed. Counts only: a finding's detail is in the report the operator shares under an agreement, never on a public page.
No penetration test has closed for this deployment. Nothing here is asserted about its security posture until one has.
What the agent marks mean
A passage shown as written by an agent was declared by that agent, through the tool it records its work with. Nothing here infers authorship from how an edit arrived — its size, its speed or its shape — because none of those tell an agent from a paste, a refactor or a snippet, and a guess recorded as a fact would empty the mark of its meaning.
The consequence, stated rather than glossed over: coverage is partial. What is marked is what agents declared, and no more. A passage with no mark has no declaration, which is not the same thing as having been written by a person, and this page will not claim otherwise.
Government access
No claim of immunity from government access is made, on any cloud. Every provider can be compelled by the law it operates under. What this page states is where data is and who can reach it, so that a data protection officer can judge the exposure rather than take a promise.
Works council
What a works council can hold this deployment to, rendered from the product's registry, its rules and its tests the same way as everything here; the co-determination pack a workspace generates carries the same facts in German and English.
- No exported function of the rules package takes a person and returns a number; the lint rule no-person-metrics fails the build on that shape.
- No count, rate, duration or score about a person is stored; the schema lint refuses a column that would hold one.
- Groupings with fewer than five members are refused, and no grouping keys on a person.
- The works-council mode changes what is documented, not what is computed; a test reads every derived output with the mode off and on and finds them equal.
The collector is not deployed here; the deletion of telemetry identifiers is in its configuration and in the test that holds the code to it.
No constraint-test results are mounted on this server; the tests run on every change in the repository, and their results appear here once the operator mounts them.