NoteBox 3 in 1 — Privacy Policy

Effective date: 18 October 2026.

Package: com.urdunavees.app
Privacy and support contact: notebox3in1@gmail.com

This policy explains how NoteBox 3 in 1 handles information when you use Notes, Password Wallet, MoneyLink, Google sign-in and Google Drive backup. Cloud features are optional; the information transmitted depends on the features you choose to use.

Information you enter and store on your device

The app stores the notes, titles, text, images, folders, wallet titles, Web/App names, usernames and passwords that you enter. It also stores MoneyLink accounts and transaction details, amounts, dates, statuses, names, optional phone numbers, and settings such as card colors, themes and locks. Local queues retain changes that have not yet synced.

Android app-managed content is encrypted using authenticated encryption, with the device encryption key protected using Android Keystore. PINs control access to the relevant app sections. A wallet PIN is separate from the password used for encrypted cloud backups. No security method can guarantee protection against every compromised device, malicious keyboard, screenshot or person who can unlock your device.

Google sign-in

When you choose Google sign-in, Google supplies account information such as your name, email address, account identifier and, when available, profile image. Authentication tokens allow the app to access the Google services you authorize. NoteBox does not ask you to provide your Google account password to the app developer.

The app requests the Google Drive drive.file permission for files it creates or that you authorize it to access. Signing out or revoking access stops future authorized access; it does not by itself delete existing local records, Drive backups or MoneyLink cloud records.

Google API data is handled under the Google API Services User Data Policy, including its Limited Use requirements, for the user-facing functions described here.

Google Drive backups

If you enable backup, the app uploads your personal backup to your own Google Drive. Backups can include notes and their images, folders, Password Wallet entries, personal copies of MoneyLink records, lock settings and other supported app settings.

New encrypted backups encrypt their content on your device with AES-GCM. A separate backup password derives the encryption key using PBKDF2-SHA256. The Android app can retain a protected key on that device so it does not need to ask for the backup password for every sync. The password is not sent to the notification service or stored as a readable password inside the cloud backup. The developer cannot recover a forgotten backup password.

File metadata is not entirely hidden: Google Drive can store the file name, account email, modification times, size, record counts or backup descriptions outside the encrypted content. Earlier unencrypted backup files may remain in your Drive to protect against migration-related data loss. Enabling encryption does not mean that every historical file was deleted or retroactively encrypted. You can manage those files in Google Drive after verifying a working encrypted backup.

MoneyLink uses Google Firebase Authentication and Cloud Firestore for its online features. Cloud data can include account and participant identifiers, names, optional phone information entered in the record, invitation codes, transaction amounts, descriptions, dates, statuses, revisions and notification events. This is separate from your encrypted personal Drive backup.

When you share or join an account, its authorized participant can access the shared information. Treat an invitation code as private: another person who receives a usable code may be able to join the account under the app's invitation rules. MoneyLink shared records are not encrypted with your personal backup password, and the app does not claim end-to-end encryption for Firestore records. They are processed by the configured Firebase service and authorized notification backend under access controls.

Deleting or hiding an individual transaction from your own view does not remove the other participant's copy or necessarily erase its underlying cloud record. Other participants may keep records and exported copies. The app's existing account-deletion actions and participant confirmation rules are distinct from a request to delete your NoteBox service account and associated personal data.

Notifications

The notification feature uses Firebase Cloud Messaging and a Cloudflare-hosted dispatch service. To route a manually requested notification, the service processes authentication information, participant identifiers, device messaging tokens, account and transaction identifiers, notification event identifiers and status. A queued delivery can be retried. The service reads the relevant shared account to validate the recipient.

The app sends operating-system push requests through the explicit Resend Notification action. It does not create an operating-system push for every newly entered transaction automatically. Pending events, delivery attempts and accepted-device information may remain in the cloud; expiry of a delivery attempt is not deletion of the event record.

Notification text can include a record identifier and its status. Android permission, device settings, connectivity and service availability affect delivery. You can turn notifications off in Android settings. Notification providers may process connection and delivery information under their own policies.

Images, clipboard and sharing

The app uses the Android file picker when you choose an image. The current Android version does not request broad access to your contacts, precise location, microphone or photo library. Selected images become part of the records you save and may be included in an enabled personal backup.

Copy actions place the selected value on the system clipboard. Other software with permitted clipboard access may be able to read it. Be careful when copying passwords.

Receipts and statements are generated when you request an export. If you select a destination in Android's share window, that destination receives the exported information and handles it under its own policies. Copies held by a recipient cannot be withdrawn by deleting your local record.

Service providers and use of information

Information is used to provide local record storage, authentication, backup and restore, shared-account synchronization, notifications and user-requested exports, and to respond to support requests. Google/Firebase and Cloudflare process information for those services. Their infrastructure may process information outside your country. Requests necessarily expose ordinary connection information, such as an IP address, to the destination service.

The current app does not display advertisements, and Firebase Analytics collection is disabled. NoteBox does not sell your personal information or use the contents of your notes or wallet for advertising. Google and Cloudflare may maintain operational or security information under their service policies. Information you send voluntarily to support is used to address your request; do not send passwords, PINs, backup passwords or private encryption keys.

Provider policies: Google Privacy Policy, Firebase privacy information, and Cloudflare Privacy Policy.

Intended audience and children's privacy

NoteBox 3 in 1 is intended for users aged 13 and older. Its note organization, password management and personal ledger features are not designed for children under 13. This describes the intended audience; the current app does not automatically verify a user's age or a parent's consent.

Some countries and service providers require a higher minimum age or parental permission for particular online services or uses of personal information. Users must meet the applicable requirements before connecting those services. This policy does not replace any consent that the law or a provider requires.

A parent or guardian who believes that a child under 13 has provided personal information through NoteBox can contact notebox3in1@gmail.com to request review and deletion. Please identify the affected account without sending passwords, PINs or the contents of a child's private notes. We may need to verify the requester's authority before acting. See Retention and deletion below for the treatment of local information, Drive backups and shared records.

Retention and deletion

Your local information remains until you remove it through the relevant app functions or Android removes the app's local storage. Notes in the Recycle Bin remain recoverable until permanently removed. Uninstalling can remove local content, pending changes and device-protected keys; it does not delete remote backups or shared records. Confirm that a usable backup has finished before uninstalling.

Google Drive backups remain in your Google account until you remove them or the app's documented backup-management operations replace or remove them. You can review the app's backup folder, including historical files, in Google Drive. Revoking Google access alone does not delete these files.

Shared records, revisions, device registrations and notification events do not currently have a general automatic deletion schedule. Hiding a record is not a promise of permanent erasure. Records another participant has received may remain with that participant.

To request deletion of your NoteBox cloud account information or ask about retained data, email notebox3in1@gmail.com with the subject NoteBox data deletion request and identify the Google email used with the app. Do not send your password or PIN. We may need to verify that the request belongs to the account holder before acting. Tell us whether you mean your NoteBox cloud account, a particular shared record, or your own Drive backups. A support request does not automatically delete anything when submitted, and it does not delete your Google account. Any information that must remain to respect another participant's independent records or a legal obligation will be explained when the request is handled.

The current app does not provide a complete in-app NoteBox service-account deletion flow. You can contact support using the email above to request assistance. Signing out is not account deletion.

Changes and contact

This policy may be updated when the app's handling of data changes. The published version will show its effective date. For privacy questions or support, contact notebox3in1@gmail.com.