Privacy Policy

PediaFlux Privacy Policy

Version: PP-1.0
Effective date: 2 October 2026
Developer: Malik Alshehri, individual developer
Privacy contact: privacy@pediaflux.com
Support: https://www.pediaflux.com/support
Published at: https://www.pediaflux.com/privacy

1. About this Policy#

1.1 This Privacy Policy explains how information is handled when you use PediaFlux on a supported iPhone, iPad or Mac, visit the PediaFlux website or contact Support.

1.2 This Privacy Policy is a notice, not a contract. At first launch on each device, before using the App, you are asked to acknowledge that you have reviewed this Policy while accepting the separate Terms of Use.

1.3 PediaFlux is intended exclusively for licensed physicians, including residents and fellows practising under any supervision required for their role. It is not intended for patients, parents, guardians, children or members of the public.

1.4 The App does not require or provide a PediaFlux account.

1.5 This Policy does not create contractual obligations or expand the Developer's liability beyond the Terms of Use, except where applicable law requires otherwise.

2. Summary#

2.1 PediaFlux is designed so that patient records, clinical drafts and templates remain locally on the user's device.

2.2 The App does not send patient records, clinical drafts or templates to the Developer.

2.3 The App has no PediaFlux server, clinical cloud, automatic synchronisation or automatic upload.

2.4 The current version contains no third-party SDKs or external code dependencies. It does not include advertising, tracking, third-party analytics, third-party crash reporting or an artificial-intelligence service.

2.5 The Developer may separately receive information if you contact Support, if Apple makes diagnostic information available after you have chosen to share it with developers, through sales and aggregated metrics supplied by Apple, or when you visit the PediaFlux website. Those activities are described below.

3. Information stored locally by the App#

3.1 Patient and encounter information

The App may store information that you enter or select for clinical documentation, including patient identifiers and demographics; history, examination, assessment and plan information; medications, allergies, measurements and results; encounter dates, times, status and workflow information; clinical drafts and completed records; and other documentation supplied by the user.

This information is stored locally on the device. The Developer does not receive, access or control it.

3.2 Clinician profile

The App may locally store profile information that you choose to enter, including your name, role, subspecialty, service, report title, institution, email address, telephone number, and settings that control whether and which of your profile details are added to reports.

When a document is created, a copy of the provider details used for it may be saved with that visit. That copy becomes part of the clinical record and is included in full backups.

3.3 Templates

Templates are optional saved structured selections. They are designed not to store patient identity, encounter dates, clinical free text, measurements, results, medication doses or links to patient records.

A template stores its name and category, the age group it was created for, the dates it was created and last changed, and, for Emergency encounter templates, medication names without doses. A template may include a structured examination selection that applies to one sex only, but it does not store the patient's sex as a separate field.

Template names and categories are free-text fields. You must not include patient identifiers or confidential clinical information in them.

Templates are stored locally with the device protection configured by the App and are designed to be excluded from ordinary device backups.

3.4 Preferences and operational information

The App may locally store settings and operational information needed for its functions, including display preferences, selected options, template settings, subscription state supplied by Apple and other non-clinical preferences.

Some profile and preference information may be included in an iCloud or computer device backup according to Apple's operating system and your device settings.

3.5 Legal-acceptance record

When you accept the Terms of Use and acknowledge this Privacy Policy, the App stores locally the Terms version, Privacy Policy version, date and time of acceptance, and language displayed.

This record is stored separately from patient records, clinical reports, exported backup files, the clinical-disclaimer acknowledgement and the report-review acknowledgement. The Developer does not receive it.

3.6 Clinical-disclaimer record

The App separately stores the local acknowledgement of the clinical disclaimer. This is not the same as accepting the Terms or acknowledging this Policy.

3.7 Report-review acknowledgement

When you finalise a report, the App stores locally with that visit a review-acknowledgement record that may include the acknowledgement time, App version, build number where available, Terms version and acknowledgement identifier (REVIEW-ACK-1.0). If the record is later reopened or changed, earlier acknowledgement records are kept with the visit as history, together with their status, and do not apply to the changed report. These records remain on the device as part of the locally stored visit and are included in any backup that contains that visit. A copy of a visit created when restoring a backup keeps them identified as belonging to the original record. The Developer does not receive it. It records the clinician's confirmation. It does not independently establish the clinical accuracy of the report and is not cryptographic proof against tampering.

4. No collection of clinical information by the Developer#

4.1 The Developer does not operate a server that receives patient information from the App.

4.2 The Developer does not remotely view, retrieve, analyse, sell or use patient records, drafts, templates or clinician-profile information stored in the App.

4.3 The App does not use clinical information for advertising, profiling, analytics, artificial-intelligence training or automated decision-making.

4.4 Subscription verification through Apple does not send patient records or clinical content to the Developer.

4.5 “Data Not Collected” statements in App Store privacy information refer to data transmitted from the App to the Developer or third-party partners. They do not mean that the App cannot store information locally or that Apple does not provide the Developer with its own sales reports and aggregated metrics under Apple's policies.

