Routemark for teams: privacy

The short version, for a member

• Your organisation gave you a key. With it, your machine sends the service facts about the work Routemark delegated in your organisation's projects. It never sends your code.
• You can read on your own machine exactly what is sent, before and after.
• Your organisation's admins can read it. Nobody else's can.
• The service never ranks you, never averages you against anyone and never orders people by a figure.

What leaves your machine

Only for a project whose own file names your organisation, and only once you have connected your key in the console:

• about each finished task: its run ids, the project's name (never a path), the harness, provider and model, how many tokens the delegate and your Controller used, how it ended, how many attempts it took, each review's verdict and who gave it, whether the credential scan was clean, and when each of these happened;
• about each merge: the commit it landed on, the tree that was reviewed, how each check ended, and whether the review was waived, a check accepted or a credential finding cleared;
• about each attempt that has ended: its numbers;
• about a run that waits: that it is judged with no verdict, or that its delegate asked a question, and since when;
• your name as your admin typed it, a random id for your Routemark home, and the label you typed for your machine, if you typed one.

Never: your code, a diff, a file name, a task's text (unless the project's own file says it may be sent), a contract, a delegate's question or an answer, any log, any provider key or login, the reason you gave for a waiver or an acceptance, or a credential finding itself.

How you can see it, and stop it

• routemark summary --json --org NAME prints the whole document your machine would send. The console's Organisations page shows the same before you connect and after.
• The console shows every line your organisation's queue shows about you.
• Take your key off in the console and your machine starts no further send. What was already received stays with your organisation.
• A project that does not name the organisation sends nothing, whatever key is on the machine.

Who can read it

Your organisation's admins, signed in. No other organisation. At Saar Inc., only the people who run the service, and only to run it. We do not sell it, share it for advertising or use it to train models.

Your name on a task records whose key the machine held when the task was delegated. It does not establish who was at the keyboard, and the service says so.

Whose decision it is

Your organisation decides what it keeps about your work; we hold it on your organisation's behalf. To have your name removed, ask your organisation's admin: they can replace it with a neutral label everywhere the service holds it. The work stays in your organisation's figures under that label. If you cannot reach an admin, write to us and we will pass your request on.

How long it is kept

• While your organisation is subscribed: each task's facts and their history, each attempt's numbers, and your machine's latest summary. The body of an older summary is deleted after 30 days.
• After your organisation stops subscribing: 90 days, then everything is deleted.
• When your organisation closes its record: at once.
• In our database's backups: for up to eight days.

For admins

To sign in we hold your email address and the fact of your sign-in, through Google's Firebase Authentication (Google, GitHub or an emailed link). We hold no password. A signed-in admin has two cookies: one keeps them signed in, one guards the forms for an hour; the service sets no other cookie and runs no analytics. For a notice by email we hold the address you gave for a person. For billing, our payment processor holds your card and billing details; we never see the card number.

Who else handles it

• Google Cloud, in the United States: runs the service, its database and the sign-in.
• Stripe: takes payment and keeps invoices.
• Resend: sends the emails.

Each receives only what its part needs. The service's data is held in the United States.

Changes, and how to reach us

When this page changes, the date at the top changes, and we email admins before a change that matters. Anything about privacy: support@saarinc.tech. Saar Inc., State of Florida, United States.