Legal

Privacy

Last updated 21 September 2026

What the reporter sends

When you add @robit-one/reporter to a test suite, each run posts a payload to Robit containing:

Test names, and their pass / fail / skip / todo status
Durations, in milliseconds
Error messages and stack traces for failing tests
The coverage summary your runner emits — lines, branches, functions, statements
The suite name and runner you configured
Branch, commit SHA, commit message and environment, read from standard CI variables

The reporter does not upload your source code. Stack traces and error messages can contain fragments of code and values your tests produced, because that is what a stack trace is. If your tests assert on production data, that data can reach Robit through an assertion message. Treat test output as you would your CI logs.

Account data

Email address and name, for authentication and for attributing spec approvals. Organisation and project names you choose. Project tokens, stored hashed.

What we do not do

We do not sell your data.
We do not use your test results or source to train models.
We do not write to your repository. Spec changes are committed only when a person approves them, from their own session.

Processors

{{LIST EACH SUBPROCESSOR}} — at minimum the database and auth provider, the hosting provider, and any model provider used for unattended analysis. Name each one, its purpose, and the region its data sits in.

Retention and deletion