Data, privacy and cookies¶
This page explains what OhPlayer stores, how long it keeps it, which cookies it sets, and which choices you have.
What OhPlayer keeps and for how long¶
| Data | How long | Can you change it? |
|---|---|---|
| Viewer analytics (plays, progress, CTA clicks, form events) | 90 days | No |
| Leads (email, name, phone and the consent text) | 90 days by default | Yes: 30 days, 90 days or 1 year |
| Webhook delivery records | 30 days | No |
| Sales (amount, currency, order id and which video was credited) | Kept with your account | See Track sales per video |
| Videos, thumbnails and captions | Until you delete them | Yes |
Lead contact details are stored encrypted, and only your account can see them. OhPlayer does not store card numbers or the buyer's email for sales. Card payments are handled by Stripe.
Choose how long leads are kept¶
- Click your name in the sidebar to open your account settings.
- Open the Data & privacy tab.
- Under LEADS, next to Lead retention, click 30 days, 90 days or 1 year.
OhPlayer deletes playgate emails and names after this period unless you export them first. See Leads and exports.
Download your data¶
In Account → Data & privacy, under EXPORT, click Download JSON. The file holds your account, videos, leads and analytics summaries. You can download it once every 24 hours.
Delete your data¶
Delete one lead in Analytics → Leads. Delete a video or your whole account from the Library and Account → Data & privacy. Deleting is permanent. See Delete a video or account.
Cookies on OhPlayer¶
When you first open the OhPlayer app or website, a banner titled Analytics cookies asks about product analytics: "We use PostHog in the EU to understand product use and catch errors." Click Accept or Reject. Login cookies that keep you signed in are set either way.
Your answer is saved in a cookie named ohp_consent for 180 days. It is shared between ohplayer.com and app.ohplayer.com, so you answer once. To be asked again, clear the site data for ohplayer.com in your browser.
Cookies on your own pages¶
Your embed runs on your page and stores a small amount of data in your visitors' browsers.
| Name | What it is | How long |
|---|---|---|
studio_vid |
A random id, set as a first-party cookie on your page and copied to the browser's local storage. It lets OhPlayer count estimated viewers and credit sales to a video. | 1 year |
| A resume marker | Where the viewer stopped, so the video can resume. Stored in the browser's local storage. | Until the viewer finishes the video or clears the data |
If a visitor arrives from an ad, the player also records ad click ids such as gclid and fbclid, and reads the Meta _fbp and fbc cookies when they exist. See What your viewers see.
The player does not show a cookie banner and does not wait for consent. You decide whether you need one under the laws that apply to you, and you set it up on your own site.
Lead form consent¶
A playgate shows a box the viewer must tick before submitting: "I agree to share my details with the owner of this video to access the video." OhPlayer stores this text with each lead and adds it to the Consent column of the leads CSV.
Ad pixels and integrations¶
OhPlayer sends viewer events to Meta, Google Analytics 4 or Google Tag Manager only if you turn on Ad pixel events, and only to pixels already on your page. Webhooks and Zapier send data only to the address you add. You can pause or disconnect them at any time.
Privacy policy¶
Read the full Privacy Policy. For questions, write to [email protected].
Next steps¶
Was this page helpful?
Your answer stays in your browser. Nothing is sent to us or to anyone else.