Privacy Policy

Last updated: March 2026

1. Overview

Airlock is a cryptographic approval gateway for AI agents. Privacy is a core architectural principle — the system is designed so that Airlock never sees the content of AI actions. This document explains what data we collect, how we process it, and your rights. Use of the Airlock mobile app and related end-user services is also subject to our End User License Agreement.

2. Zero-Knowledge Architecture

Airlock's Gateway operates as a zero-knowledge relay. All AI action payloads are encrypted end-to-end between the enforcer (your IDE) and the approver (your mobile device) using AES-256-GCM. The Gateway only processes opaque ciphertext — it cannot decrypt, read, or store the content of AI actions.

What the Gateway sees: Request metadata (timestamps, artifact type, request IDs, enforcer IDs).
What the Gateway never sees: AI command content, file diffs, terminal output, source code, or any payload data.

3. Data We Collect

3.1 Account Data

When you create an account, we collect:

  • •Email address (for authentication and account recovery)
  • •Display name (optional)
  • •Authentication credentials (hashed, never stored in plaintext)

3.2 Device Data

When you pair a mobile device, we store:

  • •Device token (for push notifications via Firebase Cloud Messaging)
  • •Ed25519 public key (for signature verification)
  • •Device name and platform (for display in the admin console)

3.3 Workspace & Approval Metadata

We store operational metadata:

  • •Workspace names and configuration
  • •Approval request timestamps and status (approved/rejected/expired)
  • •Artifact type labels (e.g., "terminal_command") — not the command content

3.4 Data We Do NOT Collect

  • ✗AI command content or terminal output
  • ✗Source code or file diffs
  • ✗Encryption keys or private signing keys
  • ✗Browsing history or usage analytics
  • ✗Repository contents or project metadata

4. Push Notifications

When an approval request arrives, we send a push notification via Firebase Cloud Messaging (FCM). These notifications contain only the request ID and artifact type — no payload content. The mobile app then fetches the encrypted artifact directly from the Gateway and decrypts it locally.

5. Data Retention

Approval request metadata is retained for audit purposes. Encrypted artifacts on the Gateway are ephemeral and automatically purged after the approval decision is made or the request expires. You may request deletion of your account and all associated data at any time.

6. Third-Party Services

  • •Firebase Cloud Messaging: Push notification delivery (Google's privacy policy applies)
  • •Google Sign-In: Optional authentication provider (if you choose to sign in with Google)
  • •GitHub Sign-In: Optional authentication provider (if you choose to sign in with GitHub)

7. Your Rights

You have the right to access, correct, or delete your personal data. You may also request a copy of all data associated with your account. To exercise these rights, contact us at the email provided in your account settings.

8. Contact

For privacy-related inquiries, please contact us through the information provided in your Airlock account or on our website.

← All Docs Back to Airlock