Skip to content

Privacy Policy

Last updated: October 21, 2026

Overview

Local tools run on your Mac or Windows PC; available integrations vary by platform. Your chosen AI provider and optional cloud connectors receive the content needed for your requests under their own terms. A desktop AI app may also use a cloud model.

Application data used by local tools

  • Email content, subjects, senders, or recipients
  • Calendar events, titles, attendees, or locations
  • Contact names, emails, or phone numbers
  • Microsoft Teams messages, channels, or chat content
  • OneDrive or local file contents
  • Notes or iMessages
  • OmniFocus tasks or project details
  • Any data processed by MCP tools at runtime

Supported files and local indexes are processed or stored on your device. Tool results are passed to the AI client you selected. With Cloud Relay enabled, requests and responses also pass through LMCP infrastructure before reaching that client; a cloud provider may process and retain the requested content under its own terms.

What data we do collect

1. Anonymous heartbeats

The app sends operational heartbeats containing version and platform information, a hashed device identifier, uptime, resource usage and local search-index counts and timings. These heartbeat measurements do not include email content, subjects, senders or recipients. This limitation applies to heartbeat telemetry, not to content you explicitly request through an AI client. Heartbeats stay anonymous unless you add your email to a bug report or feature request (see section 4).

Heartbeats are used to: detect outdated versions and push updates, understand platform distribution (Apple Silicon vs Intel), and measure overall product health.

2. Installation events

When you run the installer, we record: npm package version, macOS version, CPU architecture, Node.js version, which AI clients were configured, your approximate location (country only, resolved on our own server from your IP address with the MaxMind GeoLite Country database), and an anonymous machine ID. Your IP address is used only for this lookup and is not stored, and no IP address is sent to any third party for geolocation. The machine ID stays anonymous unless you add your email to a bug report or feature request (see section 4).

This product includes GeoLite Data created by MaxMind, available from https://www.maxmind.com.

3. License information

We store your email address and license key to verify that the app is authorized to run. No payment data is stored on our servers. License validation makes an outbound request from your device to verify the key.

4. Feedback and bug reports

If you submit a bug report or feature request via the report_problem or request_feature tools, we store the message text, server version, and your email address if you add it. If you add your email, we link it to your installation’s diagnostic data (hashed device identifier, version, setup progress, errors and tool usage) so we can follow up on your report and tell you when it’s fixed. This applies only to reports sent after the app showed you this notice; reports sent without it are never linked. The link lasts as long as the report, and deleting the report removes it. To ask us to delete it, email privacy@local-mcp.com.

5. Website analytics and your choice

Where the law requires consent, nothing is measured on your device until you say yes. In the European Economic Area, the United Kingdom, Switzerland, Brazil and Argentina — and whenever we cannot tell where you are — we ask the first time you visit. You can accept, refuse, or choose per purpose; the answer is kept in your browser for 6 months, and you can change it at any time from Privacy settings at the bottom of every page. If your browser sends Global Privacy Control, we treat it as a refusal and do not ask.

Everywhere else, measurement is on unless you turn it off. We do not ask: the analytics and the session recording described below start with your visit. You can turn each one off at any time from Privacy settings at the bottom of every page; your refusal is kept in your browser, and Global Privacy Control also counts as a refusal.

Without a yes where we ask, or after a refusal anywhere, we count page loads on our own server: the page's path (without the query, and with any token in the address replaced), the origin of the page that linked to it, your platform as read from the browser's user agent, your country, and a hash of your IP address that changes every day. Nothing is stored on your device and no third party is involved. We also count, anonymously, whether the notice was shown and which button was pressed (accept, reject or close), with only the type of page, the language and the country: no identifier, no cookie, nothing stored on your device.

Analytics (with your yes, or by default where we do not ask): Google Analytics 4, in basic consent mode — the advertising signals are never granted — and Cloudflare Web Analytics; and this site's own visit counter, which keeps an identifier in a cookie for 90 days. Google Analytics may set cookies.

Session recording (with your yes, or by default where we do not ask): Microsoft Clarity records a replay of the visit with all text masked. It never runs on pages that carry an identifier in their address (setup links and the welcome page). Clarity may set cookies on our domain and keeps one on its own domain.

If you withdraw a yes, we tell the provider, delete its cookies and our own from your browser, and reload the page so nothing keeps collecting. Clarity's cookie on its own domain cannot be deleted by us; you can delete it from your browser's settings.

Not measurement: a form you submit (a vote, a sign-up) may keep an identifier in your browser from that moment, only to tell your submissions apart. Your answer to this question, your theme and your language are also kept in your browser. If you have accepted all, Google Identity Services may also load to offer you sign-in with Google in one tap: it keeps a cookie (g_state) on our domain to remember the prompt’s state, and if you close the prompt, your browser remembers that for 7 days. None of these is used for measurement.

These providers process website usage information under their own terms; website analytics never give access to the content of your local apps.

Cloud Relay (optional)

Cloud Relay lets web AI clients connect to your local MCP server. When enabled, requests and tool responses travel through LMCP infrastructure over encrypted connections to the selected AI provider. That provider receives the content needed for your request and handles it under its own terms. Local tool execution does not mean the whole workflow stays on-device.

The Cloud Relay is on after installation. You can turn it off at any time from the menu bar, and a web AI can only use it after you connect it and approve the connection.

Data retention

  • Heartbeat records: 90 days rolling
  • Installation events: retained for product analytics, anonymized after 12 months
  • Account records: retained for account duration + 1 year
  • Feedback reports: retained until resolved or deleted on request

Third-party services

  • Railway — backend API hosting (EU and US regions).
  • Cloudflare — CDN, DNS, R2 storage for binary distribution, and website analytics.

Hosting and connectivity services may handle traffic needed to provide the service. Your selected cloud AI provider and optional connectors receive the content required for authorized requests under their own terms. Assess the complete data flow, including these recipients.

GDPR & data protection

Compliance depends on your full workflow, policies and provider agreements. LMCP alone does not guarantee GDPR or other regulatory compliance. Colibird is responsible for the account and feedback data described in this policy.

You have the right to: access the personal data we hold about you, request deletion of your data, and withdraw consent at any time. To exercise these rights, email privacy@local-mcp.com.

Security

Local access is controlled through credentials and permissions. Connections to LMCP services use transport encryption such as HTTPS/TLS or secure WebSocket. Encryption in transit does not prevent an authorized receiving AI provider from processing the content you request.

Changes to this policy

We may update this policy as the product evolves. Material changes will be announced via the in-app update mechanism. The "last updated" date at the top of this page always reflects the current version.

Contact

Questions about this policy: privacy@local-mcp.com
General support: ctpo@colibird.co