// SECURITY

Security

Version:

This page is for security reviewers. It says what Daana runs, where, and what it sends to us.

Where Daana runs

Daana is a command-line tool. It runs on your own machines and against your own databases: PostgreSQL, BigQuery, Snowflake (experimental in the 1.0 release candidate) or DuckDB. In the 1.0 release candidate, your data does not go to Daana. Your pipelines run in your own warehouse, with the credentials and permissions you give them. Daana is closed source.

What Daana sends home

In the 1.0 release candidate, the Daana CLI sends no usage data, telemetry or analytics. It does not send your data, your model, your mappings, the SQL it generates, or counts or names of any of them. Your pipelines run entirely in your own warehouse. The CLI contacts the Daana license service (license.daana.dev) when you run daana license activate, to sign this machine in to your account (which starts a trial) and to fetch your license. On a machine activated this way, a deploy that needs more than the free limit also refreshes the license when it is due. Those calls carry your account identifier, your license token, the CLI version, a one-time sign-in code when you activate, and a fixed value that identifies the release, and nothing else. Our hosting provider also records each request's IP address and user agent, kept for 30 days. No device or machine identifier is created or sent. Everyday commands such as deploy and execute check your license on your machine; only that deploy contacts the license service. On Free, the CLI never contacts Daana. The license service keeps a record of each license request (which account, when, granted or not) to run your license, check license compliance, keep the service secure and improve it. Records are kept for as long as your account exists and for 12 months after it is closed.

Accounts and licenses

You sign in on daana.dev with Google or with an email link. We do not use passwords. One account is for one person. Your license is a signed license lease for your account. Keep your license credentials, such as activation codes, tokens and leases, private. If you think they have been misused, tell us at support@daana.dev. If a license ends, Daana falls back to Free tier capacity, and loads keep running.

Where our services run

The license service runs on Google Cloud in Frankfurt. The account database runs on Neon, on AWS in Frankfurt. Sign-in uses Google Identity Platform. Google may process sign-in data outside the EU, including in the US. Every provider is listed at daana.dev/privacy.

The Daana plugin

The Daana plugin for Claude Code and Codex is public and MIT-licensed. It does not bundle the CLI, credentials or warehouse access.

Reporting a vulnerability

Write to support@daana.dev with "Security" in the subject. Please do not test our systems for security weaknesses without our written permission (Terms, section 9).