Effective date: October 11, 2026
This policy covers the PassPlayer PICO application and its associated product website. The developer uses the PassPlayer name; its PICO developer organization is named Ao. Privacy contact: contact@passplayer.space.
1. About the player
PassPlayer is a standalone player tool. It plays compatible media selected by users from their headset, configured SMB/WebDAV storage, compatible URLs or independent sources connected through custom interfaces. It does not supply video content, content subscriptions or an audiovisual service. Third parties independently provide and manage their content, accounts and access rights.
Core local, network-folder and compatible-URL playback does not require a PassPlayer account. Optional external sources may require their own authorization.
2. Data processed on your headset
Depending on your choices, the app stores file references and system file-access grants; network addresses, source configuration and connection credentials; URLs; history and playback positions; favorites, hidden items, tags and folders; language, playback and app-lock settings; thumbnails; and temporary media cache. These support the functions you request. Local and configured network media are not uploaded to a PassPlayer content server for core playback.
Connection and account credentials use the app's local secure storage. Other library state remains in the app's local storage. An app lock limits access through the app interface; it is not a guarantee that every media file or library record is encrypted.
3. Head/controller tracking and passthrough
The PICO app uses system-provided head and controller poses locally for viewing direction, pointing, selection and recentering. PassPlayer does not store or transmit those poses or tracking history.
Optional passthrough uses PICO's system-composited view. PassPlayer does not directly read, record, store or upload raw camera images. Video passthrough processing changes the selected video's pixels locally; it does not upload room images. PICO independently handles its platform features under its own policies.
4. Selected sources and optional account interfaces
Your headset connects to the source and associated account/authorization endpoints used for the interface you choose. A destination can receive your IP address, media and account requests, credentials you provide, pairing codes/session information, installation identifiers, and a device fingerprint derived from device/system identifiers. This enables connection, pairing, access control and session renewal.
The app can keep access/refresh credentials and local binding information for an optional account. An interface may use a browser-based third-party pairing flow, including Patreon. Such an account or content subscription belongs to the external service. The player and its interface do not grant content rights. We do not describe optional account interfaces as core playback requirements.
When a selected online provider creates a playback session and supports playback reports, the app can send first-frame/startup timing, cumulative time actually played, periodic player state, position, rebuffer totals, finite error codes, the actual MP4/PPV transport, and an end summary to that provider's authenticated endpoint. Device metadata can include model, platform, OS version, package name and app version. These reports support viewing records and playback reliability; they do not include media bytes, passwords, authorization tokens or private keys. Local files and offline playback without an online business session do not generate these online viewing events. Reporting is asynchronous and failure does not stop playback. The selected provider handles these records under its own data policy.
5. Authorized encrypted playback
For compatible encrypted sources, the app creates keys in the Android Keystore and uses them locally for signing or key unwrapping. The player does not export the private keys. Public keys, signed proofs, device/account/session identifiers, requested asset identifiers and authorization requests may be sent to the associated authorization endpoint. That endpoint and the media host receive the requests needed for authorized playback.
Device key storage does not, by itself, assert independently verified hardware attestation. Encrypted playback does not mean PassPlayer provides, sells or licenses the selected content. Local encrypted cache and temporary playback data can remain on the headset until cache cleanup or system data removal.
6. Storage locations and retention
Local settings, credentials, library state, thumbnails, cache and app keys are stored on your headset in its application storage/Keystore. Local records generally remain until you remove them through available app controls, clear app data or uninstall. Temporary or expired playback authorization is managed by its validity period; retained cache does not itself grant access.
Source-side account, authorization, access logs and media remain with the selected service and its infrastructure. Its storage region and retention period depend on that service and may be outside mainland China; the player does not determine those locations. Consult the specific service's policy before connecting. The product website is delivered by Render's global hosting/CDN infrastructure, whose technical request logs are handled as part of hosting and security operations.
7. Your controls and deletion
Use Clear Cache to remove generated thumbnails and temporary playback cache. It does not necessarily remove settings, history, favorites, source configuration or account bindings. Hiding an item does not delete the original media.
Removing an optional account binding removes that local binding and its locally stored access/refresh credentials; it does not delete the third-party account, cancel a subscription, erase the provider's server records or necessarily rotate installation keys. Contact the source operator for its account/data deletion process. For remaining local app data, use the PICO system's app-data removal or uninstall controls. Removing the app's data or keys can require reconfiguration and fresh authorization.
8. PICO services and the website
PICO may independently process device, store, operating-system, backup and diagnostic information. Platform backups depend on your device/account settings. PassPlayer does not control those platform practices.
The product website publishes downloads, product/support information and legal documents. It has no advertising trackers or behavioral profiling. It stores your website language choice in browser local storage; its infrastructure can process IP addresses, request times and browser/network/security information to deliver and protect pages. If you email support, we receive the address and information you choose to send and use them to handle the request. Do not send passwords, private keys or unnecessary private media.
9. Sharing and age requirements
PassPlayer does not sell personal information or your media library/viewing history to advertisers. Network exchanges with a chosen source and its authorization endpoints follow that service's practices; website delivery uses its hosting infrastructure. Information may also be handled where required by applicable law or to respond to your request.
The player does not knowingly operate a children's account service. Follow the age rules of your PICO device and any external service. Your chosen media remains subject to its own access and age restrictions.
10. Contact and policy changes
For questions, access/correction/deletion requests about information handled directly for PassPlayer, contact contact@passplayer.space. For data held by an independent source, contact that source. We will assess requests in light of the information actually held and applicable requirements.
Updates will appear on this page with an updated effective date. 简体中文 · Meta Quest privacy information.