Privacy Policy

Where VenueCircuit is right now

VenueCircuit is an interactive proof of concept. What you can use today is a public demo built on a shared, fictional dataset — there are no user accounts yet, and the role switcher inside the demo is a preview of how role-based access will work, not an access-control system. Anything you type into the demo is disposable demo data: it may be visible to other visitors and is periodically reset. Please don't put real business data in it.

What we collect

This public proof of concept does not collect personal data through feedback forms or product analytics. Please do not enter real business or personal information into the shared demo.

When production accounts launch, we'll collect what setup requires — name, email, role, venue or company details — plus the operational data you enter (show records, ledger entries, settlements, riders, guest lists). That data will belong to your organization, not us. This section will be updated before any of that goes live.

How we use it

The public demo's shared fictional data powers the sandbox and is not customer data. When production accounts launch, operational records will be used only to run the product.

We won't sell your data. We won't share it with data brokers. We won't use show records or ledger entries to train models, run ads, or build profiles. This operational data isn't a product we're monetizing — it's information you trusted us to hold while you run your business.

Where it's stored

The shared fictional demo runs on Supabase, which uses PostgreSQL hosted in the United States. The public site does not accept pilot requests or feedback submissions.

Supabase and Netlify are infrastructure providers, and like any infrastructure provider, they have access to the systems your data sits on. They operate under their own security and compliance standards.

For production accounts we plan per-organization isolation, Supabase Auth for login security, and database-enforced role access. Those protections are not live yet — which is exactly why the current demo runs on fictional data.

Who sees this data

The public PoC does not collect feedback or create a visitor list. We don't sell or share demo data with data brokers.

In production, access within an organization will be role-based — people added to an org will see what their role allows and nothing more. The demo's role switcher shows that model on fictional data today.

Integrations

The integrations you can open in the demo (ticketing, point-of-sale, accounting, payroll) are clearly labelled simulations running on the fictional dataset — no third-party connection is made and no credentials are collected.

When real integrations launch, we'll use OAuth or API keys you provide, we won't store those credentials in plain text, and we won't reuse them beyond the sync you authorized. Each third-party service has its own privacy policy that covers their end.

Your rights

Before accounts ever launch, the production privacy terms and account-data rights will be published. Email us at hello@venuecircuit.app and we'll take care of it.

We're building self-serve export tooling for the production beta. Until then, reach out and we'll handle current requests manually.

Cookies & analytics

This PoC does not load Plausible, Google Analytics, or another visitor analytics provider. There is no analytics-consent prompt because there is no analytics collection path.

There are no login cookies today because there are no accounts yet. When accounts launch, session cookies will be first-party Supabase Auth tokens that expire and aren't shared with anyone.

Contact

Questions about this policy, your data, or anything else: hello@venuecircuit.app