Privacy Policy

1. About this notice

OpenPlayer is a free TV media player and device-pairing service operated from Sweden. It does not sell subscriptions, show advertising, provide media sources, or host, proxy, or distribute television channels, films, series, or other media.

This notice explains how OpenPlayer processes personal data when you use the TV application, pairing portal, website, feedback tools, or support. It applies to OpenPlayer's own services. A media provider you independently configure has its own responsibility for its service and data processing.

2. Controller and contact

Controller: OpenPlayer, operated from Sweden.

For privacy questions, access or deletion requests, and other data-protection matters, use the contact address shown below. The reveal control protects the address from automated spam.

Privacy and data requests

3. Data processed by OpenPlayer

Device and pairing data

OpenPlayer processes a randomly generated Device ID, an authentication secret, pairing code, connection status, timestamps, application version, platform, TV model, firmware or operating-system version, and available web-engine information. Samsung Tizen devices may provide a DUID and Android TV devices may provide ANDROID_ID. These hardware identifiers are used only for service security and device-level abuse blocking.

Provider credentials

Your provider username, password, or playlist URL is encrypted on your phone for your TV before it is sent. The server relays the encrypted envelope only while the TV is online and does not store or queue it. The private decryption key remains on the TV, so OpenPlayer cannot read the credentials. After pairing, playback traffic goes directly between your TV and the provider you selected.

Diagnostics

Diagnostic logs are collected only when an administrator enables diagnostics for the device and you approve sharing on the TV. Logs can include error details, performance measurements, player events, device context, and application behaviour. The application removes known credentials, tokens, PIN values, and provider secrets before upload.

Support and feedback

If you contact support through the website, OpenPlayer processes the name, email address, Device ID, subject, message, replies, and status information you provide. If you use Telegram support, OpenPlayer also receives and stores your Telegram chat ID, display name or username, messages, selected support category, and any Device ID you provide. Telegram separately processes your use of its service under its own privacy policy.

Feedback can include your rating, written text, selected area, application version, platform, device model, Device ID, and the question shown to you. Public website feedback is reviewed before publication. Pairing and in-app answers are private and visible only to OpenPlayer administrators. A protected one-way token is used to limit repeated voting on public feedback; raw IP addresses are not stored with votes.

The public feedback form also lets you provide an optional contact email if you want OpenPlayer to follow up about that specific submission. Providing an email is not required to submit feedback. The email and consent record are encrypted at rest, are never published on the community board or returned by the public feedback API, and are available only to authenticated OpenPlayer administrators.

Website and security data

When you connect, OpenPlayer, its hosting infrastructure, and Cloudflare process technical connection data such as IP address, request time, requested path, user agent, security signals, and response status. The OpenPlayer application database does not store raw visitor IP addresses with device, support, feedback, or voting records. Temporary web-server, hosting, and security logs may contain IP addresses for operational security.

4. Purposes and legal bases

Provide pairing and device connectivity: Device and connection data is processed to provide the service you request and perform these Terms, under Article 6(1)(b) GDPR.
Protect the service: Connection data, authentication data, rate limits, and hardware blocks are processed for the legitimate interests of preventing fraud, brute force, attacks, and service disruption, under Article 6(1)(f) GDPR.
Provide requested support: Contact details, messages, Device ID, and replies are processed to answer and manage your request, under Article 6(1)(b) GDPR. General enquiries not connected to a service request are handled under the legitimate interest in answering correspondence, Article 6(1)(f).
Optional diagnostics: Diagnostic logs are processed with your consent under Article 6(1)(a) GDPR. You can withdraw consent in TV Settings at any time.
Improve OpenPlayer: Feedback, compatibility metadata, and aggregate service statistics are processed for the legitimate interest of finding problems and improving a free service, under Article 6(1)(f) GDPR.
Optional feedback follow-up: A feedback contact email is processed only when you actively consent to being contacted about that submission, under Article 6(1)(a) GDPR. The email is not used for advertising or unrelated messages. You can withdraw consent at any time through the privacy contact method above without affecting processing that was lawful before withdrawal.
Optional web analytics: Non-essential analytics are processed only after consent under Article 6(1)(a) GDPR. A supported Do Not Track or Global Privacy Control browser signal takes priority over an earlier analytics choice while that signal is present.
Legal compliance and claims: Data may be processed where required by law under Article 6(1)(c), or where necessary to establish, exercise, or defend legal claims under Article 6(1)(f) GDPR.

Where processing is based on legitimate interests, OpenPlayer limits the data and retention to what is reasonably necessary. You may object as described below.

5. Data OpenPlayer does not collect

OpenPlayer does not provide or store media libraries, streams, channels, films, or programme history.
OpenPlayer does not record what you watch, when you watch it, or your playback history on its servers.
OpenPlayer cannot decrypt provider credentials relayed during pairing.
OpenPlayer does not sell personal data or use it for targeted advertising.
The TV app does not contain an advertising SDK or behavioural tracking SDK.

6. Local data on your TV

The TV application uses device storage to keep its Device ID and secret, provider configuration, settings, PIN configuration, favourites, viewing progress, recently watched items, and other preferences. Provider credentials and viewing preferences remain on the TV and are not copied into OpenPlayer's server database. Clearing the app data or uninstalling the app normally removes this local data, subject to the TV operating system's behaviour.

7. Recipients and service providers

