Data policy

Retention & deletion

A plain-language view of how customer, billing, support, security and backup records are intended to be managed.

Owner: Wade GeorgesonLast updated: 1 August 2026
Pre-launch policy draftBusiness registration details, a public support address and final legal review must be completed before paid public launch.
01

Active league records

Incident, penalty, appeal, licence-point, carry-over, session, briefing and configuration records ordinarily remain available while the customer account and subscription are active, subject to operational limits and lawful requests.

02

After cancellation

Customers should export records they must retain before the subscription ends. Inactive league data is intended to be scheduled for deletion or de-identification after a defined post-cancellation retention window that will be confirmed before public launch.

03

Commercial records

Invoices, subscription identifiers, transaction references and other commercial records may be retained for tax, accounting, fraud prevention, dispute and legal requirements even after league data is removed.

04

Support and security records

Support messages and relevant diagnostic or security records may be retained for as long as reasonably necessary to resolve the issue, protect the service, demonstrate action taken and meet legal obligations.

05

Backups

Backup copies expire through the backup retention cycle. Deletion from the live service may not immediately remove a record from every backup; backups are isolated and ordinarily restored only for disaster recovery.

06

Requests

Access, correction and deletion requests may be directed through the official support pathway. Competition decisions may need to be referred to the relevant league administrator, while Stew-Bot remains responsible for its own handling of platform, billing and support data.