Privacy and support · Edwards Research · 14 November 2026
Contact android@edwardsresearch.au for support, privacy questions or deletion requests.
QRX Controller connects your phone to supported QRX games running on another screen. The native app supplies motion orientation, vibration feedback and a foreground keep-awake option. It opens registered controller pages, not arbitrary websites.
Motion is used when you start controller motion and stops when the app backgrounds or the controller session is stopped. Native vibration has a bounded renewable lease and stops on backgrounding. The app has internet and vibration access; it does not request microphone, contacts, camera or location permission. The built-in Hardware demo works without an account or TV.
Supported controller pages communicate with their game display and AWS-hosted backend over encrypted network connections. WebRTC uses Google’s STUN service for peer discovery, which receives network connection information; a secure service relay is used when a direct connection is unavailable. Pairing links and private session/profile capabilities authorize those connections. Phone orientation is transmitted for live control; it is not saved as a raw sensor-history feed.
Turn and Burn currently saves game progress, player names and settings, records and ghost routes. Its development playtest records first-party visit, pairing, connection and play events with random browser/session identifiers and coarse device/browser classes. Analytics events are retained for 90 days. Private development run archives include ship paths and attitude, applied controls, settings, outcomes, display-browser user agent and viewport, and session/profile references. Saved profiles and run archives currently have no automatic expiry. Eligible competitive results and pilot names appear on global leaderboards with a stable pseudonymous player identifier; other players can view sanitized gameplay replays of eligible records. Race participants can review their shared race, and private review links grant access to the selected replay. Do not use a real name or other personal information as a pilot name. The current release has no child-specific moderation or parental-consent flow. Server and connection service logs are retained for seven days; technical rate-limit records last two minutes. The game presents its own playtest data information.
Controller pages keep cookies, private game credentials and saved state in the app's WebView storage. This storage is separate from your phone browser. Clearing cached bundles does not clear your game profile. Uninstalling or clearing app data removes local storage and may lose access to a guest profile. The app has no advertising SDK and does not sell data or share it for advertising. Connection and hosting providers process data to operate the service; pairing sends control information to your selected display.
This version is an early test release. Child-inclusive audience settings and hosted-game data handling are being assessed before wider distribution. The app does not ask for a date of birth. A future child-inclusive release must meet the relevant requirements across the native shell and supported hosted games.
You can stop motion, vibration and keep-awake from the Hardware demo, background the app, or disconnect the controller. Use the game's export/backup options to preserve progress. Contact support to request data deletion or discuss which records can be identified. Do not send pairing secrets or credentials by email. A complete self-service deletion flow is not available in this early internal release; clearing local data alone does not delete server-held game records.