Minimum necessary data
Agree what is in scope, who can see it, how long it is retained, and what must never be collected.
Trust, privacy & human review
Boundaries should be clear before a pilot begins.
Circuit scopes each engagement around the minimum information needed, named access, accountable decisions, and an agreed way to stop, export, or remove pilot data.
People remain responsible
Licensed, managerial, legal, employment, and other consequential decisions stay with accountable people.
Evidence over assumption
Keep sources, confidence, approvals, exceptions, and remediation visible so claims can be checked.
Circuit Signal pilot boundary
- Employee notice and explicit pilot scope before collection
- No prompts, responses, page content, files, screenshots, or keystrokes
- Optional Companion observes only approved AI domains and requires participant confirmation
- Raw Companion observations retained for no more than 30 days during the supervised pilot
- Participants can pause or disconnect; administrators can revoke devices
Operational safeguards
- Tenant-scoped access controls and isolated workspaces
- Evidence records preserve source and confidence
- Critical privacy, integrity, or tenant-boundary concerns stop pilot intake
- Customer offboarding covers access revocation, export, and agreed deletion
- Specific contractual requirements override the public summary
Important scope note
This page summarizes current supervised-pilot practices; it is not a certification, legal opinion, security warranty, or substitute for engagement-specific terms. Controls and product scope are confirmed in writing before customer data is used.