Getting started
Blank is a managed browser extension. It finds the AI tools already in use across your company, catches secrets and customer data on the way into them, and coaches people in the moment, without blocking the tools they rely on.
An administrator deploys it through browser management (Chrome and Edge). Employees don't install it themselves. It locally inspects supported text-entry fields and outbound requests across websites. Visit reporting is limited to catalogued and candidate AI tools; findings from supported fields can also originate on other pages. Only metadata is reported, never the content someone typed. See privacy and data handling for the scope.
How it works
Blank follows three steps, in order.
- Discover. Find the AI tools running across your fleet, including ones no catalog has heard of yet. What comes back is a hostname and a count. Never a URL, never a keystroke.
- Monitor. Watch what's on the way out. When a secret, credential, or customer record is about to be sent to an AI tool, Blank records the finding: the detector that fired, the severity, and where. The matched text stays in the browser.
- Coach. When something genuinely sensitive is about to go out, the employee gets a quiet in-page note. They can remove it or say it's fine, and keep working. Blocking is an optional policy you turn on later.
You can't coach what you haven't measured, so every deployment starts in Monitor mode, with coaching and blocking off. After 14 days of real monitoring data, administrators can enable coaching or enforcement on a supported paid plan.
Start your organization and deploy
- Sign in with your work email. If you were invited to a workspace, open the invitation and accept with the matching verified email. Otherwise, create an organization on Free; no card required. Existing members return to their workspace. If organization creation cannot be confirmed, use Check organization before trying again.
- Deploy the approved production extension to a test device or group. Installation and enrollment are separate settings. Review your workforce notices and the DPA template before rollout.
- In Deployment, verify the test device's check-in, then use Check recorded visits after opening a permitted catalogued AI tool. Watch reported activity appear in the dashboard. A check-in confirms enrollment; a recorded visit confirms activity delivery.
- When you're ready, turn on coaching or enforcement, per detector or per tool, at your own pace.
In this guide
- Deploying Blank: force-install by MDM for Chrome and Edge.
- The admin dashboard: navigation, command search, saved views, activity, tool review, and People.
- Policy and enforcement: monitor, coach, and block modes, and the rules that drive them.
- SSO and SCIM: SAML sign-in and directory provisioning.
- Team, privacy & access: invitations, roles, privacy controls, temporary identity reveals, and audit history.
- Notifications: detection/tool alerts, destinations, and weekly summaries.
- Evidence packs: PDF/CSV reports, generation history, and file verification.
Prefer machine-readable docs? Every page has a Markdown twin, linked at the bottom, and the whole set is at /llms-full.txt.