Implementation disclosure

Privacy and local data

This page separates what the current Vezuna source does from what the website host does. It is a technical disclosure, not a final publisher legal privacy policy.

Publisher facts are not yet established. The repository does not provide a publisher legal identity, public privacy contact, or publisher retention commitments. This page therefore makes no commitments on their behalf. A publisher must supply and verify a final policy against the exact app and hosting configuration it ships.

App records stay in a local vault

Profiles, laboratory results, OCR candidates, medications, dose events, and local chat messages are stored in an encrypted, profile-isolated vault on the device. Camera captures, selected images, and PDFs are processed on-device for text extraction and OCR.

Android: AES-256-GCM with a non-exportable key in Android Keystore. Cloud backup and device transfer are disabled for app data.
iOS: AES-GCM through CryptoKit and NSFileProtectionComplete. The master key is a protected file, not a Keychain item.

No independent security audit or certification is claimed. These statements describe source behavior, not absolute privacy or security.

Optional health access

With permission, Vezuna reads heart rate, steps, and weight from Health Connect on Android or HealthKit on iPhone. Access is read-only and health data is read only when an import is requested. Denying health permission does not block manual records.

Camera and selected-image access support imports. Notification permission supports local reminders. Android also includes reboot handling for reminder rescheduling and Play licensing. Store declarations must reflect the merged release manifest, including SDK-added permissions.

Network and third-party boundaries

App-owned code contains no account system, application server, advertising SDK, analytics, telemetry, or health-data HTTP client. Android removes the INTERNET permission from the merged application manifest. The iOS build has no equivalent manifest guarantee and has not received a network audit.

Google Play and the App Store may handle purchase verification and planned model delivery. ML Kit, Health Connect, HealthKit, and the system share sheet have their own terms. App code does not provide health records to store services. This is not a final “no data collected” declaration: SDK behavior and the exact release build still require review.

PDF and CSV exports are plaintext. When you share an export or encrypted backup, its destination and protection are outside Vezuna’s vault. Vezuna cannot delete or manage copies stored by other apps or services.

Backup and deletion limitations

In-app backups are encrypted for restoration with the same device key. They do not provide user-passphrase, cross-device, or cross-app recovery. Changing app.vezuna or another application ID creates a separate installation and does not transfer an earlier sandbox or Android Keystore keys.

Removing the app deletes its sandbox, including the vault and downloaded models. It does not delete exports or backups already stored elsewhere.

Local models

Local model code exists, but the production model catalog is empty. When configured, inference runs locally through Llamatik/llama.cpp. Generated answers can be wrong and are not medical advice. Records, backups, and exports do not depend on model installation or AI licensing.

This website

The marketing and documentation site has no account, upload form, newsletter, advertising, analytics, or medical-record service. Documentation search runs in your browser against the static Pagefind index; it does not send search terms to a Vezuna server.

The site is hosted and delivered by Vercel. Vercel’s current privacy notice says it may receive end-user IP addresses, location derived from IP, system configuration, traffic, and request information while providing its services. Those practices and retention periods are governed by Vercel’s privacy notice, not by the Vezuna app’s local-storage design.

External links to GitHub, Vercel, and other documentation take you to services with their own privacy terms. No medical information should be included in ordinary website requests.

Questions and security reports

Use GitHub issues for privacy questions. Use the repository’s Security tab and private vulnerability reporting for security issues. No public privacy email address is currently provided.

Never attach real medical documents, screenshots of personal records, vault files, or backups. Use synthetic examples only.