Jarly

Jarly — Privacy Policy

Last updated: 25 July 2026

The short version

Jarly is local-first. Your budget lives in a file on your device, and every feature of the app works with no account and no network connection.

There is one optional exception, and you control it: if you sign in with Google, Jarly keeps a private backup of your budget in Google Cloud Firestore so a new phone can pick up where the old one left off. Nothing is uploaded before you sign in, and signing out stops it.

There are no ads, no analytics, no crash reporting, and no third-party tracking SDKs of any kind — signed in or not.

What Jarly stores on your device

Everything you enter — your jars, their names and budgets, your logged spending, your notes, your bills, and your settings — is written to a single file in Jarly's private storage:

/data/data/com.honghp.jarly/files/jarly_data.json

Android protects that directory so other apps cannot read it. This file is the source of truth whether or not you ever sign in.

If you do not sign in

Nothing leaves your device. Jarly makes no network requests at all: there is no account, no telemetry, and nothing to opt out of.

Jarly does declare Android's INTERNET permission, because the sign-in and backup features need it to exist. The permission being present is not the same as it being used — with no account, no request is ever made.

If you sign in with Google

What we receive. Signing in uses Google as the identity provider. Jarly receives your Google account's user ID and email address, and stores them only as part of your device's authentication session. Jarly never sees your Google password.

What gets uploaded. One document, containing the same budget data listed above, stored at:

budgets/{your-user-id}

in a Google Cloud Firestore database. It holds your budget as text, a timestamp, a schema number, and your device model (so a future "which device last changed this?" feature has something to show). That is the whole document.

Who can read it. Only you. Firestore security rules restrict every document to the signed-in user whose ID matches it. The rules are in firestore.rules in this app's source. Google, as the infrastructure provider, processes the data under Google Cloud's terms; the developer can technically access the database as its owner but does not read user budgets.

What it is not used for. Your budget is not analysed, profiled, sold, shared, used for advertising, or used to train anything.

Turning it off. Settings → Backup & sync → Sign out stops all syncing immediately and leaves the budget on your phone exactly as it is.

Deleting your data

To have your backup document deleted outright, email the address at the bottom from the Google account you signed in with.

Permissions, and why

Jarly requests no location, contacts, camera, or storage permissions. Exported backup files go through Android's system file picker, which grants access to one chosen file rather than to your storage.

Backup files you create yourself

Settings → Export a backup writes your data to a .json file at a location you choose. Once exported it is an ordinary file. If you save it into a folder that syncs to a cloud service, that service then has a copy under its own privacy policy. This is separate from the Google backup above, and Jarly is not involved in that transfer.

Android's own backup

Jarly allows Android's standard backup and device-transfer mechanism to include its data file, so setting up a new phone can bring your budget with it. That transfer is performed by Android and, if you have it enabled, by Google's backup service under Google's privacy policy. Turn it off for Jarly in your Android settings if you would rather it did not.

Children

Jarly is not directed at children.

Changes to this policy

If this policy changes, the date at the top changes with it.

Contact

hoang.hong@bepoz.com.au