All Bank Passbook

Privacy Policy

All Bank Passbook processes bank SMS on your device and stores your passbook records locally. The current app has no advertising, analytics, crash-reporting SDK or cloud sync.

Updated 14 October 2026

Your data at a glance

This policy explains the current Android app and, separately, the website that displays these legal pages. Local-first means your imported passbook is kept on your device, not in a developer-operated cloud account. It does not mean every feature works without the internet or that files you choose to share stay on your device.

What is handled, why, and where
InformationPurpose and locationYour control
SMS sender, message, date and identifierRead on-device to recognize supported bank messages. Recognized records retain source information in the private app database.Deny or revoke SMS permissions; delete imported app data separately.
Financial recordsBank identifiers, account suffixes, amounts, balances, transaction dates, descriptions and available payment references help build your local passbook.Review records and source messages; export needed records before deletion.
Notes, categories and settingsYour annotations stay in local storage. Preferences such as language, app lock, lock timeout and holiday state stay in private app preferences.Change settings and annotations in the app; Delete all data resets app records and preferences.
PDF, CSV and shared transaction textExports are generated in private cache. Opening or sharing content gives it to your selected viewer or receiving app.Choose the recipient and remove saved or shared copies yourself.
Holiday and website requestsOnline services receive ordinary connection metadata when contacted. These requests are separate from local SMS parsing.Avoid holiday refresh or external links if you do not want to contact those services.

How SMS becomes a local passbook

With SMS access, the app reads inbox messages and checks incoming messages against its supported bank parsing rules. Android grants inbox access, not a permission limited to bank senders: message text and sender information are examined locally to decide whether a message is supported. Unrecognized messages are ignored rather than imported as passbook entries.

  • Recognized entries may include debit or credit amounts, balances or outstanding amounts, account suffixes, bank identifiers, merchant details, payment methods, references and dates.
  • The database can retain the original recognized SMS text, sender, receipt time and SMS identifier so records can be connected to their source.
  • Notes and categories you add are stored with your local records. Do not put account passwords, card PINs or OTPs in notes.
  • The app parses messages locally; it does not upload your inbox or imported passbook to a developer server for analysis, advertising or cloud synchronization.
  • SMS formats and delivery vary. An unsupported, missing or delayed message may not produce a complete or accurate entry.

Android permissions and your choices

These are the six permissions currently declared by the app. A declaration is not the same as an approval: Android asks for runtime access where required. Some permissions, such as internet access, do not have a normal runtime approval dialog.

Declared permission names, purpose and impact
PermissionWhy it is usedControl and impact
android.permission.READ_SMSRead the inbox for supported transactions and bank balance replies.Deny or revoke in Android app permissions. Inbox import and reading balance replies here need this access; existing records are not erased.
android.permission.RECEIVE_SMSReceive incoming SMS for local bank-message handling.Deny or revoke SMS access. Incoming-message processing needs this permission; you can still read SMS in your phone's messaging app.
android.permission.USE_BIOMETRICUse Android's authentication prompt for optional app lock on supported devices.Manage app lock in Settings and biometrics in Android. Device credentials can be used; a secure device screen lock is required.
android.permission.CALL_PHONEPlace a bank-service call after you select a call action.Deny or revoke Phone access. The app can open the dialer instead; with access, a selected action can place a call directly.
android.permission.READ_PHONE_STATETrack call state for a balance-enquiry call.Deny or revoke Phone access. Tracked balance calling falls back to the dialer; you may need to confirm when the call ends.
android.permission.INTERNETDownload the public bank holiday list over HTTPS.No standard runtime prompt. Avoid refresh to avoid this request. External websites and apps also use their own connections.

Open Android Settings, find All Bank Passbook, and review Permissions; labels vary by device. Revoking access stops the relevant access but does not delete information already imported. The app opens SMS enquiry drafts in your SMS app rather than sending messages automatically.

