Terms of Use

PediaFlux Terms of Use

Version: TOU-1.0
Effective date: 2 October 2026
Developer: Malik Alshehri, individual developer
Website: https://www.pediaflux.com
Support: support@pediaflux.com
Published at: https://www.pediaflux.com/terms

1. Agreement and scope#

1.1 These Terms of Use (“Terms”) govern your access to and use of PediaFlux on supported Apple devices (“PediaFlux” or the “App”).

1.2 By selecting the checkbox stating, “I have read and agree to the Terms of Use and acknowledge that I have reviewed the Privacy Policy,” and then continuing, you confirm your agreement to these Terms and your acknowledgement of the separate Privacy Policy.

1.3 The Privacy Policy describes data-handling practices. It is not accepted as a contract except to the extent required by applicable law.

1.4 The clinical disclaimer presented separately in the App is an additional acknowledgement. Acceptance of these Terms does not replace it.

1.5 If you do not agree, do not use the App. Selecting “Not Now” keeps you at the legal-consent screen.

1.6 Before acceptance, you may access the Terms, Privacy Policy and Support information. Acceptance does not begin a subscription, purchase or introductory offer.

1.7 Acceptance is recorded separately on each device. A subscription, previous use on another device or Restore Purchases does not constitute acceptance on the current device.

1.8 Your electronic acceptance of these Terms is binding and has the same effect as a signed written agreement, to the extent permitted by applicable law.

2. Eligible users#

2.1 PediaFlux is intended exclusively for licensed physicians, including residents and fellows practising within their authorised role and under any supervision required by law, professional standards or institutional policy.

2.2 PediaFlux is not intended for patients, parents, guardians, children, members of the public or unqualified users.

2.3 By using the App, you represent and warrant that you are at least 18 years old; hold every registration, licence, credential and authorisation required for your role; are legally and professionally permitted to use the App where you practise; and will use it only within your competence, professional scope and institutional policies.

2.4 We do not independently verify professional credentials. You are solely responsible for the truth and continued accuracy of these representations and for maintaining your licence, required supervision and professional-liability arrangements.

2.5 If you use PediaFlux in the course of work for a hospital, clinic or other organisation, you confirm that you are authorised to do so and that its policies permit it. As between you and your organisation, its policies continue to apply.

3. Purpose and limitations#

3.1 PediaFlux is a structured clinical-documentation tool. It assists authorised physicians in recording information they enter or select and generating editable draft documentation. The workflows available in a given release are those shown in the App and on the App Store product page. They may include Emergency, Admission, Consultation and Discharge / Final Disposition documentation where that workflow is enabled in the installed version.

3.2 PediaFlux is not intended by us to be used as a medical device, and it has not been classified, approved, registered or certified as one by any authority. It is not a diagnostic or clinical decision-support system; a treatment, prescribing or medication-dosing system; an emergency alerting, surveillance or patient-monitoring system; a substitute for clinical examination, professional judgment, institutional policy or independent verification; or an artificial-intelligence service.

3.3 PediaFlux does not diagnose conditions, select treatments, recommend medications, calculate doses, determine urgency or decide whether a patient should be admitted, discharged, referred or otherwise managed.

3.4 Any assessment, plan, report or other wording generated by the App reflects information entered or selected by the user. It is not an independent clinical conclusion or recommendation from the Developer.

3.5 The App must not be used as the sole or primary basis for any clinical decision or action.

3.6 You confirm that you do not rely on the App, its structure, templates, reference content or output as a basis for any clinical decision.

3.7 If the App displays a calculation, unit conversion, age value, chart, score or similar figure, that figure is produced from values you entered or selected. It is not an independent clinical conclusion. You must verify every clinically significant figure against primary sources before using it for patient care.

4. Your clinical responsibility#

4.1 You remain solely responsible for examining and assessing the patient; determining relevant information; verifying patient identity and all entered information; making every diagnosis, treatment, medication, dose, referral, admission, discharge, escalation and follow-up decision; reviewing and editing every draft; identifying omissions, contradictions, inaccuracies and inappropriate wording; and deciding whether content is suitable for signing, exporting, sharing or placing in a medical record.

