Privacy Policy

Two roles, and which one applies to you

When your employer deploys Blank to you, your organization decides what Blank monitors and why. They are the "controller" of that information; we only process it on their documented instructions, as their "processor". If you are an employee, direct questions or requests about that data to your employer first, and we help them respond.

When you visit this website or hold a Blank administrator account, we are the controller of the limited information described below.

What the Blank extension collects

The managed extension performs local inspection of supported text-entry fields and outbound request content across websites. It checks for credentials, personal identifiers, financial information, and organization-defined sensitive patterns. This can include prompt or message content, but raw content and matched values stay on the device. It also examines page and network signals to identify candidate AI tools. After successful enrollment, it reports the following metadata to your organization's Blank service:

• which catalogued AI tools are visited;
• detections: the page domain, detector, category, severity, source, time, and match position and length, plus confidence and aggregate counts when available, not the matched value. Network-source findings are reported only for catalogued AI-tool pages; paste and text-entry findings can also be reported from supported fields on other pages, including tools not yet in the catalog;
• unknown AI tools ("candidates"), the domain of an AI tool not yet in the catalog, surfaced for review;
• an inventory of installed browser extensions, including IDs, names, versions, enabled state, installation type, and declared permissions;
• enforcement events, meaning a coaching prompt was shown or a request was blocked.

Each device carries an identifier and an organization enrollment token so events are attributed to the right fleet.

Blank does not send a full browsing-history log. Visit events are limited to catalogued AI tools and candidate AI-tool domains. Sensitive-data findings from other supported fields can still reveal the domain where the finding occurred. Network-layer blocking is limited to catalogued AI tools and requires an enterprise-policy installation and a blocking policy.

What it does not transmit

The extension does not send the text you type or paste, the secret or personal data that trips a detector, the contents of the pages you visit, your keystrokes, or your passwords. Only the finding metadata leaves the browser, never the matched content. Local inspection is processing on your device, not transmission of that content to Blank.

Pseudonymization

An organization can enable a mode that replaces the device identifier with a pseudonym in dashboards and exports. Re-identifying a specific person is then a deliberate, logged action that requires a second administrator's approval and is limited to a short time window.

What we collect as controller

This website

useblank.dev sets no cookies and uses no analytics or third-party trackers. If you email us at hey@useblank.dev, we receive your message and address so we can reply.

Administrator accounts

To sign in to the Blank dashboard we process your email address and authentication data. Sign-in is handled by Supabase Auth, optionally through Google sign-in or your organization's single sign-on (SAML). If your organization uses SCIM, we receive the account roster (names, emails, roles) your identity provider sends.

Billing

If your organization subscribes to a paid plan, payments are processed by Stripe. We do not receive or store full card numbers.

How we use information

• to provide, secure, and support the service, on the customer organization's instructions;
• to operate administrator accounts, authenticate sign-ins, and process billing;
• to respond when you contact us;
• to meet legal and accounting obligations.

We do not sell personal information, and we do not use the content of what employees type into AI tools to train any model. That content never reaches us.

Service providers we share data with

We use the providers below to run Blank. Their roles depend on the service: hosting, database, and email providers process service data on our behalf; payment and optional identity services also have responsibilities under their own policies.

• Supabase for database and authentication;
• Netlify for application hosting and serverless functions;
• Stripe for payment processing;
• Resend for transactional email;
• Apple iCloud Mail for support, billing, privacy, and security correspondence;
• Google for optional administrator sign-in;
• your own identity provider (for example Okta or Microsoft Entra), if your organization configures single sign-on.

Our subprocessor and service provider list describes the data each handles, processing locations, optional integrations, and provider notices. The DPA template is available for customer review and execution.

How long we keep it

Event data is retained for the window associated with the organization's plan, after which it is deleted automatically: Free defaults to 30 days, Team to 365 days, and Business to 396 days. A move from paid to Free preserves existing event and feedback data for 30 days before Free retention applies. An organization can request deletion of its data; the scheduled purge follows a reversible 30-day period. Account and billing records are kept as long as needed to run the account and meet legal and accounting requirements.

How we protect it

Data is encrypted in transit. Each customer's data is isolated at the database row level. The on-device catalog is cryptographically signed so a device will not act on an unsigned or tampered one. Access to the dashboard is role-based, and identity can be pseudonymized as described above.

International transfers

Blank is operated from the United States, with its database in US East, Northern Virginia. Hosting, email delivery, and provider operations can involve other locations; see the provider list. If your organization requires safeguards for transfers from the European Economic Area, United Kingdom, or Switzerland, contact us to complete the applicable transfer agreement before deployment. The DPA template does not itself execute Standard Contractual Clauses or promise processing within Europe.

Your rights

Depending on where you live, you may have rights to access, correct, delete, or restrict the use of your personal information, or to object to it. Residents of the EEA/UK (under the GDPR) and of California (under the CCPA/CPRA) have these rights, among others.

If your employer deployed Blank, they control that data, so please contact them first, and we will assist them. For website or administrator-account data, contact us at hey@useblank.dev and we will respond.

Children

Blank is a workplace product for organizations. It is not directed to, or intended for, children.

Changes to this policy

We will post any changes on this page and update the date above. Material changes will be communicated to customer organizations.

Contact

Happy Kamper Co. LLC (dba Blank)
hey@useblank.dev

For billing, deployment help, or security reports, see support and contacts.