Launching soon  ·  Free 7-day trial
Trust Center

Privacy Impact Assessment

Cureva Health | Personal & Family AI Health Companion for Caregiving

1. Executive Summary

Cureva Health operates a mobile application and supporting web infrastructure that enables patients and family caregivers to manage medications, track health vitals, coordinate care, and receive daily health check-ins from Eva, an AI-powered health companion. The application handles Personal Health Information (PHI) as defined under Canadian federal and provincial law.

This PIA concludes that Cureva's current technical architecture, data governance policies, and organizational controls adequately protect personal health information. All data is stored in Canada (AWS ca-central-1, Montreal), encrypted at rest and in transit, with uploaded documents encrypted using AES-256-GCM, and is never sold or shared for commercial purposes. Residual risks are low and are actively monitored.

2. Organization and System Description

2.1 Organization

2.2 System

The Cureva system consists of:

  • Mobile app: iOS and Android, built with React Native and Expo SDK. Launching on the Apple App Store and Google Play Store.
  • Backend API: Node.js REST API hosted on Railway (cloud infrastructure provider).
  • Database: Supabase (PostgreSQL), hosted on AWS ca-central-1 (Canada Central, Montreal, Quebec). All health data resides exclusively in this region.
  • AI processing: Eva's conversational health check-ins are processed by third-party AI language model providers in the United States, reached through an AI gateway. Cureva does not sell conversation data and does not use it to train AI models.
  • Notification delivery: Push notifications via Expo's notification infrastructure. No health data is included in notification payloads.
  • Billing: Stripe handles all payment processing. Cureva does not store credit card numbers.

3. Personal Information Inventory

Data ElementTypeSourceStorage LocationRetention
Medication names, dosages, schedulesPHIUser-enteredSupabase ca-central-1Until account deletion
Dose confirmation logs (taken / missed)PHIApp interactionSupabase ca-central-1Until account deletion
Vitals (blood pressure, heart rate, weight, glucose)PHIUser-enteredSupabase ca-central-1Until account deletion
Symptoms and health notesPHIUser-enteredSupabase ca-central-1Until account deletion
Eva conversation transcriptsPHIAI conversationSupabase ca-central-1Until account deletion
Health conditions disclosedPHIUser-enteredSupabase ca-central-1Until account deletion
Appointment dates and notesPHIUser-enteredSupabase ca-central-1Until account deletion
Name and email addressPersonal informationRegistrationSupabase ca-central-1Until account deletion
Push notification tokenDevice identifierApp registrationSupabase ca-central-1Until account deletion
Billing informationPaymentStripeStripe (not Cureva)Per Stripe retention policy

Cureva does not collect device contacts, precise geolocation, biometrics, or government identifiers (SIN, health card numbers).

4. Data Flows

4.1 Primary data flow

  1. User enters health data (medications, vitals, symptoms) in the mobile app.
  2. Data is transmitted over an encrypted connection to Cureva's backend API (Railway, hosted in the United States).
  3. Backend writes data to Supabase (AWS ca-central-1, Montreal). Data is encrypted at rest, and uploaded documents use AES-256-GCM.
  4. Authorized family caregivers linked to the account can view dose status and receive push notifications. Caregivers do not receive raw health data beyond dose status.

4.1a Optional medicine confirmation photo

