The Care Nexus LogoCareNexus Docs

Privacy

How The Care Nexus handles, stores, and protects user health data.

Updated June 2026 5 min read

The Care Nexus is built with a privacy-first architecture. Medical data is highly sensitive, and every system design decision reflects strict protection principles. Patient records, prescriptions, and communication data are never sold, never shared with third parties, and never used for advertising.

Data Isolation Model

Every API request is strictly scoped to the authenticated user. The backend middleware validates the JWT token and injects the userId into all database queries. This ensures that:

  • Patients can only access their own medical data
  • Doctors can only access their assigned patients
  • Clinic admins can only access their clinic’s data scope

Data Collected

  • Account data — name, email, phone, role, DOB
  • Medical data — prescriptions, diagnoses, allergies, blood group
  • Appointment data — schedules, clinic, doctor, notes
  • Chat messages — encrypted and scoped to 1-to-1 conversations
  • Voice recordings — temporarily stored during transcription

Data Retention Policy

Medical records and prescriptions are stored indefinitely to maintain a complete health history. Chat messages are retained to ensure continuity of clinical communication.

Voice recordings used for transcription are stored in Cloudinary with a 90-day retention policy, after which they are automatically deleted. Authentication sessions stored in Redis expire after 7 days.

Security alignment

The system follows modern healthcare security practices including encryption at rest, role-based access control, and audit logging. Production deployments handling real patient data should still undergo formal compliance review (e.g., HIPAA, PDPA, or local healthcare regulations).