pagu — Privacy Policy

Last updated 10 August 2026

pagu is an expense tracker for iOS and Android. This page explains what the app stores and what it sends.

Your expenses stay on your device

Every expense you enter — the amount, the title, the date and the category — is written to a SQLite database inside the app's private storage on your phone. It is never uploaded, never synced, and never sent to us. There is no account to create and no server holding your entries. Deleting the app deletes the database with it.

What the app does send

pagu uses two Google Firebase services to understand whether the app works:

• Firebase Crashlytics — if the app crashes, it sends a stack trace along with the device model, OS version and app version, so the bug can be found and fixed.
• Firebase Analytics — records which screens get opened and basic aggregate usage, plus a randomly generated app instance identifier and coarse device and region information.

Neither of these carries the contents of your expenses. Amounts, titles and any category you create yourself are never included in an event.

Turning it off

Analytics and crash reporting can be disabled from your device's system settings for the app. Doing so has no effect on the expense tracking itself — the app works entirely offline.

Data we can identify you by

None. pagu has no login, collects no name, email address or phone number, and has no way to connect an install to a person.

Children

pagu is not directed at children under 13 and collects no information from them knowingly.

Changes

If this policy changes, the revised version will be posted here with a new date at the top.

Contact

Questions about this policy can be sent to nicolaselliot0212@gmail.com.