The questions people actually ask.

No — and that is the point of deploying it from Google Admin. A force-installed extension cannot be removed or disabled by the person using the browser. That is Chrome's own behaviour, not something we add on top.

The work in Google Admin is a few minutes. Browsers pick the policy up within minutes of a restart, and Google allows up to 24 hours for it to reach every device. Nobody on staff installs anything or is asked to do anything.

Policy can only reach browsers enrolled in your Google Admin, so an unmanaged personal laptop is outside this — the same boundary every Chrome policy has.

Which rule fired, what was done, on which site, from whose browser, and when. Not the text and not the file — they never leave the device. Events are deleted when the retention window you set runs out.

No. Detection is patterns, card checksums, file types and domains, and it runs on the device. The AI in the product sits in the console and does one job: you describe what to protect, it drafts the rule for you to approve. It never sees anything your team pastes, types or uploads.

No, and not because of a policy — because the matching happens in the browser and the text is never transmitted. There is no copy of it in the console, in an export, in a backup or in anything we could be compelled to hand over.

Only where you decide it should. Masking lets the work continue without the sensitive part, warnings let a person make the call, and your own tools go on the whitelist where nothing is checked at all. Most teams start with everything on warn and tighten from there.

You find out before you save it: paste a sample into the rule checker in the console and see exactly what matches. After that, a noisy rule can sit on warn while you watch what it catches, and move to block once it has earned it.

That is what the drafting assistant is for. Describe the shape — an internal ticket number, a customer ID, an account format — and the console drafts a rule with an example it must catch and one it must ignore, both tested before you see it.

No. Capsulla protects web interfaces in Chrome on managed browsers. Desktop apps, mobile apps and IDE plugins are outside it, and we would rather say so now than let you find out later.

No. Chrome on Android and iOS does not run extensions at all, so this is a desktop control.

No. Capsulla only ever sees something as it moves through a browser. Finding what is already inside your SaaS is a different job and a different kind of tool.

Chrome keeps extensions out of Incognito unless they are allowed there, so by default Capsulla checks nothing in an Incognito window. Allowing it in the browser's extension settings turns that on. Worth knowing before you count Incognito as covered.

14 days, no card. Deploy it to one group, leave it alone, and at the end you have a record of what people tried to move out of the browser — which rules fired, on which sites, how often.

No. It is $139 a month for the workspace, whether that is ten people or five hundred, and there are no seats to count.

Export everything from the console — rules, whitelist, admins and events — then delete the organization, which removes its data. Setting the installation policy back in Google Admin takes the extension off the browsers.

Your company is the controller and Capsulla is the processor, and the design does most of the work: the personal data in a paste is never collected in the first place. The full picture is on its own page.

Yes, and in several countries monitoring at work also requires consulting a works council or an equivalent body before it starts. The product makes the telling easier: a person sees a notice when a rule fires, so nothing about this is hidden from them.