Salem — Privacy Policy
Effective date: 2026-11-19
App: Salem (iOS and Android), version 1.0.0
Publisher: Abdullah Janab M Alruwaili
Privacy contact: privacy@drjnab.com · Data protection officer: Abdullah Janab M Alruwaili (privacy@drjnab.com)
Bracketed fields are placeholders that the publisher fills in before submission. Every statement below is traced to the code in DATA_DISCLOSURES.en.md (evidence IDs
E01–E17).
1. What Salem is
Salem is a coordination app for hospital emergency-department staff. It sits above the hospital information system and never replaces it. It shows who is responsible for each patient and task, which results need follow-up, which alerts are open and what is being handed over at shift change.
Salem is for staff of hospitals that have deployed it. It is not for patients or the public, and accounts are not created in the app (E16).
2. Who is responsible for the data
- Your hospital decides why and how patient and staff data is processed. It is the data controller.
- Abdullah Janab M Alruwaili operates Salem for the hospital under a written agreement and processes data only on the hospital's instructions.
PENDING the signed DPA. The controller and processor roles above are fixed only when the signed data processing agreement names the hospital as controller and Abdullah Janab M Alruwaili as processor. That gate is not passed.
Questions about a patient record, an access request or a correction go to the hospital first. You can also write to privacy@drjnab.com and we will pass the request to the right hospital.
3. Data the app handles
3.1 Your staff account
When you sign in with your hospital account, the hospital's identity provider confirms who you are. Salem then receives your staff ID, name, role, unit and shift (E01). Multi-factor authentication is required (E01).
On your device the app keeps only your sign-in session: the session token, its expiry, the server address and your account details above. On iOS and Android these are stored in the platform's secure keystore. In a web browser they are kept only for the open tab (E02).
3.2 Patient-related work information
To do its job, Salem shows the hospital's work information: visits, care-team assignments, tasks, result follow-ups, alerts, handovers, specimen custody and specialist advice. This is health information about patients, and it belongs to the hospital.
- The app fetches it from your hospital's Salem server over an encrypted HTTPS connection (
E07). - Hospital builds do not save patient information on the device between sessions (
E03). - If you act while the connection is down, the action waits in an offline queue until the server confirms it. On iOS and Android that queue is encrypted with AES-256-GCM using a key held in the device keystore. In a web browser it is kept only in memory (
E04). - Patient identifiers are stored on the server encrypted with the hospital's own key (
E12).
3.3 What you record
Every action you take (for example accepting a task or acknowledging an alert) is saved with your identity, the time and the reason you give. This is the hospital's audit trail. It is append-only, so it can be corrected only by a linked amendment, never by editing (E11). When you open a patient-linked screen, the server records which encounters were visible to you (E11).
3.4 Camera
The camera is used only when you choose Scan with camera, to read a patient slip or specimen-container code. The app keeps the decoded code text, never an image, and sends that text to your hospital's Salem server with the action it belongs to. No photo or video is stored or sent. The app does not use the microphone, and it requests no location, contacts, photo-library or notification permission (E06, E08).
3.5 Preferences
The app remembers your interface language and the server address on the device (E05).
4. What Salem does not do
- No advertising, analytics, crash-reporting or tracking software. The app contains no third-party SDK of this kind, and it does not track you across other apps or websites (
E08). - No patient data in notifications or logs. Messages that call someone to the app say only that a response is needed. They never contain a patient's name, identifier or clinical content (
E09). Server error logs record only the error message, never request contents or patient records (E10). The tamper-evident audit chain holds no patient identifiers or clinical free text (E11). - No AI training on patient data. Salem contains no code that trains a model. Decision-support agents read the hospital's data only at the moment they run, inside the hospital's own environment, and without patient identifiers (
E14). A suggestion is shown only after the hospital's clinical owner has approved that exact agent version in writing. Every suggestion is labelled "Suggestion — not an order. Physician must review." The physician always decides, and no agent can create, change or close an order or task (E14). - No mixing of hospitals. Each hospital has its own database, login, encryption key and identity provider. Your hospital is selected by the verified issuer of your sign-in, never by anything the device sends. No role in one hospital can read another hospital's data (
E13). - No sale or sharing of personal data with third parties for their own purposes.
5. Demonstration builds
Demonstration builds and the public demo use only fictional, synthetic data from "Synthetic Hospital A". All patients, staff and results in them are invented. The demonstration PIN exists only in that mode and is refused by every hospital server (E15). Do not enter real patient information into a demonstration build.
6. Retention and deletion
How long records are kept is set by your hospital's policy and the law that applies to it. Salem has no built-in retention period of its own (E17). Because the audit trail is append-only, records are corrected by amendment, not deleted. Staff accounts are created and removed by the hospital, so ask your hospital administrator to close an account (E16).
Signing out removes the session from your device (E02).
7. Security
Salem uses encrypted connections outside the demonstration mode, server-side authorization on every action, per-hospital encryption keys for patient identifiers, an encrypted offline queue on mobile devices, and a hash-chained audit trail (E04, E07, E11, E12). No system is perfectly secure. Report a suspected problem to security@drjnab.com.
8. Where data is stored
Each hospital's data stays in the hosting region named in that hospital's own agreement, and Salem hosts no patient data outside that region. This website (drjnab.com) holds no patient data at all.
9. Children
Salem is a professional tool for hospital staff and is not directed at children.
10. Your rights
Depending on the law that applies to you, you may have the right to access, correct or object to the processing of your personal data. Send requests to your hospital or to privacy@drjnab.com. We will reply within the period the law sets.
11. Changes
We will post changes to this policy at https://drjnab.com/privacy/ and update the effective date. If a change is material, we will notify the hospitals that use Salem before it takes effect.
12. Contact
Abdullah Janab M Alruwaili · privacy@drjnab.com · https://drjnab.com/#contact
Generated from the published Salem store materials.