For help or privacy requests, contact Black and Blue at developer@blackandblue.co.in. Include HearthLedger, app/Android versions and a short description. For purchase help, include the purchase support identifier displayed in Settings. Do not send household records, card details, backup passwords or review access codes.
Keep a copy before changing devices
In Settings, choose Create encrypted backup and save it somewhere you control. Keep the password safely; we cannot reset it. The local ledger is excluded from Android's ordinary cloud backup and device transfer. Uninstalling can remove it. Restoring a backup replaces the current ledger, so back up anything you need to keep first. If a restore fails, read the result before continuing.
Imports and exports
Choose images or PDFs with Android's file picker. Text recognition processes images on-device; Google ML Kit separately handles technical app/device, installation, feature and performance records. Firebase choices do not control that SDK. Review recognized text before saving, or enter records manually. Claim PDF/ZIP exports organize selected evidence; they do not assess coverage or submit insurance claims. Exports are readable, unencrypted copies and remain outside the app until you remove them.
Purchases and Pro access
Use Restore purchase with the Google Play account used for the purchase. Purchase and restore require the store's actual result and may need network access. Optional Firebase choices do not disable billing. For missing access, email the displayed purchase support identifier and describe the result. A deletion request does not guarantee a refund.
Optional analytics and pending crash reports
Firebase analytics and local crash capture start off each app process; saved positive choices require a new choice after restart. These switches do not govern ML Kit technical records or billing. Pending-report checking has a separate disclosure and may initialize local crash capture until the process ends. The app prepares manual-report mode before its Firebase entry paths and keeps those paths unavailable if compatibility/storage preparation fails.
For an available batch, Send queues one request, Delete requests local deletion, and Not now leaves it undecided. Delivery and completed deletion are unconfirmed. A queued Send cannot be recalled; an initialized crash handler may continue local capture until process death after its switch is turned off.
Delete data or make a privacy request
There is no sign-in or cloud document account to close. Open Settings → Delete all local data, type DELETE and confirm; read any failure result. This does not clear telemetry choices, SDK identifiers or pending local crash reports. Saved exports/backups, purchases and provider records are separate. Use the pending-report controls for an available local crash batch. The privacy policy's deletion section explains retention and the email route for remote requests. Include the app name and purchase support identifier when relevant; do not attach records or passwords. Provider records and request scope must be identified before action; no fixed erasure deadline is promised.