Privacy
Privacy Policy
This page explains how Racery currently handles personal data across account registration, profile approval, public creator profiles, public events, attendance workflows, favourites, admin review, and platform insights.
Last updated: 2026-04-06 11:25 EEST
Overview
This Privacy Policy explains how Racery collects, uses, stores, and protects personal data when you use the platform. It reflects the current Racery product used for platform access, testing, and ongoing product operation.
Racery is a motorsport media platform that connects media creators, clients, and organizers. The platform includes account registration, role-specific profile applications, public creator profiles, public events, organizer media-request workflows, client favourites, and approved-media insights.
What we collect
We collect the information you provide when you register and use Racery. This can include your name, email address, password hash, role, organization or company details, media profile details, event details, links to public social channels, uploads such as profile images, event cover images, and portfolio images.
We also store workflow data required to operate the platform, including profile approval status, event approval status, attendance requests, admin review decisions, delete-account requests, legal consent records, and related audit history.
If you contact Racery support, we may keep the information you send to us so we can respond and maintain a support history.
How public and private visibility works
Approved media profiles may be shown publicly in the Racery creators directory and on public creator profile pages. Only the fields intended for public display are shown there.
Client and organizer account profiles are not currently displayed publicly as standalone public profiles. At this stage, their account data is used mainly for approval, platform access, internal workflows, and limited contextual display where applicable.
If a client saves creators to Favourites, that list is private to that client account. It is not published publicly.
Event attendance is not public by default. Media must request attendance, and the organizer must approve it first. Approved attendance may then be used in public-facing event or creator participation history where that workflow applies.
Public contact visibility is controlled by platform rules and media-profile settings. Contact details are not exposed as open public database data.
How we use your data
We use personal data to create and secure accounts, verify email ownership, review profile applications, operate public creator and event pages, process media attendance requests, manage favourites, show role-specific account tools, and maintain admin moderation and audit workflows.
We also use data to send operational emails, including email verification, password reset, approval decisions, delete-request decisions, and organizer attendance approval or rejection emails.
Insights, views, and link tracking
For approved media accounts, Racery currently tracks certain account and public-profile interactions to power Insights. This includes unique public profile views and clicks on supported public creator profile links such as website, Instagram, Facebook, TikTok, and YouTube.
At this stage, these measurements are used to show platform activity inside approved media Insights. They are not used to build advertising audiences on the platform.
Cookies and technical data
Racery uses technical data necessary to run the service, including authentication and session-related information. The platform also stores legal-consent records for Terms and Privacy acceptance.
Racery also includes cookies-consent logic, legal-version tracking, and browser acknowledgement handling as part of the platform's legal and session foundation.
Moderation, admin review, and security
Admin and master-admin workflows are used to review role-profile applications, event submissions, delete requests, and other moderation actions. We keep the records needed to support these decisions, including approval history, review reasons, and admin audit history.
Racery uses role-based access rules, database-level protections, and server-side permission checks to reduce unauthorized access to protected data.
Retention and deletion
When a user submits a delete-account request, the request enters an admin review flow. If deletion is approved, Racery removes public visibility where applicable, cleans up account-linked uploads where no active system reference remains, and anonymizes retained records where required for governance, audit, legal-consent, approval-history, or delete-request purposes.
This means some records may remain in anonymized or compliance-supporting form even after account deletion, rather than every related record being blindly removed.
Contact
For privacy questions, support requests, or data-related concerns, contact Racery at support@racery.io.
This Privacy Policy may be updated from time to time so it continues to reflect the live platform and its legal requirements.