For a medicine the user marks as "Important medicine" (off by default; a caregiver can enable it only with the patient's permission), the app opens the device camera and takes a tiny photo of the pill or bottle. On app versions with label checking, the device reads the label text on the phone (Apple Vision or Google ML Kit, offline) and compares it with the medicine name. The photo and its text are never uploaded or stored; the temporary file is deleted on the device immediately. Only the result ("confirmed", "label matches" or "label does not match", or "caregiver") and the dose time are saved. Risk: low. No new personal information is retained.

4.2 AI processing flow

  1. User initiates a conversation with Eva or responds to a scheduled check-in.
  2. The conversation content is sent from the Cureva backend to a third-party AI provider, through an AI gateway, over TLS.
  3. The provider processes the request and returns a response. Cureva does not sell conversation data or use it to train AI models.
  4. Eva's response and a summary are stored in Supabase ca-central-1 and used to build the user's longitudinal health context.

4.3 Third parties with data access

VendorPurposeData SharedLocation
Supabase / AWSDatabase infrastructureAll PHI (encrypted)ca-central-1, Canada
AI gateway and model providersAI (Eva) processingConversation contentUS
StripePayment processingBilling only, no health dataUS (Stripe infrastructure)
ExpoPush notificationsDevice token + notification text only (no PHI in payload)US
Google Analytics (GA4)Anonymous website analyticsAnonymous page views only, not in-appGoogle infrastructure

No health data is shared with advertisers, pharmaceutical companies, insurers, or data brokers. No health data is used for advertising targeting.

5. Privacy Risk Assessment

RiskLikelihoodImpactResidual RiskMitigation
Unauthorized access to health database LowHighLow Encryption at rest and in transit, least-privilege access, audit logging, Supabase row-level security policies.
Caregiver accessing more data than authorized LowMediumLow Caregiver access is limited to dose status and alert notifications. Raw vitals, symptoms, and Eva conversations are not accessible to caregivers unless explicitly shared by the patient.
AI vendor retaining health data MediumHighMedium Cureva does not sell conversation data or use it to train AI models, and sends only the conversation needed to answer. Provider-level no-retention settings are being evaluated.
Data breach or unauthorized disclosure LowHighMedium Encryption, access controls, and audit logging are in place. In the event of a breach, Cureva will notify affected users and the Office of the Privacy Commissioner of Canada within 72 hours, in compliance with PIPEDA's mandatory breach reporting requirements.
Session token compromise LowHighLow Tokens stored in device secure enclave (iOS Keychain / Android Keystore). Short expiry with refresh rotation. No tokens stored in plain text or in app-accessible storage.
User unable to exercise deletion rights Very LowMediumLow In-app account deletion is available at all times. Web-based deletion available at cureva.app/delete-account. Deletion is processed within 30 days with a confirmation email.

6. Compliance Mapping

RequirementLaw / FrameworkHow Cureva Satisfies It
Consent before collecting PHIPIPEDA, PHIPA, HIAExplicit informed consent obtained during onboarding and at each data type introduction. Users can withdraw consent by deleting their account.
Purpose limitationPIPEDA, PHIPA, HIA, GDPRHealth data is used only to provide the Cureva service. It is not used for advertising, research, or secondary commercial purposes.
Data minimizationPIPEDA, GDPROnly data necessary to deliver the medication management and health check-in service is collected. No speculative data collection.
Data residency in CanadaPHIPA (ON), HIA (AB), PIPA (BC)All PHI stored in Supabase AWS ca-central-1 (Montreal, Quebec, Canada).
Encryption at restHIPAA Security Rule, PHIPA, HIAEncryption at rest is applied at the infrastructure level (Supabase), and uploaded documents are additionally encrypted with AES-256-GCM. Supabase is SOC 2 Type 2, ISO 27001, and HIPAA certified. Cureva operates within this certified infrastructure environment.
Access controls and audit trailsHIPAA Security Rule, PHIPALeast-privilege access enforced. All administrative access to PHI is logged with timestamp and identity.
Breach notification (72 hours)PIPEDA (mandatory breach reporting)Incident response policy requires OPC notification within 72 hours for material breaches. User notification without undue delay.
Right to access and correctionPIPEDA, PHIPA, GDPRUsers can view and correct their health data in-app, generate a doctor report PDF, and download a full copy of your data. Written requests responded to within 30 days.
Right to deletionPIPEDA, GDPR, CCPAPermanent account and data deletion available in-app and at /delete-account. Processed within 30 days.
No sale of personal informationCCPA, PIPEDACureva's sole revenue is subscription fees. Health data is not sold, licensed, or shared for commercial purposes.

7. Outstanding Items and Roadmap

  • PHIPA formal registration (Ontario HIC): Planned Q4 2026. Required for formal partnerships with Ontario hospitals and long-term care facilities.
  • HIA formal registration (Alberta): Planned Q4 2026. Required for formal partnerships with Alberta Health Services and AHS-affiliated facilities.
  • SOC 2 Type 2 (infrastructure): Covered by Supabase, Cureva's database infrastructure provider. Supabase holds SOC 2 Type 2, ISO 27001, and HIPAA certification. Cureva operates within this certified environment. A Cureva-level SOC 2 audit (covering application layer controls) is a future consideration for large US enterprise partnerships.
  • EU GDPR Article 27 representative: Appointment in progress for EU/EEA users.
  • HIPAA Business Associate Agreement (BAA): Template prepared. Available on request for US healthcare organization partnerships. Formal HIPAA audit targeted for 2027.
  • Third-party penetration test: Scheduled for Q1 2027. Results summary will be made available to institutional partners under NDA.
  • HALO (Health Application Lightweight Protocol) approval: Targeted 2027. HALO is Canada Health Infoway's framework for approving digital health apps to connect directly into clinic EMR systems. HALO approval would allow physicians to launch Cureva from their existing EMR terminal without a separate login or manual patient data re-entry. Cureva's API architecture is being designed for HALO compatibility in advance of a formal application to Canada Health Infoway.

8. Sign-off

Prepared by
Taranjit Singh, Founder
Privacy Officer
Prabhjot Kaur, COO
Date issued
September 22, 2026
Next review
September 2027 (or upon material system change)

Need a signed copy or have procurement questions?

We respond to all institutional privacy requests within 5 business days.

Contact Privacy Team →