4.2 You must not sign, export, share or place an App-generated report in a medical record until you have personally reviewed and verified it.

4.3 You must independently verify all clinically significant information, including medications, doses, allergies, measurements, calculations, results, diagnoses and plans.

4.4 A report may be incomplete or inaccurate because of missing, incorrect or inconsistent user input, software behaviour, device failure or other causes. The App does not guarantee that it will identify such problems.

4.5 You must follow applicable law, professional standards and institutional policies even where they differ from the App or its output.

4.6 Until a report is finalised, the App presents it as a draft with a review warning, and a draft that you copy, print, share or export carries a draft notice. To finalise a report, you must confirm the statement: “I have reviewed and verified the entire report against the original clinical information and accept responsibility for its completeness and accuracy.” The App records that confirmation locally with the visit, as described in the Privacy Policy. A finalised report carries a footer stating that the signing clinician is responsible for reviewing and verifying it.

4.7 If a finalised record is later changed, including by reopening it for editing, correcting patient details or updating pending results, the earlier confirmation does not apply to the changed report. The record returns to draft and must be reviewed and confirmed again before it is final. Earlier confirmations are kept in the record's history.

4.8 Your confirmation records your own review. It does not mean that the Developer or the App has checked or verified the report, and it does not reduce your responsibility under this Section.

5. Emergencies and monitoring#

5.1 Do not rely on PediaFlux to identify or respond to an emergency, deterioration, abnormal result, time-critical condition or required follow-up.

5.2 The App does not continuously monitor patients, results, tasks or clinical systems and does not guarantee alerts or reminders.

5.3 Where immediate action may be required, use the appropriate clinical and emergency systems without waiting for or relying on PediaFlux.

6. Platforms and availability#

6.1 The current release supports compatible iPhone and iPad devices running iOS or iPadOS 17.0 or later and compatible Mac devices running macOS 14.0 or later, subject to the current App Store listing.

6.2 Availability and functionality may differ by device, operating-system version, region and Apple requirements.

6.3 We do not guarantee uninterrupted, error-free or permanent availability.

6.4 You are responsible for compatible hardware, software, storage, power, device security and access to required Apple services.

7. Local storage and device responsibility#

7.1 Patient records, drafts and templates are stored locally. PediaFlux does not provide a user account, PediaFlux server, clinical cloud, automatic synchronisation or automatic upload.

7.2 You are solely responsible for device security, including passcodes, biometric access, operating-system updates, access permissions and institutional controls.

7.3 You must prevent unauthorised access and must not use the App through a device or workflow prohibited by law or institutional policy.

7.4 Deleting the App or its data, erasing or losing the device, device failure or an unsuccessful restoration may permanently remove locally stored information.

7.5 Clinical data is configured to be excluded from ordinary iCloud or computer device backups. Clinician-profile information and preferences may be included according to Apple's operating system and your device settings.

8. Patient information#

8.1 For patient information, you or your organisation are solely responsible for its lawful collection, entry, use, confidentiality, security, retention, disclosure and deletion and for obtaining any authority, permission or consent required by law.

8.2 You or your organisation are solely responsible for handling suspected or confirmed unauthorised access, loss or disclosure and for making any notification required by law or institutional policy.

8.3 The Developer does not receive, access, process or control patient information stored locally in the App.

8.4 You must not send patient information to Support or include it in feedback, screenshots or correspondence with the Developer.

9. Backups, exports and sharing#

9.1 A backup or export occurs only when you initiate it.

9.2 A PediaFlux backup is an encrypted `.pediafluxbackup` file protected with AES-256-GCM. Its encryption key is derived from your password, which is not stored and cannot be recovered by the Developer.

9.3 You select the destination and recipient of every exported file. A transfer to external storage, iCloud Drive, email, messaging or another provider occurs because of your action.

9.4 Third-party destinations operate under their own terms, privacy practices and security controls. The Developer does not operate or control them.

9.5 You are solely responsible for confirming that every destination, recipient and transmission method is authorised and secure.

9.6 A full backup may contain patients and templates. A templates-only export contains templates without patient records. “Export this patient” exports the selected patient without templates.

