A development data notice
Your needs deserve
clear boundaries.
Verra is in development. This page explains the current implementation and what must be completed before a public service launch.
The judge demo
The demo begins with fictional visits and fictional venue statements. Its changes are stored under a dedicated key in this browser. It does not sign into a personal account or contact an external venue.
Use fictional information when trying it. “Reset demo” replaces your sample edits with the starting scenarios. Browser settings can also remove this storage.
Reading and accessibility
Your reading, contrast and colour-support choices are saved on this device. Read-aloud uses only voices the browser identifies as on-device. It starts only when you choose it, skips form inputs, and stops when the page changes. No page text is sent to a speech API by Verra.
The demo companion uses the selected example’s recorded details in your browser. Its questions are not sent to a model service and disappear when you change the visit or reload.
Your personal workspace
The connected application stores a name if provided, functional needs, visit details, requirements, permission choices, work requests, research findings, quoted source evidence, unsent inquiry drafts and arrangement history. Personal records are restricted to the authenticated owner.
Your saved profile needs are copied into a new visit with sharing off by default. You can decide which requirements may be shared with that venue. No diagnosis is required.
You can download your personal workspace data from Settings. Complete account deletion, retention controls and hosted recovery still need implementation and verification before public launch.
Permission is specific
Permission for one recipient and selected needs is not permission for other recipients, further disclosures, bookings or payments. The current request does not authorize follow-up messages.
Pause stops queued work. Cancellation stops queued work and revokes outreach permission. Neither can undo information already delivered by a future external provider.
External services
The personal app is designed for Supabase authentication and storage. When live research is configured, requesting a venue check sends the selected visit details and requirements to OpenAI for analysis, and retrieves the supplied public venue page. Needs marked private are withheld from venue inquiry drafts; that setting does not exclude them from the research analysis. The worker stores relevant source quotations and findings with your visit. The local verification flow uses clearly labelled synthetic inputs. Venue email and calendar services remain disconnected.
Provider selection, hosting region, retention periods, integration disconnection and a complete published privacy policy remain release requirements. This preview should not be used for real sensitive information until those boundaries are verified.