Privacy Policy

Who is responsible

DriveLab is an independently operated simulator and playtest project. The project operator, identified publicly as DriveLab, is responsible for the personal information described in this notice. You can contact the operator at [email protected].

Information we collect

• Account information: your email address, verification status, account identifiers, sign-in provider, account creation date, and any name or profile information supplied with your account.
• Authentication information: password hashes where you choose a password, authentication attempts, verification and session information. Authentication is provided by Clerk. DriveLab does not receive your Google password.
• Playtest and invitation records: account and player identifiers, access-key assignment and status, invitation codes, referral relationships, qualification results, program balances and administrative corrections.
• Download records: the build, version, platform and time associated with a download request or recorded transfer start. A recorded transfer start does not establish that you installed the software.
• Technical and support information: IP addresses, browser or device information, request and security logs, and information you choose to provide when contacting us or reporting a problem.

Signing in with Google

If you choose Google sign-in, Google and Clerk provide the account identifier, verified email address and basic profile information, such as your name and profile picture, needed to create or authenticate your DriveLab account. We use this information for account access, account recognition and the playtest services you request.

Google sign-in requests basic identity permissions. It does not give DriveLab access to your Gmail messages, Google Drive files, contacts or Google password. Google information is not used for advertising or sold to third parties. You can review or revoke the connection in your Google Account connections. Revoking Google access does not by itself delete your DriveLab records.

Epic sign-in and connected game features

In builds that use Epic Account Services and Epic Online Services (EOS), DriveLab processes Epic account and product-user identifiers, your display name, authentication proofs and session information to sign you in, recognize your player identity and protect access to connected services. DriveLab does not receive your Epic password. Our backend keeps records identifying the player, the DriveLab session, its validity and the game-version information needed to check compatibility.

The Epic consent screen identifies the permissions requested by DriveLab. Basic Profile supports account identification. Friends and Online Presence support the friends interface: DriveLab reads friend identifiers, display names, friend-request status and online status, and sends friend requests and responses that you choose. The current integration keeps the full Epic friends list in the running game’s memory. Selected player identifiers are sent to our backend for DriveLab invitations and blocks. For Epic account blocking, the game opens Epic’s blocking controls. These features depend on the permissions you grant and the services available in your build.

Where you use an offered playtest-account linking or recovery flow, DriveLab also records the verified relationship between the playtest player identity and the Epic product-user identity so that the requested account access can be maintained.

When connected game features are available and you use them, DriveLab also processes:

• Game profile and participation: player identifiers, team code or number, team name, driver number, profile visibility choices, party or lobby membership, invitations, blocked-player choices and session or match identifiers. Game profiles are private by default.
• Saved game content: robot configurations and, if you use the cloud library, private autonomous programs, including their name, source code, robot variant and starting position. This information is associated with your player identity to save and synchronize your content.
• Gameplay and publication records: match participation and results, scores and statistics, and any Skills result you submit. An available Skills publication feature can submit a score alone or a score with a replay or ghost file and its metadata, according to your selection.
• Service and safety records: game build and platform, connection or latency measurements, authentication and error information, and player reports, including the reporting and reported player identifiers, related match, category and details you submit.

The game also stores account and synchronization settings, preferences, profiles and locally saved replays on your device. Content saved only locally is distinct from content you send to a connected feature. We use connected-service records to operate the requested features, keep profiles and results consistent, investigate problems or abuse, and provide support. Describing a feature in this notice does not mean that it is available in every build.

How we use information

• Create, authenticate and maintain accounts, including recognizing an existing account and its playtest key.
• Manage access to playtest waves, provide downloads and show relevant build or account status.
• Operate invitations and referrals, calculate eligibility and program balances, and investigate duplicate or abusive activity.
• Protect the service, apply rate limits, troubleshoot failures and respond to support or privacy requests.
• Meet applicable legal obligations and establish, exercise or defend legal claims.

Where a legal basis is required, we process information to provide the service you request, for legitimate interests in operating and securing DriveLab, to meet legal obligations, or with consent where required. Information necessary for authentication and account management must be provided to use those features.

Some eligibility, capacity, rate-limit and referral checks are automated. If you believe a result is incorrect, contact us to request a review by the operator.