Local storage and app lock limits

Records are stored in the app's private database and preferences, using Android's app storage boundaries. Optional app lock asks Android to authenticate you with supported biometrics or your device PIN, pattern or password. The app uses the system authentication result; it does not receive your biometric template.

  • App lock controls access to the app interface. It is not separate database encryption and does not protect a copy already exported or shared.
  • Use a strong device screen lock, keep Android updated, and choose a lock timeout appropriate for your device use.
  • Local storage is not a guarantee against device compromise, loss, or someone you authorize to unlock the device.

Internet use and external bank services

The holiday refresh feature requests HDFC Bank's public holiday list at hdfc.bank.in. The current client makes an HTTPS download with an app-identifying user-agent; it does not attach SMS, account records or passbook contents. The contacted server receives normal connection information such as your IP address and request headers. Its own practices govern any server-side logging or retention.

  • Calling a bank connects through your phone service and exposes the normal calling information to the carrier and recipient.
  • SMS enquiry drafts contain the destination and command you review. If you send them, the SMS app, carrier and bank handle the message.
  • Bank websites and bank apps opened from shortcuts handle your interactions under their own policies. Review the destination and use your bank's official guidance.

The current app source contains no advertising, analytics or crash-reporting SDK and no cloud sync for your passbook. These statements describe this app, not external banks, carriers, browsers or apps you choose to use.

Exports and sharing are your choice

PDF and CSV exports are generated locally from selected records. They can contain bank names, account suffixes, dates, descriptions, debit or credit amounts and balances. Transaction sharing can also disclose financial information. Even a masked account suffix does not make these files anonymous.

  • Opening an export lets the chosen viewer read it. Sharing sends the content to the app you select, which may store it locally, upload it or forward it according to its own behavior.
  • Check the selected records and recipient before sharing. Only share with people and services you trust.
  • Once another app or person has a copy, All Bank Passbook cannot recall it or delete their stored copy.

Retention, deletion and backup

Imported records and annotations remain in local app storage until removed through app controls or Android app-data removal. There is no developer cloud copy to restore your passbook from. The current app disables Android cloud backup, excludes private app data from device-transfer rules and keeps its database in Android's no-backup directory.

  • Delete all data in Settings: removes app records, notes, categories, import progress, preferences and private exports, and returns the app to onboarding.
  • Not deleted by that action: SMS in your phone's inbox, files saved outside the app, or copies already shared with another app or person. Remove these in the relevant app or location.
  • Permission revocation: does not erase imported records. Use deletion controls as well if you want to remove them.
  • Importing again: messages still present in your inbox can be imported again if you allow access and restart import.
  • Temporary exports: live in private cache, which Android may clear. The app attempts to clean up exports older than a day on app startup; this is not a guaranteed deletion deadline or a backup service.
  • Before clearing data, uninstalling or changing phones: save any exports you need in a secure location. Export files are records, not a promise of full app-state restoration.

This policy website is separate from the app

Loading these legal pages sends a normal web request to the website host, which may receive information such as your IP address, requested URL, browser user-agent and request time. This is separate from the Android app's local database: visiting this page does not give the website access to your phone's SMS or passbook.

The pages contain no analytics scripts, advertising integrations, forms or cookie-setting code. Website hosting may handle request metadata under its own practices; log retention can vary.

Practical privacy checklist

  • Review Android SMS and Phone permissions and revoke access you do not want to keep.
  • Review imported entries and their source SMS before relying on or sharing them.
  • Use app lock and device screen lock, while remembering their limits.
  • Delete app data and separately remove unwanted inbox messages and exported copies.
  • Review third-party policies before using bank links, sending SMS or sharing files.

Privacy rights depend on the laws that apply to you; nothing here removes those rights. This page describes practical local controls, not a claim that every privacy statute applies. If data handling changes, review the revised policy and its updated date. For responsibilities when using the app, read the Terms of Use.