1. Scope and who operates Libra
This Privacy Policy applies to the Libra Media Player iOS application, including later updates unless a replacement policy is provided, and this website. Libra Media Player is referred to in this policy as “Libra” and is provided by Seven, referred to as “we” or “us.”
Libra is an Apple-native media player for personal media libraries. Libra does not provide or host movies, television programs, or other media. You choose the servers and third-party services that the app contacts.
2. Information stored on your device
Libra stores information needed to remember your setup and provide playback. Depending on the features you use, this may include:
- Emby server profiles, server addresses, account identifiers, display names, selected routes, and library presentation settings.
- Emby access tokens and certain service credentials in Apple Keychain. Passwords used during sign-in are not retained by Libra.
- App preferences, search history, playback history, progress, Favorites, Watchlist, and Tracking state.
- Danmaku service addresses, matching preferences, and confirmed episode bindings that you configure.
- Metadata, artwork, interface caches, and optional reusable media bytes used to improve performance and playback continuity.
- Privacy-bounded diagnostic records, Apple MetricKit reports made available to the app, and diagnostic packages you explicitly create.
3. Optional iCloud synchronization
iCloud Sync is optional. When you enable it, Apple processes synchronized data through services associated with your Apple Account.
Depending on your settings, Libra can synchronize Emby profile configuration through your private iCloud key-value store, compatible Emby access tokens through iCloud Keychain, configured danmaku service profiles, and Libra-owned viewing, Favorite, Watchlist, and Tracking state through a private CloudKit database.
The personal-media CloudKit records exclude raw credentials, server endpoints, provider delivery records, downloads, media bytes, artwork caches, and diagnostic archives. Emby profile synchronization is separate and may include configured server routes and a synchronized Keychain token when you enable that profile for a device family.
Turning synchronization off stops synchronization on that device but does not itself erase retained local or cloud copies. Profile deletion, device-family targeting, app deletion, and the iCloud controls provided by Apple may affect which copies remain.
4. Services Libra contacts
Searching, loading descriptions or artwork, and matching danmaku may send search terms, media names or identifiers, episode numbers, language, and necessary network information to the relevant service. Queries routed through the Libra gateway are also processed there. Internet services typically receive your IP address and request timing.
- Your Emby servers: authentication, library browsing, metadata, images, playback information, media delivery, progress, and supported library actions.
- TMDB: discovery, metadata, artwork, people, collections, and related-media information. The default configuration can access TMDB through the Libra gateway; you may instead configure a compatible custom TMDB service.
- Trakt: schedule and episode-airing information. Connecting an account uses authorization credentials and account information, and reads or synchronizes viewing history, playback progress, Favorites, Watchlist, and tracking-related state according to enabled features. You may disable synchronization or disconnect; disconnecting does not automatically erase data already held by Trakt.
- Danmaku services: optional search, matching, and timed comments through the service address you configure.
- Apple services: App Attest, iCloud, CloudKit, iCloud Keychain, push-notification infrastructure, and TestFlight or App Store services where applicable.
- Infrastructure and security providers: delivery and protection of this website and the Libra gateway.
5. Libra gateway and App Attest
The default TMDB connection uses a controlled Libra gateway so that application credentials do not need to be exposed directly in the app. Apple App Attest helps the gateway determine whether a request comes from a genuine instance of Libra. The app sends an App Attest registration or assertion and receives a time-limited installation authorization token for supported gateway requests.
For TMDB queries, the gateway does not require your name, email address, Emby password, Emby access token, media files, or complete personal library. Online feedback is a separate flow described below. The infrastructure and security providers used by the website and gateway may process IP addresses, request timing, user-agent information, security signals, and bounded operational logs to deliver, secure, and troubleshoot requests.
6. Photos, files, and exports
Libra asks for permission to add to your Photos library only when a feature needs to save a captured video frame. Libra does not need permission to browse your full photo library for this purpose.
Personal-media import uses Apple’s system file picker. Libra validates and imports the selected archive and does not retain the selected import file as an app-owned copy. Export creates a fresh archive only when you invoke sharing. Diagnostic packages are also created and shared only when you request them.
Files or diagnostics you choose to share are handled by the destination you select and become subject to that destination’s privacy practices.
7. Diagnostics, analytics, and tracking
Libra does not use advertising SDKs or track you across apps or websites for advertising. This website does not set first-party analytics cookies or load third-party analytics scripts.
The app keeps limited diagnostics on your device. Normal logs exclude sensitive information such as credentials, full URLs, request bodies, and media content. Diagnostic packages are not automatically uploaded in the background.
When you actively submit online feedback, your description, any server or episode details you enter, optional contact email, device model, system and app versions, diagnostic package, and selected screenshots are uploaded to Libra support to investigate and respond. Libra and third-party providers of storage and support communications process your feedback and attachments. These services may process data outside your region. Review materials before submitting and remove passwords, tokens, and unrelated personal information.
You may instead choose email or system sharing; the recipient and email or sharing provider handle materials under their own practices. Online feedback, email, and export are separate submission methods.
8. Retention and your choices
Different records have different lifetimes. Caches may expire, be evicted by the operating system, or be cleared from Libra. Account profiles and personal-media state remain until changed or deleted because they are needed to preserve your choices. Some negative state, such as an explicit removal or “stop watching” decision, may be retained to prevent deleted items from reappearing.
Uninstalling the app should not be treated as deleting Keychain credentials or data held by iCloud or third parties. Removing a local feedback record does not delete previously submitted remote copies.
Pending feedback attachments remain locally for retry and are removed on the next feedback-record access after 14 days. Successful submission removes the local upload copy; record summaries may remain. Online feedback storage has a target retention period of 14 days; this does not mean materials used in support communications or email copies are deleted at the same time. For deletion of submitted materials, contact libraplayer@163.com with the feedback reference.
- You can remove configured services and Emby profiles from the app.
- You can clear supported caches without deleting your durable personal-media state.
- You can disable iCloud Sync; disabling alone does not erase existing synchronized data.
- You can delete Libra from your device and use Apple’s iCloud storage controls for data associated with your Apple Account.
9. Security
Libra separates credentials from ordinary preferences and caches, uses Apple Keychain for supported secrets, uses encrypted CloudKit fields for personal-media payloads, and limits diagnostic contents. No storage or transmission system can be guaranteed completely secure, especially when you connect to a server or service operated by someone else.
Libra supports user-managed Emby servers that may use local HTTP connections. A non-HTTPS connection is not protected by TLS. Use HTTPS and a trusted network whenever your server supports it.
10. Children and minors
Libra is not specifically designed for children. Minors should read this policy, configure services, and use the app with a parent or guardian, accessing only age-appropriate content they are authorized to use. Guardians should help select libraries and third-party services and discourage unnecessary personal details, such as names, schools, home addresses, and contact information, in feedback, screenshots, or attachments.
In mainland China, personal information of children under 14 receives special protection. Processing that requires guardian consent must take place only after that consent and applicable special protection requirements are satisfied; using the app does not itself establish guardian consent. Local requirements apply in other regions.
If you are a guardian and believe we have improperly handled a minor’s personal information, contact libraplayer@163.com with the relevant feature or feedback reference. We will verify the relationship and request only as necessary, promptly take appropriate steps such as correction, deletion, or stopping the processing, and respond as required by applicable rules. Do not send complete identity documents, passwords, or access tokens unsolicited.
11. Your rights, changes, and contact
Contact libraplayer@163.com to request access, a copy, correction, completion, or deletion of personal information we process, withdraw relevant consent, or ask for an explanation of our practices. Identify the data, feature, or feedback reference involved. We request only information needed to verify your request, never account passwords or access tokens.
We will handle and respond to requests promptly under applicable requirements. If we cannot act directly or must retain some data by law, we will explain why and the available next steps. Device-only information requires app or system controls; independently held third-party data may require a request to that service. Withdrawal does not affect earlier processing but may affect features that depend on it. Legal complaint and remedy channels remain available.
When features or data practices change, we will update this policy and its effective date. Material changes to purposes, methods, or categories of personal information will be communicated through appropriate means, such as a website notice or in-app message, and renewed consent obtained where required.