Security and trust

Safety comes before growth. Only the first list below is in place today; everything under "Planned" is a design goal for the trial and isn't live yet.

Today (waitlist stage)

• HTTPS everywhere with HSTS, plus a strict Content Security Policy (no third-party scripts).
• Waitlist and vote data kept outside the public web folder. Hosted in SiteGround's Sydney data centre (daily host backups are kept in Singapore).
• Our application never stores raw IP addresses: it keeps only pseudonymised, daily-keyed hashes, used for rate limits and one vote per day. Our host's standard server logs do record IP addresses for security.
• Rate limits, size limits and abuse checks on our forms and endpoints.

Planned for the trial

• Client-side encryption (XChaCha20-Poly1305): designed so we'll hold only ciphertext and won't be able to read memory contents. We'll still see account details and metadata (bot names, snapshot sizes and times).
• Signed snapshots (ed25519) so you can verify nothing was altered.
• Scoped per-bot keys (snapshot:write, snapshot:read, billing:spend), hashed at rest, rotate and revoke any time.
• Tenant isolation, audit logs, idempotency keys, upload limits.
• Restore drills as a first-class feature: a backup you can't restore is worthless.
• MFA for the portal and admin; a pen-test review before paid launch.

The trade-off, stated plainly

Because the design means we won't hold your keys, if you lose your key we won't be able to recover your data. You'll get a recovery kit at sign-up.

Offline Copy custody

Planned: offline copies will be encrypted, kept off the internet at a separate secure location in Australia. Location and handling details are kept private as a physical-security measure. That never replaces encryption.

"Machine-first" is not "secret"

The bot layer is designed for machines, not hidden from scrutiny. The spec is shared with anyone who asks.

Incidents

Any security incident stops the trial. We'll follow the Notifiable Data Breaches scheme (Part IIIC of the Privacy Act) and notify affected people and the OAIC of any eligible data breach. Security researchers: see the safe-harbour rules in our terms and security.txt.