Your clinic. Your data. Your workflow.
Effective date: September 29, 2026 · Last updated: September 29, 2026
The four questions clinics actually ask: who can see this, can it be changed behind my back, what if I stop paying, and what if the internet goes.
Who can see what
KeepPulsing has three roles: doctor, receptionist and dispenser. They are not cosmetic. A receptionist can run the day — book appointments, take payments, manage the queue — without ever seeing a clinical case note. A dispenser can see what to dispense without seeing why it was prescribed.
This matters in a small clinic, where the person on the front desk is often someone the patient knows personally. Scoping access is not distrust of your staff; it is what lets you hire locally without your patients worrying about it.
- Every staff member has an individual account. Shared logins defeat the entire point of an audit trail.
- Granting and revoking access is an explicit action, and it is recorded.
- Only the clinic owner can manage staff, export the clinic's data or read the audit trail. The audit trail cannot be edited, and it records reads as well as changes: who opened which patient's record, and when.
- Sign-in is a phone number and a password. An email address is optional; if you confirm one it gives you a second way in, and it is how a forgotten password is reset. Repeated wrong passwords are slowed down, and an idle session signs itself out.
Clinic separation is in the database
If your account belongs to three clinics, those three clinics cannot see each other's records. That separation is enforced by the database itself, using PostgreSQL row-level security, not by application code checking a flag.
The difference is not academic. Application-level checks fail when someone forgets one — a new report, an export, a hastily added endpoint. A database-level rule fails closed: a query that does not name a clinic returns nothing at all.
The clinical record cannot be quietly rewritten
A consultation, once finalized, is immutable. If something needs correcting, the correction is appended as an amendment and both versions remain.
This is deliberately less convenient than an edit button. It is also the only way a record means anything months later — if any entry might have been changed after the fact, none of them can be relied on.
What happens when the connection drops
KeepPulsing has an offline-capable core. Clinical writes queue on the device and replay through the same API an online client uses when the connection returns. Nothing is written through a separate, less-tested path.
Offline work is mostly adding things — a consultation, a dispense — so two devices rarely collide. When they do, the clash is surfaced for a person to resolve: the same patient registered on two devices becomes a task to merge or dismiss, and a remedy dispensed twice is refused the second time, with the reason shown. It is never silently resolved by overwriting one side — in a clinical record, a silent overwrite is a lost fact.
It is offline-capable, not offline-only. Taking payments, and anything that depends on shared data or on messaging, resumes once you are back online. Signing out removes the cached patient records from the device, keeping only work the server has not received yet.
Export always works
You can export your patients, cases, consultations, prescriptions, dispensing and billing at any time, as CSV files in a single download that any spreadsheet opens. That includes while a clinic is suspended and after a subscription has expired.
We are stating this plainly because it is the objection that stops clinics moving off paper: the fear that records go into a system that will not give them back. Export is not a retention lever for us, and we will not turn it into one. The records are the clinic's, not ours; our Privacy Policy and Terms & Conditions set that out formally.
We do not message your patients
When you reach a patient about a follow-up, KeepPulsing opens WhatsApp with the message already written, and you send it from your own number. The product never sends a message itself, and we are never a party to that conversation.
Nothing is hardcoded to one country
Country, currency, date format and phone format are configured per clinic. That is also a data question: a date stored under an assumption about format is a date that will eventually be read wrong.
What we are still building
We would rather say this than imply a certification we do not hold. Here is where things stand today.
- Encryption in transit: in place. Everything between your browser and KeepPulsing travels over HTTPS, and browsers are told to use nothing else.
- Encryption at rest: not something we claim. We do not encrypt the database or its storage ourselves, and we do not claim the disk it sits on is encrypted. What protects stored records today is who can reach them: the database is not exposed to the internet, the application's own database account cannot see past row-level security, and our staff tools do not show clinical content.
- Backups: in place, being extended. The database is dumped to a backup on a schedule and can be restored from it. Those backups are kept on the same server today; copies held somewhere else, so that losing the server does not lose them, are planned. Until then, your own export is the copy that is entirely in your hands.
- Incident response: informal, for now. There is no dedicated security team or round-the-clock monitoring. If you find a security problem, email [email protected]. We investigate every report, act on what is confirmed, and tell the clinics a confirmed incident affects. A written incident-response procedure is planned.
- Certifications: none. KeepPulsing does not hold, and does not claim, any formal security or compliance certification or audit — no SOC 2, no ISO 27001 — and does not claim HIPAA or GDPR compliance.
- Payments: not held here. Card and wallet details are entered on the payment provider's own checkout — Safepay in Pakistan, and Paddle, as Merchant of Record, everywhere else. KeepPulsing never receives or stores full card numbers or security codes.
Have a question this page does not answer? Ask us on WhatsApp — we would rather answer it directly than leave you guessing.