Privacy Policy

VitalNexa Wellness Platform — Your health data, protected by design

Version 1.1 Last Updated: April 7, 2026 Effective Date: April 7, 2026

Table of Contents

  1. Data Controller
  2. Our Commitment to Privacy
  3. Information We Collect
  4. How We Use Your Information
  5. Legal Basis for Processing
  6. How We Protect Your Information
  7. AI and Third-Party Data Processing
  8. HIPAA Compliance
  9. HITECH Act Compliance
  10. SOC 2 Alignment
  11. Additional Regulatory Compliance
  12. Data Retention & Deletion
  13. Your Rights (EU/EEA Residents)
  14. Your Rights (California Residents)
  15. Your General Rights
  16. International Data Transfers
  17. Cookies
  18. Children
  19. Contact Information
  20. Changes to This Policy

1. Data Controller

The data controller responsible for your personal data is:

Star's End Ventures, LLC dba VitalNexa
Operating from California, United States
Contact: privacy@vitalnexa.health

For all privacy-related inquiries, data subject requests, or complaints, please contact our Privacy Officer at privacy@vitalnexa.health.

2. Our Commitment to Privacy

Privacy by design, not by afterthought. Every architectural decision in VitalNexa is made with your data privacy as the primary constraint. We built encryption, isolation, and data minimization into the foundation of our platform — not bolted on later.

VitalNexa is built on three core privacy principles:

3. Information We Collect

CategoryData CollectedPurpose
Account InformationEmail address, full name, hashed passwordAuthentication, account management
Health RecordsUploaded files (.txt, .pdf)Health data extraction and analysis
Lab/Bloodwork ResultsBiomarker names, values, units, test dates, fasting statusTrend tracking and wellness insights
Chat ConversationsMessages between you and the VitalNexa AI assistantPersonalized wellness guidance
Health SummariesAI-generated summaries of your health statusContinuity of care across sessions
Audit LogsIP address, user agent, API actions, timestampsHIPAA-required security monitoring

What we do NOT collect: We do not collect location data, device fingerprints, advertising identifiers, social media profiles, browsing history, cookies for tracking, or any data from third parties without your explicit consent.

4. How We Use Your Information

We do not sell, rent, or trade your personal information or health data to any third party, for any purpose, ever.

Under GDPR and similar data protection regulations, we process your personal data based on the following legal grounds:

Legal BasisProcessing Activities
Consent (Article 6(1)(a) / Article 9(2)(a))Given at registration. Explicit consent for processing health data. You may withdraw consent at any time via account settings or by contacting us.
Legitimate Interest (Article 6(1)(f))Service improvement, security monitoring, fraud prevention, and maintaining the integrity of our platform.
Contract (Article 6(1)(b))Providing the service you signed up for — including account management, lab result analysis, AI wellness chat, and trend tracking.
Legal Obligation (Article 6(1)(c))Maintaining audit logs and breach notification as required by HIPAA, HITECH, and other applicable regulations.

6. How We Protect Your Information

VitalNexa employs multiple layers of security, each addressing different threat vectors:

Encryption at Rest

All sensitive data fields (chat messages, health record text, health summaries) are encrypted using AES-256-GCM with per-field unique salt and nonce values. This means even if the database were compromised, encrypted fields are computationally infeasible to decrypt without the encryption key.

MeasureImplementationStandard
Field-level encryptionAES-256-GCM, unique salt + 96-bit nonce per fieldNIST SP 800-38D
Key rotationVersioned keys (v1, v2...) with admin rotation endpointNIST SP 800-57
Password hashingbcrypt with automatic salting, cost factor 12OWASP recommendation
Key derivationPBKDF2-HMAC-SHA256, 600,000 iterationsNIST SP 800-132

Multi-Tenant Data Isolation

PostgreSQL Row-Level Security (RLS) policies enforce that each user can only access their own data. This is enforced at the database level, not the application level, preventing any application-layer bug from leaking data between users.

Authentication & Access Control

HIPAA Audit Trail

Every API request is logged with user ID, action, IP address, user agent, and timestamp. Audit logs are immutable and retained for the legally required period.

