Legal

Privacy Policy

Effective date: 27 August 2026

1. Overview

PediaFlux is a pediatric clinical documentation application for Apple devices, intended for use by qualified healthcare professionals. It gives structure to the parts of a pediatric encounter the clinician already writes — History, History of Presenting Illness, Physical Examination, Assessment, Management — and formats that documentation into a clinical report.

PediaFlux does not diagnose patients, does not recommend treatment, and does not replace clinical judgement, supervision, or institutional protocols. This policy explains how information is handled by the application.

PediaFlux is developed and operated by Malik Alshehri.

2. Information handled by PediaFlux

PediaFlux has no user accounts, no registration, and no sign-in. It does not ask for or collect personal information about you as a user of the app.

The application handles the clinical documentation that you, the clinician, choose to enter. Depending on the workflow you use, this may include:

  • patient identifiers such as a medical record number or name, where you choose to enter them;
  • demographic details such as age, sex, date of birth, and nationality;
  • clinical history and history of presenting illness;
  • physical examination findings;
  • assessments and impressions that you write or select;
  • medications and investigations that you record;
  • generated clinical reports;
  • provider and attestation details identifying the documenting clinician.

All of this information originates from you. PediaFlux does not obtain clinical information from any hospital system, registry, or third-party source.

3. Local storage

Records you save in PediaFlux are stored locally on the device the app is installed on. They are not uploaded to a PediaFlux server, and the developer has no ability to view, retrieve, or recover them.

Saved Patient records are explicitly excluded from iCloud and device backup by the application. In-progress draft files and clinician profile preferences are protected at rest on the device but are not excluded from backup; if you have Apple backup enabled, they may be included in a standard device backup. Backups are governed by your Apple backup settings and Apple’s own terms, not by PediaFlux.

4. Data transmission

PediaFlux does not transmit your clinical records to a PediaFlux-owned server. There is no PediaFlux account, no cloud synchronisation of records between devices, and no remote database holding your documentation.

5. Sharing and export

A generated report leaves the app only when you deliberately export it — by copying it, or by using the system share options on your device to send it somewhere else.

Once you export information, it is outside the PediaFlux storage boundary. How that information is then stored, transmitted, or retained is determined by the destination you selected — your email provider, messaging app, hospital system, or printer — and by their terms, not by this policy.

6. Third-party services

PediaFlux does not bundle a crash-reporting, analytics, advertising, or tracking SDK. No usage telemetry, session data, or clinical content is collected or transmitted by the application itself.

Apple’s platform may separately collect diagnostic and usage information from your device and make a portion of it available to the developer through App Store Connect. Whether Apple collects this information, and what it contains, depends on your device settings and Apple’s own policies — it is not controlled by PediaFlux. This Apple platform behavior is separate from PediaFlux’s own data practices. This information does not contain your clinical documentation.

7. Advertising and profiling

PediaFlux does not use clinical content for advertising, marketing, profiling, or any form of user targeting. Clinical documentation is used only to provide the documentation and reporting features of the application.

8. Retention

Records you save remain on your device until you remove them. PediaFlux does not apply an automatic retention or expiry period, and does not delete your documentation on your behalf.

9. Deletion

You can remove saved records within the application at any time. Deleting the app from your device removes the data held in its local app container at that point in time.

Because there is no PediaFlux account or server, deletion happens entirely on your device. PediaFlux has no mechanism to reach or delete data that exists outside its local container — this includes information you have already exported or shared, and any copies of app data that your device included in a backup prior to deletion. Exported information must be removed from each destination separately. Backup copies are governed by your Apple backup settings and Apple’s own policies.

10. Clinician responsibility

PediaFlux is a tool used by healthcare professionals in the course of their clinical work. If you enter identifiable patient information, you remain responsible for complying with:

  • patient confidentiality obligations that apply to your practice;
  • the information governance and data protection policies of your employer or institution;
  • the data protection laws and health information regulations of your jurisdiction.

Keep your device protected with a passcode or biometric lock, and follow your institution’s rules on the use of personal devices for clinical documentation.

11. Children

PediaFlux is designed for pediatric clinical documentation written by healthcare professionals. Children are the subjects of the documentation, not users of the application. PediaFlux is not directed at children and is not intended to be used by them.

12. Security

PediaFlux relies on the security features of the device it runs on, including the operating system’s own protections for app data. Keeping your device updated, locked, and under your control is an essential part of protecting the information stored in the app.

No method of electronic storage or transmission can be guaranteed to be completely secure, and no absolute guarantee of security is made.

13. Changes to this policy

This policy may be updated as the application develops. Any updated version will be published on this page with a revised effective date. Continued use of PediaFlux after a change indicates acceptance of the updated policy.

14. Contact

Questions about this policy or about how PediaFlux handles information can be sent to the addresses below.