đź“„Privacy Policy

Privacy Policy

Last Updated: 17 February 2026


1. Introduction

Welcome to Wallet Cards - Digital Holder ("we," "our," or "us"). We are committed to protecting your privacy and ensuring the security of your information. This Privacy Policy explains how we handle your data, permissions, and the third-party services used in our application.


2. Data Collection and Storage


A. Personal User Data (Local Storage Only)

We strictly adhere to a local-first data policy.


Card Details & Images: Any credit cards, debit cards, IDs, or documents you scan or enter manually are stored locally on your device using an encrypted database (Android Room).


No Cloud Sync: We do not upload, sync, or store your personal card details, images, or sensitive user data on any external server.


Control: You have full control to edit or delete this data at any time directly within the app.


B. Camera & Image Data


Usage: We use the device camera to scan cards and documents.


Processing: Image processing and text recognition (OCR) are performed on-device using Google ML Kit. We do not transmit video feeds or raw images to our servers.


C. Technical & Usage Data (Third-Party Collection)

While we do not collect your personal content, our application uses third-party SDKs (Software Development Kits) for functionality, advertising, and analytics. These partners may collect:


Device Identifiers: Advertising ID (GAID), Android ID.


Usage Data: Crash logs, performance data, and app interaction metrics.


Coarse Location: Approximate location data derived from IP addresses for ad targeting.


3. Permissions Usage

We request the following permissions to provide specific features:


CAMERA: Required to scan credit cards and documents physically.


USE_BIOMETRIC / FINGERPRINT: Used to lock and unlock the app locally for security. We do not store your biometric data; we only receive a "success/fail" signal from the Android system.


INTERNET / ACCESS_NETWORK_STATE / WIFI_STATE: Required by third-party SDKs (AdMob, Firebase, Facebook Audience Network) to load advertisements and report app crashes.


POST_NOTIFICATIONS: Used to send important app updates or alerts (via Firebase Cloud Messaging).


4. Third-Party Services & SDKs

Our app integrates the following third-party libraries. Their use of data is governed by their respective privacy policies.


Analytics, Crash & Performance Reporting (Google Firebase):

We use the Google Firebase suite to ensure app stability and performance.


Firebase Analytics: Collects usage data and user engagement metrics.


Firebase Crashlytics: Collects crash logs and stack traces to help us fix bugs.


Firebase Performance Monitoring: Collects data on app launch times, network request latencies, and screen rendering performance.


Firebase Remote Config: Used to customize app functionality without requiring an update.


Firebase Cloud Messaging (FCM): Uses Instance IDs to deliver push notifications and alerts to your device.



Advertising Networks:

We use the following networks to display advertisements. These networks may use device identifiers (Advertising ID) and coarse location to show personalized ads:


Google AdMob: 


Facebook Audience Network (Meta): 


AppLovin: 


IronSource: 


Vungle (Liftoff): 


InMobi: 


Pangle: 


Scanning Technology:


Google ML Kit: Used for on-device document scanning and text recognition. Images are processed locally and are not sent to Google servers.


5. Data Security

We implement industry-standard security measures to protect your locally stored data:


Encryption: Data is stored in a secure local database.


App Lock: We provide Biometric (Fingerprint) and PIN protection to prevent unauthorized access to the app on your device.


Offline Capability: The core functionality of viewing and editing cards works entirely offline, reducing exposure to internet-based threats.


6. Children’s Privacy

Our services are not intended for children under the age of 13 (or the applicable age in your region). We do not knowingly collect personal information from children. If we discover that a child has provided us with personal information, we will delete it immediately.


7. Changes to This Privacy Policy

We may update our Privacy Policy from time to time. Thus, you are advised to review this page periodically for any changes. We will notify you of any changes by posting the new Privacy Policy on this page.


8. Contact Us

If you have any questions or suggestions about our Privacy Policy, do not hesitate to contact us via mail.

Popular posts from this blog

đź“„Terms of Use