Privacy Policy for Aeviva Longevity OS

Effective date: August 6, 2026

Developer: Primealpha Research

Privacy contact: aevivanet@gmail.com

Aeviva Longevity OS (“Aeviva,” “the app,” “we,” or “us”) is a local-first wellness application. This policy explains what the app accesses, how information is used and stored, when information can leave the device, and the choices available to you.

1. Summary

• Aeviva does not currently operate an application server that receives your HealthKit, Health Connect, camera, microphone, or wellness-log data.
• Health and wellness records are stored in the app's encrypted or integrity-protected on-device database.
• The current release reads selected Apple Health or Health Connect data only after permission; it does not write health-platform data.
• Camera and microphone access is user initiated. Raw frames and raw audio are not retained by Aeviva.
• Derived features, measurements, quality reports, trends, consent records, and integrity receipts may be stored locally.
• Aeviva does not use health data for advertising, tracking, data brokerage, or third-party AI services in the current release.

2. Information accessed and stored on your device

Depending on the features you choose, the app may access or locally store:

• Local profile and age-band information;
• Wellness logs, supplements, activities, sleep-related inputs, and user-entered notes;
• Camera-derived pulse spot checks, signal-quality information, and non-diagnostic derived features;
• Voice-session timing and signal-quality features;
• Read-only HealthKit or Health Connect records that you authorize, such as heart rate, resting heart rate, sleep, and steps;
• Verified-device imports, permission decisions, consent receipts, audit records, and integrity evidence.

This information is used to display local wellness trends, calculate non-diagnostic wellness metrics, operate user-selected features, enforce safety boundaries, and provide integrity and deletion controls.

3. Camera and microphone

Camera and microphone access begins only after you choose a feature and review its disclosure. The app processes the live signal locally. Aeviva does not retain raw camera frames, raw video, or raw microphone audio. The app may retain derived numeric features, quality indicators, session timestamps, and tamper-evident receipts.

4. Apple Health and Health Connect

The current release requests read access only to data types connected to visible app features. Access is optional and controlled through Apple Health or Health Connect. Aeviva does not use this information for advertising or marketing and does not sell it.

Data stored by Apple Health or Health Connect is controlled separately by those platforms. Removing Aeviva's local copy does not automatically delete records held by Apple Health or Health Connect.

5. When information can leave the device

Aeviva does not automatically upload health information. Information can leave the device only through an explicit user action or a future feature that is separately disclosed and consented to. Examples include exporting a file, sharing a report through the operating system, or voluntarily including information in a support message.

Do not send health records, raw images, passwords, encryption keys, or other sensitive information to support unless specifically requested through an approved secure process.

6. Platform and store services

Apple, Google, mobile carriers, payment providers, or operating-system services may process app-download, purchase, subscription, crash, device, or diagnostic information under their own terms and privacy policies. That platform processing is separate from Aeviva's local health-data architecture.

7. External analytics, advertising, and AI

The current release does not include third-party advertising, behavioral tracking, a third-party analytics SDK, or an external large-language-model provider for health processing. The final signed application and every included SDK must be re-audited before publication. This policy must be updated if those practices change.

8. Security

Aeviva uses on-device storage, non-extractable domain-separated cryptographic keys where supported, transaction integrity checks, permission boundaries, and tamper-evident receipts. No technical system can guarantee absolute security. Device compromise, operating-system backups, shared devices, and user-initiated exports can affect confidentiality.

9. Retention and deletion

Local information remains on your device until you delete records through the app, choose Delete Account & Data, clear the application's storage through the operating system, or uninstall the app. Some platform backups may persist according to Apple or Google's settings and policies.

Instructions are available on the Local Data Deletion page. HealthKit and Health Connect records must be managed separately in Apple Health or Health Connect.

10. Children and teens

Aeviva is not directed to children under 13. The app restricts under-13 use. Teen access may require a guardian acknowledgement where implemented or required by law.

11. Medical and wellness boundary

Aeviva is a wellness and educational tool, not a medical device. It does not diagnose, treat, cure, or prevent disease and does not provide emergency services. Metrics and recommendations are non-diagnostic estimates. Consult a qualified healthcare professional before making health, medication, supplement, diet, or exercise decisions.

12. Your choices

You may decline camera, microphone, Apple Health, or Health Connect access. You may revoke permissions in system settings, delete local records, uninstall the app, or choose not to export information. See Privacy Choices.

13. Changes

We may update this policy when the app, law, SDK inventory, or data practices change. The effective date will be updated, and material changes will be presented in the app when required.

14. Contact

Primealpha Research
[LEGAL ADDRESS, IF REQUIRED]
Email: aevivanet@gmail.com

Template status: legal identity, address, support email, public URL, governing law, SDK disclosures, and final signed-build practices must be completed and reviewed before publication.