security is the operating model

how we build

• Least privilege by default — every credential is scoped to the minimum access that works, and granted as late as possible.
• Human-in-the-loop gates in front of anything irreversible: payments, deletions, external communications.
• Audit trails — what the software (and the AI inside it) read and did is logged and reviewable after the fact.
• Secrets are held in a secret manager, or in a root-owned, mode-restricted file the service reads at startup — never in code, never in a repository, never in a chat thread.
• Dependencies are checked before they’re adopted — what they pull in, who maintains them, what their history looks like.
• Client software gets tests in CI on every change, so a fix can’t silently break what shipped last week.

every build is reviewed before it ships

your data during an engagement

• Access to your systems is requested narrowly, used for the step that needs it, and revoked at handover.
• Development happens against sandboxes or synthetic data wherever the work allows it.
• Client material stays segregated per engagement — findings, credentials, and evidence never mix across clients.
• When engagement data is no longer needed, it’s securely deleted — written confirmation available on request.
• What we hold about you and how long is covered plainly in the privacy policy.

found a vulnerability?

We want to hear it, and you’ll reach a human — vulnerability reports are triaged ahead of everything else in the inbox. No form to fill out, no legalese to sign before you reach a person.