Privacy Policy — Bada!

In short

What data the app handles

Bada! stores on your device the information you enter yourself:

• income, expenses and logged transactions;
• categories, fixed expenses and their planning;
• savings goals and their contributions;
• app preferences: theme, language, currency, safety margin, reminder time;
• a short local log of the app's technical errors (see “Error log”).

This data is written to the app's private storage — the area Android reserves for each app, which other applications cannot read.

What data it does NOT handle

Bada! does not collect and has no way of reading:

• name, email, phone number or other identifying details;
• location;
• contacts, photos, messages or other phone content;
• advertising or device identifiers;
• usage data or statistics;
• error reports sent to anyone: the app keeps an error log on the phone only, and shares it only if you decide to (see “Error log”).

The app neither requires nor uses any connection to banks or payment providers.

Data transmission

None. The application does not send data to any server, ours or third-party — and published versions could not do so even if they tried, because they do not have the network access permission. There are no analytics, advertising, crash reporting or profiling services. The error log described below stays on the phone.

The app works entirely without an internet connection.

When data leaves your phone

Three features write files outside the app, and you turn each on yourself.

Export transactions (CSV)

Creates a file with the transactions of the year you are looking at. The file is handed to the Android share sheet, and you choose where it goes: saving it on the phone, emailing it, uploading it to a cloud service. From that point the file follows the rules of the destination you picked, not this app's.

Daily automatic backup

This is the one feature that writes data outside the app without asking you each time, so it deserves the full explanation.

You turn it on once, by picking a folder on your phone. From then on, once a day, Bada! writes a JSON file there containing all your filled-in years, your goals and your settings. It is always the same file, overwritten each time.

Two consequences you should know about:

• that folder sits outside the app's private storage — which is exactly why the file survives uninstalling the app, the whole point of a backup — so other applications with access to your phone's storage can read it;
• if the folder you picked is synced with a cloud service (Google Drive, OneDrive, Dropbox and the like), the file leaves your phone on its own, and from there it follows that service's rules.

You can leave it off forever: until you pick a folder, nothing is written anywhere. And you can stop whenever you want.

Export diagnostics

Creates a text file with the error log (see below). As with the CSV, the file goes through the Android share sheet and you choose where it goes, if you want to send it at all. The row appears at the bottom of Settings only when at least one error has been recorded.

Importing

Importing a CSV or a backup reads only the file you selected yourself, and nothing else.

Error log

When the app hits a technical error, it keeps a note of it on the phone, in a private storage key separate from your data. The log holds at most the last five errors and deletes them after thirty days.

For each error it stores the type, the message, the execution trace, the place in the app where it happened and the Bada! version. It does not store your transactions or your settings. An error message can, however, contain an amount: that is why the file is never sent on its own. You export it yourself from Settings → Export diagnostics, you can read it before sending it to anyone, and the log is not part of the backup file.

Likewise, when a save fails, the app notes on the phone that it failed (what, which year, the error message and when), not the data it was saving, so it can tell you at the next start. That note also stays on the phone.

Android automatic backup

Android provides a system-level backup feature that can include app data in your Google account backup. If you have it enabled on your device, Bada!'s data may be included.

It is an operating system feature, not an app feature: Google manages and encrypts it, and you can turn it off in your phone's Android settings (System → Backup). Bada! does not access it and receives nothing back from it.

Notifications

The daily reminder is a local notification: it is created by your phone, stays on your phone, and never passes through a server. The app does not use push notifications and has no way to send you anything from outside.

Android asks for notification permission the first time the app schedules the reminder, which is right after you finish setting the app up. You can deny or revoke it at any time without losing any functionality: without permission the reminder simply never arrives, and everything else works the same.

Permissions requested

Published versions of the app do not request internet access permission. This is not a statement of intent: without that permission Android itself prevents the app from making any network connection, whatever the code does. You can check it in the permissions list on the store page.

Why the store listing shows a longer list

If you open that list you will find more than three entries, and this is not a contradiction: an Android app inherits into its own manifest the permissions declared by the libraries it uses, including ones it never needs. In Bada!'s case they are almost all permissions for drawing the badge counter on the app icon in Samsung, Huawei, Sony, Oppo and other launchers, which come bundled with the notification code.

There is also one from Google Play, used to tell which advert an install came from. Bada! never queries it; and without network access it would have nowhere to send an answer anyway.

None of these permissions can read what you write in the app, and none of them can move your data off the phone.

Deleting your data

Uninstalling the app deletes everything held in its private storage, the error log included, along with it.

The automatic backup file is not deleted, and that is not an oversight: it sits in a folder you chose, outside the app's own storage, precisely so that it survives uninstalling. If you want it gone, delete it yourself from the folder where you keep it. The same goes for any CSV or diagnostics file you exported: those stay where you put them, and they are yours to manage.

You can also reset a single month from the app's settings.

Children

The app is not specifically directed at children and does not knowingly collect data from children — or, for that matter, from anyone.

Changes to this policy

If the app ever changes how it handles data, this page will be updated and the date at the top will change accordingly.

Contact

Questions about this policy: bada.aituoisoldi@gmail.com