DDialyticFlow

Privacy and Data Retention Policy

Version 1.1, Effective 1 July 2026, Last Updated 26 June 2026

Applies to: Web, iOS, and Android Platforms

This policy is published in compliance with the Protection of Personal Information Act 4 of 2013 (POPIA). DialyticFlow is the Responsible Party as defined in POPIA. Please read this policy carefully before using the Platform.

1. Who We Are

Dialytic Flow (Pty) Ltd (“DialyticFlow”, “we”, “us”, “our”) is a South African company that operates a digital healthcare management platform designed for dialysis providers and their patients.

Registration Number: 2026/362831/07

POPIA Information Officer: privacy@dialyticflow.com

Deputy Information Officer: legal@dialyticflow.com

We have registered our Information Officer with the Information Regulator of South Africa as required by POPIA.

2. Scope of This Policy

This Privacy and Data Retention Policy (“Policy”) applies to all Personal Information collected through:

  • The DialyticFlow web application (browser-based);
  • The DialyticFlow mobile application (iOS and Android);
  • Our backend API services;
  • Any communications between you and DialyticFlow (email, in-app chat, notifications).

It applies to all User types: Patients, Nurses, Unit Managers, Organisation Supervisors, and Global Administrators.

3. Information We Collect

Patient Users

Data ElementPOPIA ClassificationPurpose
Full namePII: Direct IdentifierIdentity verification, session records
SA ID / Passport numberPII: Direct Identifier (Special Category)Regulatory compliance, identity verification
Date of birthPII: Quasi-IdentifierAge verification, clinical record
Email addressPII: Direct IdentifierAuthentication, notifications
Mobile phone numberPII: Direct IdentifierSMS notifications, emergency contact
Home addressPII: Direct IdentifierUnit proximity, logistical support
Dietary preferencesPII: Quasi-IdentifierSession meal management
Clinical session notesSensitive Personal InformationTreatment record-keeping
SOS / emergency alertsSensitive Personal InformationEmergency response
Next of kin name and phone numberPII: Direct IdentifierEmergency contact
Star ratings and feedbackOperational DataService quality improvement

Healthcare Professional Users (Nurses, Managers, Supervisors)

Data ElementPOPIA ClassificationPurpose
Full namePII: Direct IdentifierAccount profile, audit logs
Email addressPII: Direct IdentifierAuthentication, notifications
Mobile phone numberPII: Direct IdentifierNotifications
Professional role and unit assignmentPII: Quasi-IdentifierAccess control, shift scheduling
Shift schedulesOperational DataWorkforce management

Organisation Accounts

Data ElementPOPIA ClassificationPurpose
Organisation name and registration detailsOperational DataAccount creation
Contact email and phonePII: Direct IdentifierAccount administration
Physical address of dialysis unitsOperational DataPatient-unit matching
GPS coordinates of unitsOperational DataMap functionality (derived from verified address)

Automatically Collected

  • Device push token: used solely for push notification delivery (FCM/APNs); stored securely; not used for advertising.
  • IP address: captured in server logs for security monitoring and rate limiting; not linked to patient records.
  • Session timestamps and activity logs: for audit, compliance, and fraud detection.
  • QR scan logs: timestamp, nurse ID, and patient ID, for session arrival verification.

Location Information

