Privacy Policy for Wallet - Digital Card Holder
Privacy Policy for Wallet - Digital Card Holder
Effective Date: April 7, 2026
This Privacy Policy explains how we collect, use, and protect your information when you use the Wallet - Digital Card Holder application (Package Name: com.secured.digital.wallet.cards), hereafter referred to as "the App".
1. Local Storage of Sensitive Documents (No Cloud Uploads)
Your privacy regarding your personal documents is our highest priority. The App allows you to scan and store sensitive documents, including Identity Cards, Payment Cards, and Medical Records.
Strictly Local: All scanned documents, images, and text extracted via the document scanner are stored strictly locally on your device's internal storage using a secure local database.
No Remote Backup: We do not upload, transmit, host, or share your scanned documents, ID numbers, or financial card visuals to our servers, Google's servers, or any third-party databases.
2. Information We Collect Automatically (Analytics & Advertising)
While your documents remain offline, the App utilizes internet-connected third-party SDKs to analyze app performance, fix bugs, and serve advertisements. To facilitate this, the App automatically collects the following non-personally identifiable telemetry data:
Device Information: Device model, operating system version, and unique device identifiers (such as the Google Advertising ID or Firebase Instance ID).
Usage Data: Information on how you interact with the App, feature usage, and session durations.
Diagnostic Data: Crash logs, performance metrics, and error reports to help us improve app stability.
3. Third-Party Services and SDKs
The App integrates the following Google and Firebase SDKs. These services have their own privacy policies governing how they handle the data they collect:
Google Play Services (ML Kit): Used for on-device document scanning and edge detection. The scanning process occurs entirely on your device.
Google AdMob (ads-mobile-sdk): Used to display advertisements within the App. AdMob uses the Advertising ID (AD_ID) to serve personalized or non-personalized ads based on your device settings.
Firebase Analytics & Crashlytics: Used to monitor app usage, performance, and log app crashes.
Firebase Cloud Messaging & Remote Config: Used to send push notifications and update app configurations remotely.
For more information on how these services handle data, please review the Google Privacy Policy and the Google Partners Policy.
https://policies.google.com/privacy and the https://policies.google.com/technologies/partner-sites
4. Permissions Requested by the App
To provide its features and third-party services, the App requests the following Android permissions:
USE_BIOMETRIC: To secure the App using your device's native fingerprint or face scanner. Authentication is processed locally by your device hardware.
INTERNET & ACCESS_NETWORK_STATE: Required to serve ads, send crash reports, and retrieve remote configurations via Firebase.
POST_NOTIFICATIONS: To send you alerts, reminders, or updates related to the App.
com.google.android.gms.permission.AD_ID: To allow Google AdMob to serve relevant advertisements.
READ_PHONE_STATE: Required by certain underlying SDKs to manage app behavior during incoming calls or to determine basic device network status.
SYSTEM_ALERT_WINDOW & SYSTEM_OVERLAY_WINDOW: Used strictly to draw specific app features or lock screens over other applications to ensure your vault remains accessible and secure.
RECEIVE_BOOT_COMPLETED: To re-initialize necessary local background services or notification schedules when your device restarts.
5. Data Security
We employ industry-standard practices to protect your locally stored data:
App Lock: The App requires a custom PIN or Biometric authentication to access the vault.
Data Isolation: Data is stored within the App's isolated directory, preventing unauthorized access from other applications.
6. Data Retention and Deletion
Locally Stored Documents: Because your sensitive documents are not stored on our servers, you can delete them at any time using the in-app "Delete All" feature, or by simply uninstalling the App from your device.
Analytics/Ad Data: Data collected by Firebase and AdMob is retained according to Google's standard data retention policies. You can reset your device's Advertising ID at any time via your Android System Settings.
7. Children's Privacy
The App does not knowingly collect personally identifiable information from children under the age of 13.
8. Changes to This Privacy Policy
We may update our Privacy Policy periodically. We will notify you of any changes by posting the new Privacy Policy on this page and updating the "Effective Date."
9. Contact Us
If you have any questions or concerns regarding this Privacy Policy or our data practices, please contact us via email:
Email Support: cozer.console@gmail.com
Effective Date: April 7, 2026
This Privacy Policy explains how we collect, use, and protect your information when you use the Wallet - Digital Card Holder application (Package Name: com.secured.digital.wallet.cards), hereafter referred to as "the App".
1. Local Storage of Sensitive Documents (No Cloud Uploads)
Your privacy regarding your personal documents is our highest priority. The App allows you to scan and store sensitive documents, including Identity Cards, Payment Cards, and Medical Records.
Strictly Local: All scanned documents, images, and text extracted via the document scanner are stored strictly locally on your device's internal storage using a secure local database.
No Remote Backup: We do not upload, transmit, host, or share your scanned documents, ID numbers, or financial card visuals to our servers, Google's servers, or any third-party databases.
2. Information We Collect Automatically (Analytics & Advertising)
While your documents remain offline, the App utilizes internet-connected third-party SDKs to analyze app performance, fix bugs, and serve advertisements. To facilitate this, the App automatically collects the following non-personally identifiable telemetry data:
Device Information: Device model, operating system version, and unique device identifiers (such as the Google Advertising ID or Firebase Instance ID).
Usage Data: Information on how you interact with the App, feature usage, and session durations.
Diagnostic Data: Crash logs, performance metrics, and error reports to help us improve app stability.
3. Third-Party Services and SDKs
The App integrates the following Google and Firebase SDKs. These services have their own privacy policies governing how they handle the data they collect:
Google Play Services (ML Kit): Used for on-device document scanning and edge detection. The scanning process occurs entirely on your device.
Google AdMob (ads-mobile-sdk): Used to display advertisements within the App. AdMob uses the Advertising ID (AD_ID) to serve personalized or non-personalized ads based on your device settings.
Firebase Analytics & Crashlytics: Used to monitor app usage, performance, and log app crashes.
Firebase Cloud Messaging & Remote Config: Used to send push notifications and update app configurations remotely.
For more information on how these services handle data, please review the Google Privacy Policy and the Google Partners Policy.
https://policies.google.com/privacy and the https://policies.google.com/technologies/partner-sites
4. Permissions Requested by the App
To provide its features and third-party services, the App requests the following Android permissions:
USE_BIOMETRIC: To secure the App using your device's native fingerprint or face scanner. Authentication is processed locally by your device hardware.
INTERNET & ACCESS_NETWORK_STATE: Required to serve ads, send crash reports, and retrieve remote configurations via Firebase.
POST_NOTIFICATIONS: To send you alerts, reminders, or updates related to the App.
com.google.android.gms.permission.AD_ID: To allow Google AdMob to serve relevant advertisements.
READ_PHONE_STATE: Required by certain underlying SDKs to manage app behavior during incoming calls or to determine basic device network status.
SYSTEM_ALERT_WINDOW & SYSTEM_OVERLAY_WINDOW: Used strictly to draw specific app features or lock screens over other applications to ensure your vault remains accessible and secure.
RECEIVE_BOOT_COMPLETED: To re-initialize necessary local background services or notification schedules when your device restarts.
5. Data Security
We employ industry-standard practices to protect your locally stored data:
App Lock: The App requires a custom PIN or Biometric authentication to access the vault.
Data Isolation: Data is stored within the App's isolated directory, preventing unauthorized access from other applications.
6. Data Retention and Deletion
Locally Stored Documents: Because your sensitive documents are not stored on our servers, you can delete them at any time using the in-app "Delete All" feature, or by simply uninstalling the App from your device.
Analytics/Ad Data: Data collected by Firebase and AdMob is retained according to Google's standard data retention policies. You can reset your device's Advertising ID at any time via your Android System Settings.
7. Children's Privacy
The App does not knowingly collect personally identifiable information from children under the age of 13.
8. Changes to This Privacy Policy
We may update our Privacy Policy periodically. We will notify you of any changes by posting the new Privacy Policy on this page and updating the "Effective Date."
9. Contact Us
If you have any questions or concerns regarding this Privacy Policy or our data practices, please contact us via email:
Email Support: cozer.console@gmail.com
Comments
Post a Comment