pegasus

Last updated 22 November 2026

Pegasus Privacy Policy

Version 1.0 — 22 November 2026

Who we are

Pegasus is practice-management software for healthcare practices. It comes in Editions configured for a kind of practice — currently the Pegasus Audiology Edition and the Pegasus Psychology Practice Edition — and this policy covers all of them. It is provided by Pegasus ERP, a sole proprietorship trading from Paarl, South Africa.

  • Privacy questions, access requests and complaints: privacy@pegerp.com
  • Service and support questions: support@pegerp.com

The Information Officer for Pegasus ERP is the owner of the business, reachable at privacy@pegerp.com. We answer privacy messages in English or Afrikaans.

Who is responsible for which records

A practice decides why and how its patient and practice records are used. For those records the practice is the responsible party and Pegasus ERP is its operator: we process them on the practice's instructions, to run the service, and for nothing else.

If you are a patient, contact your practice first about your records. They hold them and they can correct them. Pegasus ERP will not confirm to anyone else whether a person is a patient of a particular practice.

Pegasus ERP is itself the responsible party for a smaller set of information: user accounts, sign-in and security records, support correspondence, and business and billing contacts.

What information Pegasus holds, and why

Information Why we hold it, and where it comes from
User names, email addresses, practice membership and passkey records To invite staff, sign them in and control what they may see; from the user and the practice's administrators
Patient names, dates of birth, contact details and appointments The practice's day-to-day work in the modules it has switched on; entered by the practice's staff
Patient numbers and medical-aid membership details Identifying a patient's file and their medical-aid cover; entered by the practice's staff
Clinical notes and documents a practice records The practice's clinical record-keeping; entered by its practitioners
Supplier, stock and sales records Running the practice's business side
Appointment reminder messages, their delivery status and the patient's answers Sending reminders a practice has switched on, and showing the practice what happened
Support messages, and account and billing contacts Answering support requests and administering the subscription
Sign-in records, audit records and technical logs Security, accountability, investigating faults and preventing misuse

Only the modules a practice has switched on collect their information. Pegasus does not build a profile of patients across practices, and a practice can never see another practice's records.

Health information is special personal information under POPIA (sections 26 to 33). A practice may process it because it is a health professional or institution with a duty of confidentiality (section 32); Pegasus ERP processes it only as that practice's operator. Pegasus user accounts are for people aged 18 or older. Records about children are held for the practice, which obtains a parent's or guardian's consent where the law requires it (section 35).

Since 6 March 2026 the Regulations relating to the Processing of Data Subjects' Health Information by Certain Responsible Parties, 2026 (Government Gazette 54268, Notice 7198) set out how health information must be handled under POPIA. They apply to insurers, medical schemes and their administrators, managed healthcare organisations, administrative bodies, pension funds, employers, institutions working for those bodies, and the operators of those bodies. A treating practice is not one of them, and neither is its software supplier, so the Regulations do not apply to Pegasus ERP directly. We hold ourselves to their standard anyway: the safeguards, the written duty of confidentiality, the care over destruction and the restriction on sending health information out of the country described below are what those Regulations require, and we apply them to every practice on Pegasus.

What Pegasus does not do

  • We do not sell practice or patient records, and we never will.
  • We do not use clinical content for advertising, or to train artificial intelligence models of any kind, whether ours or anyone else's.
  • Pegasus does not record consultations and does not transcribe patient audio. The software refuses to send patient audio to any transcription service; the only recordings it will process are synthetic test files used in development.
  • There is no advertising, analytics or third-party tracking anywhere in the application. No Google Analytics, no advertising pixels, no session recording.

Who else receives information

Provider What it does Where it processes
Amazon Web Services (AWS) Hosts the application and database, stores files and backups, and holds the encryption keys Cape Town, South Africa (af-south-1)
Amazon Simple Email Service (part of AWS) Sends sign-in links, invitations and account emails Cape Town, South Africa
Meta Platforms Delivers WhatsApp appointment reminders, but only for a practice that has switched them on Outside South Africa; see the WhatsApp section below

That is the complete list of outside parties that receive personal information from Pegasus today. We will tell practices before any new provider receives their information, and we will update this policy when that happens.

