Last updated: 7 August 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:
- Budget names you write, their limits, the plant you picked and your alert threshold.
- Every expense: amount, date and the optional note.
- No-spend days and budget cycles.
- App settings: currency, cycle reset day, alert threshold, language, notification toggle.
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 25 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:
| Data | Leaves the device? | Where it goes |
|---|---|---|
| Budget names you wrote | No | — |
| Expense notes | No | — |
| Exact amounts of money | No | — |
An amount_bucket: a coarse range such as 0-10,
50-100 or 500+ |
Yes | Firebase Analytics |
| An internal budget identifier — a random id generated by the app, not the name you gave the budget | Yes | Firebase Analytics |
| Counts and flags: number of budgets, streak length, cycle number, whether an expense was backdated | Yes | Firebase Analytics |
| Standard Firebase identifiers: app instance id, device model, OS version, country, app version | Yes | Firebase 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
- Share your garden. The image Meadow creates contains only the plants, your budget names and status words such as “Thriving” or “Wilting”, plus an optional streak count. It deliberately contains no amounts of money. Where you send the image afterwards is up to you and is handled by your operating system’s share sheet.
- Export data (CSV). This creates a file containing your real expenses, including amounts and notes, and hands it to your operating system’s share sheet so you can send it wherever you choose. Meadow does not upload it anywhere and does not keep a copy.
- Opening a shared link. Meadow also opens links that start with
https://meadow.trucph.am, so that tapping a card someone shared with you brings you into the app. Such a link carries only an image identifier — never anyone’s budgets, amounts or notes — and opening it does not send anything to us.
6. Purchases and the paid upgrade screen
Meadow’s paid features run on RevenueCat on top of Apple’s and Google’s own billing. The upgrade screen you see is built into the app itself; it is not fetched from anywhere, and its prices come straight from the App Store or Google Play. Superwall is still linked into the app, but only to keep a record of whether you hold the paid upgrade — it no longer presents any screen to you.
Payment is always handled by Apple or Google — Meadow never sees your card details, and neither RevenueCat nor Superwall receives them.
- RevenueCat receives an anonymous app user id generated on your device, plus the receipt Apple or Google issues for a purchase or trial (which product, when it started, whether it is still active). It is what tells the app whether to unlock the paid features. It does not receive your budgets, your expenses or your notes.
- Superwall receives the same anonymous app user id, standard device information such as device model, OS version and app version, and one flag: whether the paid upgrade is currently active. Because the upgrade screen is no longer delivered by Superwall, it no longer receives events about that screen — whether it was shown, which variant, or whether you dismissed it. It does not receive your budgets, your expenses or your notes, and it never receives any amount of money.
7. Third-party services
- Google Firebase (Analytics, Crashlytics) — privacy information.
- RevenueCat — subscription state — privacy information.
- Superwall — record of the paid upgrade — privacy information.
- Apple App Store and Google Play — for downloading the app and for processing purchases.
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
- Turn notifications off at any time, in your system settings or in Meadow’s Settings screen.
- Delete everything that is on your device by uninstalling the app. Uninstalling does not reach the anonymous analytics, crash reports and purchase records already sent to the services in section 7 — those are held under each provider’s own retention period.
- To have those off-device records deleted, email hi@trucph.am. Tell us the date and rough time you last used Meadow so we can find the anonymous identifier; there is no name or email attached to it, so that is the only way to locate it.
- Ask us anything about this policy at hi@trucph.am.
10. Changes
If this policy changes we will update this page and the date above.