Privacy Policy
This policy explains what information VitalsPath may handle, how it is used inside the app, and how users can contact us with privacy questions.
Information you choose to record
Depending on how you use the app, VitalsPath may handle information such as medications, schedules, symptoms, mood entries, vitals, measurements, appointments, tasks, photos, voice notes, and profile details you choose to add.
Permissions
The app may request permissions that are directly related to the features you choose to use, including notifications, health data, microphone, photos, camera, contacts, calendar, reminders, and location. These permissions are used to support the corresponding in-app functions and can be managed by the user.
Use of information
Information handled by VitalsPath is used to support personal health organization features such as treatment planning, daily follow-up, reminders, measurements, appointments, widgets, and related user-selected functions.
Medical disclaimer
VitalsPath is not a medical device and is not intended to diagnose, treat, cure, or prevent any disease. It does not replace medical advice, diagnosis, treatment, or emergency assistance.
Contact
If you have questions about privacy or data handling, contact us through the support page.
How data is stored and which services are involved
App storage and iCloud sync
VitalsPath stores profile and health records in its app database and is configured to sync records through Apple CloudKit when an iCloud account and network are available. Profiles intentionally shared through the app may be available to people who accept an invitation, subject to the access selected by the owner. Sync can be delayed or interrupted. VitalsPath does not claim end-to-end encryption for every record or feature.
Apple Health and location
With Health access, VitalsPath reads or writes only supported data types approved in Apple's permission sheet; you can change access in iOS Settings. With location permission, the app can use location for map and local-context features. For weather, coordinates are rounded to about 1.1 km before the request is sent to Open-Meteo. Holiday lookup sends a year and country code to Nager.Date. Reverse geocoding uses Apple's MapKit/CLGeocoder.
Optional product analytics
Firebase Analytics collection is disabled until you explicitly enable analytics in the app. When enabled, the app sends defined product-interaction events and coarse feature or subscription context. The event contract excludes medication names, doses, symptoms, diagnoses, appointments, clinical timestamps and free-form text. The linked Google Analytics 4 property currently retains event-level data for 2 months and user-level data for 14 months. The setting that resets user-data retention with each new activity is enabled, so the user-level period can extend while activity continues. Google says this retention control does not affect standard aggregated reports. You can turn collection off again in app settings.
Crash and technical diagnostics
Firebase Crashlytics can collect crash reports and technical context such as app/build version, device model, operating-system version and locale. Crash reporting is enabled by default in production unless you turn it off in app settings. When disabled, the app deletes reports that have not yet been sent. Google retains received crash stack traces and associated identifiers for 90 days before starting removal from live and backup systems. Crash reports differ from product analytics and may contain diagnostic stack or breadcrumb data.
Purchases and subscriptions
Apple StoreKit/App Store processes payment and purchase transactions; RevenueCat receives the app-user identifier and transaction/entitlement information to support product availability, purchase restoration and entitlement checks. Purchase records and subscription entitlements are outside the analytics/diagnostics retention settings and follow the providers' terms and applicable obligations. Deleting or resetting VitalsPath data does not cancel an App Store subscription or currently send a customer-deletion request to RevenueCat. Contact vitalspath@gmail.com to request deletion of RevenueCat data; manage or cancel an App Store subscription through Apple's subscription settings.
Retention and requests
Health and profile data stored in the app remain on the device and in CloudKit until you delete them, except historical logs and reports subject to app retention controls. Medication-dose records and medication activity entries share a retention setting with 30, 90, 180 or 365 days or permanent storage; the default is 30 days. Appointment and condition activity entries follow their own category settings. Other activity types without a retention setting remain until you delete them. Professional reports default to 30 days and can be retained for 1–365 days. Cleanup runs when the app starts and when a retention setting changes. You can delete a profile or reset all app data under Settings > Data Management. A full reset erases local data and attempts to purge the CloudKit zone. If iCloud or a network connection is unavailable, local deletion still proceeds and remote CloudKit removal may not complete at that time; the app shows a warning during onboarding. Analytics and diagnostic retention are described above and differ by service. For access or deletion requests about a particular provider record, contact vitalspath@gmail.com.
VitalsPath
VitalsPath is designed for personal health organization and follow-up. It does not replace medical advice, diagnosis, treatment, or emergency care.