This page is prepared for business and legal review. Highlighted notes identify details RaceCore must confirm before this document is published as its policy.
Overview
This draft describes how RaceCore Network handles information in connection with its marketing website, inquiries, and beta applications. Separate agreements or notices may apply to customer websites and the RaceCore platform. Where a racing organization controls information in its own workspace or website, contact that organization about its use of your information.
Review before publishing: The operating entity is RaceCore Network, LLC. Confirm its legal mailing address, countries served, and the relationship between RaceCore Network, customer organizations, and service providers.
Information you provide
You may provide contact information when you email us, inquire about our products, or apply to a beta program. A beta application asks for your name, email address, role, organization, country or region, racing discipline, team size, product interests, goals, and testing preferences. A website address, event volume, current tools, and additional notes are optional.
Please do not include passwords, payment information, government identifiers, or confidential team documents in an application. Applying does not create a customer account or collect a payment.
Review before publishing: Inventory information collected through account registration, customer workspaces, support, billing, newsletter subscriptions, integrations, server logs, and any other installed plugins. Add their actual data categories here.
How information is used
Beta application answers are used to evaluate participation, understand racing workflows, plan testing, and contact applicants about the beta. An application does not enroll the applicant in a marketing newsletter. Information provided in a direct inquiry is used to respond and continue the relevant conversation.
Application submissions are stored as private records in WordPress for administrator review. A short-lived, salted network identifier is used to limit repeated submission attempts; the application record does not contain a raw IP address. Hosting or security systems may maintain separate logs.
Review before publishing: Confirm all additional uses, analytics, legal bases where required, and whether any data is used for advertising, profiling, or product training. Do not claim a practice that has not been verified.
Service providers and disclosures
Operating a website can involve hosting, storage, security, communications, and other service providers. Information may also need to be disclosed to respond to a lawful request, protect rights and safety, or complete a business transaction, subject to applicable requirements.
Review before publishing: Identify the providers actually used, the information each receives, their purposes and safeguards, and any business transfers. Confirm whether any disclosure qualifies as a sale, sharing, or targeted advertising under applicable law before stating that it does or does not occur.
Cookies and similar technologies
WordPress and installed services may use cookies or similar technologies for sign-in, preferences, security, and site operation. Browser settings can limit cookies, though doing so may affect functions such as signing in.
Review before publishing: Complete a live cookie and tracker inventory, including analytics, embedded media, payment tools, and advertising. List actual purposes and durations, explain available controls, and configure consent where required. This draft does not assert that the website is cookie-free.
Retention and security
Access to beta applications is restricted to WordPress administrators. Administrators can review and remove applications, and the application feature connects to WordPress personal-data export and erasure tools. These controls do not guarantee the security of the entire hosting environment.
Review before publishing: Set a documented retention period for applications, inquiries, accounts, backups, and logs. Confirm encryption, access controls, processor arrangements, and backup deletion practices. No automatic application-deletion schedule has been approved.
Your choices and requests
You can leave optional application fields blank. To ask a privacy question, request a correction, or request access to or deletion of application information, contact hello@racecore.com. We may need information to verify that a request relates to you. Please do not send identity documents unless a verified process specifically requires them.
Privacy rights, exceptions, and response requirements depend on the laws that apply to you and to the service. Requests concerning information controlled by a customer organization should be directed to that organization.
Review before publishing: Confirm the monitored privacy contact, verification process, applicable regional rights, response deadlines, appeals, authorized-agent requests, and complaint routes.
Audience and international use
The marketing website and beta application are designed for people representing racing operations. The application does not request a date of birth. Contact us before submitting information about a child or another person.
Review before publishing: Set the minimum age and any parent or guardian process. Confirm hosting locations, international transfers, and any required transfer safeguards or regional notices.
Updates and contact
The effective date at the top of this page will identify the approved version. Material changes should be communicated through an appropriate notice. For questions about this policy or your information, contact hello@racecore.com or visit our Contact page.
Review before publishing: Confirm the legal mailing address, notice procedure, and effective date. Have qualified counsel review the policy against the actual service and regions served.