1. Scope
This Privacy Policy explains how The Unpirator processes information when customers create accounts, configure workspaces, connect media providers, integrate protected playback, manage viewers and devices, use billing features or contact support.
The Unpirator is designed to minimize viewer information while still providing accountable protected playback. Protected playback requires the customer's backend to provide the authenticated viewer email and a stable application-generated device ID; unrelated profile data is not required.
2. Account and workspace information
We process information needed to create and operate an account and workspace, such as account email, organization or workspace name, authentication state, role, plan, billing status, site configuration, API-key metadata, webhook configuration, audit events and support communications.
Authentication secrets such as passwords are handled through the authentication system and are not intended to be stored in readable form. Customers are responsible for protecting their own credentials and API keys.
3. Media and provider information
To create protected playback, customer servers may send media source information, provider references, storage configuration or provider credentials to The Unpirator. This information is used to resolve and deliver media through the protected playback path and is not intended to be exposed to viewers through browser code.
Customers should send only the provider information required for the selected integration. Sensitive provider configuration may be encrypted or otherwise protected at rest where supported by the service architecture.
4. Viewer information
For protected playback, the customer's backend sends the authenticated viewer email after authenticating the viewer and checking access to the requested content. The browser is not treated as a trusted source of viewer email.
The Unpirator does not mirror the customer's viewer profile or password database. For operational correlation, the service stores an internal viewer record, a keyed lookup derived from normalized email, and an application-encrypted copy of the email so authorized workspace and security views can identify the viewer when necessary.
When dynamic watermarking is enabled, the authenticated viewer email may be displayed to that viewer inside the protected player together with session-specific information. Customers are responsible for the lawful basis, notices and permissions required for the viewer data they send to the service.
5. Device identifiers
The official player generates a random stable application device ID and sends it during playback bootstrap. Protected playback requires this device identifier so the authenticated viewer email can be associated with the device, playback sessions and security events.
The device ID is not intended to be a hardware serial number or invasive hardware fingerprint. Clearing browser storage may create a new application device identifier, and customers should not treat it as a government or hardware identity.
6. Playback, usage and security telemetry
We may process playback-session identifiers, asset and site references, timestamps, request outcomes, authenticated viewer email linkage, device context, client or browser context, viewer IP/network information supplied by the customer's server, usage counters, concurrency state, revocation state, security events, gateway activity and error logs.
This information is used to create and validate protected sessions, enforce plan limits, detect abuse, operate revocation and device controls, troubleshoot failures, measure usage, support customers and maintain service reliability and security.
7. Billing information
We process plan, subscription, invoice, payment-status and transaction metadata needed to operate paid access. Payment-card or financial details may be handled by a payment provider rather than stored directly by The Unpirator, depending on the payment method in use.
We may retain billing records where required for accounting, dispute handling, fraud prevention or legal compliance.
9. Why we process information
We process information to provide and secure the service, authenticate accounts, create protected playback sessions, enforce purchased plan features and limits, process billing, prevent abuse, maintain reliability, debug incidents, respond to support requests and comply with applicable legal obligations.
We may also use aggregated or de-identified operational information to understand reliability, capacity and product performance where that information no longer reasonably identifies an individual or customer viewer.
11. Retention
Retention depends on the type of information, the active plan, operational needs and legal requirements. Some security, session, audit or usage records may have plan-specific retention periods. Account and billing records may be retained longer where needed for compliance, fraud prevention, dispute resolution or accounting.
When data is no longer needed for the purposes described here, we may delete, anonymize or aggregate it, subject to backups, legal holds and technical retention cycles.
12. Security
We use technical and organizational measures intended to protect customer and operational data, including access controls, separation of browser and server trust boundaries, short-lived playback authorization, secret-handling controls, keyed viewer lookup values and application-level encryption of stored viewer email.
No system can guarantee absolute security. Customers remain responsible for securing their own application, authentication system, API keys, provider credentials, domains, storage accounts and authorization logic.
13. Customer and processor roles
For account, billing and direct customer relationship data, The Unpirator may determine the purposes and means of processing needed to operate the service. For viewer or end-user data submitted by a customer through its integration, the customer generally determines why that data is processed and The Unpirator processes it to provide the service on the customer's behalf.
Where required, customers may request additional data-processing terms appropriate to their use case and applicable law.
14. Access, correction and deletion requests
Account holders may use available product controls to review or update certain workspace information. Requests concerning account data, deletion or privacy questions can be submitted through our contact page.
If you are an end user of one of our customers and your request concerns viewer data that customer submitted to The Unpirator, you should usually contact that customer first because it controls the viewer account and the purpose of the playback relationship. We may assist the customer with a valid request where appropriate.
15. International processing
Infrastructure and service providers may process information in countries other than the country where a customer or viewer is located. Where applicable law requires safeguards for international transfers, appropriate contractual or legal mechanisms should be used for those transfers.
16. Children and education customers
The Unpirator may be used by education platforms. The current protected-playback identity model requires the authenticated viewer email, so education customers must determine whether they may lawfully send that email and obtain any notices, consents or agreements required for their users.
Customers serving minors should minimize all other viewer data and avoid sending profile fields that are not required for protected playback, security operations or their chosen features.
17. Changes to this Policy
We may update this Privacy Policy as the product, infrastructure or legal requirements change. The current version will be posted here with an updated effective date. Material changes may also be communicated through the product, account email or another reasonable channel.
18. Contact
Privacy questions, account-data requests or security concerns can be submitted through the contact page. If a customer's separate agreement provides a dedicated privacy or security contact, that contact may also be used.