Drag Racing 3D

Privacy Policy

Effective July 22, 2026

Short version: the Drag Racing 3D companion app and App Clip do not create accounts, show ads, track you, or send analytics to us. Controller data travels directly between your iPhone and your computer on the local network. It does not pass through our servers.

Scope

This Privacy Policy applies to the Drag Racing 3D companion iOS app, its App Clip, and the pairing website at dragracing.ycydev.org. The companion app turns an iPhone into a controller for a copy of Drag Racing 3D running on the user’s own computer.

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 name assigned to the iPhone is sent to the user’s computer so the game can identify the connected controller.
Controller input: steering, throttle, brake, gear, camera, and recovery commands are sent to the game while connected.

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 full app uses 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 App Clip does not use the camera.
Local network: the app and App Clip request local 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 app and App Clip do not create an account or maintain a cloud user 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. The computer holds the controller name and connection state in memory only while the controller is connected.

The pairing website

The website contains no advertising, analytics scripts, tracking pixels, or account system. If an App Clip invocation 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, message, and any device details you choose to provide. We use that information only to answer the request and diagnose the reported problem. Our hosting provider processes the form 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 when it distributes the app, App Clip, or TestFlight build; that processing is governed by Apple’s privacy policy. The website’s infrastructure provider processes requests only as needed to host and protect the site.

Your choices

Camera and local network access can be denied or changed in iOS 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.