9.7 Restoration is manual, requires the correct password and may not support a file created by a newer unsupported App version.

9.8 You are responsible for maintaining appropriate independent backups. No storage or backup method is risk-free.

10. Templates#

10.1 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.

10.2 Template names and categories are user-entered. You must not place patient identifiers or confidential information in them.

10.3 Applying a template creates or fills part of a draft. It does not finalise a record, verify accuracy or replace clinical review.

10.4 Templates remain viewable, renamable and deletable after subscription access ends. They remain stored locally until you delete them individually, use “Delete all”, or delete the App or its data. Copies included in backup files you created remain until you delete those files.

11. Clinician profile#

11.1 You may enter information including your name, role, subspecialty, service, report title, institution, email and telephone number.

11.2 Selected profile information may appear in reports according to your settings.

11.3 You are responsible for ensuring that profile and signature information is accurate, current and authorised.

12. Subscriptions and purchases#

12.1 Subscriptions and purchases are offered and processed solely through Apple.

12.2 Products, prices, billing periods and introductory offers are those displayed on the App Store at purchase.

12.3 A seven-day introductory trial may be offered on the App Store if Apple determines that you are eligible.

12.4 Subscriptions renew automatically unless cancelled through Apple under its applicable rules and deadlines.

12.5 Apple handles billing, payment processing, renewal, cancellation and refund requests.

12.6 The subscription screen is not displayed automatically at launch. Subscription status is checked when you request an action that requires an active entitlement.

12.7 An active entitlement is required to start a new visit, reopen a finalised record for editing, or edit a saved response. Without one, you may open the App; view, copy, print, share, export, back up, restore and delete existing records; correct patient identification details and update pending results, which returns a finalised record to draft until it is reviewed and finalised again with an active entitlement; and complete an accessible unfinished record where its workflow permits it.

12.8 Restore Purchases and Manage Subscription are available after legal acceptance. Neither constitutes acceptance of these Terms.

12.9 When subscription access ends, you cannot start a new visit, reopen a finalised record for editing or edit a saved response until access is restored. The other functions described in Section 12.7 remain available, and no record or template is deleted solely because access ended.

12.10 A completed encounter must not be reused or duplicated as a new visit to avoid the subscription requirement.

12.11 PediaFlux does not currently offer a separate organisation or volume-purchasing programme.

13. Acceptable use#

13.1 You must not use the App outside your authority or competence; permit unauthorised access; use it for automated diagnosis, treatment or prescribing; represent output as independently verified by PediaFlux; bypass subscription, security or access controls; reverse engineer, modify or distribute it except where expressly permitted by law; interfere with it or introduce malicious code; use it unlawfully or contrary to professional or institutional obligations; or use it in a way reasonably likely to harm a patient, person, Apple, the App or its users.

13.2 You are responsible for the legality and appropriateness of all information you enter, store, export or share.

14. Intellectual property and licence#

14.1 The Developer retains all rights in the App, software, design, structure, original text, branding and documentation, except identified third-party material.

14.2 You retain responsibility for and any rights you hold in clinical content you enter or create.

14.3 You receive a limited, personal, non-exclusive, non-transferable and revocable licence to install and use the App on Apple-branded products that you own or control, as permitted by the Usage Rules in the Apple Media Services Terms and Conditions, except that the App may be accessed by other accounts associated with the purchaser through Family Sharing or volume purchasing where available.

15. Privacy and acceptance evidence#

15.1 The Privacy Policy at https://www.pediaflux.com/privacy describes information handling.

15.2 The App stores locally the accepted Terms version, acknowledged Privacy Policy version, acceptance time and displayed language. The Developer does not receive this record.

15.3 The local acceptance record may be relied upon as evidence of your acceptance and acknowledgement.

15.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. If a future version includes any additional library or service, that version's Terms and Privacy Policy will describe it.

16. Third-party and Apple services#

16.1 PediaFlux relies on Apple services and operating-system functions, including the App Store, StoreKit, Apple Accounts, printing, sharing and file storage.

16.2 Those services are governed and controlled by their providers. The Developer is not responsible for their availability, security or operation.

