Security & Data Handling
M9R treats agent activity, evidence, and connection tokens as sensitive. Redaction runs before storage across the product, and the local CLI redacts secrets from anything it prints. Do not submit API keys, secrets, private keys, customer PII, PHI, payment data, or other regulated sensitive data through any channel or evidence submission.
Evidence submissions, run activity, PR/commit content, and workspace rules all pass through the same redaction path before they're written. It always runs.
Common secret patterns are scanned and redacted: OpenAI keys, Anthropic keys, Stripe keys, AWS keys, GitHub tokens, bearer tokens, JWTs, private keys, and common contact data. The local CLI additionally redacts your own connection token from anything it prints.
Git features (push, PR create, git-as-events) are scoped to each workspace's own GitHub App installation. A workspace's token can only ever touch repos it connected, enforced by GitHub itself.
Content agents produce (commit messages, PR bodies, run activity) is treated as data. It is not used as a system prompt and cannot invoke tools.
Sensitive review actions and controlled-run events are written to a hash-chained audit log, so a record can't be silently edited after the fact.
Application-level rate limits apply to sensitive API routes. Edge firewall and bot controls are operated separately and may vary by deployment.
- User-initiated deletion of uploaded runs
- Account deletion on request
- Broader bot protection on public endpoints
Do not submit
API keys, secrets, private keys, customer PII, PHI, payment data, or regulated sensitive data, in messages, evidence submissions, or any other channel.
M9R does not claim SOC 2, HIPAA, GDPR, or enterprise compliance. The product is early. We will only add a security claim here once it is implemented and verifiable.
Contact: runleak@proton.me