1. NextDose app privacy
The first release of NextDose is described as a local-first iPhone app. Based on the provided product requirements, medication entries, timing schedules, and dose history are stored locally on the user’s device.
The first release does not require a user account and does not provide cloud sync.
If the user enables reminders, NextDose uses local notifications on the device. Those notifications are generated from the data stored on that device.
NextDose supports Siri shortcuts for checking whether a medication is ready and for logging a dose. Those shortcut actions rely on the timing information the user entered into the app.
NextDose is a reminder and tracking tool only. It does not provide medical advice, dosage recommendations, or clinical validation of user-entered instructions.
2. What the app stores
Based on the current product description, the app may store information such as:
- Medication names and schedule details entered by the user
- Dose log history entered by the user
- Reminder preferences needed for local notifications
- Shortcut-related data needed for Siri shortcut support on the device
3. What the first release does not require
- No required account sign-up for the app
- No cloud sync in the first release
- No claim here that app medication history is transmitted to Xelseor servers in the first release
4. Website privacy for xelseor.com
For these public website pages, no embedded web analytics tooling was identified in the current Laravel codebase.
The broader Xelseor website does include a public project contact form at /contact. The current codebase shows that submissions to that form can store submitted contact and project details in the site database, record request metadata such as IP address and user agent in application logs, and use Google reCAPTCHA for spam protection when configured.
That project contact form is separate from the local-first behavior described for the NextDose app.
5. Changes
If NextDose later adds accounts, cloud sync, analytics, or server-backed features, this privacy statement should be updated before those changes are published.