5. Responsibility for patient information#

5.1 For patient information stored in the App, you or your organisation determine what is entered, why it is used, how long it is kept and whether it is exported or disclosed.

5.2 You or your organisation are responsible for having a lawful basis, authority or consent; complying with confidentiality and privacy requirements; applying retention and deletion requirements; securing the device; controlling authorised access; selecting authorised recipients and destinations; and assessing and reporting any suspected or confirmed unauthorised access, loss or disclosure.

5.3 You must not send patient information to the Developer through support email, feedback, screenshots or other communications.

5.4 Because the Developer does not receive or control locally stored patient information, the Developer cannot access, correct, export or delete it for you. Those functions must be performed locally by the user where available.

5.5 For patient information that remains solely on the user's device and is not sent to the Developer, the Developer does not determine the purposes or means of its processing and does not receive or process that information. If patient information is sent to the Developer unintentionally through Support or another communication channel, the Developer will restrict access to it and take reasonable steps to securely delete it when identified, unless retention is required by applicable law.

6. Backups and exports#

6.1 A backup, copy, print, share or export occurs only when you initiate it.

6.2 A PediaFlux backup is stored as one encrypted `.pediafluxbackup` file using AES-256-GCM. The encryption key is derived from the mandatory password you provide. The password is not stored by PediaFlux and cannot be recovered by the Developer.

6.3 A full backup may include patient records and templates. A templates-only export includes templates without patient records. “Export this patient” exports the selected patient without templates.

6.4 You choose where an exported file is stored or sent. Destinations may include local folders, external storage, iCloud Drive, email, messaging services or other file providers.

6.5 When you choose a third-party destination, the transfer is initiated by you. The destination provider processes the file under its own terms, privacy practices, retention rules and security controls. The Developer does not operate or control those destinations.

6.6 Restoration is manual and requires the correct password. A backup created by a newer unsupported App version may not be restorable.

7. Information the Developer may receive separately#

7.1 If you contact Support, the Developer receives the information you choose to provide, such as your name, contact details, message, non-clinical attachments and technical information. Do not include patient information or confidential clinical content.

7.2 If you choose through Apple's settings to share diagnostic information with developers, Apple may make crash or diagnostic information available to the Developer. PediaFlux does not include a third-party crash-reporting SDK.

7.3 When you visit the PediaFlux website, the browser and hosting infrastructure may process technical information such as IP address, browser and device type, requested page, date and time, and security or server-log information. The website is hosted by Cloudflare. It does not use advertising or analytics cookies. The hosting provider may use strictly necessary security cookies or similar technologies to protect the website against abuse.

7.4 Apple processes purchases, introductory-offer eligibility, billing, renewal, cancellation and refunds. The App receives the entitlement information needed to determine whether actions that require a subscription are available. The Developer does not receive payment-card details from the App.

7.5 Apple may provide the Developer, through App Store Connect, with sales and subscription reports and aggregated app-usage and crash metrics from users who have chosen to share them, under Apple's policies. These reports do not include patient records or clinical content.

8. How separately received information is used#

8.1 Support information is used to respond to requests, investigate technical issues, maintain an appropriate support record, protect the App and users, and establish, exercise or defend legal claims where necessary.

8.2 Apple-provided diagnostic information is used to investigate crashes, reliability problems, compatibility issues and security concerns.

8.3 Website technical data is used to deliver pages, maintain security, detect abuse, investigate faults and operate the website.

8.4 Apple reports are used to understand sales, subscriptions and app reliability.

8.5 The Developer does not use separately received information for unrelated advertising or sale.

9. Legal basis#

9.1 Where the Saudi Personal Data Protection Law applies, separately received personal information is processed only where an applicable lawful basis exists.

9.2 Depending on the circumstances, processing may be necessary to respond to an action or request initiated by you; provide and secure support or website functions; comply with a legal obligation; protect lawful interests in security, fault investigation and legal claims where permitted; or act with your consent where required.

9.3 Patient information stored locally is entered and controlled by you or your organisation. You or your organisation are responsible for determining the applicable lawful basis.

10. Retention#

10.1 Patient records and drafts remain locally until you delete them, delete the App or its data, or erase the device. Subscription expiry does not delete or hide them.

10.2 Templates remain locally until you delete them individually, use “Delete all”, delete the App or its data, or erase the device. Copies included in backup files remain until you delete those files.

10.3 Local acceptance records, clinical-disclaimer records and report-review acknowledgement records remain for as long as required by the App to determine the accepted or acknowledged version, or, for a report-review record, for as long as the related visit remains stored. Deleting the App or its data may remove them.

10.4 User-created backup and export files remain in their selected destination until the user or destination provider deletes them.

10.5 Support communications are retained only as long as reasonably necessary to respond, investigate, maintain an appropriate record, resolve disputes and comply with legal obligations, then deleted or anonymised where reasonably practicable.

10.6 Diagnostic information accessed through Apple is retained only as long as reasonably necessary to investigate the relevant issue and meet applicable legal obligations.

