Who this notice covers
This notice explains how Turnstone handles personal data when you visit the website, create an account, join an organisation, or connect a GitHub or Gitea repository. "Turnstone", "we", and "us" refer to the Turnstone service.
Data we collect
Account data
When you sign in, we receive your WorkOS user identifier, email address, name, profile picture, and organisation identifier when one exists. If you choose Google, Google authenticates you through WorkOS. Turnstone does not request custom Google scopes and does not receive or store Google access or refresh tokens. We also store your choice of light, dark, or system theme.
Organisation data
We store your organisation's name, its members, and the role of each member. When a member invites someone, we send the invited person's email address and role to WorkOS, and WorkOS sends the invitation.
We keep an audit log for each organisation. The log records which member created or renamed the organisation, sent or revoked an invitation, changed a role, removed a member, created a project, or added or deleted a Gitea host. An invitation entry holds the invited email address. A project entry holds the repository's provider, host, and name.
Project and repository data
When you connect a repository, we store the project name, the member who created the project, and the repository's provider, host, owner, name, default branch, and web address. If you name a separate issues repository, we store its name.
For a GitHub repository, we store the GitHub App installation identifier. We use a short-lived GitHub user token to check repository access during setup. We do not store that token.
For a Gitea host, we store the host address, a display name, the OAuth2 client identifier, the encrypted OAuth2 client secret, the member who added the host, and a certificate bundle when your organisation supplies one. When someone connects a Gitea repository, we store a read-only access token and a refresh token for that Gitea host. We encrypt both tokens. We also store their expiry time and their scopes.
Bug facts
When Turnstone syncs a repository, it reads the issues that carry the testkit label. For each of those issues, we store the issue number and link, whether the issue is open or closed, the severity, the area, the cause, the impact, the confidence in the cause and in the impact, how the bug was caught, the reason that earlier tests did not catch it, the test type, the campaign, commit identifiers, and dates. We also store how Testkit found the commit that introduced the bug, and whether Turnstone could read the facts in the issue.
For the commit that introduced a bug, we store the commit identifier, the date it landed, the pull request number, and the kind of change. For each area, we store its identifier, its name, and its share of the code. For each project, we store the time of the last sync, the last sync error, and a time that records how far the sync has read.
We do not store issue titles, issue text, file paths, authors, tests, or evidence.
Service data
Like most hosted services, our infrastructure may process request metadata such as timestamps, IP addresses, user-agent strings, and error details to operate, secure, and troubleshoot the service.
How we use data
We use this data to authenticate users, authorise access to organisations and projects, read bug facts from the repositories you connect, show analytics about those bugs, prevent abuse, secure the service, and diagnose failures. We do not sell personal data or use it for third-party advertising.
Turnstone reads from GitHub and Gitea. It does not write to either.
Cookies
Turnstone uses essential cookies for the sign-in flow, the invitation flow, the authenticated session, the repository authorisation flow, and one-time interface messages. These cookies are required for the service to work. One more cookie remembers your theme choice. We do not currently use analytics or advertising cookies.
Services that process data
We use service providers to run Turnstone: WorkOS for authentication, organisation membership, and invitations, Google when you choose Google sign-in, GitHub for repository authorisation and for reading connected repositories, Fly.io for application hosting, and Neon for PostgreSQL. Each provider processes data under its own terms and privacy commitments.
A Gitea host that your organisation adds is not one of our service providers. Turnstone connects to that host at your organisation's request, to authorise access and to read connected repositories.
Retention and deletion
We keep account, organisation, project, and bug-fact data while it is needed to operate your account, show your analytics, meet security requirements, or resolve disputes. Turnstone does not currently offer self-service account deletion or publish a fixed deletion schedule. Contact us to request access, correction, export, or deletion. We will assess the request against any legal, security, and integrity obligations that require us to retain specific records.
Security
We use safeguards appropriate to the service, including encryption of stored Gitea credentials, short-lived provider credentials where supported, authenticated access controls, and encrypted connections. No online service can guarantee absolute security.
Your choices and rights
Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or receive a copy of your personal data, and to complain to your local data-protection authority. We may need to verify your identity before completing a request.
Changes to this notice
We may update this notice when the service or its legal obligations change. The effective date above shows when this version took effect.
Contact
For privacy questions or requests, email hello@turnstone.cloud.