Privacy Policy for TrackMedi

TrackMedi is published by RaadCraft Solutions, a software engineering studio based in Chattogram, Bangladesh. In this policy, "we," "us," and "our" refer to RaadCraft Solutions, and "the app" refers to the TrackMedi mobile app for Android.

This policy applies exclusively to the TrackMedi app. It does not govern other products we publish or the third-party services mentioned herein, which operate under their respective privacy policies. You may contact us regarding this policy at support@raadcraft.com.

TrackMedi allows you to create a secure backup of your records. This feature is entirely optional, available to all users at no cost, and only activates upon your explicit request.

TrackMedi secures your records on your device using AES-256-GCM encryption before creating a backup. The encrypted file reveals absolutely nothing about your health data or the number of records stored; the readable header contains only non-sensitive metadata (format, app and schema versions, creation time, and the public scrypt parameters and salt used for key derivation).

Your Passphrase

Only your passphrase can unlock your backup. We never store or transmit your passphrase. The app retains only a key derived via scrypt, stored safely in the device's protected keystore.

Passphrase Recovery

Because TrackMedi never stores your passphrase and cannot reset it, losing it means permanently losing access to your backup. The file cannot be decrypted without it.

Passphrase Length

While passphrases of four to six characters are permitted for accessibility, doing so triggers a security warning: short passphrases are significantly more vulnerable to offline brute-force attacks.

Updating Passphrases

Changing your passphrase applies only to future backups. Previously created files are not retroactively re-encrypted and will still require the original passphrase used at the time of creation.

For security reasons, backups strictly exclude the following:

• The encryption key protecting your local device database
• The key derived from your backup passphrase
• Premium entitlement or purchase status
• Google Drive connection or authorization tokens
• Onboarding status, in-app review state, and backup configuration
• Operating-system notification identifiers

You may direct backups to a local device folder or Google Drive. For local backups, you select the destination using Android's system folder picker. TrackMedi requests access only to that specific folder and never requests broad device storage permissions. Device-folder backups do not transmit data over a network.

Within that folder TrackMedi retains the seven most recent files matching its backup naming convention and deletes older matching files. Files that do not match are left untouched, but because a matching name is not proof that TrackMedi created the file, do not rename unrelated files to resemble TrackMedi backups. Clearing the designated folder in the app's Settings revokes this access and disables daily backups.

Daily backup is an optional feature, applying to whichever destination is currently selected. It is not a scheduled background task: the app checks when you launch it or return to it, and only once 24 hours have passed. It then writes a new file if your records or preferences have changed, or if it cannot confirm that the previous backup still exists. Changing your backup destination automatically disables daily backups until manually re-enabled.

Restoring from a backup replaces all current records in the app. The process authenticates the file, enforces a 25 MiB size limit, and rigorously validates every record and relationship before showing you what the file contains. Because the replacement cannot be undone, it requires two confirmations and a short delay before proceeding.

If you opt to use Google Drive for backups, the app requests a single restricted scope. It allows TrackMedi to view and manage only the files it creates, or that you explicitly select for it; it cannot access the rest of your Drive.

Requested scope

https://www.googleapis.com/auth/drive.file

Backups are uploaded to a visible "TrackMedi Backups" folder. The file is fully encrypted prior to upload, meaning neither Google nor TrackMedi can read its contents. Data is transmitted directly between your device and Google, and passes through no server of ours - we operate none.

The app locally stores the connected Google email address to display connection status, alongside a folder ID hint. It does not request offline access and does not store access or refresh tokens. The Google sign-in library manages the session dynamically.

Upon successful upload, the app retains the seven most recent backups in Drive and removes older ones. You may disconnect Google Drive at any time via Settings, which terminates the app's access but leaves existing backups in your Drive untouched.

The free version of TrackMedi utilizes Google AdMob to deliver advertisements. To select, deliver, and measure these ads, the Google Mobile Ads SDK may process the following data:

