Privacy Policy

Dutch Defend is privacy-first and local-first by design. Core planning data lives on your device. This policy explains what stays local, what leaves your device when you choose to export or share, what APIs are called for reference data, and how consent works for monetization features.

Data Stored On Your Device

Core planning data is stored locally on your device. Sensitive values use encrypted secure storage; non-sensitive preferences use standard app storage.

Encrypted secure storage holds:

• Salary and income inputs
• Savings, debts, contracts, windfalls, and partner income
• Visa and permit expiry dates

Standard app storage holds:

• Name, language, and notification preferences
• Ruling dates and employment start date
• Consent toggle states

Demo Mode: When you run Dutch Defend in Demo Mode, none of your real financial inputs are used. Demo Mode calculations are based on a pre-built synthetic profile and are not linked to your data.

Exporting and Sharing

Dutch Defend includes two opt-in sharing features. Both use the operating system share sheet only — nothing is uploaded to Dutch Defend servers.

Calendar Export: When you tap Export Key Dates, the app generates a plain-text list of your upcoming financial milestones. You select which events to include, then share via the OS share sheet. Dutch Defend does not write events directly to your calendar, does not read your existing calendar contents, and does not require calendar permission.

Shareable Defense Summary: When you choose to share your Defense Summary, the app generates a text snapshot of your planning position. You see a preview before any share action fires. Once you share, the exported text is outside Dutch Defend's control. You are responsible for where you send or store it.

Reference API Calls

We fetch public reference data for app behavior. These calls do not include your full financial profile:

• /api/config: tax rules and feature flags
• /api/translations: localized UI strings
• /api/providers: provider metadata for contracts/offers
• /api/forex: exchange rates
• /api/inflation: inflation reference data

Monetization and Consent

Some monetization features use backend events and partner integrations. These are controlled by feature flags and your consent choices:

• Personalized Offers Consent: controls consent-based monetization event tracking.
• Partner Contact Consent: required before submitting advisor/partner lead forms.
• Affiliate Attribution: if enabled and consented, offer interactions may include attribution IDs and campaign context.
• Paid Features: checkout and entitlement flows may exchange purchase metadata with payment/subscription processors.

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.

Contact and Support Requests

If you contact Dutch Defend through the website contact or support form, your message is processed by Formspree (formspree.io), a third-party form provider. The information you choose to include in the message is used only to respond to your request. Please do not include sensitive financial, tax, visa, passport, BSN, bank, salary, or residence-permit documents in support messages. This is separate from app profile data, which remains on your device by default and is not sent through the contact form.

Third-Party Processors

Depending on enabled features, we may use:

• Formspree: contact and support form submissions on this website
• Frankfurter API: exchange-rate reference data
• CBS Open Data: inflation reference data
• Stripe: payment processing for paid report/subscription checkout flows
• RevenueCat: subscription/entitlement orchestration

These services may process limited operational metadata under their own privacy terms.

Retention and Deletion

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.

Policy Changes

We may update this policy when features, processors, or legal obligations change. Updates are posted on this page with a new “Last updated” date.

Questions?

If you have privacy concerns, please open an issue on GitHub or contact us through the app or via the support page.