Access is limited to OpenPlayer administrators who need it for operation, security, or support. OpenPlayer may also use:

Cloudflare: Content delivery, TLS, DDoS protection, bot detection, Turnstile, and optional aggregate web analytics. Cloudflare may process IP address, device and browser data, and security signals. See the Cloudflare Privacy Policy and Cloudflare Customer DPA.
Hosting and infrastructure providers: Server, database, network, backup, and security services needed to operate OpenPlayer. These providers process data only to provide infrastructure and protect the service.
Telegram: Only when you choose Telegram support. Telegram receives messages and account information involved in that conversation. See the Telegram Privacy Policy.

OpenPlayer does not disclose provider credentials or viewing history to these services. Personal data may also be disclosed where required by Swedish or EU law, or where necessary to protect legal rights.

8. International transfers

OpenPlayer is operated from Sweden, but Cloudflare, Telegram, or infrastructure providers may process data in other countries. Where GDPR requires safeguards for a transfer outside the EEA, the transfer must rely on an adequacy decision, approved contractual safeguards such as the European Commission's standard contractual clauses, or another lawful transfer mechanism. Details relevant to each provider are available in its linked privacy information.

9. Retention

Device records: Kept until you unpair, the record is administratively deleted, or it is no longer needed for pairing and security. There is currently no fixed automatic deletion period for an ordinary connected device record.
Provider credentials: Not stored or queued by the OpenPlayer server.
Hardware blocks: Kept until the block is reviewed and removed. You can ask for review if you believe a block is incorrect.
Diagnostic logs: Normally deleted after 7 days. Diagnostic collection normally switches off automatically after 24 hours and can be stopped earlier in TV Settings.
Support: Open tickets are kept while the request is handled. Resolved or closed tickets and replies are normally deleted after 90 days.
Feedback: Public feedback is kept while it remains useful to the public board or product planning. Private feedback is kept while needed to evaluate and improve the relevant feature. Administrators can delete feedback earlier.
Optional feedback contact email: Removed automatically no later than 180 days after submission, and removed earlier if you withdraw consent, the administrator removes the contact detail, or the feedback item is deleted. The feedback text may remain without the email under the feedback retention rule above.
Feedback voting tokens: Deleted after 90 days.
Security and web logs: Kept only for the period needed to investigate incidents, maintain reliability, and meet infrastructure security requirements.

Data may be retained longer when required by law or necessary for a specific legal claim or security investigation.

10. Cookies and similar storage

The TV application does not use browser cookies. It uses local device storage for the purposes described above.

The website and pairing portal may use strictly necessary storage or cookies for security, bot protection, pairing, and remembering your privacy choice. Cloudflare may set security cookies. Optional analytics is used only after the applicable consent choice.

If a browser exposes Do Not Track with the value 1, or exposes Global Privacy Control as enabled, OpenPlayer treats that browser signal as an opt-out from optional analytics. While the signal is present, it overrides an earlier “Accept All” choice, keeps the analytics preference switched off, and prevents OpenPlayer's website code from enabling the optional analytics beacon. You can reopen Cookie Preferences from the control shown on public pages and can also remove stored data using your browser settings.

These browser signals do not disable storage or processing that is strictly necessary for pairing, security, fraud prevention, rate limiting, or remembering your privacy choice. They also do not control processing performed independently by your media provider, TV manufacturer, browser, network operator, or another third party outside OpenPlayer's website.

11. Your GDPR rights

Subject to the conditions and exceptions in the GDPR, you may request access, correction, deletion, restriction, and a copy of eligible data in a portable format. You may object to processing based on legitimate interests. Where processing is based on consent, you may withdraw that consent at any time without affecting processing that was lawful before withdrawal.

OpenPlayer may need information such as your Device ID, support email, optional feedback contact email, or Telegram chat details to locate records and verify that a request concerns you. Requests are normally answered within one month. They are free unless a request is manifestly unfounded or excessive.

You can unpair a TV to delete its server-side device record and device-scoped diagnostic logs. For other requests, use the contact method above or follow Delete your OpenPlayer data.

You may lodge a complaint with the Swedish Authority for Privacy Protection (IMY) or another competent supervisory authority in the EEA.

12. Security

OpenPlayer uses HTTPS and WSS, authenticated device connections, encrypted device secrets and feedback contact emails at rest, rate limiting, restricted administration, and limited retention. Provider credentials are protected during pairing using ECDH P-256 key agreement and AES-256-GCM encryption for the TV. No internet service can guarantee absolute security, so you should keep the TV software current, protect physical access to the device, and use a provider password that is not reused elsewhere.

13. Children

OpenPlayer is a general-purpose media player and does not curate content. It is not designed to collect information directly from children. A parent or guardian should manage provider access, content restrictions, and support contact for a child. If you believe a child has submitted personal data through support or feedback, contact OpenPlayer so it can be reviewed and deleted where appropriate.

14. Automated decisions

OpenPlayer does not use personal data for profiling or decisions that produce legal or similarly significant effects. Automated rate limits and security checks may temporarily reject suspicious requests. A hardware block is applied for service abuse and can be reviewed by contacting support.

15. Changes to this notice

This notice may be updated when the service, providers, or legal requirements change. The updated date will be shown on this page. Material changes will be highlighted on the website or in the application where reasonably appropriate.

OpenPlayer is an independent media player. It does not provide, host, sell, or distribute media content, and it is not affiliated with a media provider.