Privacy & security
How patient information is handled.
This page describes how the platform handles information so your pharmacy can make its own assessment. Items marked To be confirmed are being confirmed by NYZ Digitals.
At a glance
| Information | What happens to it |
|---|---|
| Booking and request details | Encrypted Identifying and clinical details are sealed in one encrypted record per booking or request (AES-256-GCM). Uploaded photos are encrypted. |
| Staff access | Two-step Username and password plus an emailed code on new browsers; sessions end after 60 minutes idle; activity log. |
| MedCheck patient name and phone | Not saved Shown and printed, not part of the saved MedsCheck review. |
| Voice audio (MedCheck) | Optional Sent to a third-party speech service for transcription. |
| eFax and texts | Optional Sent through accounts in the pharmacy's name. Off until connected. |
| Hosting region | Disclosed Current deployments use a United States (US-East) database region. See below. |
Bookings and prescription requests
Collected from patients: name, date of birth, phone, email, address, Ontario health card number, family doctor, emergency contact, weight where a condition needs it, sex at birth where relevant, screening answers and the reason for the visit; for prescription requests, medication details, Rx numbers, prescriber, current pharmacy for transfers, delivery address and photos.
- These details are stored in one encrypted record per booking or request. The encryption key is held as a server secret, separate from the database.
- Uploaded files are checked to be real images or PDFs and stored encrypted.
- The public booking and request service only accepts requests from the pharmacy's own website, applies rate limits, and rejects links in free-text fields.
- Patients look up or cancel with their reference number and phone number together.
- Pages use a strict content security policy, and a web application firewall with bot protection sits in front of the site.
MedCheck
When a pharmacist saves a MedsCheck review, MedCheck stores the review content (allergies, conditions, readings, medicines, counselling covered, handouts, follow-up and sign-off) under a reference number. It does not save the patient's name or phone typed for the printout, or details typed into print forms such as date of birth or health card number. Saved reviews are still health information and sit behind sign-in.
Voice entry
Optional, in MedCheck. Audio is sent to OpenAI's speech service for transcription, and the text to an OpenAI model to tidy the note or pick out medicines. We recommend pharmacists do not say patient identifiers while dictating.
- Provider processing region and retention: To be confirmed
- Switching voice off for a pharmacy: To be confirmed
Email, fax and texts
- Email (Resend): staff alerts for new bookings and requests; patient confirmations. The patient confirmation includes the booking details the patient entered. Every send attempt is logged.
- eFax (SRFax, the pharmacy's own account): doctor's records and MedsCheck records, sent only when the pharmacist chooses. Fax logs keep the reference, last four digits of the fax number, provider ID and status.
- Texts (Twilio, the pharmacy's own account): appointment reminders for patients who tick the consent box. Off by default.
Staff access
- Username and password, then a six-digit code by email on browsers not yet trusted (trust lasts 60 days).
- Server-side sessions: 12 hours maximum, 60 minutes idle. Secure, same-site cookies.
- Activity log of sign-ins and changes, visible in Settings.
- Repeated failed sign-ins are locked out for a period.
- Individual accounts per staff member and roles: To be confirmed
Hosting and service providers
- Application hosting: Vercel. Database: Neon (PostgreSQL). Current deployments use a US-East database region.
- Canadian-region hosting option: To be confirmed
- Email: Resend. Optional: SRFax (fax), Twilio (texts), OpenAI (MedCheck voice).
- Data-processing agreements with each provider: To be confirmed
Retention, backups and incidents
- Encrypted records cannot be read without the server key; losing that key makes them unreadable.
- Default retention period and deletion when a pharmacy leaves: To be confirmed
- Backups beyond the database provider's built-in history, and restore testing: To be confirmed
- Incident handling and notification to the pharmacy: To be confirmed
Request a privacy and security review
Before onboarding, your pharmacy can ask for a written description of data flows, providers and controls, and raise questions from your privacy officer or advisor. We answer what is confirmed and say plainly what is not.
This page describes the platform. For this website's contact form, see the website privacy policy. Last updated: 2026-11-18.