Privacy Policy
Last updated: May 22, 2026
Overview
Dango is an open-source analytics platform that runs entirely on your own infrastructure. We are committed to respecting your privacy. This policy covers the Dango marketing website (getdango.dev) and the Dango application itself.
Website Analytics
This website uses Google Analytics 4 with Consent Mode v2 to understand how visitors use this site.
- Analytics cookies are only set after you consent via the cookie banner
- If you decline, no cookies are set and no personally identifiable data is collected
- Data is retained for 14 months, then automatically deleted
- We do not use Google Analytics data for advertising
This website also uses Cloudflare Web Analytics, a privacy-first service that collects only aggregated metrics without cookies or personal data.
Cookies
This website uses a cookie consent banner. If you accept analytics cookies, Google Analytics will set cookies to measure site usage. If you decline, no analytics cookies are set. Your consent choice is stored in your browser's local storage so you are not asked again on each visit.
You can change your choice at any time by clearing your browser's local storage for this site, which will cause the consent banner to reappear.
Infrastructure
This website is hosted on Cloudflare Pages. Cloudflare may process standard HTTP request data (IP addresses, user-agent strings) as part of serving web pages and providing security. This is governed by Cloudflare's Privacy Policy.
The Dango Application
Dango runs entirely on your own infrastructure — your laptop, your server, your cloud. The application:
- Does not send telemetry or usage data to us
- Does not phone home or require an internet connection to run
- Stores all data locally in your DuckDB database
- Keeps all configuration on your filesystem
Your data never leaves your infrastructure unless you explicitly configure an external service (e.g., connecting to a cloud database).
External Links
This website contains links to external sites (GitHub, PyPI, documentation for dlt, dbt, DuckDB, and Metabase). These sites have their own privacy policies, and we are not responsible for their content or practices.
Contact
If you have questions about this privacy policy, please open an issue on GitHub.
Changes
We may update this policy as the project evolves. Changes will be committed to the project repository with a clear commit history. The "Last updated" date at the top reflects the most recent revision.