Where patient data is kept.

The Pulse servers and database are in London.

Where patient data goes
Practice system
  • Dentally
  • Where the practice keeps its patients and appointments
Patients and appointments are read
Bookings are written back
Pulse, in London
  • Servers on AWS, London region
  • Database hosted in London
  • Every Campaign message is approved before it is sent
  • Choices and blocks checked before every send
Messages
Choices to stop messages
Patient
  • Can stop offers and news at any time
  • Messages about their own care are a separate choice

Storage and access.

Where it is kept

Pulse runs on Amazon Web Services in the London region. Its database is hosted in London.

What Pulse reads

Pulse reads patients and appointments from the practice’s Dentally system, and writes bookings back to it.

It reads treatment history only when the practice turns it on.

Signing in

Nobody can create their own account. Each person is added by invitation, by Visure or by the practice.

People sign in with a password of at least 12 characters, or with a passkey on their own device. Repeated failed attempts are limited.

Who can open what

A practice’s users see only their own practice, and only the pages Visure has opened for it. Visure staff sign in with a Visure email address and can open every practice, to run its Campaigns.

When a user is removed, their access ends at once.

Every table in the Pulse database has row level security switched on: a database setting that limits which records each kind of connection can read.

Who can open what

Practice user

  • Their own practice only
  • Only the pages Visure has opened for the practice
  • Cannot edit Campaigns

Visure staff

  • A Visure email address
  • Every practice, to run its Campaigns
  • Approvals and settings

When a user is removed, their access ends at once.

Handling and safeguards.

Encryption

Browsers reach Pulse over an encrypted connection, through Cloudflare. Pulse’s servers connect to the database over an encrypted connection too.

Some records are also encrypted inside the database, with a key kept outside it in AWS Secrets Manager: the practice’s Dentally connection details, and the details a patient gives on a booking page while their deposit is being paid.

Treatment history has its own key for each practice, protected by AWS Key Management Service in London. Treatment notes are not kept in plain text.

The codes Pulse texts to patients on a booking page are stored only in a form that cannot be turned back into the code.

Patient choices

Patients can stop offers and news at any time. Messages about their own care are a separate choice.

Pulse records those choices and any blocks, and checks them before every send.

Approval

Every Campaign message is approved before it is sent.

Records of who did what

Pulse keeps a record of:

  • who approved each version of a message
  • every change to a patient’s choices and blocks, and who made it
  • every deposit refund asked for in Pulse, and its outcome
  • changes to treatment lists and treatment rules
  • who dealt with each phone message and callback

Testing

A Campaign can be tried first on test patients: staff added by hand. A test patient never enters a real Campaign.

Who is responsible

The practice remains the controller of its patient data. Visure acts on the practice’s instructions, as its processor.

This website

This website sets no advertising cookies.

What you type into a form on this website is covered by our privacy notice.

The services Pulse uses.

What each one is for, and what it receives.

Dentally
The practice system. Bookings Pulse writes back, and tags if the practice turns them on. Pulse reads patients and appointments from it, and treatment history only when the practice turns it on.
Resend
Email. Each email Pulse sends: the address and the message.
Twilio
Text messages and phone numbers. Each text Pulse sends: the mobile number and the message. Calls to a Pulse phone line pass through it.
Stripe
Deposits and payments. The amount, what it is for and a booking reference. Patients type card details on Stripe’s own page, and deposits go to the practice’s own Stripe account.
Retell and xAI
The phone line. Calls to a Pulse phone line, which their voice agent answers. Only when the practice has a phone line.
Telegram
Booking notices to the practice. What was booked, when, and where it came from. A notice never names a patient. Only when the practice turns notices on.
Google Ads
Advert results. For a booking that followed an advert: the advert’s click reference, the time and the value. Never a name or contact details. Only when the practice connects Google Ads.
Cloudflare
Delivery. Every visit to Pulse, over an encrypted connection.
Amazon Web Services and Supabase
Hosting, the database and sign in. The Pulse servers and database, in London.

Send data questions on the contact page.