Legal
Privacy
Robit is operated by Zero Copy Labs LLC (“Robit”, “we”). This page says what we collect, why, who else touches it, and how to have it removed. The short version:we collect only what the product needs, we do not sell it, and we share it only with the infrastructure providers listed below. This page describes our current practices. It is not a warranty, and the Terms govern our liability.
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
- Test file paths, retry counts and similar per-test details your runner reports
- The suite name and runner you configured, and any custom metadata you attach
- 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, and keep secrets and personal data out of it.
MCP server and CLI
If you connect an AI client to the Robit MCP server (mcp.robit.one), anything that client sends is transmitted to us, which can include file contents, transcripts and prompts. Unlike the reporter, this path can carry source code and conversation text. Send only what you are comfortable sending, and do not send confidential transcripts or secrets. Keep MCP tokens out of commits and client configuration files.
Account and organisation data
- Email address, name and a password credential, for sign-in and for attributing approvals.
- Organisation, project and repository names you choose, and member roles.
- Project tokens, which we store hashed. We cannot read them back.
- Basic technical data our servers log to run and secure the service: IP address, user agent, request time and error details.
GitHub and Fly.io connections
If you install the Robit GitHub App or connect Fly.io for Actions runners, we store the minimum needed to run the feature:
- From GitHub: the installation and account identifiers, the repositories you select and the permissions granted, and metadata about the workflow jobs routed to Robit runners (repository name, job identifiers, labels, status and timing).
- From you: the Fly.io API token and organisation name you provide. The token is stored encrypted in a secrets vault and is used only to run your jobs. You can remove it at any time by disconnecting.
Runner provisioning is still being built. As designed, jobs execute on machines in your own Fly.io organisation, and we do not intend to read your repositories’ contents, job logs or build artefacts. The permissions you grant the GitHub App and the Fly.io token are what bound what we can do; review them before you approve. Granting a Fly.io token gives us the access that token carries.
What we do not do
- We do not sell, rent or trade your data, and we do not share it for advertising.
- We do not use your test results, coverage, specs or source to train models, ours or anyone’s.
- We do not run advertising or cross-site tracking, and this site sets no cookies. It uses a privacy-focused analytics service, described below.
Website analytics
This site uses Umami Cloud to count visits. It sets no cookies and does not build profiles of individual visitors. When a page loads, Umami receives the page address, referrer, browser and device type, screen size, language and country, and uses your IP address only to derive those, without storing it. We use the counts to see which pages are read. Blocking the script has no effect on how the site works.
Cookies
This marketing site sets none. The app sets strictly necessary cookies to keep you signed in. We do not use them for tracking.
Why we use your data
To provide the service you asked for: authenticating you, ingesting and displaying your results, running the integrations you enable, keeping the service secure and fixing faults, and contacting you about your account. We do not use it for anything else without asking you first.
Who touches it
These providers process data on our behalf to run Robit. We do not share your data with anyone else, other than as described under legal requests below:
- Fly.io: hosts the web app and API servers, in the United States (San Jose).
- Supabase: the database, authentication and encrypted secrets storage.
- Cloudflare: hosts this marketing site and sees ordinary connection data, such as IP addresses, to deliver it.
- Umami: provides the website analytics described above, for this marketing site only.
- GitHub: when you install the GitHub App, it sends us the events described above.
- Trigger.dev: runs background jobs for features that are in build. Those jobs may handle integration credentials, such as GitHub App and Fly.io tokens, and job metadata.
- Email provider: sends invitations, magic links and account notices, and so receives recipient email addresses and message content.
- Anthropic: only if an optional server-side AI fallback is enabled, and then only for the analysis you requested. Under Anthropic’s commercial terms, inputs are not used to train its models. We will update this page before turning it on for any account.
We may disclose data if the law or a valid legal request requires it. Unless prohibited, we will tell you first and share only what is required.
Where it is stored
Our servers are in the United States. If you are in the EEA, the UK or Switzerland, your data is transferred to the United States under the safeguards our providers offer, such as standard contractual clauses. We will sign a data processing agreement on request.
Security
Data is encrypted in transit and at rest by our providers. Project tokens are hashed, integration secrets sit in an encrypted vault, access is limited by role and per-organisation row-level rules, and webhooks must carry a valid signature. No system is perfectly secure. If a breach affects your data, we will tell you without undue delay and, where the law sets one, within the required deadline.
Retention and deletion
- We keep your data while your account is active.
- You can delete a project, member, integration or token from the dashboard. To delete an organisation or your account, or to ask for a copy of your data, email us. On request, we delete from live systems within 30 days.
- Backups age out on our database provider’s schedule, after which deleted data is no longer recoverable.
- Some records, such as job history and security logs, may be kept for a limited time after deletion.
- We may keep limited records longer where the law requires, such as billing records if we ever charge, or to resolve a dispute or prevent abuse.
Your rights
Depending on where you live, you can ask us to access, correct, export or delete your personal data, to restrict or object to how we use it, and to withdraw consent. California residents have the equivalent rights under the CCPA; we do not sell or share personal information as those laws define it. Email us and we will respond within 30 days. You can also complain to your local data protection authority.
For account data we are the controller. For the test results and other content you send us, you are the controller and we process it on your instructions.
Children
Robit is for professional use and is not directed to anyone under 18. We do not knowingly collect data from children.
Changes
If we change this page in a way that matters, we will email account holders at least 30 days before it takes effect. The date above always shows the latest version.
Contact
Privacy questions and requests: hello@zerocopylabs.com.
Zero Copy Labs LLC, 1554 E Talo Ct, Millcreek, UT 84106, USA.