RaceCard Portal Privacy Notice
Effective date: November 15, 2026
RaceCard LLC ("RaceCard," "we," or "us") operates the organizer portal at portal.racecard.app. This notice explains information handled through the portal. The RaceCard racer app and public website have separate privacy notices.
Information handled through the portal
- Account and access information: Name, contact email, verification status, your connected sign-in provider and its account identifier, organization membership, roles, account status, and acceptance records for portal documents. Your contact email may differ from your sign-in email.
- Organization and event information: Organization details, saved tracks and addresses, series settings, event details, uploaded race reports and standings, badge definitions and awards, and claim decisions. Reports may contain driver names and other race information supplied by organizers.
- Support information: Ticket descriptions, comments, status, contact information and email-notification preferences.
- Usage and security information: Account activity and administrative actions, authentication and session records, and technical information processed by hosting and sign-in services, which may include IP addresses, browser/device information and request times.
- Subscription information: Organization access dates and subscription administration records. Do not enter payment-card details in the portal or support tickets.
Sign-in and verification
RaceCard uses Microsoft to broker supported federated sign-in and multifactor verification. Google is available initially; Apple will be offered after its setup is complete. RaceCard receives verified identity information needed to connect your sign-in with your portal account. RaceCard does not receive your Google or Apple password. Those providers and Microsoft handle information under their own privacy notices as well.
Invitations and contact verification use time-limited links. Your contact email is used for communication and verification; an email-address match alone does not connect or merge accounts.
How information is used
We use information to provide and secure the portal, verify users, control organization access, administer subscriptions, process and publish race reports and badge awards, review claims, provide support, and investigate errors or misuse. We also provide organization reports using available participation information. Reports may use racers' state and chassis-brand information supplied through their app profiles when those reporting features are connected.
Who can receive information
- Authorized organization personnel and RaceCard staff: Information is available according to assigned permissions. Some administrative and support functions are restricted to managers or platform administrators.
- Racers and other users of RaceCard: Information you publish, including race results, standings and badge awards, can be shown through RaceCard. Publishing race information is different from making private portal account or support information public.
- Microsoft: Hosting, storage, sign-in, security and operational email services.
- Google and Apple, when available: The sign-in provider you select handles the associated authentication process.
- GitHub: Support ticket information and replies may be stored in RaceCard's private helpdesk repository for authorized support personnel. Portal replies can be synchronized with that repository.
- Legal or operational recipients: Where reasonably necessary to comply with law, address a dispute, protect rights or security, or transfer the service as part of a business transaction, subject to applicable requirements.
Cookies and similar technologies
The portal uses essential cookies to maintain secure sign-in, protect requests and bind account setup to the browser. Blocking these cookies can prevent the portal from working. The portal is not currently configured with optional visitor analytics or advertising cookies. Any future optional analytics must be reviewed and disclosed before it is introduced.
Retention
We keep account, organization and published race records while needed to operate the service and maintain relevant race history. Access restrictions and subscription expiry do not automatically delete those records.
Resolved support tickets are scheduled for deletion after 12 months from their first resolution, except where an open or queued action prevents deletion or a dispute or legal obligation requires a retention hold. Expired account-verification and invitation-message content is removed through the service's retention processes. Hosting and identity-service logs have separate retention settings.
Your choices and requests
Contact support@racecard.app to request a correction, information about your data, or removal of portal access. We may verify your identity and authority before acting. A request can require coordination with the organization that supplied the race information. We consider applicable legal requirements and the rights of others; removing access does not automatically remove published race records.
Optional support-update emails can be disabled where offered. Invitations, verification messages and account-security communications are needed for the associated workflows.
Security and processing locations
We use access controls, federated sign-in and multifactor verification to protect portal access. No service can guarantee complete security. Information may be processed where RaceCard and its service providers operate.
Changes and contact
We will update the effective date when this notice changes and provide notice of material changes as appropriate.
Privacy questions and requests: support@racecard.app
RaceCard LLC