العربية
Contact us
Try free for 7 days

How we protect your patients' data

The first question every clinic manager asks: where do patient messages go? Here is a message's journey through Sanad, step by step.

A patient message's journey

  1. The patient's message arrivesfrom your clinic's WhatsApp, through an official Meta partner, and we verify it really came from WhatsApp before reading it.
  2. A local protection layerA small AI model running on Sanad's own machine, not in the cloud, reads the message first, removes the patient's name, phone number and ID number, and flags emergencies.
  3. The AI prepares a replyIt sees the request without the patient's identity. Instead of the name it sees «[name kept inside the clinic]».
  4. We check the reply before it goes outEvery price, appointment or service in the reply must actually exist in your clinic's data, otherwise the reply is rejected and redone.
  5. The reply reaches the patienton your clinic's WhatsApp, from the number they already know.

If the protection layer goes down

Not a single character goes to the cloud AI. Sanad continues with limited canned replies until the protection layer is back.

Each clinic's data stays separate

Each clinic has its own database, and one clinic's messages never mix with another's. An answer about one specific patient never becomes a general answer for others.

Processing inside Saudi Arabia

Available as an option: we run the AI from Google Cloud's Dammam region, and Sanad refuses to run on any model we haven't confirmed processes inside the Kingdom.

Who can see conversations

Only your clinic's staff, each with their own account and PIN. Sensitive actions, like cancelling a doctor's day, are for supervisors only, and every action is logged with who did it and when.

Patient consent

Reminders only go to patients who agreed, and marketing messages need separate consent. A patient can stop everything by replying «stop».

No diagnosis, no medical advice

Sanad is a receptionist, not a doctor. If a patient describes serious symptoms, it stops the booking, directs them to 997 and alerts reception.

What we claim, and what we don't

Sanad was designed with Saudi Arabia's Personal Data Protection Law (PDPL), issued by SDAIA, in mind. We don't claim an official compliance certificate, because that comes from an accredited body after an audit, not from us.

Automatic name removal greatly reduces the data that leaves your clinic, but we don't claim it is 100% perfect. That's why the local protection layer reads every message before anything else.

Have a data question we didn't answer here? Contact us, and we'll send you the full technical details.