GPS coordinates are collected from your device in two limited circumstances, both requiring your explicit prior consent:

  • Session check-in (I've Arrived): GPS coordinates are used transiently to verify proximity to your dialysis unit and are discarded from server memory once the check-in is complete. They are not stored in our database.
  • Live distance sharing (I'm on my way): When you tap “I'm on my way” and have given GPS consent, the app sends your GPS coordinates to our servers periodically while your session status is En Route. Your coordinates are used solely to compute your straight-line distance from the dialysis unit. The coordinates themselves are never stored, logged, or visible to any party. Only the derived distance in metres and an estimated arrival time are stored on your session record and shared with your assigned nurse and unit manager so they can prepare for your arrival. This sharing stops automatically when your session progresses to Arrived or beyond. If you have not given GPS consent, tapping “I'm on my way” notifies your nurse and manager that you are en route without any location data.

The GPS coordinates of dialysis units (captured once from verified street addresses) are stored as operational data.

What We Do Not Collect

  • Biometric data (the Android app may use device biometrics for local unlock, but this is processed entirely on-device by the OS, so we do not receive or store biometric data)
  • Financial or payment card information
  • Advertising identifiers (GAID/IDFA)
  • Audio or video recordings
  • Your contacts, photos, or files (camera is used only for QR scanning)

4. How We Use Your Information

PurposeLegal Basis (POPIA)Data Used
Creating and managing your accountContract performanceName, email, phone, ID number
Patient booking and session managementContract performance / ConsentSession data, meal preferences, bed assignment
Appointment reminders and alertsLegitimate interest / ConsentEmail, phone, device token
Emergency SOS alert routingVital interestPatient ID, alert content, timestamp
QR check-in and arrival verificationContract performanceQR scan log, GPS (transient, not stored)
Live distance sharing while en route to session (with GPS consent)ConsentGPS (transient; only derived distance stored, not coordinates)
Notifying nurse and manager patient is on their way (without GPS consent)Contract performanceSession status only, no location data
Clinical session record-keepingLegal obligation (National Health Act)Session notes, timestamps, clinician assignments
Security monitoring and fraud preventionLegitimate interestIP address, login events, audit logs
Platform improvement and analyticsLegitimate interestAggregated, de-identified usage data
Regulatory compliance and auditLegal obligationAudit logs, consent records
POPIA compliance (consent records, data subject requests)Legal obligationConsent records, identity
Sending system notificationsContract performanceEmail, phone, device token

We do not use your data for targeted advertising, sale to third parties, profiling for non-healthcare commercial purposes, or automated decision-making that produces legal or similarly significant effects without human oversight.

“Platform improvement and analytics” refers solely to internal operational analytics on aggregated, de-identified usage data (for example, measuring feature adoption or session-flow efficiency). DialyticFlow does not currently conduct formal health-related human subject research using patient data. If this changes in the future, this Policy will be updated in advance to describe the research, its legal basis, and the consent and ethics-review process that will apply.

5. How We Share Your Information

We do not sell your Personal Information.

5.1 Within Your Healthcare Organisation

Patients' session and booking data is accessible to authorised Healthcare Professionals (Nurses, Unit Managers, Supervisors) within the patient's registered Organisation. Access is enforced by role-based controls and row-level database security.

5.2 Technology Sub-Processors

We use the following sub-processors to operate the Platform. Each is bound by a Data Processing Agreement and processes data only on our documented instructions. Each sub-processor is contractually required to provide the same or equal level of protection for your Personal Information as is described in this Policy and required under POPIA.

Sub-ProcessorLocationData ProcessedPurpose
Amazon Web Services (AWS) af-south-1Cape Town, South AfricaAll Platform dataPrimary database hosting (PostgreSQL)
Google Cloud Platform (Cloud Run)europe-west1 / us-central1API application trafficBackend application hosting
Google FirebaseGlobal (Google infrastructure)User credentials, push tokensAuthentication, FCM push notifications
SendGrid (Twilio Inc.)United StatesEmail address, notification contentTransactional email delivery
Twilio Inc.United StatesMobile phone number, SMS contentSMS / OTP delivery
Expo Application Services (EAS)United StatesMobile app buildsApp compilation and distribution

Where sub-processors are located outside South Africa, we rely on Standard Contractual Clauses or equivalent adequacy safeguards under POPIA Section 72 to authorise cross-border transfers.

5.3 Third-Party AI Services

DialyticFlow does not currently use any third-party artificial intelligence (AI) service to process Personal Information. We are evaluating AI-assisted features (such as clinical note summarisation) for potential future development. Before any such feature is introduced, we will update this Policy to clearly disclose which third-party AI provider is used, what data is shared with it, and for what purpose, and we will obtain your explicit, informed consent before any of your Personal Information is shared with or processed by that AI service.

5.4 Legal Requirements

We may disclose Personal Information if required by law, court order, or regulatory authority (including the Information Regulator), or where we believe in good faith that disclosure is necessary to prevent imminent harm.

5.5 Business Transfers

In the event of a merger, acquisition, or sale of substantially all of our assets, Personal Information may be transferred as part of that transaction, subject to the acquirer assuming equivalent privacy obligations.

6. Data Security

6.1 Data Classification & Encryption Requirements

We classify all data we hold into one of four tiers and apply a matching set of security controls. This classification-based approach ensures that our most sensitive data always receives the highest level of protection, regardless of the specific field it appears in.

ClassificationExamplesEncryption at RestAdditional Controls
PublicOrganisation name, unit address, shift timesNot required (infrastructure disk encryption applies)None
InternalSession scheduling metadata, shift slot IDs, bed numbersRecommended (infrastructure disk encryption)RBAC, audit logging
Confidential: PII Direct IdentifiersFull name, email address, phone number, physical address, next-of-kin details, date of birthAES-256-GCM at application layer; plaintext never persisted to databaseRBAC scoped by Organisation ID, masking in logs, audit logging, TLS 1.2+ in transit
Special Personal InformationSA ID / passport number, clinical PHI (CKD stage, dialysis type, prescription details, medication history)AES-256-GCM at application layer; HMAC-SHA256 hash columns for lookup; plaintext never storedRBAC, masking, MFA for privileged access, enhanced audit logging, POPIA explicit-consent gate, TLS 1.2+ in transit

Email addresses are treated as Confidential PII Direct Identifiers. Uniqueness checks and database lookups are performed against a deterministic HMAC-SHA256 hash of the normalised address so the plaintext email is never written to disk.

6.2 Additional Security Controls

ControlImplementation
Encryption in transitTLS 1.2+ (HTTPS) enforced on all connections; HSTS enabled
AuthenticationFirebase ID token verification on every API request; multi-factor authentication available
Access controlRBAC with row-level security scoped by Organisation ID
Network securityGoogle Cloud Armor WAF; rate limiting on all public endpoints
Secrets managementGoogle Secret Manager; no secrets in source code or environment variables in production
Vulnerability managementDependency CVE scanning (OWASP Dependency-Check); regular security reviews
Audit loggingAppend-only audit trail for all data mutations; 7-year retention
Breach responseIncident response aligned with POPIA Section 22 (72-hour notification obligation)
Dev/test isolationSynthetic data only in non-production environments; no production PII in dev/test

While we apply industry-standard security measures, no system is completely impenetrable. You are responsible for maintaining the security of your account credentials.

7. Data Retention

We retain data only for as long as is necessary for the purpose for which it was collected, or as required by applicable law.

Data CategoryRetention PeriodBasis
Clinical session records (session notes, bed/meal assignments, arrival logs)5 years from date of sessionNational Health Act 61 of 2003
Audit logs (immutable event trail)7 yearsPOPIA accountability; accounting records legislation
Consent records (GPS consent, reshuffle consent, and arrival consent flags stored on patient record)5 years after last consent action or until account deletionPOPIA Section 11
Patient account and PIIUntil account deletion request, then pseudonymisedPOPIA Section 14 (right to erasure)
GPS location (transient during check-in)Not stored; discarded after proximity check is completeData minimisation principle
Device push tokensUntil account deletion, token invalidation, or 12 months of inactivityNotification delivery
QR scan logs5 years (operational record of session attendance)National Health Act
Emergency alert records5 yearsClinical safety record
Marketing communications preferencesUntil you unsubscribe or delete your accountPOPIA Section 69 (direct marketing)
IP address / server logs90 days, then purged or anonymisedSecurity monitoring

When a Patient requests account deletion (directly within the app via Settings → Delete Account, without needing to email or contact support), an automated process pseudonymises all directly identifying fields (name, email, phone, ID number, address) by replacing them with cryptographic hashes. Clinical session records are retained in pseudonymised form for the legally required period.

Organisations may not be permanently deleted while they have active clinical records in the retention window; their accounts are suspended instead. Scheduled database jobs enforce the retention periods above and are audited on a quarterly basis.

8. Your Rights Under POPIA

RightHow to Exercise
Access (Section 23): request a copy of your dataEmail privacy@dialyticflow.com with subject “POPIA Access Request”
Correction (Section 24): correct inaccurate informationEmail us or update in app under Profile → Edit
Deletion / Erasure (Section 24)App: Settings → Delete Account, or email us
Object to processing (Section 11(3))Email privacy@dialyticflow.com with subject “Objection to Processing”
Object to direct marketing (Section 69)Tap Unsubscribe in any communication, or update in app Settings
Complain to Information Regulatorinforegulator.org.za

We will respond to all POPIA requests within 30 calendar days. If a request is complex or voluminous, we may extend this period by a further 30 days and will notify you accordingly. We may request proof of identity before processing a request to protect against unauthorised access.

9. Children's Privacy

DialyticFlow is designed for use by individuals 18 years of age and older. If a minor (under 18) requires access to the Platform for their healthcare management, they must be registered by a parent, legal guardian, or authorised healthcare representative who accepts responsibility for the minor's data. The registering adult's contact details are captured as part of that minor's patient record, and all communications and consent obligations relating to the minor's data are directed to that registered parent, guardian, or representative.

We do not knowingly collect Personal Information from children under 13 without verifiable parental consent. If you believe we have inadvertently collected information from a child under 13, please contact privacy@dialyticflow.com immediately.

10. Push Notifications

We send push notifications via Firebase Cloud Messaging (FCM) for Android and Apple Push Notification Service (APNs) for iOS to deliver:

  • Appointment reminders;
  • Session status updates;
  • Emergency alerts;
  • Off-hours query responses;
  • Platform announcements.

You may opt out of non-critical push notifications in your device operating system settings. Emergency alerts related to your active dialysis session cannot be disabled while you have an active booking, as they are a patient safety feature.

11. Cameras and Sensors

PermissionWhy RequiredWhen Active
CameraQR code scanning for session check-inOnly when you open the QR scanner screen
LocationProximity verification during check-inOnly during active check-in; not tracked in background
NotificationsAppointment reminders and alertsBackground, when you have granted permission
Biometric (Android: fingerprint / face unlock)Device-level authentication only, used to unlock the app session; biometric data is processed on-device by the OS and never transmitted to or stored by DialyticFlowWhen using device biometric unlock

All permissions are requested at the point of use. You may revoke any permission at any time in your device operating system settings. Revoking camera or location permission will affect QR check-in functionality.

12. Data Breach Notification

In the event of a security compromise that involves Personal Information, we will:

  • Contain and investigate the breach immediately;
  • Notify the Information Regulator of South Africa within 72 hours of becoming aware of the breach, in accordance with POPIA Section 22;
  • Notify affected data subjects as soon as reasonably possible, describing the nature of the breach and the steps taken or recommended to mitigate harm;
  • Maintain an internal breach register.

13. Cookies (Web App Only)

CookiePurposeDuration
Authentication session cookieMaintains your logged-in state (Firebase auth token)Session (cleared on logout)
CSRF tokenPrevents cross-site request forgery attacksSession
Preference cookiesStores your language and accessibility preferences1 year

We do not use advertising cookies or third-party tracking pixels. The mobile application does not use browser cookies; it uses secure encrypted storage (expo-secure-store) for session tokens.

14. Changes to This Policy

We may update this Policy from time to time. We will notify you of material changes by:

  • Displaying a prominent notice within the Platform;
  • Sending a notification to your registered email address at least 14 days before the changes take effect.

Continued use of the Platform after the effective date constitutes acceptance of the updated Policy. The “Last Updated” date at the top of this document will always reflect the most recent revision.

15. Google Play Data Safety and Apple App Store Privacy Labels

The following disclosures are made to comply with Google Play Store Data Safety requirements and Apple App Store privacy nutrition label requirements.

15.1 Data Collected and Its Use

Data TypeCollectedLinked to IdentityUsed for TrackingPurpose
NameYesYesNoAccount management, clinical records
Email addressYesYesNoAuthentication, notifications
Phone numberYesYesNoNotifications, emergency
SA ID / Passport numberYesYesNoIdentity verification (encrypted)
Date of birthYesYesNoClinical record
Next of kin name and phoneYesYesNoEmergency contact
Health information (session data)YesYesNoHealthcare service delivery
Approximate location (transient)YesYesNoCheck-in proximity verification (not stored); live distance computation during en-route (coordinates not stored, only derived distance)
Device identifiers (push token)YesYesNoPush notification delivery
Usage data (session timestamps, logs)YesYesNoSecurity, audit, compliance
Crash dataYesNoNoApp stability

15.2 Data Sharing

  • Data is not sold to third parties.
  • Data is not shared for advertising or marketing profiling.
  • Data is not used for cross-app tracking.

15.3 Security Practices

  • Data is encrypted in transit (TLS) and at rest (AES-256).
  • Users can request deletion of their data, including directly within the app.
  • A privacy policy is available at the public URL linked in the app store listing.

16. Contact Us

Contact TypeDetails
Privacy requests (POPIA)privacy@dialyticflow.com
POPIA Information Officerlegal@dialyticflow.com
Security disclosuressecurity@dialyticflow.com

Dialytic Flow (Pty) Ltd, Republic of South Africa

Information Regulator of South Africa:
JD House, 27 Stiemens Street, Braamfontein, Johannesburg 2001
inforegulator.org.za | enquiries@inforegulator.org.za