Privacy policy
Capsulla is a product about not collecting things, and this page is where that is spelled out. It covers visiting this website, running Capsulla in your company, and the extension installed on its own.
In effect from 13 October 2026
- 01
What this website collects
Our analytics records the pages you view, the site that sent you, your device type and an approximate location, under a random identifier kept in a cookie. Where the law requires consent, it runs only after you choose Accept in the cookie banner; elsewhere it runs until you choose Reject. We use it to see what people read, not to advertise to you. The fonts are served from this domain rather than from a font provider.
- 02
Changing your mind
Choose Reject in the banner and analytics stops: its cookies are deleted and no new ones are set. Cookie settings, at the bottom of every page, brings the banner back at any time.
- 03
Why we may, and where it goes
Where we ask first, the basis is your consent, and you can withdraw it as easily as you gave it. Elsewhere it is our legitimate interest in knowing which pages are read, and Reject is your objection. Our analytics provider processes this data for us and may do so outside your country, under safeguards such as the EU–US Data Privacy Framework.
- 04
Server logs
Our hosting provider keeps short-lived request logs that can include an IP address, as any web server does. They are used to keep the site running and to investigate abuse, and we do not use them to build anything about you.
- 05
When you write to us
An email to us contains whatever you put in it, and your address. We keep that correspondence for as long as it takes to deal with the matter and for a reasonable period afterwards, and we do not add you to a mailing list because you asked a question.
- 06
What the console stores about an account
Here we decide the purpose, so for this data we are the controller. Creating an organization stores:
- Your work email address, which is also how you sign in.
- Your display name and profile picture, if you sign in with Google and Google provides them.
- Your role, whether the invitation has been accepted, when the account was created and when it last signed in.
- Your notification preferences, so we know what to send and what to leave alone.
- The organization's name, its key, and the settings you choose — rules, whitelisted domains and the retention window.
- 07
What arrives from a browser
Inside the service your organization decides what is collected and why, so there your organization is the controller and we act on its instructions. What the extension sends when a rule matches is the shape of what happened:
- Which rule matched, by the label you gave it, and what was done — block, warn, mask or allow.
- Where it happened: the site, without the query string, and the page title.
- Whose browser it was: the work email of the signed-in person and the Chrome profile.
- For files, the name, type and size. For text, how many times a rule matched and how long the text was.
- When it happened.
- 08
What never arrives
The text that matched, the file that was stopped and the contents of the clipboard stay on the device. Matching runs inside the browser, so there is no copy of them on our side — not in the console, not in an export, not in a backup, and not in a subpoena response.
- 09
The extension on its own
Installed without an organization, the extension keeps its rules and settings in the browser and sends nothing to us or to anyone else. There is no account, and no event leaves the device.
- 10
How long things are kept
Events are deleted once they pass the retention window your organization chooses, and browsers that have gone quiet with no events left attached are removed with them. Account and organization data is kept while the organization exists; when it is deleted, that data goes with it.
- 11
Who else processes anything
Two companies, for two jobs: our hosting provider runs the application and its database, and an email provider delivers sign-in codes, alerts and summaries. Neither is ever sent the text a rule matched, because we do not have it either. Both are named on the subprocessors page.
- 12
Your rights
If you are in the EEA or the UK you can ask for a copy of your data, ask us to correct or delete it, object to processing, or complain to your data protection authority. Write to us and we will answer. If your request is about data inside a customer's console, that organization is the controller and we will pass the request to them and help them answer it.
- 13
Security
The strongest control is architectural: the sensitive text never leaves the device, so most of what could be lost does not exist here. Beyond that, admins sign in with a one-time code sent to their work address, each organization sees only its own data, the extension only talks to the console it was given a key for, and traffic is encrypted in transit.
- 14
This is a product for companies
Capsulla is sold to organizations and deployed by an administrator. Anyone can try the extension in their own browser, where it collects nothing; the paid service is for businesses only, and none of it is directed at children.
- 15
Changes
When this policy changes, the date at the top changes with it and starts the new version. If a change affects how we handle data for existing customers, we write to the admins rather than quietly editing the page.
Questions about any of this go to hello@capsulla.io.