Privacy policy

• Ledger. Your tasks, schedule, carbon receipts and audit log are in a local SQLite file, ~/.tidegap/queue.db. The receipt signing key is in~/.tidegap too. Tidegap never uploads them.
• Receipts. A receipt records the task id, time, grid region and source, carbon estimate and actual, provider, model, duration, token count and the prompt. Tidegap removes known API-key patterns from the stored prompt. A receipt stays on your machine unless you share it.
• Settings and secrets. Provider API keys and other settings are in your environment or in ~/.config/tidegap/env (mode 0600).
• Client tokens. A client token pairs an app with tidegap ui. The registry, ~/.tidegap/ui-clients.json (mode 0600), keeps only the SHA-256 of each token. ~/.tidegap/ui.json (mode 0600) holds the port and process id of the running UI. You can revoke a token at any time.

• The task's own provider call. When a task runs, Tidegap sends its prompt to the LLM provider you chose, with your key. For Claude Code, Tidegap runs your own claude CLI, which uses your Claude sign-in. The provider's privacy policy applies to that call.
• Grid data. To find a clean window, Tidegap fetches public grid carbon-intensity data directly from the public source (UK Carbon Intensity API, US EIA, ENTSO-E, WattTime or Electricity Maps), not through a Tidegap server. These requests carry a grid region and, for providers that need one, your own API key. They carry no task content.
• Telegram, only if you set it up. The Telegram channel talks to the Telegram Bot API with your bot token. It sends task notifications and replies to your chat. Telegram handles those messages under its own policy.

Nothing else is sent. Tidegap contains no telemetry and no crash reporting.

tidegap ui listens on 127.0.0.1 only. The Mac app and the browser extension talk to it with a client token.

The Mac app creates its token with tidegap clients add and keeps it in~/Library/Application Support/Tidegap/client-token (mode 0600). It keeps its settings in macOS user defaults. It connects only to 127.0.0.1.

The extension takes a token that you paste once. It stores the token, the port and a few display settings in the browser's local extension storage (storage.local). It requests only http://127.0.0.1/*. It reads no web page, browsing history or tabs, and it sends nothing to the Tidegap project or to any third party. It has no remote code.

www.tidegap.com is hosted on Vercel. Vercel keeps standard server logs (IP address, user agent, requested URL) to run the service. The site has no analytics, no advertising and no tracking cookies. The Google and Bing verification tags in the page head only prove site ownership; they do not track visitors.

Delete ~/.tidegap, ~/.config/tidegap and ~/Library/Application Support/Tidegap to remove all stored data. Remove the extension to remove its storage. Revoke a client token with tidegap clients revoke <id>.

Questions or requests: https://github.com/tidegap/tidegap/issues. Changes to this policy appear on this page with a new date.