A product of StreamOn Technologies Inc. — enterprise event delivery since 2014
Privacy Policy

Privacy, consent, and
data governance.

VIDE — Virtual Integrated Digital Engagement Platform — is designed to help enterprises run digital, in-person, and hybrid events while respecting attendee privacy and supporting customer compliance obligations.

Last updated: June 16, 2026

1. Data We Process

VIDE processes information required to register attendees, operate events, deliver communications, capture engagement, support on-site activity, and provide reporting to event organizers.

Registration data:

Name, email, organization, role, ticket type, form fields, consent, UTM source, and attendee preferences.

Engagement data:

Attendance, watch time, Q&A, chat, polls, quizzes, reactions, downloads, CTA clicks, and session scans.

On-site data:

Check-ins, badge scans, lead capture, session attendance, networking actions, QR access, and incident or fraud signals.

Technical data:

Device, browser, IP address, audit timestamps, session metadata, security logs, and delivery diagnostics.

2. How We Use Data

  • To register attendees, issue confirmations, manage access, and support event participation.
  • To deliver live, simulive, on-demand, in-person, virtual, and hybrid event experiences.
  • To send operational notifications, event reminders, certificates, replay links, and approved marketing communications.
  • To provide analytics, intent scoring, campaign attribution, post-event reporting, and AI-assisted summaries for organizers.
  • To maintain security, prevent fraud, troubleshoot delivery, enforce access rules, and comply with lawful requests.

3. Platform Privacy Controls

Versioned consent

Admins can publish consent versions and record attendee decisions with timestamp, IP, and user agent.

Retention policies

Configurable TTL policies cover registrations, leads, and check-in logs.

Deletion queue

Right-to-delete requests can be logged, reviewed, and executed by authorized admins.

4. Security Controls

VIDE uses layered application controls including enterprise identity, access governance, secure browser delivery headers, restricted admin areas, and event-level operational audit data. These controls support customer security reviews and control-alignment assessments; they do not by themselves constitute formal certification or attestation.

Identity: OIDC/OAuth, Okta, Azure AD, Google Workspace, domain allowlists, and role-based permissions.
Browser hardening: CSP, X-Frame-Options, nosniff, strict referrer policy, and permissions policy.
Sensitive data: Encrypted duty-of-care payload support for sensitive on-site workflows.
Operational assurance: Fraud signals, audit history, incident visibility, and post-event evidence reports.

5. Marketing Website Cookies and Trackers

On www.videplatform.com we use a self-hosted cookie consent banner — not a third-party consent platform. Your preference is stored in your browser (vide_cookie_consent); optional scripts load only after you choose Accept or save preferences. Google Consent Mode v2 defaults to denied until you opt in.

Essential storage:

Consent preference, sticky CTA dismissal, region selection, and form attribution session keys required to operate demo enquiries.

Analytics (opt-in):

Google Analytics 4 and first-party visit/session IDs for page views, scroll depth, CTA clicks, and conversion audit events.

Marketing (opt-in):

Meta Pixel, LinkedIn Insight Tag, and Google Ads conversion tags for campaign measurement.

Google Tag Manager: If configured, the site loads a GTM container after Consent Mode defaults are set. Consent updates push a vide_consent_update event to the data layer for tag triggers. Set VITE_GTM_MANAGED_TAGS=true to route analytics and marketing tags through GTM instead of direct script loading.

You can change your choice anytime via Cookie Preferences in the site footer. Rejecting analytics clears stored visitor identifiers.

Legal basis: Consent for EU/EEA/UK visitors; legitimate interest for strictly necessary site operation where permitted.

6. Attendee Rights

Depending on applicable law, attendees may request access, correction, deletion, portability, objection, restriction, or withdrawal of consent. VIDE supports organiser workflows for consent history, retention configuration, and deletion request execution. Some event data may be retained where required for legal, security, fraud-prevention, contractual, or audit purposes.

AI Data Use & Trust Commitment

VIDE publishes a dedicated Trust Commitment separate from this privacy policy. It includes a contractual no general model training commitment, a feature-level AI Data Use Statement (11 AI features), attendee AI notice support, subprocessor disclosure, and machine-readable JSON at videxperience.com/api/trust/*.

Read Trust Commitment

7. Subprocessors and Integrations

VIDE may integrate with infrastructure, streaming, communications, CRM, marketing automation, analytics, payment, identity, and AI providers based on the services enabled for a customer event. AI subprocessors and data-region behavior are disclosed in the Trust Commitment and live JSON at /api/trust/subprocessors. Customer-specific subprocessors, regions, and data transfer terms should be documented in the applicable data processing agreement or security pack.

8. Contact

For privacy, security, or data processing questions, contact the VIDE team.