Stored media objects are private. Authorized player sessions use short-lived signed media URLs for playback.
EU VIDEO HOSTING
Know where it lives.
Know what it records.
Primary video storage is only one part of a hosting decision. See how Visiroll stores media in Frankfurt, delivers playback to viewers, and measures engagement without cookies in the embedded player.
Three parts of the data flow
- Primary storage · Frankfurt, Germany
- The application, account database, video storage, and playback analytics use primary infrastructure in the European Union.
- Playback delivery · CDN
- Authorized viewers receive web-ready media. An EU storage region does not mean every CDN delivery location is in the EU.
- Supporting services · separate providers
- Billing, email, and error monitoring involve their own processors. The privacy policy lists these providers and their roles.
WHAT REACHES THE VIEWER
Private media.
Explicit publishing rules.
Your team chooses where a video is embedded. The player receives authorized playback access, not an unrestricted link to the uploaded master file.
Allow the production domains and intentional staging domains you need. Domain restrictions control embedding; they are not DRM or protection against screen recording.
The embedded player sets no cookies or advertising identifiers. Visiroll account pages use sign-in cookies; optional website analytics has a separate consent flow.
PLAYBACK ANALYTICS
Useful reporting,
defined inputs.
Cookie-free does not mean no data is processed. These are the signals behind playback reports, with the full description in our privacy policy.
See the reporting featuresPlayback events
Impressions, qualified views, watch time, completions, and playback interactions explain how a video is used. They are associated with the video and publishing website.
Daily pseudonymous identifiers
The server derives a website-scoped identifier from network and browser inputs and the UTC day. It is not saved to browser storage and is not an anonymous-person guarantee.
Country, device, page, and campaign
IP addresses are processed for country lookup and abuse prevention, but raw IPs are not saved in playback analytics or rate-limit records. Keep personal information out of page URLs and UTM parameters.
Retention and deletion
Default retention is 90 days for individual playback events and 24 months for aggregates. Successfully processed source files are retained for 7 days. Deleting a video removes its stored media and analytics; generated playback files are retained separately from source files.
BEFORE YOU PUBLISH
Review the whole
data flow.
Hosting location, cookies, and pseudonymisation describe technical choices, not a blanket compliance certification. Your content, audience, website configuration, and provider arrangements also matter.
A practical review checklist
- Check the content and destinations
- Confirm permission to publish the footage, then review each production and staging domain in the allowlist.
- Review analytics and retention
- Read what playback records contain, how identifiers work, and what your own privacy notice needs to explain.
- Check supporting processors
- Review the roles of DigitalOcean, Stripe, Simplenet, Sentry, and optional Google Analytics, rather than assuming the primary storage location covers every service.
Need security or data-processing details for your review? Contact us with your requirements or write to privacy@visiroll.com.
TEST YOUR PUBLISHING FLOW
Start with one
approved website.
Try a real embed on Free, then compare storage, bandwidth, and analytics before scaling.
Create a free workspace