Privacy Policy

• Account data — name, email, and authentication identifiers managed by our authentication provider (Clerk).
• Billing data — subscription, payment status, and invoices managed by our payment processor (Stripe). We do not store full payment card numbers.
• Usage data — agent runs, tool invocations, token counts, and benchmark metrics, used to enforce limits, surface analytics, and improve the service.
• Workspace metadata — when you connect a local workspace, ADA may send file paths, snippets, and code embeddings to your configured backend for indexing and recall. This is governed by your deployment configuration.
• Diagnostic data — logs, error reports, and OpenTelemetry traces used to operate the service and respond to incidents.

We use the data above to (a) provide and operate the service, (b) authenticate you and protect your account, (c) bill subscriptions and meter usage, (d) detect and prevent abuse, (e) communicate with you about your account or service incidents, and (f) improve the product through aggregated and anonymized analytics. We do not train foundation models on your code, prompts, or workspace content.

When you connect your own provider API keys (OpenRouter, Anthropic, OpenAI, Google AI, Vortex AI, and others), your prompts and tool inputs are sent directly to those providers and are subject to their privacy practices. When you connect MCP servers, GitHub, or other tool integrations, traffic flows to those services per your configuration. We do not control third-party services and are not responsible for their data handling.

The ADA desktop application is designed for local-first execution: filesystem reads, code edits, terminal commands, and browser automation run on your machine. Outbound traffic from the desktop is limited to (a) your configured backend, (b) LLM providers you have enabled, and (c) MCP servers and explicit web fetch / web search calls.

We share personal data only with the processors needed to operate the service — authentication (Clerk), payments (Stripe), cloud infrastructure (Railway and the hosting providers it depends on), observability (Sentry, OpenTelemetry sinks where configured), and product analytics (where enabled). Each processor has a contract that restricts how they use your data. We do not sell personal data.

Account and billing records are retained while your account is active and for the period required by tax and compliance law. Usage and diagnostic data is retained for operational and audit purposes for up to 24 months unless a shorter period is required by law or your plan. You can request export or deletion of personal data from the dashboard or by contacting support; some records (e.g. invoices) are retained for legal compliance.

See the Cookie Policy for the complete list of cookies we set and your controls.

We use TLS in transit, encryption at rest for managed data stores, scoped API keys and rotation, least-privilege backend services, audit logging, and Sentry for incident capture. No service is fully secure; treat your account credentials and provider API keys as sensitive. Report security issues through the channel listed in our security policy.

Depending on your jurisdiction, you may have rights to access, correct, port, delete, or restrict processing of your personal data, and to object to certain processing. See our GDPR notice for EU/UK-specific rights. To exercise these rights, use the controls in the dashboard or contact support. We will respond within the timeframes required by applicable law.

Our infrastructure may transfer data across jurisdictions, including to the United States. Where required, we use contractual mechanisms (such as Standard Contractual Clauses) to protect data during such transfers.

The service is not directed to children under 13 (or the equivalent minimum age in your jurisdiction). We do not knowingly collect personal data from children.

We may update this Policy from time to time. Material changes will be communicated through the dashboard or by email at least 30 days before they take effect. Continued use after the effective date constitutes acceptance.