16.3 You must comply with applicable third-party terms.

17. Updates and discontinuation#

17.1 The Developer may update the App for compatibility, security, legal, technical or product reasons.

17.2 Updates may change, add or remove functionality. No feature is guaranteed to remain available indefinitely.

17.3 Updates are designed to preserve existing records and backward compatibility, but no migration, storage or restoration process is guaranteed to succeed in every circumstance.

17.4 Where reasonably practicable, advance notice will be provided before discontinuing the App or a material part of it so that records may be exported or backed up. Notice may not be possible where immediate action is required for legal, regulatory, security or technical reasons.

18. Suspension and termination#

18.1 The Developer may suspend or terminate subscription-dependent functionality because of non-payment, fraud, misuse, security risk, legal requirement or material breach.

18.2 Where reasonably practicable, notice and an opportunity to remedy a remediable breach will be provided.

18.3 Suspension or termination does not authorise the Developer to access, alter or delete locally stored records.

18.4 The right to start new visits may end, but existing locally stored records and available export, backup and deletion functions remain accessible while the App remains installed, compatible and operational.

19. No warranties#

19.1 To the maximum extent permitted by applicable law, PediaFlux is provided “as is” and “as available”. Your use of PediaFlux and of any output is at your sole risk.

19.2 The Developer does not warrant that the App or any output will be uninterrupted, error-free, complete, accurate, clinically appropriate, suitable for a particular patient, compatible with every workflow or free from loss or corruption.

19.3 The Developer does not warrant that the App will identify omissions, contradictions, abnormal findings, deterioration, emergencies or required follow-up.

19.4 No information supplied by PediaFlux creates a medical, clinical, professional, fiduciary or advisory relationship between the Developer and a patient or user.

19.5 Nothing in this section excludes a warranty or statutory protection that cannot lawfully be excluded.

20. Limitation of liability#

20.1 To the maximum extent permitted by applicable law, the Developer is not liable for losses arising from clinical decisions or patient care; reliance on output without independent review; inaccurate, incomplete or incorrectly selected information; unauthorised access; loss or disclosure after a user-initiated export, copy, print, share or backup; data that was not appropriately backed up; failure of a device, operating system, Apple service or third-party destination; use outside the intended purpose; use contrary to law, professional standards or institutional policy; or any error, omission, defect or inaccuracy in App output, whatever its cause, that you could have identified through the review and verification required by Sections 4.2 and 4.3.

20.2 To the maximum extent permitted by applicable law, the Developer is not liable for indirect, incidental, special, consequential, exemplary or punitive loss or for loss of profit, revenue, opportunity, goodwill, business, expected savings or data.

20.3 Subject to Section 20.4, the Developer's total aggregate liability arising out of or relating to the App or these Terms, whatever the legal basis of the claim, will not exceed the greater of the total amount you paid for PediaFlux during the 12 months immediately before the event giving rise to the claim or SAR 100. This limit applies to claims between you and the Developer. It does not purport to limit a claim by a person who is not a party to these Terms.

20.4 Nothing in these Terms excludes or limits liability for fraud, wilful misconduct, gross negligence or any other liability that cannot lawfully be excluded or limited under applicable law.

20.4A These Terms are between you and the Developer, with Apple as a third-party beneficiary under Section 25.8. Nothing in these Terms waives, limits or transfers any right or remedy that a patient, parent or guardian may have under applicable law, and nothing excludes or limits any liability that cannot lawfully be excluded or limited.

20.5 The limitations apply regardless of the legal basis of the claim and even if a remedy fails of its essential purpose, but only to the extent permitted by applicable law.

20.6 To the extent permitted by applicable law, any claim against the Developer must be notified in writing through the contact details in Section 27 within 12 months after the event giving rise to it.

21. Indemnity and third-party claims#

21.1 To the maximum extent permitted by applicable law, you will indemnify and hold harmless the Developer against any third-party claim, loss, liability, cost or expense, including reasonable legal costs, brought by or on behalf of a patient, guardian, employer, institution or other third party and arising out of or relating to your clinical decisions or patient care; information you entered, selected, exported or shared; use of App output without independent review; your breach of these Terms, applicable law or professional obligations; or unauthorised access resulting from your failure to secure your device or files.

