airlock

Privacy

Your workspace and your choices.

Effective November 16, 2026 · Applies to the standalone Airlock local assistant and this informational website.

Airlock is an open-source assistant that runs on a user's computer. This policy explains what the standard Airlock application accesses, why it uses that information, where it is stored, and what optional connections can receive. Independently operated connectors and company-memory services may have additional policies; review the operator and destination before enabling them.

Google Calendar access

Connecting Google is optional. Airlock requests calendar.calendarlist.readonly to list calendars you can access and let you select sources, and calendar.events.readonly to read their events. The Google authorization applies at the account level; your calendar selection limits what Airlock ingests locally.

Calendar API responses can include calendar identifiers, names and timezones; event identifiers, titles, descriptions, start and end times, locations, attendee information, recurrence information and cancellation or attendance status. Airlock uses the primary calendar identifier to identify the connected account. It stores the selected event information and synchronization metadata locally to display your schedule, refresh changes and avoid duplicates.

Airlock does not request Gmail, Drive or Google Contacts access in this integration, and does not write to Google Calendar. It connects directly to Google's authorization and Calendar services to complete consent, refresh access and read selected calendars.

Local processing and storage

Chat messages, uploaded documents, notes, contacts, tasks and imported calendar records are stored in the local workspace. Searchable content may be chunked and embedded for retrieval. Relevant retrieved context, including calendar context, can be provided to the local Ollama model when you ask a question. Airlock does not use this information to train or fine-tune a generalized AI model and has no automatic hosted-model fallback.

Google authorization tokens are stored in macOS Keychain. Workspace records, search indexes and activity records are held locally; backups you create can contain sensitive data. The database is not independently encrypted by Airlock. Device encryption, user-account security, backup protection and retention are the operator's responsibility. Installing Airlock does not upload your database or Google tokens to the project maintainers.

Optional sharing

External planning sharing begins paused and unpaired. If you pair a connector, choose release rules and enable sharing, Airlock sends only the approved planning projection to that connector over HTTPS. Calendar projections can contain time blocks, all-day status, timezone and either a generic or explicitly approved title. Task projections can contain reviewed titles, status, approved due dates and board categories, along with opaque identifiers and synchronization metadata.

Calendar descriptions, attendee lists, private notes, documents, contacts, chat and saved memory are excluded from the external planning protocol. Google access and refresh tokens are not shared with a connector or receiving planner. Approved titles may still contain sensitive information; review them before release.

A separately enabled company-memory prototype can send bounded research queries and reviewed memory candidates from selected eligible sources to its configured service, and retrieve context for local reasoning. It is independent of the planning connector and disabled by default. The current prototype is intended for local demonstration, not production organization-wide hosting.

Google Limited Use

Airlock's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Google user data is used for the visible calendar, local assistant and user-authorized planning features described here. It is not sold, used for advertising or credit decisions, or used to develop or train generalized AI models. Project maintainers do not receive automatic access to users' local calendars. Do not send private records in a public support issue.

Retention, disconnecting and deletion

Local content remains in your workspace until removed. Acknowledging a chat message hides it from the active feed; it is not full deletion of the stored history. Disconnecting Google removes local account tokens and pauses its sources, but retains previously imported records and local notes. You can also revoke Airlock's Google authorization in your Google Account connections.

Removing source records, deleting an entire local database, and removing backups are distinct operations. To erase all workspace content, stop Airlock and remove its local database and content stores, including any backups you retain; ask for installation-specific guidance before doing this. Revoking Google access does not erase existing local copies.

Pausing an active planning connection requests withdrawal on its next successful exchange. Expiring leases tell compliant recipients to stop using stale projections. Neither mechanism erases copies already retained in a recipient's database, logs or backups. Contact the relevant service operator for its retention and deletion procedures.

This website and support

This informational website does not accept calendar connections, upload workspace documents or read your local database. It has no application analytics or advertising scripts. Its hosting provider may process ordinary request information, such as IP addresses and browser headers, to serve and protect the site. Links to GitHub and Google lead to services with their own privacy policies.

For privacy questions, use the support address displayed on Airlock's Google consent screen, or open a repository issue requesting a private contact channel without including sensitive data. Security-reporting guidance is in SECURITY.md.

Policy changes

Material changes to how Google data is accessed, used or shared will be disclosed before the changed use begins, with renewed consent where required. The effective date above identifies this version. Modified builds and independently operated services are the responsibility of their respective operators.