Vigilant Council public workspace privacy notice
The public demo uses a short-lived browser cookie to open a workspace and remember session state.
If you submit the demo or assessment form, Vigilant Council may use the provided business contact details to respond to your request, coordinate a demo review, or plan a detection quality assessment.
We collect first-party session analytics on public Vigilant Council pages, including page views, route changes, button clicks, form events, visible time on pages, workspace path progress, source, UTM parameters, referrer, browser/device metadata, and follow-up state. Post-gate workspace routes are not recorded by the public analytics collector. We use this to operate the workspace, understand Vigilant Council interest, improve the experience, and follow up on business requests.
In API-backed deployments, assessment requests and qualified workspace-access submissions are stored in our Supabase/Postgres-backed system of record and shown to authorized internal operators in the lead dashboard. In static public workspace mode, the access form opens a local browser session and does not persist access lead/session records. Operational emails, when enabled, are delivered through the configured provider to future@vigilantcouncil.com, with delivery status and errors retained in the notification ledger.
Public lead, session analytics, contact requests, and related email-operation records are retained for up to 180 days, then deleted or anonymized by the internal retention processor unless a longer period is required for security, legal, or abuse-prevention reasons.
Public demo workspaces use example workspace data. Do not enter secrets, regulated data, production credentials, or confidential detection logic into public forms.
Contact future@vigilantcouncil.com for privacy questions, deletion requests, or evaluation support.