Mirage is designed with privacy as a core principle. The app is intended to access and play media stored on servers located on your local network, such as Stash, DLNA servers, or SMB shares. Mirage does not require its own user accounts, does not require internet connectivity, and does not collect or transmit personal data.
This Privacy Policy further explains what information Mirage does and does not collect, and how your data is handled.
Information That Is Not Collected
Mirage does not collect, store, or transmit any of the following:
- Personal information
- Email addresses
- Media library contents
- Video viewing history
- Device identifiers
- Analytics data
- Advertising identifiers
- Usage tracking information
Mirage does not include or integrate with any advertising services, analytics frameworks, or tracking technologies.
Information That Is Collected
Mirage stores certain information locally on your device that is necessary for the app to function, including:
- Server addresses you have configured (e.g., IP address and port)
- Server connection settings you have provided (e.g., username or API credentials)
- App preferences (e.g., user-set options and remembered sort fields)
This information is never transmitted to the developer.
Media Content
Media files and metadata remain on your servers. Mirage only retrieves this information to display it and play media within the app. The developer has no access to your media library details or its contents.
Local Network Access
Mirage connects only to servers that you configure, typically on your local home network. These may include Stash servers, DLNA media servers, and SMB file servers. All browsing and playback occur directly between your device and your server. Mirage does not proxy, relay, or transmit data through any developer server or third-party server.
Internet Access
Mirage is designed to function without requiring Internet access. If the app communicates over the Internet at all, it is only in relation to an action you initiate with your explicit consent. For example, you may choose to transmit a crash report which would send limited diagnostic data to the developer.
Crash Reports (Optional)
If Mirage encounters an unexpected error, the app will log diagnostic details to a crash report stored on the device. You have the option to provide crash reports to the developer to assist in diagnosing and fixing problems, but only by taking explicit action to submit individual crash reports. Diagnostics are never automatically transmitted.
Crash reports may include technical details such as:
- App version
- Device model
- Operating system version
- Error messages
- Stack traces
Crash reports do not include information about your server, your media files, or your media library contents.
Changes to This Policy
This Privacy Policy may be updated from time to time. Updates will be reflected by a revised “last updated” date at the top of the page.
Contact
If you have questions about this Privacy Policy or Mirage, you may contact the developer at [email protected].