7. AI and Third-Party Data Processing

No personally identifying information ever reaches the AI model. This is enforced by an automated PII filter that runs on every outbound request.

VitalNexa uses Anthropic's Claude AI for wellness chat. Before any data is sent to the AI:

What Gets Stripped (Automatically)

PII TypeDetection MethodReplacement
User's full nameExact match + individual name parts[NAME_REDACTED]
Email addressesRegex pattern matching[EMAIL_REDACTED]
Phone numbersMultiple format patterns[PHONE_REDACTED]
Social Security NumbersXXX-XX-XXXX pattern[SSN_REDACTED]
Street addressesNumber + street type pattern[ADDRESS_REDACTED]
Dates of birthDOB/birthday context matching[DOB_REDACTED]
Medical record numbersMRN/Patient ID patterns[MRN_REDACTED]
Insurance/policy numbersPolicy/Member/Group ID patterns[ID_REDACTED]

What the AI Receives

What the AI Does NOT Receive

Anthropic's data use policy prohibits using API inputs for model training. Your conversations are not used to train AI models.

8. HIPAA Compliance

VitalNexa is designed to comply with the Health Insurance Portability and Accountability Act (HIPAA), including the Privacy Rule (45 CFR Part 164, Subparts A and E) and the Security Rule (45 CFR Part 164, Subparts A and C).

Administrative Safeguards

RequirementImplementationStatus
Security Management ProcessRisk analysis, security policies, audit loggingImplemented
Workforce SecurityRole-based access, principle of least privilegeImplemented
Information Access ManagementRow-Level Security, JWT authenticationImplemented
Security Awareness TrainingDeveloper security training programImplemented
Security Incident ProceduresIncident response plan with severity classificationImplemented
Contingency PlanDatabase backups, disaster recovery proceduresImplemented

Technical Safeguards

RequirementImplementationStatus
Access ControlUnique user IDs, JWT tokens, email verificationImplemented
Audit ControlsComplete API request logging with user, action, IP, timestampImplemented
Integrity ControlsAES-256-GCM authenticated encryption (tamper detection)Implemented
Transmission SecurityTLS/HTTPS for all data in transitImplemented
Encryption at RestAES-256-GCM field-level encryption with key rotationImplemented

Physical Safeguards

RequirementImplementationStatus
Facility Access ControlsCloud infrastructure with provider-managed physical securityImplemented
Workstation SecurityContainerized deployment, no direct database accessImplemented
Device and Media ControlsEncrypted volumes, secure file storageImplemented

Breach Notification Rule

In the event of a breach of unsecured protected health information, VitalNexa will notify affected individuals within 60 days, the HHS Secretary as required, and prominent media outlets if the breach affects more than 500 individuals in a state or jurisdiction.

9. HITECH Act Compliance

VitalNexa complies with the Health Information Technology for Economic and Clinical Health (HITECH) Act, which strengthens HIPAA enforcement:

10. SOC 2 Alignment

VitalNexa's architecture is designed to meet the AICPA's SOC 2 Trust Service Criteria. While we have not yet undergone a formal SOC 2 Type II audit, our controls are aligned with these standards:

Trust Service CriterionOur ControlsStatus
Security (Common Criteria)JWT authentication, bcrypt passwords, AES-256-GCM encryption, RLS isolation, account lockout, CORS restrictions, audit loggingAligned
AvailabilityDocker containerization, health check endpoints, database connection pooling, graceful error handlingAligned
Processing IntegrityInput validation (Pydantic schemas), UUID parameter validation, authenticated encryption (GCM tamper detection), database constraintsAligned
ConfidentialityField-level encryption, PII scrubbing before AI calls, Row-Level Security, encrypted file storage, key rotation capabilityAligned
PrivacyData minimization, user consent for collection, right to delete, transparent data use policy, no third-party data salesAligned

We plan to pursue formal SOC 2 Type II certification as we scale to production.

11. Additional Regulatory Compliance

CCPA / CPRA (California)

California residents have the right to:

GDPR Considerations