Beyond those providers, we disclose information only to the practice's own invited users, to Pegasus ERP support when a practice asks us for help with a problem, and where the law obliges us to. A legal demand is assessed on its terms and recorded.

How we protect information

  • Each practice's rows are separated in the database by PostgreSQL Row Level Security, enforced by the database itself. The application's database role is not a superuser and cannot bypass it.
  • Staff see only what their role permits, and sensitive actions are written to an audit record with who did them and when.
  • Disks, backups and stored files are encrypted, with keys held in AWS Key Management Service in Cape Town.
  • On top of that, Pegasus encrypts particular fields inside the application, each practice with its own key: patient first and last names, dates of birth, email addresses, mobile numbers and physical addresses, appointment notes and cancellation reasons, patient numbers, and medical-aid membership and main member identity numbers. Other fields, such as landline and postal details, are stored without this extra layer.
  • Signing in uses a passkey on your own device, or a single-use link sent to your email address. There are no passwords to steal or reuse. A signed-in session lasts eight hours.
  • Traffic to and from Pegasus is encrypted in transit (HTTPS).
  • Everyone who may reach a practice's information is under a written duty of confidentiality, which is the basis POPIA section 32(2) requires for processing health information. For Pegasus ERP that duty is in the agreement we sign with the practice; for the practice's own staff it is their employment and their profession.
  • We follow generally accepted information security practice for software of this kind, as POPIA section 19 requires, rather than a standard of our own invention.
  • When we delete a practice's records we remove them from the live database rather than hiding them from the screen, and the copies inside backups fall away as those backups expire. Storage and backups are encrypted, so an expired copy cannot be read without its key. We do not hand disks, drives or exported files to anyone for disposal.

Encryption does not mean every field is encrypted, and it does not stop someone your practice has authorised from reading what their role allows. Keeping staff access current is the practice's responsibility.

How long we keep information

Practice and patient records stay in Pegasus for as long as the practice subscribes, and then as described in the practice's agreement with us. A practice must keep clinical records for the period its professional and legal duties require, which is usually several years after a patient's last visit, so Pegasus does not delete clinical records on its own.

Backups exist to recover from a disaster, not as an archive. Each daily backup is kept for 35 days, one backup a month for 12 months, and one a year for seven years. This means a record you deleted can still exist in a backup for a while afterwards. Sign-in sessions expire after eight hours, and single-use sign-in links after 15 minutes.

Ending a subscription, removing a user, or a patient withdrawing permission for reminders does not by itself erase existing records or backups.

Your rights, and how to use them

Under POPIA you may ask whether we hold information about you and ask for a copy of it (section 23), ask us to correct or delete it (section 24), and object to certain processing (section 11(3)).

  • For patient or practice records, contact the practice that holds them. They decide these requests; we help them carry them out.
  • For your Pegasus account, support or billing information, write to privacy@pegerp.com. Say what you want to see, correct or delete, and give us enough detail to find the record.

Please do not send a full clinical record or a copy of your identity document in a first email. We may need to verify, proportionately, who you are and that you are entitled to ask.

We acknowledge a request promptly, tell you who is responsible for the records, pass practice requests securely to that practice, and tell you the outcome. A request to delete something does not override a legal duty to keep it; if we refuse, we tell you why.

You can raise a privacy concern with us at privacy@pegerp.com. You may also complain to the Information Regulator of South Africa, whose site has the current complaint forms and contact details.

How to ask us to delete information

If you have been asked for Pegasus's data deletion instructions, this is the section to read.

"Delete my data" can mean three different things on Pegasus, and they go to different places.

Your Pegasus user account. Write to privacy@pegerp.com from the address the account uses, or ask your practice's administrator to remove you. We delete the account, its passkey records and its sign-in history, and we tell you when it is done. Audit records showing what the account did are kept where we are obliged to keep them, because their whole purpose is to show who did what; if that applies to your request we say so and explain why.

Patient records held by a practice. Contact the practice. It decides these requests, because the records are its responsibility and its professional rules govern how long it must keep them. If you cannot reach the practice, write to privacy@pegerp.com and we will pass the request to it securely and tell you we have done so. We do not delete a patient's clinical records on our own.

