Key takeaways
- Recording is off until you deliberately enable it.
- Explicit customer consent is prompted and stored.
- Declining leaves the session running, unrecorded.
- Disclosure text is customisable for your jurisdiction.
Default off, explicitly enabled
Recording is not on by default. Enabling it is a workspace-level decision, and it can be restricted to specific teams or templates.
How consent is captured
When recording is enabled, the customer sees a clear on-screen notice and must accept before capture begins. Declining does not end the session — it proceeds unrecorded, so a refusal never blocks help.
The consent event is stored with the session: what was disclosed, who accepted, and when.
Two-party consent jurisdictions
Several US states and many countries require all parties to consent. The explicit prompt plus a stored consent record is designed for exactly those regimes.
You can customise the disclosure text per workspace to match the language your legal team requires.
What happens to recordings
Recordings are stored under the same encryption, access control, and retention policy as inspection media, and every subsequent view is logged.
Recordings can be deleted on request, independently of the rest of the session record.
People also ask
- Are captured photos treated as recordings?
- Photos captured during a session are part of the inspection record; continuous video recording is the separately consented capability.
- Can we require recording for certain workflows?
- Yes, recording can be mandatory for specific templates where your policy demands it.
- Who can watch a recording later?
- Only roles you grant, and every playback is logged.
Need a hand with something more specific?
help@virtualinspection.ai