Immivio1. Who this policy covers
This policy covers the official Immivio application and website maintained independently by EthanKang. “We” means the project maintainer, not the operating-system vendor, headset platform, website host, or a media service you choose to use.
2. We do not collect user data
We do not collect personal data through the application or this website. We do not operate a user-data collection backend, require an Immivio account, include advertising or behavioral-analytics SDKs, sell user data, or build advertising profiles.
Immivio does not automatically upload your media, credentials, playback history, device identifiers, interaction or tracking input, or diagnostic reports to the maintainer.
3. Information that stays on your device
The application processes information locally to provide the features you use:
- Selected videos, subtitles and associated audio, plus directory listings and file operations you request.
- Preferences, playback position, history, bookmarks, source connections, credentials or authorization tokens, and thumbnail caches.
- Head, controller and hand input for local XR interaction, and local diagnostic information for troubleshooting.
These local operations are not data collection by the maintainer. System permissions are used for the corresponding device features. You can revoke permissions in system settings; the affected features may then be unavailable.
4. Connections you choose
Network features communicate with the sources or services needed to perform your request. Their operators may receive your IP address, authentication information and the request details. This is separate from collection by the Immivio maintainer.
- Media sources: SMB, DLNA and configured media servers receive requests to discover devices, authenticate, browse, fetch covers or subtitles, and play media. Plex authorization communicates with Plex.
- Server playback history: with playback history enabled, supported Emby/Jellyfin connections can send playback start, progress and stop information to your selected server. Disabling history stops new playback reports; already dispatched requests cannot be recalled.
- Updates and external pages: in web builds, explicitly checking for updates contacts GitHub and includes the app version in the request’s User-Agent. Opening a release page or downloading a build uses GitHub or your browser. Update checks are not initiated automatically at app startup.
Use sources you trust and review their privacy policies. Removing a connection or clearing local app data does not delete records already held by a media server, Plex, GitHub or the headset platform.
5. Website hosting and browser storage
The website does not include advertising, visitor analytics, tracking pixels, or
tracking cookies set by our code. Its theme preference is stored only in your
browser’s local storage under immivio-theme; our website code does not
transmit that value.
The site is hosted on GitHub Pages. GitHub states that it logs visitors’ IP addresses for security purposes. Hosting and download requests are governed by GitHub’s own practices, so this policy does not promise that the hosting provider processes no data. See GitHub Pages data collection and the GitHub Privacy Statement.
6. Your controls and optional feedback
You can manage playback history and caches in the app, remove saved connections, revoke permissions, or clear app data or uninstall through your device settings. Operating-system backup behavior and third-party account records are controlled by those providers.
Diagnostic logs stay local unless you choose to export or share them. Exporting a log saves a file on your device; it does not automatically send it to us.
If you voluntarily submit an issue, comment or diagnostic attachment on GitHub Issues, the maintainer can read the content you submit, and GitHub processes it under its own policy. This is optional user-submitted communication, not background collection. Public issues are public: do not post passwords, tokens, private media or other sensitive information. Use GitHub’s controls for content you submit there.
7. Changes and contact
Changes to this policy will be published on this page with an updated date. A material change to data practices must be described before it takes effect; an edit to this page does not by itself authorize new collection.
For privacy questions, contact the maintainer through the project’s issue tracker with a non-sensitive description. Do not include private information in a public request. This policy applies equally to all users, including younger users; we do not request age information.