For users in the European Economic Area, we process health data under the legal basis of explicit consent (Article 9(2)(a)). Users have rights to access, rectification, erasure, data portability, and the right to withdraw consent at any time.

FTC Health Breach Notification Rule

As a health-related technology provider, we comply with the FTC's Health Breach Notification Rule, which requires notification to consumers, the FTC, and in some cases the media, following a breach of unsecured health information.

21st Century Cures Act

VitalNexa supports health data interoperability through FHIR-based import connectors, allowing users to bring their health records from Epic, Cerner, Quest Diagnostics, Labcorp, and other certified health IT systems.

12. Data Retention & Deletion

Data TypeRetention PeriodDeletion Method
Account informationWhile account is active + 30 days after deletionPermanent erasure from database
Health records & lab resultsWhile account is activeFile deletion + database record removal
Chat conversationsUntil user deletes them, or account deletionEncrypted records permanently deleted
Health summariesUntil account deletionPermanent erasure from database
Audit logs6 years (HIPAA requirement)Automatic purge after retention period

When you delete your account, all personal data, health records, lab results, chat history, and health summaries are permanently and irreversibly deleted within 30 days. Audit logs are retained for the legally required period with user identity anonymized.

13. Your Rights (EU/EEA Residents)

If you are located in the European Union or European Economic Area, you have the following rights under the General Data Protection Regulation (GDPR):

RightDescriptionHow to Exercise
Right to AccessObtain a copy of all personal data we hold about youUse the data export feature in Settings, or contact us
Right to RectificationCorrect inaccurate or incomplete personal dataEdit directly in the app (profile, biometrics)
Right to ErasureRequest deletion of your personal dataDelete your account in Settings
Right to Restrict ProcessingLimit how we process your dataContact us at privacy@vitalnexa.health
Right to Data PortabilityReceive your data in a structured, machine-readable format (JSON)Use the JSON export feature in Settings
Right to ObjectObject to processing based on legitimate interestContact us at privacy@vitalnexa.health
Right to Withdraw ConsentWithdraw your consent at any time without affecting the lawfulness of prior processingContact us or delete your account

You also have the right to lodge a complaint with your local Data Protection Authority (DPA). We will respond to all data subject requests within 30 days.

14. Your Rights (California Residents)

Under the California Consumer Privacy Act (CCPA) and California Privacy Rights Act (CPRA), California residents have the following rights:

To exercise your California privacy rights, contact us at privacy@vitalnexa.health with subject line "CCPA Request".

15. Your General Rights

To exercise any of these rights, contact us at privacy@vitalnexa.health. We will respond within 30 days.

16. International Data Transfers

VitalNexa stores and processes data on servers located in the United States and the European Union. If you are located outside the US, your data may be transferred to and processed in the US.

For transfers of personal data from the EU/EEA to the US, we rely on the following transfer mechanisms:

We ensure that any third-party service providers who process data on our behalf provide equivalent safeguards through Business Associate Agreements and data processing agreements.

17. Cookies

VitalNexa uses essential cookies only. Specifically:

CookiePurposeTypeDuration
access_tokenSession authentication (HttpOnly, Secure)Essential60 minutes
cookie_consentRecords your cookie consent preferenceEssentialPersistent (localStorage)
No tracking cookies. No analytics cookies. No advertising cookies. We do not use any third-party tracking scripts, pixels, or cookie-based profiling.

18. Children

VitalNexa is not intended for users under 16 years of age. We do not knowingly collect personal information from children under 16. If we become aware that we have inadvertently collected personal data from a child under 16, we will take steps to delete that information as quickly as possible. If you believe a child under 16 has provided us with personal data, please contact us at privacy@vitalnexa.health.

19. Contact Information

ContactDetails
Privacy Officerprivacy@vitalnexa.health
General Supportsupport@vitalnexa.health
Data Protection Requestsprivacy@vitalnexa.health (subject: "Data Request")
Security Concernssecurity@vitalnexa.health

20. Changes to This Policy

We may update this Privacy Policy from time to time. When we make material changes, we will:

Continued use of VitalNexa after the effective date of changes constitutes acceptance of the updated policy. If you disagree with any changes, you may delete your account at any time.