Cometline

Privacy Policy

Effective date: August 14, 2026. This policy covers the Cometline macOS desktop app and this website.

Who we are

Cometline is a local-first desktop AI companion published by the Cometline project (github.com/Cometline/cometline). The app runs on your Mac. It is not a hosted chat service, and this website does not create accounts.

Contact: tomlord1122@gmail.com

What this website collects

cometline.github.io is a static site. It does not use analytics, advertising, cookies, or account login. Your browser may request fonts from Google Fonts when a page loads. We do not receive that request, and we do not log visitors.

What stays on your Mac

Conversations, workspace files the app reads, semantic memory, the local wiki, inbox notes, scheduled jobs, settings, and connector credentials are stored on your computer, under your user directory (including ~/.cometmind). Cometline does not operate a server that receives this data, and the app does not include telemetry, crash reporting, or usage analytics.

You can delete this data by removing the app’s local files, or by deleting a session, memory, or connector inside the app.

Data you choose to send

Cometline only contacts the network when you configure a provider, model, or connector and then use it. In those cases the app sends the content needed to fulfill that request, from your machine, to the service you selected:

Google account data

Cometline requests access to your Google account only if you connect a Google service as a connector. The app uses that access to perform the actions you or the agent invoke through that connector (for example reading or writing the Google data the granted scopes allow). Cometline does not sell Google user data, does not use it for advertising, and does not transfer it to a Cometline server. Google’s processing of the API call is governed by Google’s policies.

You can revoke access at any time from the connector settings in the app, and from your Google Account permissions. Revoking access deletes the locally stored token for that connector.

What we do not do

Security

Credentials and OAuth tokens are written to local files with restricted permissions. Workspace file access is sandboxed to the workspace you open. No storage method is perfectly secure; protect your Mac user account, and do not share provider keys.

Changes

If this policy changes, the updated text will be published on this page with a new effective date. Continued use of the app after that date means you accept the update.