Lanes is a desktop and CLI tool for running AI coding agents on your own machine. Your code, your terminal, and your prompts stay on your device. This page documents what we protect, how we protect it, and what is still on the roadmap.
Source code, terminal output, prompts and agent responses never leave your machine.
The Lanes MCP server runs locally on your machine.
Remote workspace data is stored in Supabase, EU region, with logical workspace isolation.
TLS 1.2 or higher for all traffic, Google Cloud platform-managed encryption at rest.
GitHub and Linear OAuth tokens live on disk in integrations.json, not on Lanes servers.
Six vendors process customer data. The full list is on the Sub-processors tab.
An honest note on certification
Lanes has not yet completed SOC 2 or ISO 27001. We are documenting controls publicly while we work toward formal attestation. Anything marked Planned on the Controls tab is on our roadmap rather than in place today.
Status page
Live uptime and incident history for the Lanes service.
Privacy Policy
What we collect, how we use it, and how to exercise your rights.
Terms & Conditions
The agreement that governs your use of Lanes.
Cookie Policy
Cookies we set, what they do, and how to manage your preferences.
GDPR
Our role, lawful bases, sub-processors and your rights under the GDPR.
Targeted response within 2 business days.
Each control is marked with its current status. Implemented means it is in production, Planned means it is on the roadmap. We update this list as the picture changes.
TLS for all web traffic
Every request to lanes.sh and the Lanes API is served over HTTPS with modern TLS.
Lanes Desktop MCP server
The Lanes MCP server runs locally on your machine.
Hosted DDoS protection
Edge protections inherited from Firebase and Supabase shield public endpoints.
Tenant isolation via row-level security
Remote workspace data is logically segregated per workspace in Supabase.
Encryption in transit
HTTPS with TLS 1.2 or higher for all client and server traffic.
Encryption at rest
All persisted data is encrypted using Google Cloud platform-managed keys.
EU data residency
Remote workspace data is stored in Supabase, EU region.
Customer-managed encryption keys
Bring your own keys for sensitive workspace data.
Field-level encryption for sensitive metadata
Column-level encryption for issue titles and bodies on request.
SSO via Google
Authentication is brokered by Firebase Auth with Google sign-in.
OAuth tokens stored locally
Desktop keeps GitHub and Linear tokens in integrations.json on your device. Lanes Link keeps its own in an encrypted store in your workspace. Neither is retained on Lanes servers.
Scoped OAuth grants
GitHub: repo, read:user. Linear: read. Lanes Link asks per product and lists every scope in plain language before the browser opens.
Google Limited Use
Google user data obtained through Lanes Link is never used to train generalised AI or ML models, never used for advertising, and never read by a human outside the documented exceptions.
Credentials unreachable from an agent
In Lanes Link, tokens live in a store no capability can read or enumerate, separate from the vault an agent may read under policy.
Workspace role-based access
Members of a remote workspace see only the issues and sessions they have access to.
SAML and enterprise SSO
SCIM provisioning and SAML for managed organisations.
Admin audit logs
Tamper-evident audit trail for workspace and billing administrative actions.
Dependency vulnerability scanning
Dependabot watches the Lanes source repositories for vulnerable packages.
Secret scanning
Pushed credentials and high-entropy strings are surfaced before merge.
Public security disclosure channel
Reach hello@lanes.sh for vulnerability reports.
Peer review on every change
All production code changes require a reviewed pull request before merge.
Public status page
Live incident and uptime reporting at lanes-sh.instatus.com.
Public sub-processor list
Every vendor that processes customer data is listed on this page.
GDPR data-subject request flow
Email-based intake with a 30 day target for access, export and deletion requests.
Cookie consent with denied-by-default
Google Consent Mode v2 keeps all signals denied until explicit consent.
SOC 2 Type II
Independent attestation of operating controls over a 12 month window.
ISO 27001
Certification of the Lanes information security management system.
Most of what you do in Lanes never reaches our servers. The sections below describe exactly what stays on your device, what syncs when you opt into remote workspaces, and how integrations and the MCP server handle credentials.
Local workspaces process everything on your device. We do not receive, log, or store any of the following.
Repository contents read or modified by the app or agents.
Commands you run and any output produced inside Lanes sessions.
Conversations with Claude Code, Codex, Gemini CLI or other agents.
Responses returned by the AI provider you have configured.
The on-device store of issues, sessions and workspace settings.
Anthropic, OpenAI, Google and other provider credentials you configure.
When you opt into a remote workspace, the following metadata is stored in Supabase to enable collaboration. Code and prompts remain local.
Titles, descriptions, statuses and tags you create in the remote workspace.
Who is part of the workspace and what role they hold.
Discussion threads attached to issues in the remote workspace.
References to sessions linked to issues. Session contents stay on the originating machine.
Tokens are issued through the standard OAuth consent flow, stored on your device, and used directly by agents running on your machine.
Lanes Link runs on your machine or in your own cloud. Accounts are connected from there and the data never passes through Lanes.
A local Model Context Protocol server lets agents drive your workspace. It runs on your machine.
We update this list before any new sub-processor receives customer data. If you operate a workspace and want to be notified of changes, email hello@lanes.sh.
| Provider | Purpose | Data processed | Region | Link |
|---|---|---|---|---|
| Firebase Authentication | User authentication and account profile | Email, display name, auth tokens | Google global | Privacy |
| Supabase | Primary database for remote workspaces and Lanes Forms | Workspace metadata, issues, comments, Lanes Forms submissions | EU | Privacy |
| Resend | Transactional email and Lanes Forms submission forwarding | Recipient emails, forwarded form submission content | US | Privacy |
| Stripe | Subscription billing | Billing email, payment method tokens, plan | Stripe-managed (US / EU) | Privacy |
| Google Analytics 4 | Anonymous web analytics, consent-gated and denied by default | Hashed identifiers, page views (only after consent) | US / EU | Privacy |
| Sentry | Error and crash reporting | Stack traces, environment metadata | EU | Privacy |
For full processing terms, lawful bases, and your rights as a data subject, see our GDPR policy.
