Your ledger. Your control.

mCheckbook privacy notice

Draft for publication · Updated November 5, 2026

MCODE, Croatia, operates mCheckbook. Contact hello@mcode.hr for privacy questions, access or deletion requests. This notice explains how the app and its optional services handle information.

Your ledger on your device

Accounts, transactions, amounts, categories, payees, notes, check numbers, recurring schedules and reconciliation history are stored locally. The app does not connect to your bank, execute payments or read payment-card details. Local-only ledger content is not sent to MCODE merely by recording an entry. The optional privacy lock uses the operating system's authentication service; mCheckbook does not receive or store your fingerprint or face template. The operating system protects device storage. Exported CSV, QIF, HTML and JSON backup files are not encrypted by mCheckbook.

The app automatically starts a seven-day local preview the first time it opens. Its timing record is stored separately from your ledger to preserve the original expiry across normal relaunches. It does not start a purchase, require a card, renew or bill you. Restoring or deleting ledger content does not reset the timing record.

Optional cloud account and backups

You can use the local ledger without a cloud account. If you choose cloud backup, Google Firebase Authentication processes your email address, password and authentication/security records, including connection metadata such as IP address and user agent. Native sign-in credentials are stored through the operating system's secure storage. Browser development sessions are memory-only.

A backup is uploaded only when you explicitly choose to save it. It contains your ledger, financial amounts and any payees, notes or other personal information you entered, associated with your authenticated user ID. The app retains the most recent ten snapshots, up to 700 KB each. Backup is not continuous synchronization. You choose and confirm a snapshot before it replaces the device ledger; a previous local recovery copy is retained. Google Firebase provides authentication and database hosting. Cloud services may process data outside your country under their applicable contractual and transfer safeguards.

Purchases and subscription services

Apple or Google processes checkout and payment. RevenueCat processes app-user identifiers, purchase and receipt/transaction information, subscription state and related technical data to validate access and provide purchase analytics. If you sign into the optional cloud account, its user ID is linked to your subscription identity; this can associate purchases with your account. We do not send ledger rows to RevenueCat and do not receive your payment-card details.

RevenueCat also derives and retains country-level location from the IP address of app connections for customer and subscription analytics. RevenueCat states that the IP address itself is discarded after the country is determined. The app does not request GPS or precise device location.

There are no ads or cross-app advertising trackers in the app. We do not add general screen, behavior or event analytics; RevenueCat's purchase analytics is a separate service described above. No claim of zero data collection is made.

Exports, retention and deletion

Exports and sharing go to the destination you select. A destination such as another app or cloud drive follows its own privacy terms. You are responsible for copies you share or retain outside mCheckbook.

Local data stays until you remove it, replace it or uninstall the app, subject to operating-system behavior. Transaction trash and local recovery copies may retain removed records until cleared. To remove all local ledger and recovery data, use the app's privacy deletion controls. Cloud deletion is separate from local deletion.

Cloud settings lets you delete individual snapshots or delete your cloud account after password verification. Account deletion removes its active cloud snapshots and login; provider security logs and backups may be retained for limited periods. Firebase documents authentication IP logging for a few weeks and removal of other deleted authentication data from live and backup systems within 180 days. Subscription and store records are not deleted by the cloud-account button. Contact hello@mcode.hr to request associated RevenueCat data deletion; we may ask for enough information to verify ownership. Stores may retain transaction records for their legal and accounting obligations. Deleting data or an account does not cancel a store subscription: cancel it in the store's subscription settings.

Your choices and rights

You can read and export existing records, restore your own backups and remove personal data even after preview or paid access expires. Optional cloud use can be stopped by signing out and deleting its stored snapshots/account. You may contact us to request access, correction, portability, restriction or deletion as applicable to your location. We use account data to deliver the service you request, purchase data to administer subscriptions and relevant security data to protect the service; legal obligations may require some retention. You may complain to your competent data-protection authority, including Croatia's AZOP.

mCheckbook is intended for people aged 13 and older managing personal records and is not directed at children under 13. If you believe a child under 13 supplied personal information, contact us. Material changes to this notice will be reflected by an updated date and, where appropriate, an in-app notice.

Processor references

Firebase privacy and security, RevenueCat privacy policy, RevenueCat customer profile and country information, RevenueCat Apple disclosure guidance.

This website

These public support and policy pages use Firebase Hosting. Google processes request IP addresses for delivery, abuse prevention and usage analysis, retaining IP data for a few months. We do not add advertising, analytics scripts or account forms to these pages. See Firebase privacy information.

For information MCODE receives directly in support requests, retention depends on resolving the request, related disputes and applicable legal obligations. You may contact us about the information we hold. Data-protection concerns can also be raised with the Croatian Personal Data Protection Agency (AZOP).