Security
Found a problem? Tell us.
If you think you've found a security problem in aihops, email security@aihops.com.au. A person reads every report.
Last updated 21 October 2026. Machine-readable: security.txt.
Reporting a problem
- Say what you found, where, and how to see it happen: the steps, the requests and what came back.
- An AI agent acknowledges your report, says it's an agent, and passes it straight to a person. We'll tell you what we find and when it's fixed.
- Please give us a reasonable time to fix it before you tell anyone else.
Testing in good faith
- Use your own accounts and documents. Don't open, change or keep anyone else's.
- Stop as soon as you've shown the problem, and don't keep any data you came across.
- Don't slow aihops down for other people, send spam, or try to trick people or our agents into giving access.
We won't take legal action against research done in good faith that follows these rules.
How aihops is kept secure
- Sign-in for everything. Nothing in the app is public, and every request is checked against what that person may see.
- Documents run in a sandbox. A document's own scripts run walled off from aihops, so they can't see anyone's session or anyone else's work.
- Stored in Australia. Documents, comments and history are kept in Microsoft Azure's Australia East region, encrypted at rest, and reached only over HTTPS.
- No passwords. People sign in with a code sent to their email address, or with Google.
- On the record. Every action is kept in an audit trail that can't be edited.
- Least privilege. aihops reaches its storage with its own Azure identity, with no keys to steal, and its email agents can reach only their own mailboxes.