Salvera Privacy Policy
Know what is stored, shared and deleted before entrusting an app with health information.
Last updated: October 18, 2026
Salvera is in development. These pages explain its intended use and available support routes. Ask support for the information that applies to your testing build before sharing health information.
1. Status and scope
Salvera is an Android medication-management and family-care project from NextFlow Apps. This notice covers pre-release privacy information and the website support route. Build-specific app data handling must be provided before health information is shared.
The existing policies for HushFlow, Noctra and Temvica describe those products. Their storage, advertising or analytics statements should not be assumed to apply to Salvera.
2. Health and account information
Before using a testing or released build, obtain the build-specific notice covering Google Sign-In identifiers and profiles, medication names and schedules, dose events, adherence, inventory, refills, caregiver invitations and relationships, daily check-ins and any appointment records.
3. On-device records and synchronized records
The final notice must identify which records stay on a device and which selected records are synchronized. The local database and settings behavior, cloud database contents, device backups and multiple-device behavior have not been verified for the pre-release app. Do not assume that signing in synchronizes every record or that clearing one device deletes a cloud account.
4. Care Circle consent and access
The Care Circle design calls for patient consent and permission-limited caregiver access. The actual fields shared, permitted actions, invitation lifetime, relationship removal and access-revocation behavior require confirmation for the build you use.
5. Health Connect
Health Connect is an optional integration in the development scope. The released notice must name the exact data types, read/write purposes, storage and any synchronization of that information. Review permissions in Android Health Connect settings; revoking a permission should not be confused with deleting copies already stored by an app.
6. Security and service providers
No claim of end-to-end encryption, universal encryption at rest, regulatory approval or health-sector certification is made here. Actual account/session security, network protection, database encryption, service providers, transactional email, diagnostic services and any third-party APIs must be confirmed before the policy is finalized.
7. Retention and deletion
Retention periods, server deletion behavior, local data removal, caregiver access removal and backup limitations are not specified in this pre-release information. You can contact support about account and data deletion. No immediate automated deletion is promised by this website.
8. Contact and updates
Developer: NextFlow Apps. Privacy contact: [email protected].
This pre-release notice was updated on October 18, 2026. A released build must provide its applicable data-handling information and effective policy date. Contact support for the notice that applies to your build.