Cookies and similar storage

Clerk and the website use cookies or similar browser storage for authentication, session continuity, security and necessary interface behavior. The invitation flow also uses a browser-bound referral cookie to retain your invitation choice; that cookie can last up to seven days.

You can manage cookies in your browser. Blocking necessary cookies may prevent sign-in or invitation features from working. The website does not currently configure advertising cookies. Google, Discord and other services you choose to visit have their own cookie and privacy practices.

Who receives information

Access is limited to the operator, authorized administrators and service providers where needed to operate or protect DriveLab. Current providers include:

• Clerk for authentication and account management.
• Vercel and Cloudflare for website delivery, hosting and network protection.
• OVHcloud for backend and game-service infrastructure, and bunny.net for download delivery.
• Google when you choose Google sign-in.
• Epic Games for Epic sign-in and the Epic Online Services integrated into the build you use. DriveLab exchanges authentication and selected social-feature information with Epic for these features. Epic’s own privacy notice explains its handling of information.

Other players receive the information needed for the game interactions you choose, such as your displayed player or team identity and party or match participation. If you make your game profile public, its team code, team name, driver number and published statistics can be visible to other players; the public team search does not include the internal product-user identifier. If you publish a Skills result or replay using an available sharing feature, the selected result or replay can be visible to its audience. Avoid including contact details or other private information in public names or submissions.

If you share an invitation link, its recipient may see the associated display name or invitation information. If you join the linked Discord community, the information you provide there is handled under Discord’s policies and the community’s rules.

We may disclose relevant information when required by law, to respond to lawful requests, or where necessary to protect the service and people from abuse. We do not sell personal information.

International processing

DriveLab uses international service providers. Depending on the service and your location, information may be processed in the United States, the European Union, Canada and other countries where those providers operate their delivery networks. Their data-protection rules may differ from those in your country. The provider policies linked above describe their locations and transfer arrangements. Contact us for information about the arrangements relevant to your data and any safeguards required by applicable law.

Storage, protection and retention

Account information, Epic-linked player identifiers, game profiles, saved cloud content and associated playtest records are retained while needed to provide the relevant account and game services. Gameplay results, published records and account-linking records are retained according to their purpose, including maintaining the results or access you request. Authentication sessions have limited validity and expired session records are periodically removed; expiry of a session does not by itself delete separate account or gameplay records. Invitation, player-report, security, support and administrative records may be retained for longer where reasonably necessary to address abuse, resolve disputes or satisfy legal obligations. Retention is assessed according to the purpose of each record; providers also apply their own applicable retention arrangements.

The portal uses encrypted storage for recoverable playtest keys and stored contact email addresses, and uses keyed digests for certain lookups and security checks. Access to administrative functions is restricted. No storage or transmission method can guarantee complete security.

Your choices and requests

Depending on applicable law, you may request access, correction, deletion or a copy of your information, object to or restrict certain processing, or withdraw consent where processing relies on consent. Contact [email protected] using the email associated with your website account, or describe the game platform and player identity concerned if you use Epic sign-in without a website account. Do not send passwords, access tokens or your full playtest key. We may need proportionate information to verify a request before changing or disclosing account records.

To request deletion across the associated DriveLab systems, contact us directly. Deleting a sign-in profile or revoking a social connection alone may leave separate DriveLab player, playtest, invitation, gameplay or security records. For information held directly by Epic, use the choices and contact methods in Epic’s privacy notice. You can also change the profile visibility and social controls offered in the game. Changing visibility, removing an item from a library or revoking a public replay does not necessarily erase every related stored record; contact us for a deletion request across DriveLab systems. We will explain any records that must be retained and the reason. You may also raise a concern with the data-protection authority competent for your location.

Younger users

If you are not old enough under the rules applicable to you to independently accept the service terms or authorize the relevant processing, involve a parent or legal guardian before creating an account. A parent or guardian can contact us about a child’s information or request its removal.

Changes to this notice

We may update this notice as DriveLab or its providers change. The effective date above identifies the current version. Material changes will be communicated through the website or another appropriate channel when required.

Contact

For questions or requests about DriveLab, contact the project operator at [email protected].