Privacy Policy — AIX Player
Last updated: 26 August 2026
AIX Player is a video player for Windows, published by Ace Thought Technologies, which operates the AixApps brand. This policy describes exactly what the app does and does not do with information.
The short version: AIX Player has no account, shows no advertising, and does not record what you watch. Your videos and your library stay on your device. Anonymous diagnostics are off until you say yes where the law asks first, and on elsewhere until you switch them off in Settings; either way this page describes in detail what they contain.
1. There is no AIX Apps account
There is no sign-up and no sign-in. We do not ask for your name, email address, phone number or date of birth, and we hold no account or profile for you.
Two other companies’ accounts may be involved, and neither is ours:
- Microsoft account — if you buy the optional upgrade. The purchase happens entirely in the Microsoft Store, under Microsoft’s terms.
- Roku account — if you cast to a Roku. Roku requires our receiver channel to be added from your Roku account, so that step takes place on Roku’s website, under Roku’s terms.
2. Your videos and your library stay on your device
AIX Player reads video files from folders you choose. To build your library it stores an index on your own PC: file names and locations, durations, resolutions, thumbnail images, playlists, favourites, and the position you stopped at in each file.
That index is never uploaded. We have no way to read it. It lives in the app’s storage on your PC and is removed when you uninstall the app.
3. Diagnostics are optional, and you are always in control
Whether AIX Player asks before sending diagnostics depends on the country or region set on your device.
In regions whose law requires opt-in consent — the European Union and wider European Economic Area, the United Kingdom, Switzerland, South Korea, China, Brazil and Russia — the first run asks, once, whether to send diagnostics. If you do not say yes, nothing is ever sent.
Everywhere else, anonymous diagnostics start enabled, so crashes and casting failures can be found and fixed — and you can switch them off at any time. If the app cannot determine your region, it asks; it never assumes.
In every region the control is the same: Settings → About → Send anonymous diagnostics. The setting is re-read every single time, so switching it off takes effect immediately. Your region is read from your device’s own country setting; the app never uses your network location to decide this.
While diagnostics are on — because you said yes, or because your region starts enabled — the app sends technical reports to Microsoft Azure Application Insights, a service operated by Microsoft.
3.1 What is sent
There are two kinds of report. Both are described here because both are sent.
Crash and error reports — when something goes wrong: the error type, its message, and the technical stack trace.
Usage events — a small set of named events that tell us whether core features work. They are not behavioural tracking and are not used for advertising or profiling. They are:
| Event | What it carries |
|---|---|
| Graphics hardware detected | Adapter model, generation, video memory, shared memory, whether it is integrated or discrete, and the graphics driver version |
| Playback failed | The failure reason, the player engine’s own reason code, the video codec, the file extension, and whether the source was a network stream |
| Casting outcomes | Which casting technology was used (Chromecast, DLNA, Roku, and so on) and what happened: connected or not, the pairing outcome, a start that failed, a wait that timed out, a conversion that faulted and how far it had got, a remote command (play, pause, seek, volume) that failed, or a queue the app refused as invalid |
| Purchase attempted | The product identifier, the outcome reported by the Microsoft Store, and the reason for a failure; also that the Store page was opened, and that the app asked you to rate it |
| Library maintenance | Counts only: how many folders were scanned, how many stale or duplicate library rows were pruned or merged, that a file could not be analysed or thumbnailed (its extension and the attempt count), and that the library database could not be opened (the error type) |
| Download or network failure | For a download that failed: the URL scheme (such as https), the kind of address (a category, not the address itself) and the reason; for a network operation that timed out: which operation |
Events are sent when they happen, with the values listed and nothing else. A category such as “the kind of address” is a fixed label the app assigns; the address, file name or path is never included.
Every report also carries: which part of the app it came from, the app version, whether it is a Debug or Release build, whether the app was shutting down, and a random identifier generated fresh each time the app starts. That identifier groups the reports from a single session and cannot link one session to another.
3.2 What is removed, and the limits of that
Error messages are automatically redacted before sending. Email addresses, and anything that looks like a password, token, key or secret, are replaced.
File paths and web addresses are reduced rather than deleted, and we want to be precise about it:
- A file path becomes its file extension plus a short one-way hash of the file name. The folder structure and the readable name are gone. However, the hash for a given file name is always the same, so in principle the same file name can be recognised across reports — even though the session identifier changes.
- A web address keeps its scheme and its host (for example
https://example.com); the rest of the address is reduced to an extension and the same kind of hash.
One limitation worth stating plainly: the redaction above is applied to error messages. The properties attached to the usage events in the table above are sent as the app composes them, and are not passed through that same filter. Those properties are the fixed, technical values listed in the table — they are not free text and are not drawn from your file names or your library — but they are not additionally filtered.
3.3 What is never sent
- The contents of your video files
- What you watched, when, or for how long
- Your library, playlists, favourites or playback positions
- Your name, email address or contact details
- Your location, or any advertising identifier
- Any identifier that persists between sessions
4. Casting stays on your network — with one honest exception
When you cast a video to a TV, the video itself never leaves your local network. AIX Player starts a temporary web server on your PC and your TV fetches the file directly from your PC. Your video is not uploaded to us or to anyone else, and it does not pass through any server we operate.
The exception is set-up, not playback. Getting some devices ready can involve their manufacturer:
- Roku requires our receiver channel, added from your Roku account on Roku’s website.
- Chromecast devices load their receiver through Google’s infrastructure.
- Other TVs may ask for a one-time pairing step.
Where a TV gives the app a pairing code or token, it is stored on your PC only and is never sent to us. Your TV is made by another company, with its own privacy policy governing what that TV does.
5. Where diagnostics are stored, and for how long
Diagnostic reports, when enabled, are stored in Microsoft Azure Application Insights, processed in the United States, and retained for no more than 90 days, after which they are deleted automatically.
6. Purchases
The optional upgrade is sold and processed entirely by the Microsoft Store, under Microsoft’s terms and privacy policy. We never see or receive your card number, billing address, or any other payment detail. The app only asks Windows whether a purchase is currently active.
7. No advertising, no third-party tracking
AIX Player contains no advertising in any version, free or paid. It contains no advertising identifiers, no social-media trackers, no marketing pixels, and no third-party analytics or attribution products. We do not sell or share information about you, and there is no profile of you to sell.
8. Features not included in this version
Some capabilities exist in the code but are switched off in this release and cannot be reached: browsing local network (SMB) shares, connecting to media servers, and linking cloud-storage accounts (OneDrive, Google Drive, Dropbox). Because they are disabled they collect nothing and connect to nothing, and no cloud-account credentials are handled at all. If a future version enables them, this page will be updated before that version ships.
9. Children
AIX Player is a general-purpose media player and is not directed at children. We do not knowingly collect personal information from anyone, including children.
10. Your choices
- Turn diagnostics off or on at any time in Settings → About. It takes effect immediately.
- Delete everything by uninstalling AIX Player. That removes the library index, thumbnails, playlists, favourites, playback positions and any saved TV pairing codes from your PC.
- Ask us anything using the address below.
Because the app holds no account and no personal data, there is normally nothing for us to look up, export or erase on request. If you have sent diagnostics and want them removed, contact us with the approximate date and time and we will do what we reasonably can — but the reports are anonymous by design and are not linked to you, so we may be unable to identify which were yours.
Depending on where you live you may have rights under laws such as the GDPR or the CCPA. We do not sell personal information, and we have none to sell.
11. Changes to this policy
If this policy changes we will update the date at the top and publish the new version here. If a change materially affects what is collected, we will say so plainly rather than quietly amending the text.
12. Contact
Questions about this policy, or about privacy in AIX Player:
support@aixapps.net
AixApps