21.2 This section does not require you to indemnify the Developer for the Developer's fraud, wilful misconduct, gross negligence, or any fine, penalty or liability that cannot lawfully be transferred or indemnified.

22. Force majeure#

22.1 To the maximum extent permitted by law, the Developer is not liable for failure, interruption or delay caused by circumstances beyond reasonable control, including failure of Apple services, an operating system, hardware, storage, network, electricity, telecommunications or third-party provider; cyberattack; natural disaster; epidemic; government action; change in law; or regulatory requirement.

22.2 This section does not exclude liability that cannot lawfully be excluded.

23. Governing law and disputes#

23.1 These Terms and related non-contractual obligations are governed by the laws and regulations of the Kingdom of Saudi Arabia, without prejudice to mandatory rights under applicable law.

23.2 Before formal proceedings, the parties will attempt in good faith to resolve the dispute for 30 days after written notice is received through the contact details in Section 27.

23.3 Section 23.2 does not prevent urgent interim relief where reasonably necessary.

23.4 Subject to a mandatory jurisdictional right, unresolved disputes will be submitted to the competent courts of the Kingdom of Saudi Arabia.

23.5 Nothing removes or restricts a mandatory right that cannot lawfully be waived or limited.

24. Changes to these Terms#

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

24.2 The Developer may change these Terms for legal, regulatory, security, technical or product reasons.

24.3 Reasonable advance notice of a material change 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.

24.4 If re-acceptance is required, you may not start a new visit until acceptance. Existing locally stored records and available export, backup and deletion functions remain accessible.

24.5 Existing records will not be deleted or hidden solely because acceptance is pending.

24.6 If you do not accept an updated version, you may cancel your subscription through Apple.

25. Apple minimum terms#

25.1 These Terms are between you and Malik Alshehri, not Apple. The Developer, not Apple, is solely responsible for the App and its content, subject to these Terms.

25.2 Apple has no obligation to provide maintenance or support services.

25.3 If the App fails to conform to an applicable warranty that cannot lawfully be excluded, you may notify Apple, and Apple will refund the purchase price for the App, if any, to you. To the maximum extent permitted by law, Apple has no other warranty obligation concerning the App.

25.4 The Developer, not Apple, is responsible for addressing claims relating to the App, including product-liability, regulatory and consumer-protection claims, subject to these Terms and applicable law.

25.5 The Developer, not Apple, is responsible for investigating, defending, settling and discharging a third-party claim that the App or its authorised use infringes intellectual-property rights.

25.6 You represent that you are not located in a country or region subject to a United States government embargo and are not listed on a United States government restricted-party list.

25.7 You must comply with applicable third-party terms.

25.8 Apple and its subsidiaries are third-party beneficiaries and may enforce the Apple-specific provisions upon your acceptance.

26. General provisions#

26.1 If a provision is invalid or unenforceable, it will be limited or removed only to the minimum extent necessary, and the remainder will continue in effect.

26.2 Failure to enforce a provision is not a waiver.

26.3 You may not assign or transfer your rights without prior written consent. The Developer may assign these Terms as part of a lawful transfer of the App or related business.

26.4 These Terms, Apple's applicable purchase terms and any provisions that cannot legally be excluded constitute the agreement governing use of PediaFlux. The Privacy Policy and clinical disclaimer are separate notices.

26.5 Headings do not affect interpretation.

26.6 These Terms are provided in English.

26.7 Feedback and suggestions may be used to improve or develop PediaFlux without payment or obligation. Feedback must not contain patient information, confidential clinical information or information you are not authorised to disclose.

26.8 Sections 3, 4, 5, 8, 9, 13, 15, 19, 20, 21, 22, 23, 25, 26 and 27 survive any termination, expiry of subscription access or deletion of the App.

27. Contact#

Questions, dispute notices and other communications concerning these Terms may be sent to:

Malik Alshehri
Individual developer
Email: support@pediaflux.com
Support: https://www.pediaflux.com/support
Terms: https://www.pediaflux.com/terms
Privacy: https://www.pediaflux.com/privacy