Last updated: March 5, 2026
Dutch Defend is privacy-first and local-first by design. This policy explains what data stays on your device, what data may be sent when monetization features are enabled, and how consent works.
Core planning data is stored locally in app storage and secure storage. This includes:
We fetch public reference data for app behavior. These calls do not include your full financial profile:
Some monetization features use backend events and partner integrations. These are controlled by feature flags and your consent choices:
You can disable or withdraw consent in app settings at any time. If consent is off, monetization tracking and lead/contact flows are blocked by design.
Depending on enabled features, we may use:
These services may process limited operational metadata under their own privacy terms.
Local app data can be deleted with in-app reset controls. Monetization event, lead, and order data retained on backend systems follows operational retention windows documented in release and compliance materials. You may request data deletion through support channels.
We may update this policy when features, processors, or legal obligations change. Updates are posted on this page with a new “Last updated” date.
If you have privacy concerns, please open an issue on GitHub or contact us through the app.