Data processing addendum
The GDPR asks a processor to put its promises in writing. These are ours. The addendum is part of the terms of service, so it applies to every organization from the moment it is created, with nothing to sign.
In effect from 17 November 2026
What it covers
The personal data that reaches the service from your organization's browsers: events, the browsers that sent them and the people signed in to them. For this data your organization is the controller and we are the processor. The addendum lasts as long as we hold any of it. If you need a copy signed by both sides, write to us.
Only on your instructions
We process this data to run the service for you and for nothing else. Your instructions are the terms, this addendum and the settings your admins choose in the admin panel: the rules, who the extension goes to and how long events are kept. We do not sell the data, use it for our own purposes or combine it with another customer's. If we think an instruction breaks data protection law, we tell you. If a law ever requires us to process the data in another way, we tell you before we do, unless that law forbids it.
Confidentiality
Only people who run the service can reach the data, only as far as their work needs it, and they are bound to keep it confidential.
Security
Most of the protection is the design: matching runs in the browser, so the text, the files and the clipboard never reach us. For what does arrive:
- Data is encrypted in transit and at rest.
- Each organization sees only its own data, and the admin panel is open only to the admins it invites.
- Events are deleted once they pass the retention window your organization sets.
- The security page lists every field an event carries.
Subprocessors
You authorize the companies on the subprocessors page, which names each one with its address and contact, what it does and where it processes data. Each is bound by data protection terms no weaker than these, and we stay responsible to you for its work. Before we add or replace one, we email your organization's admins at least 30 days ahead. This covers the companies we use directly; each of them changes its own providers under its own notice to us. If you object on data protection grounds, tell us within that time. If we cannot resolve it, you can end your subscription before the change applies.
Where the data is
The admin panel and its database run in the EU, in Frankfurt, Germany. Email delivery is the exception: sign-in codes, alerts and summaries go through a provider in the United States. Any transfer outside the EEA, the UK or Switzerland rests on an adequacy decision, including the EU-US Data Privacy Framework, or on the European Commission's standard contractual clauses.
Helping you answer requests
Most requests from the people you protect can be handled in the admin panel: search one person's events, export them, or shorten the retention window. For anything the admin panel cannot do, write to us and we will do it. We also give you what you need for a data protection impact assessment or a consultation with your supervisory authority.
If there is a breach
If a personal data breach affects your organization's data, we tell your admins without undue delay and no later than 72 hours after we learn of it. We say what happened, which data and which people it touches and what we are doing about it, and we add details as we learn them. We help you notify your supervisory authority and the people affected where the law requires it.
Audits
We answer your security and data protection questionnaires and give you the information you need to check that we keep to this addendum. You, or an auditor you appoint who is bound by confidentiality, may also audit how we process your data, including by inspection. Give us reasonable notice, normally 30 days. We expect an audit about once a year, and sooner when there is a breach, a supervisory authority asks, or you have reason to doubt that we keep to this addendum. Each side bears its own costs.
When the service ends
When the service ends, you choose whether the data comes back to you or is deleted, and you can ask for either by writing to us. Admins can also do it themselves: export events from the Events page and everything else from the organization page, then delete the organization, which removes the data at once. An export from the admin panel has a size limit and an organization with a renewing subscription has to cancel it before deleting, so for a complete copy, or if either gets in the way, write to us: we send all of the data and then delete it. Once the data is returned or deleted we keep no copy, except in our database provider's backups, which expire within 30 days and are not restored except to recover the service, and except where a law requires us to keep it.
Customers in the United States
Where US state privacy laws apply, such as the California Consumer Privacy Act, we act as your service provider and comply with the obligations those laws and their regulations place on us. You disclose the personal information to us only for the limited and specified purposes in this addendum: providing the service described in the details of the processing below. We process it only for those purposes, do not sell or share it, do not keep, use or disclose it outside our direct business relationship with you, and do not combine it with personal information from other sources. We give it the same level of protection those laws require of you, help you answer consumer requests, and tell you if we can no longer meet these obligations. You may take reasonable steps to make sure we use the information in line with them and to stop and remedy any use that is not.
Details of the processing
What the GDPR asks a processing agreement to state:
- Purpose: running Capsulla for your organization — recording where your rules fired, showing it in the admin panel, and sending the alerts and summaries your admins ask for.
- People: your staff whose browsers run the extension.
- Data: the work email and Chrome profile of the person signed in; the site and page address, without the query string, and the page title; whether the window was incognito; how the data was about to leave (copy, paste, typing, upload or download), the rule's label and what was done; for files, the name, type and size; for text, how many times a rule matched and how long the text was; the time; the operating system, the browser's version and language, and the extension version.
- Never received: the text that matched, the file that was stopped and the contents of the clipboard.
- Duration: for as long as your organization exists, and for each event until it passes your retention window.
If this and the terms differ
For personal data inside the service, this addendum wins.
Questions about this page?
Write to us and a person will answer.