• Your device's advertising identifier and app set ID
• Approximate location derived from your IP address
• Device and app metadata (e.g., model, OS version, app version)
• Diagnostic metrics (e.g., app launch time, hang rate, energy usage)
• Ad interaction data (e.g., impressions, clicks, load failures)

Google utilizes this data for advertising personalization, analytics, and fraud prevention in accordance with its published disclosures. TrackMedi health data - including medications, dose history, and vital signs - is strictly isolated and is never sent to AdMob, used for targeting, or included in ad requests.

Advertisements are fulfilled by Google and select third-party ad technology providers. These providers act as independent data controllers under their own respective privacy policies:

• Google Privacy Policy
• How Google uses information from sites or apps that use its services
• Ad technology providers in AdMob

In jurisdictions where required by law (including the EEA, UK, and Switzerland), TrackMedi implements Google's User Messaging Platform to request explicit consent prior to displaying personalized ads. You may choose to allow or decline personalized advertising.

What follows depends on your answer. If you allow ads but decline personalization, they continue to appear and are selected from contextual signals rather than a profile built about you. If you decline outright, banners stop appearing altogether. Either way, no app feature or functionality is restricted.

Wherever that consent message applies to you, the app's Settings menu keeps an "Ad privacy settings" entry that reopens it, so you may withdraw or modify your consent at any time. It remains available after a premium upgrade, even though you no longer see ads. You may also reset or delete your device's advertising identifier through your Android system settings (Settings › Google › All services › Ads).

TrackMedi offers premium subscriptions or a lifetime purchase to remove advertisements. All financial transactions are processed securely by Google Play Billing.

We do not collect, process, or store your payment details, billing address, or Google account credentials. The app receives only the entitlement status it needs in order to switch ads off, and stores that status on your device.

Subscriptions are managed entirely through the Google Play Store, and refunds are governed by Google Play's refund policies:

• Manage Google Play Subscriptions
• Google Play Refund Policy

Notifications

Required for delivering local medication and appointment reminders. TrackMedi does not utilize remote push tokens or notification servers.

Exact Alarms (Android 12+)

Ensures dose reminders trigger at their precise scheduled time, bypassing system batching delays.

Battery Optimization Exemption (Optional)

Exempts TrackMedi from aggressive power saving that would otherwise delay or drop scheduled reminders. Declining it does not disable any feature.

Network Access

Utilized exclusively to request advertisements, verify premium purchases, and facilitate Google Drive backup uploads. It is never used to transmit health data to our servers.

Directory Access (Optional)

Required only if utilizing local backups. Android restricts TrackMedi's access solely to the single user-designated backup folder.

Permissions may be revoked at any time via your Android device settings. While revoking permissions will not lock you out of the app, it may severely impact the reliability of dose reminders.

We do not sell personal information. Because we do not collect your health records, we cannot and do not share them. Data is only processed directly from the app by the following three services:

Google may share advertising data with select third-party ad technology providers to facilitate the bidding and delivery of ads. No other advertising or analytics SDKs are integrated into TrackMedi.

We may disclose information we possess if legally compelled by law enforcement or regulatory authorities. However, because we operate no backend and therefore collect and store no user data or health records, there is functionally no personal data available for us to disclose.

Because your records are strictly stored locally, data retention is entirely under your control. You may delete your data via the following methods:

• Deleting specific medications, logs, or profiles directly within the app interface.
• Using the "Reset App Data" function in Settings, which permanently erases every health record the app has stored.
• Uninstalling the TrackMedi application from your device.
• Manually deleting backup files from your local storage folder or Google Drive.

Resetting app data securely clears the local database, backup keys, and configuration settings, which consequently disables automatic backups. A local reset does not affect previously exported backup files; those files remain under your control and require your original passphrase to decrypt.

Data processed by Google for advertising and purchases is retained according to Google's data retention policies. You may reset your device advertising identifier at any time via Android settings.

Depending on your jurisdiction (such as under the GDPR, UK GDPR, CCPA, or Swiss data protection laws), you may possess specific rights regarding your personal data. TrackMedi is designed to allow you to exercise these rights directly on your device:

