AAIRLOCK
FeaturesUsagePricing
Get Airlock
PRIVACY — EFFECTIVE JULY 27, 2026

Your content is not our product.

This page explains what Airlock reads, where processing happens, and what can leave the browser when you deliberately enable an integration.

SummarySubmitted contentBrowser permissionsOllamaWebhooksBillingRetentionYour choices

Privacy summary

Airlock processes scanned text locally by default. We do not operate a cloud LLM for submitted content, sell browsing data, or maintain a database of the text you scan.

Airlock activates only after an explicit action: pasting text, reading a focused field, using its context menu, or starting a Pro page scan.

Submitted content

Text supplied to the scanner is evaluated in the extension using deterministic rules, entropy checks, protected-term dictionaries, and—if enabled—your local Ollama service. Safe versions are generated on the device.

Whole-page scans

Pro page scans inspect visible page regions and relevant editable fields. Temporary element identifiers are added so findings can scroll to and highlight their source. Airlock does not continuously monitor pages, inspect hidden scripts or styles, or upload page content to Airlock.

Browser permissions

activeTab and scripting access allow Airlock to read or update the current page only after a user gesture. Side Panel provides the interface. Storage retains local settings. Context Menus enable scan-selection and scan-field commands. A webhook origin is requested separately only when its endpoint is saved.

Local Ollama

Ollama support is optional and limited to localhost or 127.0.0.1. When enabled, scanned text is sent to the Ollama service running on your device. Your model installation and Ollama configuration are outside Airlock’s control.

Enterprise webhooks

Webhook delivery is disabled by default. When enabled, Airlock sends a versioned audit event to the endpoint chosen by the organization. Default events contain detector category counts, decision, destination origin, timestamp, character count, and optional user/device identifiers.

Raw submitted text and matched secret values are not included. Events explicitly carry contentIncluded: false.

Billing and licensing

Paid checkout is provided by Lemon Squeezy. Payment details are handled by that provider under its own privacy terms. When a user activates Pro, Airlock sends the entered license key and a browser-instance label directly to Lemon Squeezy for activation and periodic validation. Airlock stores the license key, returned instance ID, plan variant, and validation time locally so it can enforce the purchased entitlement.

Storage and retention

Settings, protected terms, and pending context-menu scans are stored locally in Chrome extension storage. Pending scan transfers expire after one minute. Removing the extension deletes local extension storage according to Chrome’s behavior. Organization webhook retention is controlled by the receiving organization.

Your choices

You can disable Ollama or webhooks, remove protected terms, revoke optional site access, or uninstall Airlock. For privacy requests related to billing or support records, contact support@builtbykris.com.

Chrome Web Store Limited Use: Airlock’s use of information received from Chrome and Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Data is used only to provide Airlock’s disclosed privacy-firewall functionality and is not used for advertising, profiling, creditworthiness, or sale to third parties.

AAIRLOCK

Stop secrets before they leave your browser.

PrivacyUsageContact
© 2026 Airlock. Local first, by design.