Who is responsible for what
Your organization is the controller: you decide which rules run, who the extension is pushed to and how long events are kept. Capsulla is the processor, acting on the instructions those settings express. We do not use your events for anything of our own.
Data minimisation is the architecture, not a policy
Rules are patterns, card checksums, file types and domains, and they run inside the browser against text that never leaves the device. There is no copy of the paste, the typing or the file on our side to protect, to breach or to hand over. What leaves the browser is a description of an attempt.
The personal data an event does carry
A work email address, an identifier for the Chrome profile, the hostname and page title where a rule fired, file names and sizes for uploads and downloads, timestamps, the operating system and version numbers. That is personal data under the regulation, and it is the set your DPIA should describe.
Storage limitation
Events are deleted once they pass the retention window your organization sets. The same job removes browsers that have gone quiet and have no events left attached. The window is a setting in the console, not a support request.
Access, portability and erasure
Admins can search events for one person and export them as CSV, which covers an access request. Erasure runs through the retention window your organization sets, and anything a request needs sooner than that, write to us and we will handle it.
Telling the people you protect
Informing staff that this is running is your duty, and in several countries monitoring also needs a works council consultation before it starts. The product makes the telling easier: an employee sees a notification at the moment a rule fires, and a force-installed extension is visible in their browser. Nothing happens silently on their screen.
A subprocessor list or a security questionnaire — write to us and we will work through it with you: hello@capsulla.io.