Privacy. That’s Voxtrona.

Everything stays on your device.

Voxtrona is local‑first. Every playlist you build, every track you favourite, every console preset you dial in and every minute of listening history is written to your own storage and read back from it.

There is no Voxtrona account, no user database and no sync service, so there is nothing of yours for us to hold, lose or be asked to hand over.

No trackers. No telemetry.

The app ships without analytics SDKs, advertising identifiers, attribution libraries or a crash-reporting vendor such as Sentry. Nothing measures what you play, how long you play it or where you are while you do.

This is a build-time guarantee rather than a setting you have to find and switch off — the code to do that reporting simply is not in the app.

This website is the one exception, and a small one. It uses Vercel Web Analytics for anonymous page‑view counts. It sets no cookies, does not fingerprint your browser, and builds no profile of you across sites. It is entirely separate from the app, which still ships with no analytics SDK at all.

Crash reports, and nothing else.

If you installed from Google Play, standard anonymous crash logs and performance statistics are aggregated by the Google Play Console, the same as for any app on the store. We use them to find and fix stability problems.

Those reports carry stack traces and device model information. They do not carry your listening history, your playlists or any account credentials.

Your accounts, only when you ask.

Signing in to YouTube or YouTube Music is optional and off until you do it. If you additionally turn on history upload, Voxtrona talks directly to YouTube’s API to record what you played against your own Google account — never through us.

The same applies to Spotify lyrics and canvas, and to Discord rich presence. Each is opt‑in, each is disabled by default, and each can be revoked at any time without affecting the rest of the app.

Processed on your hardware.

Audio decoding, the ten‑band console, spatial rendering, head tracking and every visual effect run on your device’s own silicon.

Head tracking uses the front camera when you switch it on. Those frames are read and discarded on device to position the soundstage; no image is stored, and none leaves the phone.

Changes, and how to reach us.

If this policy changes, the revised version appears on this page with a new date below. Material changes will also be posted to Announcements.

Questions about how any of this works are welcome — reach us through Support.

Last updated 7 July 2026