Organisation isolation
Every club, region and federation is a separate organisation. Postgres row-level security enforces the boundary on every query.
Volunteer-run committees still hold sensitive information about kids, parents and members. Here's how we keep it safe — in plain English.
Six pillars, every one of them measurable rather than aspirational.
Every club, region and federation is a separate organisation. Postgres row-level security enforces the boundary on every query.
TLS 1.2+ in transit, AES-256 at rest. Backups are encrypted and stored in the same region as your primary data.
Production access is restricted to a small named team and gated behind SSO + hardware MFA. Every access event is logged.
Admin actions, role changes and configuration tweaks are recorded per organisation and exportable as CSV.
Daily encrypted backups retained for 30 days, with point-in-time recovery on Pro and Enterprise plans.
Primary infrastructure runs in Australia, aligned with the Privacy Act and the Australian Privacy Principles.
Where we are, what's in flight, and what we won't claim until it's audited.
Our internal controls are mapped to the SOC2 Trust Services Criteria. A formal Type 1 audit is on the roadmap.
Data minimisation, lawful basis tracking, and deletion-on-request are built into our admin tooling.
Default hosting in Australia, with notifiable-breach handling and APP-aligned data practices.
The vendors that touch your data. The full list lives in our sub-processors register.
| Vendor | Purpose |
|---|---|
| Supabase | Postgres database, auth, storage |
| Vercel | Web hosting and edge runtime |
| Cloudflare | DNS, WAF and edge caching |
| Cloudflare R2 | Object storage for media uploads |
| Stripe | Subscription billing and payments |
| Resend | Transactional and broadcast email |
| Inngest | Background jobs and scheduled tasks |
| Sentry | Error monitoring |
| Axiom | Application logging and analytics |
| Better Stack | Uptime and incident alerting |
Reliability is a trust promise too. Bugs happen in every product — what matters is whether they get noticed, reported and fixed, or quietly ignored.
Every page reports crashes automatically — and also the failures that never throw an error, like a button that does nothing when clicked or a request that fails behind the scenes.
Every signed-in user can report a bug in one click — throughout the admin, from their account page, and on any error screen. The report carries the page and recent errors, and from an error screen it files onto the same tracked issue as the crash itself — so it reaches the engineer with the evidence attached.
Screen recordings are captured only when an error occurs, and text, inputs and media are masked by default — member rosters, waivers and payment fields never appear in recordings.
Synthetic checks exercise the platform continuously, background jobs report their failures like any other error, and the live service status is public on our status page.
Want to see the product before trusting it with a season? The live demo is open to anyone — no sales call, no sign-up wall. Current platform health is always visible on the service status page.
We take security reports seriously. Email security@clubhelix.com with details and the team will review your report.