Security
Last updated 18 November 2026.
Report a vulnerability
Email hello@getmandateops.com with the steps to reproduce it. Please give us time to fix it before you share it.
Runs on your machine
- Where. The SDK and CLI run tests against your own containerised deployment on your machine.
-
Records. Each run’s record is written to its run
directory, such as
runs/<run-id>. Records hold what your tests report, such as failure messages and response bodies, so keep secrets out of them. -
Upload. A record leaves your machine only when you
run
mandateops upload. Database table names and query text are removed first. On GitHub Actions the repository, commit, ref, pull request and workflow run are sent too. Credential-named fields and private addresses are masked. -
Raw inputs. Sent only with
--share-inputs, so a teammate canmandateops recheckthe verdict from them. Recheck re-derives the verdict; it does not rerun your backend. If an input holds a credential-named value, no inputs are shared.
Hosted runs
- What is sent. The scenario and, if you name one, the backend.
- Where. MandateOps servers run MandateOps example backends against the test provider.
- Records. Kept in your workspace for your plan’s run history.
Money and keys
- Money. None moves. Payouts go to the MandateOps test provider, which records test effects and settles nothing.
- Network. The CLI calls api.getmandateops.com only for workspace features, such as uploads and hosted runs.
-
Agent keys. Read from
MANDATEOPS_AGENT_KEYor your system keyring, never from a command argument. - Coding agents. They draft tests and read results; they get no payment authority.
Personal data
See the privacy policy.