Demo safety
Why this is safe to open, and safe to forward
This page is the sandbox's contract with you. It describes the boundary around this demo — what it can reach and what it structurally cannot — rather than how the production system is defended, which would help an attacker and help you not at all.
Public synthetic sandbox — no real customer data, no account, no upload, no live AI execution.
Synthetic data only
Every organisation, person, timestamp, procedure and event in this sandbox was written for the demo. Each organisation name carries a "(fictional)" marker. There is no real customer, no real worker, no real site and no real business information anywhere in it.
A static application
This site is pre-built HTML, CSS and JavaScript served as files. There is no server-side code running behind it to reach.
No authentication
There is no sign-in, no sign-up, no password field and no session. Nothing here can be logged into, because there is nothing to log into.
No database
The sandbox reads pre-authored content shipped with the page. It queries nothing and stores nothing.
No API
The sandbox makes no requests to any backend, product endpoint or third-party service while you use it.
No file upload
There is no upload control anywhere on this site, and no way to send a file to it. The capture stage shows pre-built synthetic sources instead.
No camera or microphone
The sandbox never asks for camera or microphone permission and contains no code that could use them.
No cookies or local storage
Your progress lives in the page's memory for as long as the tab is open. Refresh and it is gone. Nothing is written to your device and nothing is read from it.
No payment
There is no checkout, no pricing form, no card field and no payment step. The sandbox cannot take money and never asks for a payment detail.
No live AI or model request
Every "AI draft" here is pre-authored text shipped with the page. No prompt is sent, no model is called, and no inference happens while you use the sandbox.
No customer environment
The sandbox is not connected to any deployment. Nothing you do here reaches a real installation of the product.
No product account
This is a showcase, not product access. Access to the real application is arranged separately and controlled at app.sopcam.in.
No private evidence or audit data
The version histories, evidence entries and audit logs shown in the Governance stage are illustrative samples. No real evidence, audit record or governance data is present or reachable.
Claims this site does not make
Absences are part of the contract too.
- No certification, accreditation or compliance standard is claimed anywhere on this site.
- No customer count, market position, saving or return figure is claimed anywhere on this site.
- The sandbox does not claim to be the production application, and does not demonstrate its performance.
The human approval rule, reproduced here
The one product behaviour the sandbox enforces rather than describes.
In the sandbox, the stages after Approval do not open until a manager approves, and the worker, training and governance stages do not open until the approved version is published. You can try to skip either gate — in the guided tour or while exploring freely — and you will not get past it. Approval and publication stay two separate, deliberate actions.
If any of this ever stops being true
It would be a defect, not a change of policy, and we would want to know immediately. The three SOPCam surfaces stay separate on purpose: sopcam.in is the public website, demo.sopcam.in is this synthetic sandbox, and app.sopcam.in is the controlled product application. Nothing on this site reaches the third.