• Access, correct, or erase your health records directly within the app interface.
• Export a secure, encrypted copy of your data at any time without requiring our intervention.
• Withdraw or modify your advertising consent via the app's privacy settings.
• Reset or delete your advertising identifier globally via Android device settings.
• Submit data subject requests directly to Google regarding advertising and purchase data.
• Object to or restrict processing, or request portability, by writing to us.
• Lodge a complaint with your local data protection supervisory authority.

Because we do not collect, transmit, or store your health data, we cannot fulfill requests to produce copies of data we do not possess. Our legal basis for processing limited data (such as identifiers for AdMob) relies on your consent where required, and our legitimate interest in maintaining and funding the application.

Google operates globally, so the advertising and purchase data it receives may be processed outside your country, including in the United States, under the transfer safeguards described in Google's own privacy policy. We transfer nothing ourselves, because we receive nothing.

Notice for California Residents: Displaying personalized ads via AdMob may constitute the "sharing" of personal information for cross-context behavioral advertising under the CCPA, despite no direct financial exchange or health data involvement. You may opt out of personalized advertising by resetting or deleting your advertising identifier in your device settings.

TrackMedi is intended exclusively for adults. The application is not directed at children, and users must be 18 years or older to use the app.

Standard privacy policies usually state they do not knowingly collect personal information from children. We go further: we do not collect personal information from anyone, at any age. Because the app has no accounts, no sign-up process, and no backend servers, nothing you enter ever reaches us. There is no store of children's data for us to hold, disclose, or delete, because there is no store of anyone's data.

To ensure compliance with advertising standards, TrackMedi strictly configures the Google Mobile Ads SDK to classify users as neither child-directed nor under the age of consent, capping all ad content at a PG rating.

Adults can track a child's medication by adding them as a care recipient. Those records remain encrypted on the adult's device, like every other record, and are never transmitted to us. If you believe we have inadvertently received personal information about a child (for example, through direct email correspondence rather than the app), please contact support@raadcraft.com, and we will promptly delete it.

TrackMedi mitigates security risks primarily through data minimization: because we do not collect health data, there are no remote accounts to compromise or backend databases to breach. All local data utilizes encryption at rest.

Encrypted Storage

User records are stored within a SQLCipher database protected by AES-256 encryption. Both the database and its write-ahead log are maintained as ciphertext.

Keystore-Backed Encryption Key

The 256-bit encryption key is generated on your device and held in platform-protected secure storage, wrapped by an Android Keystore key and backed by hardware where the device provides it. This key never leaves the device and is never transmitted.

System Backup Exclusion

TrackMedi explicitly opts out of Google's Auto Backup service, so the operating system never copies your encrypted database into your Google account. The only copy that leaves the device is a backup you create yourself.

Manual Backup Security

User-initiated backups utilize a separate cryptographic lineage. Files are sealed using AES-256-GCM under a scrypt-derived key, ensuring that tampered files fail authentication during restoration.

If the local encryption key is lost (e.g., due to a factory reset or migrating hardware without an authorized backup), the existing database cannot be decrypted by anyone, including our team. In such cases, recovery is only possible using an exported backup file and your original passphrase.

While we employ robust encryption, no method of electronic storage or local device operation is completely immune to compromise. We cannot guarantee absolute security against malware or unauthorized physical access to an unlocked device.

We reserve the right to update or modify this Privacy Policy to reflect changes in functionality or legal requirements. The "Last updated" date at the top of this document indicates the effective date of the current revision.

Material changes to our data practices will be communicated within the application or via the Google Play Store listing prior to implementation. If a change requires explicit user consent, we will request it natively within the app.

If you have questions, privacy requests, or concerns regarding this Privacy Policy, including inquiries from regulators or application store reviewers - please contact us using the details below:

Email

support@raadcraft.com

Publisher

RaadCraft Solutions

D-U-N-S® Number

73-223-6807

We strive to respond to all inquiries within one business day.