Privacy Policy

What personal data OhPlayer processes, why, who we share it with, and the rights you have.

Last updated 5 October 2026

Who is responsible

The data controller is OhPlayer, a business registered in Poland at aleja Grunwaldzka 472B, 80-309 Gdańsk. Contact: hello@ohplayer.com. OhPlayer is a business-to-business service and is not directed at consumers.

Two roles: your account and your viewers

For your account and your use of the service, we are the controller.

When your video captures a viewer or lead on your own site, you are the controller of that viewer data and we act as your processor, under our Data Processing Agreement (ohplayer.com/dpa). You are responsible for your own privacy notice and for obtaining any consent your viewers need.

What we collect

Account data: your name, email address and Google subject identifier, and your plan and billing status.
Content: the videos and images you upload, captions and transcripts, and the player, CTA, gate and embed settings you configure.
Viewer and engagement data: player events such as play, pause, progress, completion, call-to-action clicks and gate submissions, plus watch time, per video and version.
Lead data: the email address, name and phone number a viewer submits through a gate or form you configure.
Attribution and device data: a stable viewer identifier stored in the host page, plus click identifiers such as gclid or fbclid when present.
Billing data: handled by Stripe. We receive payment status, not full card numbers.
Support and product usage data, including product analytics where enabled.

How we use it and why

To provide the service: hosting, encoding, delivery, analytics and AI proposals. Legal basis: performance of a contract.
To secure the service, prevent abuse and enforce fair use. Legal basis: legitimate interests.
To improve the product and understand general usage in aggregate. Legal basis: legitimate interests.
To communicate about your account, billing and changes. Legal basis: contract or legitimate interests.
To meet legal, tax and accounting obligations. Legal basis: legal obligation.
For anything else that needs consent, we ask first and you can withdraw it.

Cookies and local storage

We set a strictly necessary login cookie to keep you signed in.

The studio uses PostHog in cookieless mode for product analytics and error tracking. It sets no analytics cookies and stores nothing in your browser for analytics; PostHog counts visits with a privacy-preserving hash on its servers and does not link them to your account.

We set a viewer identifier on pages that host your embed, and read attribution parameters already present in the URL. Because the embed runs on your site, your own cookie notice also applies there.

We use service providers (processors) under contract. The current set is:

Google for sign-in.
Vimeo and Wistia when you connect a library for migration. Access tokens stay encrypted on our servers.
Slack when you connect Coach. Workspace tokens stay encrypted on our servers.
API keys you create to operate the account from MCP or other clients. We store a hash, not the secret, after the one-time reveal.
Neon for the account database.
Cloudflare for object storage and content delivery. Private originals are stored in R2 in the EU; encoded streams and posters are delivered from a public CDN hostname.
OVHcloud for the API server (Warsaw, Poland) and the encoding servers (Gravelines, France, and Erith, United Kingdom).
Stripe for payments and subscription management.
OpenRouter for AI transcription and recut proposals.
PostHog, in the EU, for cookieless product analytics and error tracking.
Resend for account emails, such as billing, trial and deletion notices.
Destinations you configure, such as a webhook, Zapier, Make or n8n, which receive the events and leads you choose to forward.

International transfers

Some providers process data outside your country. Where required, transfers rely on appropriate safeguards such as an adequacy decision (for example, video encoding in the United Kingdom) or standard contractual clauses.

Retention

Account data is kept while your account is active.
Deleting a video removes its management records and enqueues removal of the source and encoded files, including the CDN cache. Abandoned uploads expire after 24 hours.
While your plan is active, completed videos stay until you delete them. If a subscription lapses, published playback continues through the paid period plus a 3-day grace, then public players pause.
An account whose plan or trial ended is deleted, with its videos, analytics and leads, 90 days after the 3-day playback grace ends. We email the account owner 7 days before. Starting a plan before then keeps everything.
Lead submissions captured on your videos are deleted after 90 days by default. You can set 30, 90 or 365 days in account settings. Export or forward leads if you need them longer.
You can download a copy of your account data, video records, leads and analytics summaries from account settings once per 24 hours.
Billing and tax records are kept as long as the law requires.
Backups expire with the configured backup window.

Your rights

Depending on where you live, you may have the right to access, correct, delete, restrict or object to processing, to receive a portable copy, and to withdraw consent. Contact us to exercise them, and you may complain to your local supervisory authority.

If you are a viewer whose data was captured on someone else's video, contact that business first: they control it. We will help them respond.

Security

We use hashed sessions, encrypted secrets for integrations, access controls and transport encryption. No system is perfectly secure; keep your account credentials safe.

Children

OhPlayer is a business tool and is not intended for children.

Changes

We will notify material changes before they take effect.

Contact

Privacy questions and requests: hello@ohplayer.com.