Master Control

Security Overview

Last updated: June 16, 2026

Master Control touches two sensitive things: your live product and, if you connect it, your source code. Here is how we handle them. This page describes how the system actually works today — not aspirational claims.

How code access works

You connect a repository by installing our GitHub App on the specific repositories you choose. You can revoke it at any time from your GitHub settings.
To propose a change, the Mind works on a short-lived clone of your repository, makes its edits on a dedicated mc/… branch, and opens a pull request.
It never merges, never pushes to your default branch, and never force-pushes. You review and merge every change. These limits are enforced in code, not just policy.
Access tokens are short-lived installation tokens, encrypted at rest, and are scrubbed from logs.

Tenant isolation

Each customer’s project, conversations, and connected repositories are isolated. A customer’s access credential is scoped to their own project only and cannot read or act on another customer’s data.

Model & key handling

On Bring Your Own Key, the Mind runs on your Anthropic key; your key is encrypted at rest and used only for your project. Model spend is yours to see and cap.
On Managed plans, we provide and pay for the key.
Secrets (API keys, tokens, webhook secrets) are stored encrypted and never logged.

Payments

Payments are handled by Stripe. We never see or store your full card number. Webhook events are signature-verified before they’re trusted.

Transport & hosting

All traffic is served over HTTPS with HSTS. The application and database run on managed cloud infrastructure.

Operator note: as you mature, add specifics customers ask for — data region, backup/retention schedule, incident-response contact, and any third-party audit (e.g. SOC 2) once available. Don’t claim certifications you don’t hold.

Reporting a vulnerability

Found a security issue? Email ford.genereaux@dysonswarmtechnologies.com and we’ll respond promptly.