Privacy Policy for SCMS (Specialist Clinic Management System)
Effective date: August 6, 2026
Developer / Data Processor: UltraSoft Systems
Contact: info@ultrasoftsystem.com
1. Who this policy is for, and two important roles
SCMS is a clinic and hospital management application used by clinic staff — Admins, Doctors, Staff, Hospital Staff, and Viewers — to manage patients, clinical records, appointments, medicine stock, and billing for a specific clinic.
Because the App is used by clinics to manage records belonging to their patients, two distinct roles apply under data protection principles:
- The clinic that operates the App is the Data Controller for all patient data entered into it. The clinic decides what patient information is collected and how it is used in the course of care.
- UltraSoft Systems is the Data Processor — we provide the software and (where a clinic chooses to enable it) the backend infrastructure that stores and synchronizes data on the clinic's behalf. We do not decide what data a clinic collects about its patients, and we do not use patient data for our own purposes.
If you are a patient and have questions about your medical records, please contact the clinic that treated you directly — they control your data. If you are a clinic administrator or staff member, this policy explains how the App itself handles data on your and your patients' behalf.
2. Information the App Collects
2.1 Account / staff information
When a clinic Admin creates a user account, the App stores:
- Full name, email address, postal address, contact number, job title/post
- Role (Admin, Doctor, Staff, Hospital Staff, or Viewer)
- Password (stored as a salted hash, never in plain text)
- For Doctors: consultation fee ("Charges") profile field
2.2 Patient information (Protected Health Information)
Entered by clinic staff during registration and treatment of a patient:
- Identity data: name, father's/husband's name, age, gender, CNIC (national ID number), contact number, city, nationality, marital status, number of sons/daughters, address, email
- Visit metadata: submission date, revisit date, internal patient ID (Monthly/Yearly ID), a QR code generated to identify the patient record
- Clinical data: vitals (blood pressure, pulse, oxygen saturation, respiratory rate, temperature, weight, height), diagnoses, treatments, prescriptions, lab/investigation results, procedure records, doctor/staff assignment history
- Attachments: photographs or PDF scans of lab reports, prescriptions, and procedure documents, captured via the device camera or picked from the device's file system/gallery
- Billing data: payment records, consultation charges, payment type and date
2.3 Master/reference data
Clinic-configured catalogs that are not personal data on their own: disease names/descriptions, treatment templates, medicine names and stock quantities, investigation/lab test definitions.
2.4 Technical and device information
- Local device storage: all of the above is stored in an encrypted-at-rest local database on the staff member's device so the App works fully offline.
- Sync/network data: when a device pairs with another device for offline peer-to-peer (P2P) sync, we process the device's local IP address, a pairing code/QR token, and connection metadata to establish that connection. This traffic stays on the clinic's local Wi-Fi network — it is not routed through the internet.
- Backend sync data (if enabled): if a clinic connects the App to our backend service for cross-device/cross-location sync, the same clinical, staff, and billing data described above is transmitted to and stored on our servers on the clinic's behalf.
2.5 What we do NOT collect
The App does not include advertising SDKs, does not use third-party analytics or crash-reporting services, and does not access contacts, call logs, SMS, precise GPS location, or the device's photo library beyond the specific images a staff member deliberately selects/captures for a patient attachment.
---
3. Device Permissions and Why We Request Them
| Permission | Purpose |
|---|---|
| Camera | Scanning a patient's QR code to open their record; scanning a pairing QR code to set up device-to-device sync; photographing lab reports, prescriptions, or procedure documents for attachment to a patient's file. |
| Wi-Fi / local network state | Discovering and connecting to other clinic devices on the same Wi-Fi network for offline peer-to-peer sync, and determining this device's local IP address so its QR pairing code can be generated. |
| Storage / file access | Picking image or PDF files to attach to a patient's lab, prescription, or procedure record, and saving generated documents (printable stickers, prescriptions, reports) for printing or sharing. |
You can decline these permissions, but doing so will disable the specific features that depend on them (e.g., declining Camera access disables QR scanning and photo attachments).
4. How We Use the Information
Data collected through the App is used exclusively to:
- Provide clinic management functionality: patient registration, clinical documentation, appointment scheduling, medicine dispensing, and billing.
- Allow a clinic's staff to access the same patient records across multiple devices, whether via our backend sync service or direct peer-to-peer sync on the clinic's local network.
- Generate printable/shareable clinical documents (prescriptions, stickers, reports) at staff request.
- Maintain basic account security (authentication, password hashing).
We do not use patient or staff data for advertising, profiling, or any purpose unrelated to operating the App on behalf of the clinic.
---
5. How Data Is Stored and Synchronized
The App is **offline-first**: every feature works without an internet connection, and all data is written to an on-device database first.
- On-device storage: Data lives in a local SQLite database on each staff member's device. Authentication tokens are stored using the operating system's secure credential storage (Android Keystore / iOS Keychain).
- Peer-to-peer (P2P) sync: A clinic may sync records directly between staff devices over its own local Wi-Fi network, without any data leaving that network. Pairing is authorized via a QR code, and the data package exchanged between devices is encrypted in transit.
- Backend sync: Where a clinic opts to use our hosted backend (thespecialists.net) for sync/backup across locations, data is transmitted over an encrypted (HTTPS) connection and stored on servers operated by or on behalf of UltraSoft Systems.
- Pending changes: Records created or edited offline are queued locally ("pending sync") until a sync connection (P2P or backend) becomes available.
---
6. Data Sharing and Disclosure
We do not sell patient or staff data, and we do not share it with third parties for marketing or advertising purposes.
Data may be disclosed only in the following circumstances:
- Within the clinic: to authorized staff of the same clinic, according to the role-based permissions the clinic's Admin has configured (e.g., a Viewer role only sees reports, not edit rights).
- Service providers: to infrastructure providers (e.g., cloud hosting) strictly to operate the backend sync service, under confidentiality obligations, and only if the clinic has enabled backend sync.
- Legal requirements: if required to comply with a valid legal request from a competent authority in Pakistan or another applicable jurisdiction, or to protect the rights, property, or safety of UltraSoft Systems, our users, or the public.
- Business transfers: in connection with a merger, acquisition, or sale of assets, subject to continued protection of the data under this policy or an equivalent standard.
---
7. Data Security
We apply the following safeguards:
- Passwords are stored as salted hashes, never in plain text.
- Authentication tokens are stored in OS-level secure storage (Keystore/Keychain), not in plain files.
- P2P sync packages are encrypted before transmission over the local network.
- Backend sync traffic is transmitted over HTTPS.
- Access within the App is restricted by role (Admin/Doctor/Staff/Hospital Staff/Viewer), limiting who can view, edit, or delete sensitive records.
No method of storage or transmission is 100% secure. If a clinic's device is lost, stolen, or compromised, locally stored data on that device could be at risk — clinics are responsible for their own device-level security (screen locks, device encryption, physical custody) and for promptly deactivating a staff account if a device is lost.
---
8. Data Retention
Patient and clinical records are retained for as long as the clinic continues to use the App, or as required by the clinic's own record-retention obligations under applicable healthcare regulations in Pakistan. A clinic Admin can delete a patient record (including its attachments) or a staff account at any time; deletion removes the record from the device and, where backend sync is enabled, from our servers on the next sync cycle, unless retention is legally required.
---
9. Children's / Minors' Data
The App itself is intended for use by adult clinic staff, not by children. However, because clinics treat patients of all ages, patient records may contain health information about minors. Such data is entered and controlled by the treating clinic (acting on behalf of the minor's guardian), and is handled with the same protections described in this policy. If you are a parent or guardian with questions about a minor's record, please contact the treating clinic.
---
10. Your Rights and Choices
- Clinic staff (App users): you may request access to, correction of, or deletion of your own account information by contacting your clinic Admin or UltraSoft Systems directly .
- Patients: because the clinic is the data controller for patient records, requests to access, correct, or delete patient data should be directed to the treating clinic. UltraSoft Systems will assist the clinic in fulfilling such requests where backend sync is in use.
- Withdrawing permissions: device permissions (Camera, Wi-Fi/network, Storage) can be withdrawn at any time through your device's OS settings; this will disable the corresponding features.
---
11. International Data Transfers
If a clinic enables backend sync and our hosting infrastructure is located outside Pakistan, patient and staff data described in this policy may be transferred to and processed in that country. In such cases we take reasonable steps to ensure the data continues to receive a comparable level of protection to that described in this policy.
---
12. Contact Us
For questions about this Privacy Policy, or to make a data access, correction, or deletion request:
UltraSoft Systems
Email: info@ultrasoftsystem.com
Address: Airport Road Quetta.
13. Changes to This Policy
We may update this Privacy Policy from time to time to reflect changes in the App's functionality or applicable law. Material changes will be reflected by updating the "Effective date" above. Continued use of the App after a revised policy is posted constitutes acceptance of the changes.