Drag Racing 3D
Privacy Policy
Effective August 14, 2026
Scope
This Privacy Policy applies to the Drag Racing Companion iOS app, its App Clip, the Android companion app, and the website at dragracing.ycydev.org. It describes the data path used when a companion app controls Drag Racing 3D on the user’s own macOS, Windows, or iPad game device. App Store and Google Play services have their own privacy policies and are not operated by us.
Information handled by the app
The app handles only the information required to pair and control the game:
- Pairing information: a local network address, port, session identifier, protocol version, and short-lived single-use token contained in the pairing code.
- Device name: the phone’s model name is sent to the user’s game so it can identify the connected controller.
- Controller input: steering, throttle, brake, gear, camera, and recovery commands are sent to the game while connected.
- Optional game-service profile: when a full companion app is authenticated with Game Center or Google Play Games, the service provider, player identifier, and display name may be sent to the user’s game for the in-game driver identity. The App Clip remains a Guest and does not sign in to a game service.
- Motion input: if the user enables tilt steering, the app reads motion sensors on the device to calculate steering. It does not record or upload raw motion-sensor data.
This information is transmitted directly to the computer identified by the pairing code. We do not receive it, store it on a developer-operated server, use it for advertising, or share it with data brokers.
Camera and local network access
- Camera: the iOS and Android companion apps use the camera only when the user chooses to scan a pairing code. Camera frames are processed on the device and are not recorded, stored, or transmitted to us. The iOS App Clip is opened by the system from the camera’s scan result and does not use the camera itself.
- Local network: the companion apps and App Clip request network access to connect directly to the game on the user’s Wi-Fi network. Pairing and controller functions cannot work without this access.
Storage and retention
The companion apps and App Clip do not create a Drag Racing 3D account or maintain a developer-hosted cloud profile. Pairing credentials and controller state are held only for the active session. A pairing token expires after a short period, can be used only once, and is discarded when pairing ends. Controller preferences are stored locally on the phone. The game holds the controller name, optional driver profile, and connection state in memory while the controller is connected.
Game Center and Google Play Games
The full iOS app may use an existing Game Center session, and the full Android app may use Google Play Games when that service is configured. These platform services can receive achievements and leaderboard results that the user earns in the game. The App Clip connects as a Guest and does not use Game Center. We do not receive platform account credentials, operate the platform leaderboards, or send this information through our servers. Apple and Google independently process information for their game services under their own privacy policies.
The pairing website
The website contains no advertising, analytics scripts, tracking pixels, or account system. If an App Clip or pairing link opens in a browser, standard web requests may expose ordinary technical information to our hosting provider, such as an IP address, browser type, request time, and the URL path and query parameters. The single-use pairing token is kept in the URL fragment, which browsers do not send as part of an HTTP request.
Our hosting provider may process and retain server logs to operate, secure, and diagnose the website under its own terms and privacy policy. We do not use these logs to profile users or for advertising.
If you voluntarily submit the support form, we receive the name, email address, selected product and platform, message, and any device details you choose to provide. We use that information only to answer the request and diagnose the reported problem. Netlify, our hosting and form-processing provider, processes the submission on our behalf. We do not sell this information or use it for advertising.
Third parties
We do not sell personal information and do not integrate third-party advertising or analytics SDKs. Apple may independently process information through the App Store, App Clip, TestFlight, and Game Center; Google may independently process information through Google Play and Google Play Games. Those services are governed by Apple’s and Google’s privacy policies. The website links to these stores but does not receive their account or payment information. Netlify processes website requests and support submissions only as needed to host, secure, and operate the site.
Your choices
Camera, motion, and local network access can be denied or changed in the device’s Settings. The user can also stop processing immediately by disconnecting the controller, closing the App Clip, or deleting the app. Because we do not maintain user accounts or a developer-hosted database of controller sessions, there is no account data for us to retrieve or delete. Support messages are kept only as long as needed to answer the request, diagnose the issue, and meet legitimate legal or security requirements. You can use the support form to request deletion of a previous support message.
Security
Pairing uses a cryptographically random, short-lived, single-use token. Controller traffic stays on the local network and does not use a cloud relay. Users should connect only to pairing codes they generated and use a trusted local network.
Changes to this policy
We may update this policy if the app’s features or data practices change. The effective date at the top of this page identifies the latest version. Material changes will be reflected here before the related app version is released.
Contact
Privacy questions and support requests can be submitted through our support form.