CineConvert
TermsPrivacy

Privacy Policy

Last updated October 28, 2026

This page is provided in English. Where a translated version exists, the English text governs.

This policy explains what CineConvert collects, why, and who it goes to. It covers two different groups of people, and the distinction matters throughout: customers, who hold an account and publish videos, and viewers, who watch a video a customer published. Most of the data described here is collected about viewers, on behalf of the customer who published the video.

CineConvert is operated by David Media Group, 367 St Marks Ave, Brooklyn, NY 11238. For any privacy question or request, contact elite@davidmediagroup.com.

What we collect from customers

  • Account details: email address, password (stored hashed by our authentication provider), and workspace name.
  • Content you upload: video files, thumbnails, titles, calls to action and page copy.
  • Billing details. Card numbers are entered directly with Stripe and are never sent to or stored on our servers. We retain the subscription status and the last four digits Stripe returns.
  • Integration credentials you choose to add, such as a GoHighLevel private integration token. These are encrypted at rest.

What we collect from viewers

When someone watches a video published through CineConvert, we record engagement events so the customer can measure performance. These events include:

  • Video loads, view starts, replays, progress milestones and periodic watch time while the video is visible and playing.
  • Impressions and clicks on calls to action, poll answers and branching choices.
  • Short link and bio page clicks, including the referring domain and any campaign or source tag on the link.
  • Approximate technical context derived from the request: device type, browser, and country. We do not store full IP addresses alongside these events.

If a viewer submits an opt in form on a video, we also collect what that form asks for, which is typically name, email address and phone number. That information is provided knowingly by the viewer and is passed to the customer who published the video.

Cookies and visitor recognition

On a direct visit (a video link, a short link or a link-in-bio page) we set a first party cookie named cc_vid containing a random identifier. It is marked httpOnly, so page scripts cannot read it. Its purpose is to recognise the same browser across visits, so that a viewer who watches on Monday and returns on Thursday is counted as one returning person rather than two strangers, and so a link click can be connected to the view that follows it.

When a video plays inside another website (an embedded player, or a link-in-bio page shown inside another website), that cookie cannot be used. There, and only there, we set a separate cookie named __Host-cc_vidp containing a different random identifier. It is also httpOnly, and it is marked partitioned: in browsers that support partitioned cookies, the browser keeps a separate copy for each website the player appears on, so it can recognise a viewer who returns to the same website but cannot connect visits to different websites. An older browser, or an app's built-in browser, that ignores the partitioned setting but accepts third-party cookies may keep a single copy for every website. Visits from browsers that block it are counted without an identifier.

These identifiers are not tied to a name until the viewer is known. That happens when they voluntarily submit a form; when they open a personalised link that a customer made for them by name; when they open a link a customer sent them from their CRM (GoHighLevel) that carries their contact id; or, if the customer has turned this on, when a booking or purchase made after clicking through is reported to us with an email address. A personalised or CRM link identifies its recipient, so if it is forwarded, whoever opens it is recorded as that recipient; in the same way, a booking or purchase is tied to the browser that clicked through to it. From then on, that browser's earlier anonymous activity is visible to the customer as that contact's history. We do not sell this data and do not use it for our own advertising. A customer who connects their own Meta (Facebook) ad account has the leads and sales from their videos sent to it, as described under Who we share it with.

A customer can choose to add their own Meta (Facebook) pixel to their video and link-in-bio pages. When they do, Meta's script runs on those pages, sets Meta's own cookies and receives events such as how far a video was watched and which buttons were pressed. That data is handled under Meta's privacy policy and the customer's own.

CineConvert is operated from the United States and does not currently display a cookie consent banner. Where local law requires a viewer's consent before non-essential cookies are set, responsibility for obtaining it rests with the customer who published the video and chose to enable tracking, as the party that controls how that data is used.

Who we share it with

We use a small number of processors, each for a specific function:

  • Supabase, for database hosting and authentication.
  • Cloudflare R2 and Cloudflare Stream, for video storage and delivery.
  • Vercel, for application hosting.
  • Stripe, for payment processing.
  • Resend, for transactional email.
  • GoHighLevel, only where a customer has connected their own account, and only for leads captured on that customer's videos.
  • Meta (Facebook), only where a customer has connected their own ad account under Facebook ad conversions: the leads and sales from that customer's videos are sent to Meta's Conversions API, with the email address and phone number hashed, together with the viewer's IP address and browser, so the customer can measure their ads.

Lead and engagement data belongs to the customer whose video captured it. We act as a processor for that data and do not use it for our own purposes.

Retention

Engagement events and contact records are retained for as long as the customer's account is active. Customers can delete individual contacts and reset a video's analytics from within the product. When an account is closed we delete its content and associated records within 30 days.

Your rights

Depending on where you live, you may have the right to access, correct, export or delete the personal information we hold about you, and to object to certain processing. To make a request, contact elite@davidmediagroup.com. If you are a viewer rather than a customer, your request may need to be directed to the customer who published the video, and we will help identify them and pass the request along.

Children

CineConvert is not directed to children under 13 and we do not knowingly collect their information.

Changes

If we change this policy materially we will update the date above and, for customers, give notice by email before the change takes effect.