Medfolio

Privacy policy

Effective: 13 October 2026 · Last updated: 16 October 2026

Medfolio is developed by Adeel Nawaz. This policy covers the Medfolio iOS and Android app and these privacy and support pages.

Information you add and how the app uses it

The app accesses the documents and images you choose to import, images you capture with its document scanner, and record details you enter. These can contain sensitive health and personal information, including names, dates, providers, prescriptions, test results, and other content in your documents.

Medfolio stores original attachments, record details, extracted document text, and search indexes in its local app storage. It processes them to organize records and make them searchable. Text recognition, classification, and extraction run on your device; documents are not sent to us or an online AI service for processing. Extracted information may be incomplete or incorrect. Check the original document.

Permissions and selected files

• Camera: used when you scan a document. Camera access is requested for this feature, not for background capture or health measurement.
• Photos and files: the system pickers give the app access to the images or files you select. Medfolio does not request broad photo-library or external-storage access. A selected file may come from a cloud provider you use.
• Face ID or biometrics: optional App Lock uses device authentication, which can include the system passcode or credential fallback where supported. Medfolio does not receive or store your biometric templates.

The app does not request microphone, location, contacts, or HealthKit/Health Connect access.

Storage, App Lock, and device backups

Records remain in local app storage until you delete them or remove the app's data. App Lock limits access to the app screen; it does not encrypt your vault or exported backups. The app relies on your device's operating system and security settings for storage protection. App Lock settings are kept in platform secure storage and are not included in manual backups.

Medfolio configures the vault to be excluded from automatic iCloud/device backups on iOS and automatic cloud backups and device-transfer backup on Android. This uses operating-system backup controls; it cannot control every third-party transfer tool or copies made by older app versions. Medfolio does not provide an automatic backup service.

Create a manual backup before changing phones, uninstalling, resetting, or losing access to your device. Without a usable saved backup, we cannot recover your records.

Exports and sharing you choose

When you export a backup or share an original document, you choose a destination through your device's sharing controls. ZIP backups contain your records and original documents and are not encrypted. The destination may be another app, a cloud drive, or another person. That destination handles the copy under its own policies. Store and share copies only where you trust them.

The app uses cache storage for temporary exports and restore staging and attempts to clean up temporary files after the operation. The operating system may also clear caches. Cleanup does not remove copies you save or share outside Medfolio. Restoring a backup replaces the current vault after validation and your confirmation.

Collection, sharing, and software components

Medfolio does not use your medical records for advertising or sell them. We do not operate an app analytics or remote crash-reporting service. The app uses Expo/React Native, Apple Vision and PDF components, and Google ML Kit for local functions.

Google ML Kit collects SDK diagnostics and usage data. According to Google's disclosures, this includes device and app information, an installation identifier, performance and error information, and configuration and event metadata. This telemetry is separate from your medical documents and extracted text, which are processed on-device. Google's Android disclosure states that the telemetry uses HTTPS and is not transferred to third parties.

See Google's Android SDK data disclosure, iOS SDK data disclosure, and privacy policy for its practices. Medfolio does not provide an in-app control to disable this SDK telemetry. Deleting a local record does not delete telemetry already received by Google.

The operating system, app store, and external services you choose may separately process information under their own policies.

Retention and deletion

You control the records held in the app. Open a record and use its delete action to remove it and its documents from the vault. Archived records remain stored; archiving is not deletion. You can delete an attachment separately from a record. Removing the app's local data or uninstalling the app removes the local vault according to your operating system's behavior.

Deletion in Medfolio does not remove existing exports, copies shared with others, or backups made outside the app. Delete those separately at their destination. We cannot remotely access, delete, or restore your local vault. There is no Medfolio account to delete.

Support and these web pages

If you contact support, we receive the address and information you send and use them to respond, troubleshoot the issue, and address privacy requests. Please do not send medical documents, names, identifiers, test results, or an unencrypted backup. Redact any screenshot before sending it.

Support correspondence is retained only as needed to handle the request and any applicable obligations. You can request deletion of correspondence by contacting support. Your email provider and the service used to receive support mail may also process the message under their policies.

These pages do not include a medical-record upload form. Visiting them sends normal request information, such as your IP address, browser information, and requested page, to the hosting provider (Cloudflare and its delivery infrastructure) to serve and secure the site. That information is separate from your app vault.

We use PostHog for cookieless website analytics: which pages are visited, links and buttons clicked, the referring site, and browser, device, and screen type. These pages set no analytics cookies and store nothing in your browser. PostHog counts visitors with a one-way hash of your IP address, browser details, and a random value that changes daily and is then deleted, so visits on different days are not linked and the hash cannot identify you. We do not record your session, build a profile of you, or use this information for advertising. It applies to these web pages only, not to the app.

Changes and contact

We will update this page and its date if our practices change. For questions about this policy or your information, email support@getmedfolio.app or use our support page.