Security and privacy
What our agents will and won't do on your app, and how we handle what you give us.
On your app
- Each environment has a switch for tests that change data. With it off, our agents sign in and look around your app. Apart from signing in, they don't save, pay for or send anything.
- We only press billing buttons like Pay, Buy or Subscribe on an environment you've marked as a payment sandbox. The only card number we ever type is a standard test number.
- Sign-up tests use made-up details, never a real person's.
- A never-press list keeps agents away from account controls like Delete account, and from billing buttons unless you've marked the environment as a payment sandbox.
- We recommend pointing SpecHawk at a staging or test environment.
With your data
- A saved Jira token only ever goes to the Jira site it was saved for, and GitHub connections only go to GitHub.
- On the app-builder hosts we know, like Lovable, Bolt and Base44, a saved sign-in cookie stays on your app's own address.
- Agent recordings reach an AI model only after an admin has given consent.
Not yet
- No SOC 2 report yet, and no single sign‑on for SpecHawk accounts beyond Google.
Our privacy page names our AI providers and says what we keep.