Cross-Employee Surveillance Protections
A platform-level guardrail that prevents Digital Twins from being used to monitor colleagues — so Viven helps people work, not watch each other.
What Is This Protection?
When a user queries another employee's Digital Twin, Viven automatically refuses surveillance-style questions — questions about things like time tracking, location, break monitoring, or productivity metrics. The Twin simply won't answer them, regardless of how the question is phrased.
This is a cross-twin only guardrail. Querying your own Twin is completely unaffected — you can ask your own Twin anything about yourself. The restriction only applies when one employee is querying another person's Twin.
What It Blocks
The guardrail specifically refuses questions in these categories when directed at another person's Twin:
| Category | Examples |
|---|---|
| Time tracking | "How many hours did X log this week?" |
| Location tracking | "Where is X working from today?" |
| Break monitoring | "When did X take breaks yesterday?" |
| Productivity monitoring | "How productive has X been this month?" |
| Surveillance | "What has X been working on all day?" |
Borderline productivity-style phrasings can occasionally slip through. Viven measures this actively and tightens the guardrail on each release using a dedicated regression test set. If you encounter a query that should have been blocked, flag it to your Viven rep.
Why It Matters
Enterprises adopting AI tools face increasing scrutiny from legal, HR, and employee trust perspectives. The core concern: could this tool be used to monitor my people?
This feature gives a concrete, verifiable answer: no. Cross-twin surveillance queries are blocked at the platform level — not by policy, not by honor system, but by the product itself.
Most AI copilots don't distinguish between querying your own context and querying a colleague's. Viven does, and enforces different rules for each. This distinction is increasingly important in regulated industries and large enterprise deals.
How It Works
- The guardrail is evaluated at query time, on every cross-twin request
- No data is exposed — blocked queries return a refusal, not partial results
- Employees retain full visibility into all queries asked on their own Twin via the audit log, including any that were blocked — giving the queried person full transparency
- The protection is validated against a regression test set on every release, so it doesn't silently degrade
Availability
This feature is off by default and enabled per organization on request.
Contact your Viven representative to turn on cross-employee surveillance protections for your account. There is nothing to configure on your end — your rep handles it.