Skip to content

Trust · The controls

How your data is looked after.

The questions a school, a club or a council asks before it puts its entrants on a platform, answered: where the data is, how it is protected, who can reach it, and what happens if something goes wrong. Each control is written against ISO/IEC 27001:2022 and the SOC 2 trust services criteria.

Version 2026-09 · Effective 11 September 2026

Where your data is held

The database that holds entries, results and accounts runs in the Sydney region, and uploaded media is stored in the Asia-Pacific region. The application itself runs at the edge, close to whoever is reading it, and reads from that same database.

Encryption

Connections to AnyRun are encrypted in transit, and the database and the media store are encrypted at rest. On top of that, the fields that identify a person, such as a phone number, a date of birth and an emergency contact, are encrypted again by the application before they are written, so they are not readable from the database alone.

Who can reach your data

Access is decided in the database itself as well as in the application: every read and write is checked against the person making it, so a request that goes around the interface is refused in the same place. Inside an organisation, access follows the role you were given: an accountant sees the finance pages, and a volunteer sees their own shifts. Administration of the platform requires a second factor.

Backups

The database is backed up daily, and the backups are held separately from the running system.

If something goes wrong

If a breach of personal information is likely to cause serious harm, we tell the people affected and notify the Office of the Australian Information Commissioner, as the Notifiable Data Breaches scheme requires. Organisers whose entrants are involved are told directly, with what we know at the time.

The companies that receive any part of it

Payments, email and file storage are handled by named providers, and every one of them is listed with what it receives, why, and where it runs.

Reporting a security issue

If you have found something, write to support@anyrun.net. We will acknowledge it, and we will not pursue anyone who reports a genuine finding in good faith. Our disclosure policy is published at /.well-known/security.txt.

The full documents

Six documents sit behind these controls. Write to support@anyrun.net and we will send the ones you need.

  • Information security policy
  • Access control policy
  • Secure development policy
  • Business continuity and backup policy
  • Privacy impact assessment
  • Incident response plan

Your data and who has access

What we hold about you and the buttons that make your rights real, plus every company that receives any part of it.

Optional analytics cookies. We'd like to load Google Tag Manager (it carries Google Analytics, our advertising measurement and Microsoft Clarity) to understand how AnyRun is used. Until you accept, none of it is loaded at all; "necessary only" keeps it that way, and we don't sell your data. Details in the Cookie Policy.