Venue Vision

Security and trust

How the product protects your money, your data and your content

What follows describes how Venue Vision is built. It is a description, not an audit report and not a certification, and we have not yet run a live customer event on it.

What we do

Six specific things

Stripe handles card data

Card entry happens on Stripe-hosted checkout. Card numbers do not pass through our servers. Payments go to your own connected Stripe account.

Organizations are kept apart

Every table that holds an organization's data is protected by row-level security in the database, so the database itself limits each organization's staff to their own orders, attendees and streams. That is a second layer behind the application code.

Signed tickets

Ticket codes are signed with a secret key, so a guessed or edited code does not validate. The scanner checks the signature and the live record, which is how refunded and already-scanned tickets are caught.

Two-factor for admins, no passwords

Everyone signs in with a one-time code sent to their email. The codes expire, work once and are stored only as a keyed hash. Our platform admin area refuses access until two-factor authentication is on, and it is available to every user.

A rights workflow

A stream cannot go live until its rights record is complete, and the record is enforced while people watch. Platform staff can review, flag or reject records.

A takedown process

There is a public copyright notice form, a counter-notice record, a strike count and a kill switch that ends a stream and stops playback at once. See the copyright page.

Also in place

  • Stream playback uses short-lived signed tokens that are checked again as the viewer watches
  • Support access to a stream is by a one-person link that expires and is logged
  • Administrative actions are written to an audit log
  • Pages set strict content security rules, and this marketing site loads no third-party scripts or fonts
  • Contact and takedown forms use a CSRF token, a hidden trap field and per-network rate limits

What we are not claiming

  • We do not hold a third-party security certification, and we are not stating that we meet any compliance standard.
  • We have not published uptime figures, because we have no live customer history to base them on.
  • Screen capture of a stream cannot be prevented. Device limits and watermarks are deterrents.
  • Our legal pages are drafts prepared for attorney review and are not a promise of legal sufficiency.

Related

Found a security problem? Please contact us and say so in the message.