Data handling and pilot support
What leaves CI, how reports are accessed, and what the pilot does not certify.
Greenroom is an advisory pilot. A report supports a human release review; it is not a certification that an app is safe or defect-free.
Data flow
| Data | Where it goes |
|---|---|
| GitHub identity, installation and repository metadata | Greenroom's control plane and PostgreSQL database, for workspace access and run provenance |
| Simulator or web build | Built and walked inside your CI runner; Greenroom does not receive the compiled build |
| Screenshots, accessibility trees and traces | Greenroom's private Vercel Blob evidence store; accepted evidence is supplied to the configured model routes for judgment |
| Changed file names and route contract | Greenroom's planner, to scope the test |
| Source patches and source index | Off by default; uploaded only when both repository configuration and workspace policy allow them |
| Finding reviews and activity events | Greenroom's database; used for support, activation measurement and quality review |
The checked-in model routes use Anthropic and OpenAI directly, and OpenRouter to route requests to Anthropic, Google, OpenAI or xAI. Workspace overrides can change the recipients. The operator must confirm the effective routes and provider data terms for your pilot before sensitive test data is used. This page does not promise provider zero retention or a particular processing region.
Use synthetic test data
Screenshots can contain every visible value, including names, messages and account information. Re-encoding an image does not mask personal information. Text redaction recognizes selected credential patterns and can optionally redact email addresses; it is not a guarantee that all sensitive data has been removed. Keep production accounts, production credentials and real customer data out of the test environment.
Access and retention
Reports and evidence require an active GitHub workspace membership. A report URL is not a public sharing link. Downloaded agent handoffs contain the selected report and authenticated evidence paths; they contain no access token and grant no repository write permissions. Treat downloaded copies according to your team's own retention policy.
The default evidence retention is 90 days, configurable by the operator per workspace. The retention job deletes expired blobs and run records. Workspace usage records are retained separately for reconciliation; a billing estimate is not a charge. Scheduled deletion must be monitored by the operator and does not delete copies already downloaded by your team.
Support during the pilot
For a failed pass, open the report's GitHub Actions link, record the run ID and failing stage, and use the recovery instructions in the report. Do not paste credentials or raw customer data into support requests. Until a public support contact and terms are published, support and data-deletion requests go through your existing pilot contact. Public self-service launch remains gated on publishing the operator identity, support contact and reviewed terms.