10.7 Website and security logs are retained only as long as reasonably necessary to operate and secure the website, investigate abuse or faults and comply with legal obligations.

10.8 Information may be retained longer where reasonably necessary to establish, exercise or defend legal claims or where required by law.

11. Disclosure#

11.1 The Developer does not sell personal information.

11.2 The Developer does not disclose patient records stored locally because the Developer does not receive them.

11.3 Separately received information may be disclosed only where reasonably necessary to a provider supporting email, website hosting or related technical operations, such as our website hosting provider (Cloudflare) and our email service provider; to Apple in connection with Apple-operated services; to professional advisers subject to confidentiality; to comply with a binding legal requirement; to protect rights, security or legal claims; or as part of a lawful transfer of the App or related business, subject to applicable safeguards.

11.4 Providers may process only the information needed to perform their relevant service, subject to their applicable terms and legal obligations.

12. International processing and transfers#

12.1 The App does not transfer locally stored patient information to the Developer.

12.2 Apple may process purchase, subscription and diagnostic information in countries where Apple operates, under Apple's policies.

12.3 Support communications and website technical data may be processed where the relevant email, hosting or technical provider operates.

12.4 Where a transfer outside the Kingdom of Saudi Arabia is subject to the Saudi Personal Data Protection Law, the Developer will apply the requirements and safeguards required by that Law, its Implementing Regulations and the Regulation on Personal Data Transfer outside the Kingdom.

13. Security#

13.1 While stored by the App, patient records and clinical drafts use the operating system's complete file protection, which is designed to keep those files unreadable while the device is locked. This depends on your device passcode and settings.

13.2 Clinical information is configured to be excluded from ordinary device backups. Templates are stored with complete file protection and configured to be excluded from device backups.

13.3 Backups created through PediaFlux are encrypted as described in Section 6.

13.4 No storage, device, software, password, encryption method or transmission can be guaranteed completely secure or error-free.

13.5 You remain responsible for securing the device, passwords, exported files and selected destinations.

13.6 If a security incident affects personal information held by the Developer, such as support communications, the Developer will take the steps and make the notifications required by applicable law. Incidents affecting information stored on your device or in destinations you selected are your or your organisation's responsibility, as described in Section 5.

14. Your choices and rights#

14.1 You can manage locally stored information using available App functions, including viewing, editing before finalisation, deleting, exporting and backing up information.

14.2 For personal information the Developer actually holds, such as support communications, you may contact privacy@pediaflux.com to request access, correction or deletion or exercise another applicable right. Requests will be answered within the period required by applicable law.

14.3 A request may be limited or refused where permitted or required by law, including where identity cannot reasonably be verified, information must be retained, another person's rights would be affected or the Developer does not possess the requested information.

14.4 Requests concerning purchase, subscription or information controlled by Apple should be directed to Apple through its available account and privacy controls.

14.5 You may contact privacy@pediaflux.com with a privacy concern. Where applicable, you may also complain to the competent authority, including the Saudi Data & AI Authority where it has jurisdiction.

15. Children and public users#

15.1 PediaFlux is not directed to children, patients, parents or the public.

15.2 The Developer does not knowingly collect personal information through the App from children or patients.

15.3 Patient information entered locally by an authorised physician remains under the responsibility of that physician or organisation as described in Section 5. This Policy does not treat the Developer as the party that decides how that local patient information is used.

16. Third parties and links#

16.1 The current version uses Apple system frameworks and contains no third-party SDKs or external code dependencies. If a future version includes any additional library or service, that version of this Policy will describe it.

16.2 Links may open PediaFlux legal or support pages in your browser. The browser and website infrastructure then process technical information as described in Section 7.3.

17. Changes to this Policy#

17.1 Each version has a version identifier and effective date. Previous versions are available at https://www.pediaflux.com/legal/archive.

17.2 The Developer may update this Policy to reflect legal, regulatory, security, technical or product changes.

17.3 Reasonable advance notice of material changes will be provided through the App or website. A change may take effect immediately where required by law or reasonably necessary to address an urgent security or technical risk.

17.4 Where a material change requires renewed acknowledgement, the App may prevent a new visit from being started until acknowledgement occurs.

17.5 Pending acknowledgement does not by itself remove access to existing locally stored records or available export, backup and deletion functions.

18. Saudi regulatory information#

18.1 Where applicable, personal information is handled in accordance with the Saudi Personal Data Protection Law, its Implementing Regulations, the Regulation on Personal Data Transfer outside the Kingdom and other binding privacy requirements.

18.2 The Developer will maintain any processing records and complete any assessment, notification, reporting or registration required for the Developer's actual processing activities by applicable law.

18.3 Nothing in this Policy states or implies that PediaFlux has been classified, approved, registered or certified by a regulatory authority.

19. Contact#

Questions, requests or complaints concerning privacy may be sent to:

Malik Alshehri
Individual developer
Privacy email: privacy@pediaflux.com
Support email: support@pediaflux.com
Support: https://www.pediaflux.com/support
Privacy Policy: https://www.pediaflux.com/privacy
Terms of Use: https://www.pediaflux.com/terms