A practice's WhatsApp connection. A practice that has connected its WhatsApp Business Account to Pegasus may ask us to disconnect it and delete what we hold because of that connection: the connection's credentials, the reminders sent through it, and their delivery status. Write to support@pegerp.com or privacy@pegerp.com from an address we hold for the practice. We disconnect on request and delete within 30 days. Disconnecting does not delete the practice's appointments or patient records, and it does not close the practice's WhatsApp Business Account with Meta — only Meta can do that. A patient who simply wants the messages to stop should reply STOP instead, which is immediate.

Everything a practice holds in Pegasus. A practice may ask for all of its records and for deletion afterwards. The Terms of Service set out how: a free machine-readable export within 30 days of the request, then deletion from the live system within 30 days of that export being delivered and confirmed.

In every case:

  • Tell us what you want deleted, with enough detail for us to find it. Please do not send a full clinical record or a copy of your identity document in a first email.
  • We may need to check, proportionately, who you are and that you are entitled to ask.
  • We delete from the live database rather than hiding records from the screen. Copies inside backups fall away as those backups expire, on the schedule above, and an expired copy cannot be read without its key.
  • A request to delete does not override a law that requires us to keep something. Where we have to refuse, we tell you why.
  • We answer within 30 days of the request, and sooner where we can.

Appointment reminders over WhatsApp

A practice may choose to send appointment reminders over WhatsApp. When it does, Pegasus sends them on that practice's behalf through Meta's WhatsApp Business Platform, from the practice's own WhatsApp business number. Reminders are off unless a practice switches them on.

  • A reminder carries only what identifies the appointment: the patient's first name, the practice, the practitioner, the date, the time, the place, and answer buttons. It carries no diagnosis, no test result and no other clinical detail.
  • The practice records each patient's permission for WhatsApp reminders against one specific mobile number. If the number changes, the permission does not carry over, and the practice must ask again.
  • Replying STOP stops WhatsApp reminders immediately. The patient receives one acknowledgement and nothing further until the practice records a new permission. Stopping reminders does not delete the patient's records or cancel their appointments.
  • A patient's answer — confirming, cancelling, or asking to move the appointment — and the delivery status of each message are kept in that appointment's history at the practice.
  • Pegasus links an answer to an appointment only through the reference it put in the message it sent, never by matching a phone number.
  • Knowing that a person has an appointment at a healthcare practice is itself health information, even when the message carries no diagnosis. We treat a reminder that way, and so does the practice.
  • Meta processes the message content and delivery information, and does so outside South Africa. Health information may leave South Africa only on one of the grounds in section 72(1) of POPIA, and the 2026 Regulations repeat that restriction. Two of those grounds apply here, and we rely on both: Meta is bound by its own data protection terms for the WhatsApp Business Platform, which commit it to a comparable level of protection and limit what it may pass on (section 72(1)(a)); and the practice has recorded the patient's consent to reminders on that number (section 72(1)(b)). A practice's agreement with us records Meta as a further operator before reminders are switched on.
  • WhatsApp reminder delivery is the only reason any health information leaves South Africa. Hosting, the database, stored files, backups and account email all stay in Cape Town.
  • WhatsApp itself is Meta's service. Meta's own privacy terms govern what it does with a WhatsApp account, separately from this policy.

To ask about information held because of a WhatsApp connection, write to privacy@pegerp.com and tell us which practice and which number. Note that disconnecting a practice's WhatsApp connection and deleting a patient's clinical records are two different requests: ask for whichever you mean, or both.

Cookies and what the browser stores

Pegasus sets one cookie, _pegasus_key. It holds your signed-in session, is signed so it cannot be tampered with, and is necessary for the service to work. There are no advertising or analytics cookies.

Your browser also remembers a few preferences on your own device, in its local storage: light or dark appearance, your chosen font, and how you left the sidebar and panels. These never reach our servers and are not personal information about anyone else. Clearing your browser's site data removes them.

Changes to this policy

This is version 1.0, effective 22 November 2026. If we change something that matters — a new provider, a new category of information, a new purpose — we update the version and date at the top of this page, and we tell practices before the change takes effect. The version in force is always the one published here.

Privacy PolicyTerms of Service
Sign in