Every security lead asks the same question: where does the data go. Here is the full answer, including the parts that do not flatter us.
Detection and substitution happen in the browser, before anything is sent. There is no remote classification service to query, so no copy of the employee's text reaches Context Security or any processor acting for us.
The mapping between original and synthetic value stays on the workstation for the length of the session. It serves the local restore in the reply, then it is gone.
Each one can be observed by your own team during a pilot, without taking our word for it.
No account to create, no token to exchange, no outbound call to our systems during use.
The reporting dashboard, if adopted, installs on a server you own.
Configuration is pushed by your fleet management tooling and stays editable without going through us.
Written to be quoted as is inside your privacy impact assessment.
Send your vendor questionnaire or assessment grid. We answer in writing, including where the answer is no.
communication@contextsecurity.ca
Context Security