Privacy Policy

The short version

• Your conversations, code, vector index, and configuration stay on your device. We do not operate a backend that receives this data.
• When you send a message, the relevant prompt is sent directly from your device to the model provider you selected (for example OpenAI or Anthropic), using your own API key.
• Embeddings used for memory and retrieval are generated on-device by local models. Your source code is not bulk-uploaded to an embedding provider.
• We do not collect your prompts, your code, your model outputs, or your API keys.

1. Data that stays on your device

Tide does not phone home. The following are stored locally on your machine and never transmitted to us:

• Chat sessions, turns, and assistant responses (session logs).
• The files in your git repositories and any worktrees the agent creates.
• The vector index and embeddings used for retrieval-augmented generation.
• Your configuration database, including provider selections and per-session settings.
• Your API keys, which are stored using your operating system's secure credential storage where available.

Deleting the application, or its data directory, removes this data. You can also clear an individual session or the whole index from within the app at any time.

2. Data that leaves your device

Tide is bring-your-own-key (BYOK). When the agent runs a turn, the prompt, your message, and any context the orchestrator has selected are sent directly to the model provider you chose. This call is initiated by the application on your computer; it does not pass through any Tide server.

Once data reaches a provider, it is governed by that provider's own privacy policy and terms. We encourage you to review them. Tide has no access to, or control over, what a provider does with the prompts you send it.

3. Embeddings and retrieval

To answer questions about your code, Tide builds a local vector index. Embeddings are produced by on-device models, so your source code is not shipped to an embedding provider to be indexed. Only the small slices of context the orchestrator deems relevant are included in a prompt when a turn is sent to your chosen model provider.

4. API keys

Provider API keys are entered by you and stored locally. They are sent only to the provider that issued them, as an authorization header, when the app makes a request on your behalf. They are never transmitted to us and never included in prompts or model context.

5. Telemetry and analytics

The current release of Tide does not include analytics, tracking, or crash-reporting that sends data to us. If this changes in a future release, it will be opt-in, clearly disclosed, and documented here.

Updates are delivered through standard operating-system update channels (for example an app store or a download host). The host may log routine request metadata such as IP address and timestamp when you check for or download an update; that metadata is governed by the hosting provider's policy and is not associated with your usage of the app.

6. Tool execution and your repositories

The agent can run shell commands and read or edit files inside your git repositories. This happens entirely on your machine. You control how much autonomy the agent has, and file changes are made inside isolated git worktrees so they remain reviewable and reversible. Commands the agent runs are subject to the same risks as any command you would run yourself.

7. Children's privacy

Tide is a professional development tool and is not directed at children under 16. We do not knowingly collect information from children.

8. Open source

Tide is released under the MIT License. Because the source is available, you can audit exactly what data the application accesses and transmits. See the License page for details.

9. Changes to this policy

If we materially change what the application does with data, we will update this page and revise the “Last updated” date above. Continued use after a change constitutes acceptance of the revised policy.

10. Contact

Questions about this policy can be opened as an issue on GitHub.