Privacy Policy

Effective Date: 28th February 2026 Last Updated: 28th February 2026


1. Who We Are

This Platform is operated by: Tableized Limited

Tableized Limited
Registered in the United Kingdom Company Number: 12822719 Email: privacy@tableized.com

For the purposes of UK GDPR and EU GDPR:

Organisers using the Platform are generally independent Data Controllers in respect of the events they manage.


2. Scope of This Policy

This policy applies to:


3. Categories of Personal Data We Process

3.1 Account & Profile Data

3.2 Emergency Contact Data (Stored at Account Level)

Users may store emergency contact details in their account to enable prefilling of race entry forms and to assist Organisers in safeguarding participants.

This may include:

We do not use emergency contact details for marketing or SMS campaigns.

3.3 Event Entry Data

3.4 Payment Data

Payments are processed by:

We do not store full payment card details. Payment providers act as independent Data Controllers.

3.5 Race Results Data

3.6 Technical & Security Data


4. How We Collect Data

We collect data:


5. Lawful Basis for Processing (GDPR)

We rely on the following lawful bases:

Processing Activity Lawful Basis
Account creation Contract
Event entry processing Contract
Payment validation Contract
Emergency contact storage Legitimate Interests / Contract
Security monitoring Legitimate Interests
Publication of entry lists/results Legitimate Interests
Membership validation Legitimate Interests
Transactional SMS Contract
Marketing SMS Consent
Financial record retention Legal Obligation

Where processing relies on Legitimate Interests, we ensure that those interests do not override your fundamental rights.


6. Emergency Contact Information

Emergency contact details are stored to:

User Confirmation

By providing emergency contact details, you confirm that:

Access Controls

Emergency contact details:

Sharing

Emergency contact details may be shared with:


7. Children’s Data

Where events involve participants under 18:

We take additional care in relation to publication of junior competitor information.


8. SMS Communications & US A2P 10DLC Compliance

8.1 Collection of Mobile Numbers

We collect mobile numbers for:

8.2 A2P 10DLC Compliance

For US mobile numbers:

Marketing SMS messages are sent only where express consent is obtained.

Users may opt out at any time by:

Transactional messages relating to event entries may be sent where necessary for contractual performance.

Emergency contact numbers are not enrolled in SMS campaigns.


9. Publication of Entry Lists and Results

Organisers may publish limited competitor information for:

Published information may include:

Publication is based on legitimate interests in fair competition and sporting transparency.

You may object to publication in accordance with Section 14.


10. Data Sharing

We may share data with:

We do not sell personal data.


11. International Transfers

Where data is transferred outside the UK or EEA, we ensure appropriate safeguards are in place, such as:

Payment providers may process data internationally under their own safeguards.


12. Data Retention

Data Category Retention Period
User accounts Duration of account + 3 years inactivity
Emergency contact data While account active
Event entry data 6 years
Payment records 6 years
SMS consent records 4 years
Security logs Up to 12 months

Users may delete emergency contact details at any time via account settings.


13. Security Measures

We implement appropriate technical and organisational safeguards including:


14. Your Rights

Under UK GDPR / EU GDPR you have the right to:

Requests may be submitted to:
privacy@tableized.com


15. Automated Decision-Making

We do not conduct automated decision-making that produces legal or similarly significant effects.


16. Organiser Responsibilities

Organisers using the Platform:

We maintain Data Processing Agreements with Organisers where required.


17. Changes to This Policy

We may update this Privacy Policy from time to time. The latest version will always be published on this page with an updated effective date.