Privacy policy
Muny, Hearth and Arden for Android
The apps connect your phone to a server you run. Your data lives on that server, not with me. This page covers the Android apps Muny (io.github.mikedmor.muny), Hearth (io.github.mikedmor.hearth) and Arden (io.github.mikedmor.arden), published by Michael (mikedmor).
Last updated 17 November 2026.
In short
- I don't collect, receive, sell or share any of your data. There are no accounts with me.
- No ads, no analytics, no tracking.
- The app only talks to the server address you enter, plus, if you turn notifications on, the notification services described below.
Your server
Everything you see in the app (your finances in Muny, your family's calendar and devices in Hearth, your chats in Arden) comes from the server you set up and run yourself. The app sends what you type and do to that server, the same as its web page would. That server is yours: what it keeps and for how long is up to you and how you've set it up. I have no access to it.
What the app keeps on your phone
- Your server's address and whether to ask for your fingerprint or screen lock.
- Your sign-in to your server (cookies), so you stay signed in.
- The web app's own storage and cache, which lets it open quickly and, where the app supports it, offline. Muny's offline copy is encrypted with a key that never leaves the phone, and is deleted when you sign out.
- Notification keys, if you turn notifications on: an encryption key pair made on the phone, used to read your alerts.
This stays in the app's private storage, isn't backed up to the cloud, and is removed when you uninstall the app or clear its storage.
Notifications
Only if you turn them on in the app. Then:
- The phone gets a push token from Google's Firebase Cloud Messaging and hands it, with a public encryption key, to your server.
- For each alert, your server encrypts it for your phone and sends it through the apps' push relay (a small service on Cloudflare that I run) to Google, which delivers it. Only your phone can decrypt it.
- The relay and Google see only the push token and encrypted data: never what the alert says. The relay stores nothing and keeps no logs.
- Without Google: if you choose a UnifiedPush app (such as ntfy) in the app's Server and lock settings instead, your server sends the encrypted alert straight to that app's server, with no relay and no Google. That push service then sees only the encrypted data.
- Turning notifications off in the app deletes the token and the keys. Whoever runs the server can also turn app notifications off for everyone (for Muny,
MUNY_PUSH_RELAY=off).
Google's handling of push tokens is covered by Google's privacy policy; Cloudflare's by Cloudflare's.
Permissions
| Permission | Why |
|---|---|
| Internet | To reach your server. |
| Notifications | To show your server's alerts. Asked only when you turn them on. |
| Biometrics | To ask for your fingerprint, face or screen lock. The check happens on the phone; the app never sees your fingerprint. |
Files you choose to upload are read only when you pick them. Downloads you open are saved to your Downloads folder or handed to your phone's viewer.
Children
The apps aren't directed at children. Hearth can show a family's start page to everyone in the house, set up and controlled by the household's own admin.
Deleting your data
See Delete an account or your data.
Changes and contact
If this policy changes, this page changes with it, with a new date at the top. Questions: github.com/mikedmor (open an issue on the app's project).