Privacy, by architecture.
ObGynAssist™ keeps clinical computation — and the clinical modules' patient data — on the iPhone. The one deliberate exception is the opt-in Delivery Room, a shared clinic workspace, disclosed here in full. Privacy isn't a policy bolted on afterward; it's how the system is built.
Two data planes: local by default, shared by choice.
Clinical computation runs entirely on-device. Patient data in the clinical modules — Fetal Growth, PregAssist, GynAssist — is processed and stored on the iPhone and never leaves it. The optional Delivery Room is different by design: a shared clinic ward board, synced to the colleagues you invite.
- On-device processing. Biometry, Doppler, classification and the resulting plan are computed locally on the device. No patient clinical data is transmitted to any backend for the engine to do its work.
- On-device storage for the clinical modules. Cases and clinical entries of Fetal Growth, PregAssist and GynAssist are stored on the iPhone (SwiftData and local files). They do not leave the device by design, and are never linked to your account.
- Account data leaves the device, and we name it. Signing in is required. Your email address, name and an account identifier — together with your sign-in provider, sign-in timestamps, push-notification device tokens and any referral fields — are processed through Firebase Authentication and stored in an account profile record held by Google Firebase in the EU. Account data is used solely for app functionality (never advertising or tracking), and it is never linked to your clinical-module data. You can erase it in-app at any time — see Retention & deletion.
- The Delivery Room is a shared clinic workspace — opt-in, and we name that too. Creating or joining a clinic turns on cloud sync for that clinic's ward board: ward patient records, emergency calls and on-call rosters are stored in Google Cloud Firestore in the European Union and are visible to the clinic's approved members. Emergency (SOS) pushes deliberately carry the patient's name, bed, ward location and the raiser's name, so the summoned clinician knows where to run. Full detail in the policy below.
- Data minimisation. The app asks for the clinical inputs the engine uses, and nothing more. GDPR-ready by design through on-device processing and minimisation.
- No third-party analytics on patient data. Patient clinical data is not fed to advertising or analytics services.
Because the clinical engine is deterministic and local, the same inputs produce the same outputs without any round-trip to the cloud. Privacy and reproducibility come from the same architectural choice: keep the computation — and, in the clinical modules, the data — on the device. Where data is shared, it is shared with exactly one audience: the approved members of the clinic it belongs to.
The summary above is not the policy. The complete Privacy Policy — identical to the text shown inside the app under Settings → Privacy Policy — follows in full below.
The full policy.
This is the same text shown in the app under Settings → Privacy Policy.
1. Introduction
ObGynAssist (“we”, “our”, or “the app”) is a clinical reference companion application designed exclusively for qualified healthcare professionals working in obstetrics and gynaecology. It is not a medical device and does not provide medical advice, diagnosis, or treatment.
This Privacy Policy explains how the app handles information when you use it. The app has two distinct data planes: the clinical modules (Fetal Growth, PregAssist, GynAssist), whose data never leaves your device, and the optional Delivery Room, a shared clinic workspace whose ward board is synced with the colleagues you invite. Both are described below. By using ObGynAssist, you agree to the practices described in this policy.
2. Data we collect
Stored only locally on your device:
- Profile information: your name, professional role, institution, and specialty — entered during onboarding.
- Clinical data of the Fetal Growth, PregAssist and GynAssist modules: patient identifiers, biometry measurements, Doppler indices, growth assessments, and visit records that you enter. This data is never uploaded.
- App preferences: your chosen settings such as reference standards, language, and display options.
Account data. Signing in is required to use the app. When you sign in with Apple or Google, your email address, name, and an account identifier are processed through Firebase Authentication and stored in an account profile record, together with your sign-in provider and sign-in timestamps, to provide and maintain account access. The same record also holds your push-notification device tokens (needed so emergency pages can reach your phone — see section 3) and, if you used an invite code, the referral fields that credit the colleague who invited you. Account data is used solely for app functionality — never for advertising or tracking. When you sign up we send a one-time welcome email to your address.
Delivery Room clinic data (only if you create or join a clinic). The shared ward workspace described in section 3 — ward patient records, emergency calls, on-call rosters, and your clinic membership entry (name, role, specialty, approval and paging status).
We do not collect analytics, usage data, crash reports, or any form of telemetry.
3. How data is stored & shared within your clinic
Clinical modules (Fetal Growth, PregAssist, GynAssist). All patient and clinical data of these modules is stored only locally on your device (SwiftData / JSON) within the application sandbox, protected by iOS Data Protection. It is never transmitted, never linked to your account, and has no remote database.
Delivery Room (optional — active only when you create or join a clinic). The ward board is a shared clinical record. When you or a colleague chart on it, the following is stored in the app's cloud database (Google Cloud Firestore, hosted in the European Union) and synced live to the clinic's approved members:
- Ward patient records — the woman's name, date of birth, contact details, record number, and her full labour chart (observations, assessments, plans, birth and complication records), tagged with the account identifier of the member who last edited them.
- Emergency calls — the reason, the patient's name and bed, an optional note, and the names of who raised, acknowledged and resolved the call (the clinic's debrief log).
- On-call rosters and clinic settings — member names, roles, specialties, beds, ward location, paging policy.
Access is restricted server-side to members of that clinic whom an admin has approved; an invite code lets a colleague request to join, and until approval they cannot read the board. Treat invite codes like keys and share them only within your team.
Emergency push notifications. When an SOS is raised, a push is sent to the on-call team through Google Firebase Cloud Messaging and Apple's push service. This notification deliberately carries the patient's name, bed, ward location and the raiser's name, so the summoned clinician knows where to run — it can appear on recipients' lock screens. Ward alarms (monitoring cadence, labour-progress alerts) are local notifications generated on your device and carry no patient name.
If you enable iCloud Drive backup at the operating-system level, iOS may back the app's local data up to Apple. Such a backup is governed by the Apple privacy policy and is outside ObGynAssist control.
4. Data sharing
ObGynAssist does not sell or rent your data, and never uses your patient or clinical data for anything except providing the features described above.
Local-module data (Fetal Growth, PregAssist, GynAssist) is never shared with anyone. Delivery Room clinic data is shared with exactly one audience: the approved members of the clinic it belongs to.
Our third-party processors, all engaged solely to run the app:
- Apple — Sign in with Apple, and push-notification delivery (APNs).
- Google — Firebase Authentication, Cloud Firestore (the account profile and the Delivery Room clinic data), Cloud Functions (the referral credit, account deletion, and the SOS pager), Firebase Cloud Messaging (push delivery), and Google Workspace (the one-time welcome email).
Account and clinic data is hosted in Google Cloud's European Union regions (Cloud Functions in europe-west3, Frankfurt).
When you explicitly choose to export a PDF report, the file is generated locally and shared through the iOS share sheet; the destination is chosen by you, and that sharing is your own action under your control.
5. Patient data responsibility
You and your clinic are solely responsible for:
- Ensuring that any patient data you enter — on-device or on the shared ward board — complies with applicable regulations (KVKK, GDPR, HIPAA, or other local data protection laws) and your institution's policies.
- Recording only authorised, task-limited, necessary, and proportionate patient data.
- Minimising identifiable patient information whenever possible.
- Obtaining any required patient consent for data entry, storage, and — for the Delivery Room — sharing within the care team.
- Securing your device with appropriate access controls (passcode, Face ID, Touch ID), and sharing clinic invite codes only within your team.
The Developer hosts Delivery Room clinic data solely to provide the sharing feature, does not use it for any other purpose, and restricts access to the clinic's approved members. ObGynAssist's developers are not responsible for data entered by users or for any breach of confidentiality resulting from device loss, theft, unauthorised access, or an invite code shared outside the care team.
6. Data retention & deletion
On-device data (clinical-module patients, profile, and preferences) remains on your device until you delete it: individual cases from the patient list, everything from Settings → Data & Privacy, or by uninstalling the app. We have no access to this on-device data and cannot recover it after deletion.
Delivery Room clinic data belongs to the clinic and remains with it. Ward patient records and the emergency debrief log are a shared clinical record and are not deleted when one member leaves. Leaving a clinic removes you from its member list — colleagues stop seeing you, SOS stops paging you, and your server-side access ends; the board itself stays with the clinic. Uninstalling the app does not delete clinic data you contributed.
Account data is retained for as long as your account exists. Settings → Data & Privacy → Delete Account permanently removes your account profile (including push tokens and referral fields) and your sign-in credential from our servers, removes you from every clinic's member list, and anonymises your name on emergency-log entries. Ward patient records you edited remain with their clinic, as part of its clinical record. Uninstalling the app on its own does not delete the server-side account record — use Delete Account first if you want it erased. You may also exercise your access, correction, and erasure rights by contacting info@obgynassist.com.
7. Third-party services
Beyond the processors listed in section 4 (Apple and Google, for sign-in, hosting, push delivery, and the welcome email), ObGynAssist integrates no third-party analytics, advertising, tracking, or social media services.
The app does not use cookies, web beacons, or any similar tracking technologies.
8. Children's privacy
ObGynAssist is designed for use by qualified healthcare professionals only. It is not intended for use by individuals under the age of 18.
9. Changes to this policy
We may update this Privacy Policy from time to time. Changes will be reflected in the “Last updated” date above and will be available within the app. Where a change concerns the medical disclaimer or a new data flow, the app presents the updated disclaimer for re-acceptance.
Continued use of the app after changes constitutes acceptance of the updated policy.
10. Contact
If you have questions about this Privacy Policy or your data, contact us at info@obgynassist.com.
A companion, not a medical device.
ObGynAssist is a clinical companion and reference tool — not a regulated medical device.
Its outputs are classification labels and guideline citations. They are designed to support — never replace — the judgment of a qualified healthcare professional. The app surfaces what criteria are met, what a pattern is consistent with, and which named guideline a label traces to. It does not provide directives.
Acuity tags such as DELIVER NOW, URGENT, ADMIT · CONSIDER and OUTPATIENT are classification labels, not instructions. Clinician evaluation is part of every assessment, and the final clinical decision rests with the responsible clinician.
In plain terms
- It is a clinical reference tool, used at the clinician's discretion.
- It does not diagnose, and it does not issue clinical directives.
- No doctor–patient relationship is created by its use.
- App Store category: Medical Reference.
Concordance figures published elsewhere on this site reflect agreement with standard-of-care guideline references on synthetic cases — not neonatal outcomes. A prospective clinical-validation study is in design.
Terms of use.
Plain-English terms for a clinical reference tool. Concise by intent — a starting point, not the final word.
1. Purpose and scope
ObGynAssist is a clinical companion and reference tool that produces classification labels and guideline citations to support clinical assessment. It is not a regulated medical device and is used at the discretion of a qualified healthcare professional.
2. Provided "as is"
The tool is provided "as is," without warranty of clinical outcomes. While the engine is deterministic, guideline-wired and extensively tested, no guarantee is made that any output is correct or complete for a given patient.
3. Clinical responsibility
The user — the responsible clinician — remains accountable for all clinical decisions and for interpreting any output in the full context of the patient. Outputs support, and do not substitute for, professional judgment.
4. Intellectual property
The software, the engine, its content and the ObGynAssist™ trademark belong to the owner. The sub-brands FetalGrowth, PregAssist, GynAssist and LaborAssist are referenced as product names and carry no trademark symbol. Nothing here transfers ownership of these to the user.
5. Third-party marks
Third-party names and marks — including RCOG, NICE, ISUOG, ACOG, INTERGROWTH-21st, WHO and Apple — belong to their respective owners and are referenced for attribution only. Their mention does not imply endorsement, affiliation or sponsorship.
6. Changes
These terms may be revised as the product and its regulatory posture evolve. Material changes will be reflected on this page.
Built to be trusted — and to be checked.
Privacy by architecture, decisions you can audit, and a companion that supports the clinician rather than speaking over them.