Privacy information
Apexra is an independently developed, free, single-player browser racing game. You do not need an account. The game has no payment, advertising service, public leaderboard, chat or player-upload feature.
Information used on your device
The game processes your keyboard or gamepad input, race state and performance in your browser to run the game. It saves Career progress, unlocked ranks, race history and Endless Career VR in localStorage under apexgp.progress.v4. Older saves (apexgp.progress.v3, apexgp.career.v1 and apexgp.ranked.v1) can remain for migration.
Race choices, camera and resolution preferences use apexgp.settings.v1. Automatic graphics adjustment reads browser and device capabilities, including the GPU renderer, CPU-core count, approximate memory, screen size and frame timing. It can save a graphics tier, GPU renderer name and failed tiers under apexgp.gfx.v1. These are used for graphics compatibility and performance; the game does not create a tracking identifier from them.
These saves stay in this browser profile on this device. The game code does not upload them or synchronise them across devices. Local race identifiers and timestamps prevent duplicate results and preserve Career state; they are not sent as visitor identifiers. Saves have no built-in expiry. They remain until replaced, cleared or removed by your browser. Private browsing, storage limits or browser cleanup may remove them.
Hosting and network information
Vercel hosts and delivers Apexra. Loading the site sends connection and request information to the hosting infrastructure, including your IP address, requested URL, browser request headers and request time. This technical information can be personal data. It is used to deliver and protect the site and diagnose delivery problems. Do not put personal information in the website address or query string.
The audited application has no analytics, Speed Insights, tracking pixel or remote error-reporting integration. Its fonts and Three.js engine are served from this site. Ordinary play does not request assets from Google Fonts or public JavaScript CDNs. Your browser may keep downloaded files in its ordinary HTTP cache; the game does not install a service worker or maintain a separate application cache.
Vercel may process information outside Singapore and use service providers under its arrangements. See Vercel’s Privacy Notice. Hosting logs, retention and international processing depend on Vercel’s services and the deployment configuration. Provider retention and deletion are not controlled by the local-save button below.
Cookies, sharing and purposes
The audited game code does not set cookies, use sessionStorage or IndexedDB, or include non-essential tracking. Browser saves support gameplay and preferences. Hosting requests support delivery and security. We do not sell game saves or send them to advertising services. External source and license links contact the linked site only when you follow them; that site’s privacy terms apply.
Hosting-provider behavior can change with deployment settings. This policy does not promise that every provider request is anonymous or that no hosting or security cookie can ever be used. We will review the policy and any consent requirements before introducing analytics or other new processing.
Your choices and rights
You can remove local saves using the control below or your browser’s settings for this site. Close other Apexra game tabs first, as a running game can write its in-memory save back. Clearing site data can permanently remove Career progress, unlocked ranks, race history, VR and preferences. It does not clear copies in another browser, device or old site address.
The developer has not yet published a public privacy-contact channel. The game has no account-based save recovery. You may raise Singapore data-protection concerns with the PDPC or an applicable local authority.
Children and policy changes
The game does not ask for a date of birth or run age verification. A parent or guardian can help younger players understand browser saves and clear them.
We will post changes here with a new effective date and explain significant changes before new processing begins.