Privacy Policy

01 · Local playback and stored information

To open media, remember settings and resume playback, the app processes media files, subtitles, file paths or access bookmarks, media source addresses and account names, playback positions, and audio and subtitle preferences on your device. When history is enabled, it also saves viewing history and recent search terms.

Playback may also store supporting data locally, such as temporary subtitle files and disc title selection caches. The macOS version may register recently opened files with the system. These records are managed separately from the app’s viewing history.

Saved passwords or service tokens are stored in encrypted local files. Both credentials and the local key are kept in the app’s data directory. Local storage does not mean that this information is excluded from system backups, device migration or file provider services you use.

02 · Connecting to servers you select

When you connect to SMB, WebDAV, NFS, Fn Media, Jellyfin, Emby or Plex, the app sends connection, authentication and request information required by that protocol to the relevant server. This can include an account name, password or token, file or media identifiers, directory requests and search queries. The server also receives network information needed for the connection, such as your IP address. NFS access control depends on the server’s configuration.

Media service connections report playback start, progress and end events and audio or subtitle choices according to the service’s capabilities. Actions you take, such as favorites or marking content watched, may also update the corresponding service account. Jellyfin, Emby and Plex requests include a client identifier and app protocol information. Clearing local history or removing a media source does not automatically delete records held by the server.

Artwork, descriptions and other media information are provided by the connected media service. When you authorize a Plex login, the app also contacts Plex’s official authorization service and your browser opens a Plex authorization page. Your chosen file provider, media server and Plex apply their own rules to their services.

The app connects to media services at the addresses you configure. We do not provide media servers, media proxies or relay services to users. Transport protection depends on the protocol and server configuration. You should not assume that all content is encrypted when using connections such as HTTP or NFS.

03 · Apple services and purchases

In versions where purchasing is supported and enabled, purchases, purchase restoration and subscription management use Apple’s StoreKit and App Store. The app uses transaction verification results and entitlement status returned by Apple to determine access to features. Payment information is handled through Apple’s purchase flow. Availability depends on the version you use.

Apple handles data for the App Store, system diagnostics and its other services under its own privacy rules. When you use a TestFlight beta, Apple automatically collects crash logs and usage information and shares them with the application provider. Examples include device model and identifier, system and app versions, and installation and session counts. Feedback and screenshots you submit are also shared. Whether the developer sees your name and email depends on the invitation and feedback method. See Apple’s TestFlight privacy notice for details.

04 · Diagnostics and contacting support

The app produces local error and diagnostic information to help investigate playback or connection failures. Some Mac features let you copy diagnostic information. Copying to the clipboard does not send it to the developer; a recipient you subsequently choose receives whatever you send.

If you contact liuyuhang091@gmail.com, we receive your email address, message and any logs or screenshots you choose to attach, to reply, troubleshoot and handle privacy requests. Email is processed by the mail services used. Please do not send passwords, tokens or unnecessary private media content.

The app does not integrate advertising, behavioral analytics or a separate third-party automatic crash-reporting service, and we do not provide a separate backend for app log uploads. This does not exclude the processing described in this policy by Apple/TestFlight, media servers, support email and website services.

05 · This website

www.avoplayer.cn uses Cloudflare to host static pages. To deliver pages and maintain service security, Cloudflare processes network request information, such as IP addresses, requested addresses, times and request headers sent by your browser. Processing is governed by Cloudflare’s relevant policies and the actual service configuration.

The website’s pages contain no third-party analytics scripts, advertising, remote fonts, forms or tracking cookies, and do not use browser storage to remember language. Language switching uses ordinary page links. Cloudflare’s infrastructure processing of request information is separate from the pages not setting tracking cookies.

The support email link opens your email app. We receive a message only if you choose to send it.

06 · Retention, deletion and your choices

You can manage media sources, clear in-app viewing history and manage recent search terms in the app. Turning history off stops saving new local viewing history; clear existing viewing history separately if you want to remove it. Credentials for a media source are deleted when that source is removed. Manage data in system backups, on other devices and on third-party servers through those services. Clearing in-app viewing history does not clear all playback caches or the macOS system’s recent items.

Support email, troubleshooting materials, and crash reports, usage information and feedback made available to us by Apple/TestFlight are accessed only by the operator for support and fault investigation and improvement. We do not proactively export raw TestFlight data. Troubleshooting attachments we store are deleted after the issue is resolved. Support email is retained for 90 days after the request is closed, then deleted, unless retention is required by applicable law.

We handle information within Apple’s platform through the access and management features it provides. When information is no longer needed for troubleshooting, or we receive a deletion request, we delete copies we hold and control and address platform records through available deletion or request channels. Apple manages the retention and deletion of information it holds, and we cannot guarantee deletion of all its copies. Cloudflare, email services and media services you select also separately manage the data they hold.

To request access, correction or deletion of personal information we hold, contact the email below. We will handle requests according to their nature and applicable rules and may ask for information needed to verify a request.

07 · Changes and contact

We will update this page and its effective date when our data practices change. Where applicable rules require additional notice or choices, we will handle them accordingly.

Privacy and support: liuyuhang091@gmail.com.