Privacy policy
This policy explains what Cracker (“the app”) does with your information. The short version: it collects nothing, transmits nothing, and cannot — the release build has no network permission. Everything below is a description of a design, not a promise about a practice.
Version 1.0.0 · Effective 6 September 2026
No personal data is collected, transmitted, sold, shared or processed by the app's creator or by any third party. There is no account, no sign-in, no server, no analytics, no advertising, no crash reporting and no third-party tracking of any kind.
1 · Who this applies to
This policy covers the Cracker Android application. The app is offered as-is by an individual developer. There is no company, no service and no backend behind it. Using the app means you accept this policy and the terms and conditions.
2 · What the app stores, and where
Everything you enter or import is stored only in the app's private storage on your device. Nothing is uploaded, backed up to a cloud, or copied anywhere else.
| What | Where it is kept |
|---|---|
| Cards, transactions, rewards, redemptions, categories, people, settings | A SQLCipher-encrypted database in the app's private storage. The 256-bit key is generated on your device and held by the Android Keystore. |
| Your name, date of birth and card digits | Keystore-backed secure storage (AES-GCM), not in the database. Optionally sealed under a second key that the hardware releases only on a fingerprint. |
| Imported statement PDFs | Read from wherever you picked them and parsed on the device. The app keeps the extracted transactions and a hash of the file to detect a re-import — not the PDF. |
| Statement passwords | Never stored. Only the identifier of the rule that opened a file is kept, so the password can be rebuilt next month. |
| Backup files and CSV exports | Written to a location you choose, on your device or wherever you send them. Once written they are outside the app's control. |
3 · What the app sends
Nothing, and it cannot
The release build of the app declares no INTERNET permission. Android enforces this at the operating-system level: the process cannot open a network socket. It is not a setting inside the app, and it is not something the developer asks you to take on trust — you can read it on your own phone under Settings → Apps → Cracker → Permissions, where no network entry appears. An automated check fails the build if the permission, or any SMS, location, contacts or call-log permission, is ever reintroduced by the app or by one of its dependencies.
Android's own cloud backup is disabled for this app (allowBackup="false"), because backing the database up off the device would defeat its encryption.
4 · Permissions the app requests
| Permission | Why, and when |
|---|---|
| USE_BIOMETRIC | To show the fingerprint prompt for App lock and the identity seal. It grants access to nothing except the prompt itself, and the app works without a fingerprint sensor. |
| POST_NOTIFICATIONS | Requested only at the moment you switch payment reminders on. Never at launch. Reminders are scheduled and fired entirely on the device. |
| RECEIVE_BOOT_COMPLETED | So reminders you have already scheduled survive a restart instead of silently disappearing. |
| ACCESS_NETWORK_STATE | Added by Google Play's billing library, which backs the Donate screen and checks for a connection before it talks to the Play Store app. It reads whether a network exists; it grants no way to use one. INTERNET is still absent. |
| File access | Through Android's own file picker, one file at a time, when you import a statement or write a backup or export. The app receives only the file you choose. |
The app requests no SMS, location, contacts, call-log, camera, microphone or advertising identifier permission, and holds no device identifier of any kind.
5 · Third parties
One. No analytics provider, no advertising network, no crash reporter, no cloud storage provider and no bank integration. The app never contacts your bank; it reads the statement file you hand it. Open-source components bundled inside the app (for storage, encryption, PDF reading, notifications and fonts) run entirely on your device and transmit nothing.
The one is Google Play, and only if you choose to donate. Settings → Donate offers a yearly amount taken through Google Play's billing system. Google takes the payment, holds the receipt and handles renewal and cancellation under its own terms and privacy policy. This app has no internet permission and talks to the Play Store app on your phone, not to Google: it sees that a subscription exists, acknowledges it so it is not refunded, and stores nothing about it — no token, no amount, no date. A donation is voluntary and unlocks nothing.
One thing to be plain about. Google's billing library bundles a Google diagnostics component that would report the library's own usage to Google if it could. It cannot: the permission it needs is the internet permission this app removes from the build, and the operating system enforces that. It is present and inert, and this paragraph exists so that finding it inside the app is not a surprise.
6 · Children
The app is intended for adults managing their own credit cards. It collects no information from anyone, of any age, so it cannot knowingly collect information from a child.
7 · Your control over your data
Because your data never leaves your device, every right you might want to exercise over it is exercised directly in the app rather than by making a request to anyone:
- Access and portability — Settings → Export a copy writes every transaction as a CSV.
- Correction — every card, transaction, category and person is editable.
- Erasure — Settings → Erase everything destroys the encryption key, the database files including the write-ahead log, the identity vault and the biometric seal. Uninstalling the app removes its data too.
- Withdrawing a permission — revoke notifications in Android settings at any time; the app degrades gracefully.
There is no account to close and no request to file, because there is no recipient of your data to file it with.
8 · Security, and its limits
The ledger is encrypted at rest, the identity fields are held in hardware-backed storage, and both can be put behind your fingerprint. What that protects against is someone who obtains the storage — a stolen phone image, a device backup, a file copied off.
It does not protect against: a phone someone else can already unlock while App lock is off, a compromised or rooted device, files you export or share yourself, or screenshots. No security measure is absolute, and none is warranted here.
9 · No grievance officer, no responsibility assumed
No grievance officer or data protection officer is appointed, and no support desk is operated. Questions about this policy or the app can be sent to praveen.dev.mys@gmail.com, which is a contact address rather than a support channel and carries no undertaking to reply. It cannot reach your data either way: the app processes no personal data outside your own device, holds no records about you, and has no ability to access, retrieve, restore, correct or investigate anything on your phone.
The app and its creator accept no responsibility or liability whatsoever in connection with your use of the app or with any data held in it — including its loss, corruption, disclosure or inaccuracy, and including any financial consequence of relying on it. The app is provided as-is, without warranty of any kind. Your data is yours, on your device, and keeping it — and keeping a backup of it — is entirely your responsibility. See the terms and conditions.
10 · Changes to this policy
If this policy changes, the updated version ships with a new version of the app and carries a new date. Since there is no way for the app to contact you, checking this page or the copy inside the app under Settings → Privacy policy is the only notice there will be. Continuing to use the app after a change means you accept it.