Trust & Transparency

Data Retention & Deletion Policy

How long R3 keeps your information, what happens when service ends, and how deletion is handled.

Version and effective date: 17 August 2026

1. Approach

R3 keeps client data for as long as it is needed to provide the service, and then for as long as it is reasonably needed to meet legal, accounting, contractual, security or dispute obligations. After that, R3 deletes or de-identifies it where practicable.

This page describes how the platform actually behaves today. It deliberately avoids precise retention periods where none is genuinely implemented or legally required.

2. While your service is active

Operational data — horses, ownership, race results, costs and owner returns, uploaded documents, published reports, and the account records needed to run your portal — is retained for as long as it is needed to provide the service to you.

You can request a standard export of this data at any time. See the Data Export Policy.

3. After service ends

Data may be retained temporarily so you can complete an export and transition away without losing records.

Some data is retained longer where reasonably needed for legal, taxation, accounting, contractual, security or dispute purposes. Once no longer reasonably required, it is deleted or de-identified where practicable.

4. Quick Add Race source material

Quick Add Race lets an operator attach a source image or PDF while entering a result. The platform is designed to purge rejected drafts and abandoned drafts, and their attached source material, 30 days after rejection or abandonment. The purge routine exists in the platform and is run by R3; R3 does not claim it runs on an automatic schedule.

That 30-day period applies to Quick Add draft source material only. It does not apply to accepted race results, your documents, published reports, or any other category described on this page.

5. Audit, security and administrative records

Administrator actions, access decisions, suspension and reactivation events, and similar security records are retained for longer than ordinary operational data where that is reasonably necessary to keep the service accountable and secure.

These records exist to protect clients. They are not used for marketing.

6. Backups

Backup copies held by R3's infrastructure providers age out under those providers' normal backup and rotation cycles.

R3 does not promise immediate erasure from every historical backup, because that is not something the platform can honestly guarantee. Backup copies are not used for ordinary operational access, and they age out over time.

7. Deletion requests

You can ask R3 to delete data. R3 will action reasonable requests where it can.

A request may be refused or limited where R3 is required or reasonably entitled to keep the information — for example for taxation and accounting obligations, an unresolved dispute, a contractual record, or security and audit integrity. R3 will explain the reason if that happens.

  • Requests are made from your portal or by email to the address on the Contact page.
  • R3 verifies authority for the account before acting on a deletion request.
  • R3 will tell you what was deleted and what was retained, and why.

8. Your rights

Access and correction rights are described in the Privacy Policy. Standard export rights are described in the Data Export Policy.

Nothing on this page limits or excludes rights you have under the Australian Consumer Law or other laws that cannot lawfully be excluded. Where any wording here conflicts with those rights, those rights prevail.

Rishav Aryal (ABN 34 930 918 759) is the sole-trader service provider. R3 Racing Analytics is the service/brand name used on this site.