Audex is built around a simple principle: your media library and listening activity belong on your device, not on our servers. This policy explains, in plain language, what limited information Audex does handle, why, and the choices you have over it.
Audex is designed to minimize what ever leaves your device. The categories below cover everything we handle.
If you sign in with Google, we receive your name, email address, and account identifier from Google, solely to identify your account within the app. This is stored securely on your device.
Audio files, documents, playlists, listening progress, and app preferences are stored locally on your device. We do not upload, inspect, or have access to this content.
If you choose to connect a cloud storage account (such as Google Drive, Dropbox, OneDrive, or a self-hosted server) to import content, Audex accesses only what's needed to browse and retrieve the specific items you select. Any access credentials are stored securely on your device and are never sent to us.
Purchases are handled entirely by Google Play and confirmed directly on your device through Google's own Play Billing system. We never receive your payment card, billing address, or any other financial or purchase detail on any server we operate.
To recognize your free trial consistently across reinstalls and devices signed into the same Google account, our servers store a minimal record tied to that account: an account identifier and the date your trial first began. This record does not include whether or when you've purchased Audex — that's determined entirely on your own device, directly from Google Play, each time the app checks.
We also retain a second, separate value: a one-way cryptographic hash of your account identifier, which cannot be reversed to reveal who it belongs to. Its only purpose is recognizing that a given account has already used a trial, even after the record above has been deleted — without it, deleting and recreating that record would let a trial be reset indefinitely. This hash carries no information about you or your activity beyond that one yes/no fact, and nothing else about you or your activity is stored on our servers.
If you submit a bug report or feature request, we receive the message you write along with basic app and device information (app version, device model, Android version) to help us respond. You may optionally choose to include a screenshot and a short excerpt of on-device diagnostic logs — these are only ever sent if you actively opt in for that specific report, and you can review exactly what will be sent before it's submitted.
If Audex crashes on your phone, tablet, TV, or watch, a technical crash report is sent automatically so we can identify and fix the underlying bug. This report contains only a stack trace (which line of code failed and why) and basic app and device information (app version, device model, Android version). It never includes a screenshot, a copy of your on-device activity log, or the contents of your media library — on rare occasions, the stack trace itself may reference a local file or folder path if that's what the underlying error refers to, but it never includes what's inside that file. A crash on a paired Wear OS watch is relayed through your phone to reach us, since the watch has no direct internet connection of its own for this. Automatic crash reporting is on by default and can be turned off at any time in Settings on your phone or TV — turning it off on the phone also stops crash reports being sent on behalf of a paired watch.
We use the information described above only to:
We do not use your information for advertising, profiling, or any purpose beyond operating the features described in this policy.
Certain optional Audex features connect directly to services you choose and authorize yourself. When you use these, the corresponding provider's own privacy policy governs how they handle your data — Audex acts only as a conduit for the request you initiated, and in most cases the data involved never passes through our servers at all.
This includes cloud storage providers you connect (Google Drive, Dropbox, OneDrive, or a WebDAV/SMB server you configure), any self-hosted media server you point Audex at, and any API key you optionally supply yourself for an enhanced text-to-speech voice. Google Play Billing is likewise governed by Google's own privacy policy for payment processing.
Access credentials and sign-in tokens stored on your device are encrypted at rest. All network communication uses industry-standard encryption (HTTPS/TLS) in transit. Audex contains no advertising or analytics SDKs that could introduce additional data-collection surface beyond what is described in this policy.
No method of storage or transmission is 100% secure, and we cannot guarantee absolute security — but we design Audex to minimize what could ever be exposed in the first place, by keeping as little data as possible off your device.
Depending on where you live, you may have rights to access, correct, or delete your personal information. In Audex, you can exercise most of these directly:
To make any other request regarding your personal information, contact us at the email address in Section 11.
Audex is not directed at children under 13, and we do not knowingly collect personal information from children. If you believe a child has provided us with personal information, please contact us and we will take appropriate steps to remove it.
Audex is used by people around the world. Any information described in this policy that we process on our servers may be stored and processed in a country other than your own. Wherever it is processed, it remains subject to the protections described in this policy.
We may update this policy from time to time. Any changes will be reflected by an updated "Effective" date at the top of this page, and material changes will also be noted in the app's release notes.
Questions about this policy, or requests regarding your personal information, can be sent to:
↑ Back to top