Know where your MedBud data goes

Local app data

The “Me” calculator-default profile, household labels, calculator searches and inputs, dated calculator results, water and sleep histories, reminder details, and user-added records are stored in the app's private local storage. Records and medicine data use an encrypted local database; lightweight preferences and histories use private app storage.

Local does not mean invulnerable. Someone with access to an unlocked, rooted, compromised, or shared device—or to an operating-system backup—may be able to access locally stored information.

App lock and biometric unlock

When app lock is enabled, MedBud stores verification material instead of a readable PIN. Biometric unlock asks the operating system whether authentication succeeded. Fingerprint and face templates remain under the device's biometric system and are not available to MedBud or its developer.

Portable local export

A local export packages supported structured data and available attachment files into an encrypted .medbud archive. You choose where the archive is saved or shared. Once it leaves private app storage, you control its location, recipients, retention, and security. Import merges supported data rather than guaranteeing a full replacement of everything already on the device.

Optional Google Drive backup

After you connect a Google account, MedBud requests the private Drive appDataFolder scope. This lets the app work with its own hidden AppData container; it does not grant permission to browse ordinary Drive documents.

Disconnecting Drive does not automatically delete an existing AppData backup. Manage that copy with the relevant Google account controls. Check what a backup contains before deleting an original.

When network services receive data

• Google Play processes purchases and may provide a purchase token for entitlement verification.
• The developer service can receive a random installation identifier and configuration, entitlement, or reward-verification metadata.
• AdMob can process advertising and device event data where ads are enabled, but MedBud does not provide user-entered wellness content for targeting.
• Google receives authentication and backup traffic when you choose Drive backup.
• A reference website receives normal browser-visit data only after you tap its source link.
• Google Fonts can receive ordinary web-request metadata when you view these hosted pages.

Deletion and retention

Use in-app controls to delete individual history entries, records, reminders, and member labels or to disable notifications and app lock. Clearing app storage or uninstalling normally removes local app data, subject to operating-system backups. Separately exported archives and Drive backups must be deleted from their own destinations.