Last updated: 26 July 2026

Privacy Policy

Meadow is a local-first budgeting app. Your budgets, your expenses and your notes never leave your device. This page describes exactly what the app does and does not send anywhere. It was written against the app’s source code, not from a template.

1. Data that stays on your device

Everything you type into Meadow is stored in a database file (SQLite, via Drift) inside the app’s private storage on your phone:

There is no server copy and no backup held by us. If you uninstall Meadow, this data is deleted with the app and cannot be recovered by anyone, including us.

2. Anonymous usage analytics

Meadow uses Google Firebase Analytics to understand how the app is used. The app sends a fixed set of 21 product events — for example that a budget was created, an expense was logged, the garden was viewed, a streak milestone was reached, or a paywall was shown.

These events deliberately carry no financial detail:

DataLeaves the device?Where it goes
Budget names you wroteNo
Expense notesNo
Exact amounts of moneyNo
An amount_bucket: a coarse range such as 0-10, 50-100 or 500+ YesFirebase Analytics
An internal budget identifier — a random id generated by the app, not the name you gave the budget YesFirebase Analytics
Counts and flags: number of budgets, streak length, cycle number, whether an expense was backdatedYesFirebase Analytics
Standard Firebase identifiers: app instance id, device model, OS version, country, app versionYesFirebase Analytics

The amount_bucket is worth spelling out: it is a bucketed range, never the real number. The app is built so that logging a raw amount is not possible — the analytics layer only accepts the bucket type, never a number.

3. Crash reports

Meadow uses Google Firebase Crashlytics. If the app crashes, a report is sent containing the technical stack trace, the device model, the OS version and the app version. Crash reports do not include your budgets, amounts or notes.

4. Notifications

Alerts such as “this budget is running low” are local notifications produced by your own phone. They are not push messages: nothing is sent to a server to generate them, and no notification token is collected. Meadow asks for notification permission only after you have created your first budget, and the app works fully if you decline.

5. Sharing and export — actions you start

6. Purchases

Meadow’s paid features are planned to run on RevenueCat on top of Apple’s and Google’s own billing. In the current build this is not active: no purchase is processed and no payment data is collected. When it is enabled, payment itself is always handled by Apple or Google — Meadow never sees your card details.

7. Third-party services

Meadow contains no advertising SDK and no attribution or tracking SDK.

8. Children

Meadow is not directed at children under 13 and does not knowingly collect data from them.

9. Your choices

10. Changes

If this policy changes we will update this page and the date above.