Personal data can stay on the viewer's device.
OmmaVQ merges data and video on the client, at watch time. With the Client Isolated method, your app hands the variables to the player locally, so personal data never touches our servers. Integration is light work for IT, and compliance reviews stay short.
On-device merge, by design.
The VQ Player assembles each viewer's video in their browser or inside your app. Three of the five feeding methods keep regulated data inside your perimeter, no additional data processing agreement needed.
- Client Isolated: your app injects variables on the device itself
- URL Proxy: parameters served under your own domain, encrypted in transit
- External API: the player fetches from your endpoints directly
Five methods. Mix them per campaign.
Start with a spreadsheet, end with a real-time API. Warehouse turns an uploaded .csv into a ready data store with zero development. URL parameters get a campaign out the same day. And the methods map onto each other, so an ID carried in a link can key a live lookup against your API.
Your data, shaped on the fly.
Every data point becomes a named variable in the designer, and variables can be transformed inside the content: a birth date becomes an age, a raw figure becomes a formatted amount. No pre-processing pipeline on your side.
What your IT team actually does.
Less than they expect. There is no infrastructure to build and nothing to host beyond an optional static file.
- 1
Pick the method
Choose by data sensitivity: spreadsheet, URL, proxy, API, or on-device injection.
- 2
Map the variables
Each field becomes a variable usable across scenes, voiceover, and thumbnails.
- 3
Go live
A standalone link or a lightweight embed serves every viewer their own video.
Integration and compliance, answered.
Bring your DPO. Seriously.
The fastest way to believe the compliance story is to walk through it. One session with your IT and privacy teams, and you will know exactly which method fits.