Legal notice
These terms describe ClinicTreat, the clinic queue and token system. They are the product terms for this service.
Using ClinicTreat means you accept these terms for the clinic queue, token tracking, and related desk tools. If you use the service for a hospital, clinic, or doctor, you do so for that practice. ClinicTreat is a queue and practice tool. It is not a medical device and it does not provide emergency care.
Clinic managers, reception staff, and doctors are responsible for the accounts they open and the actions those accounts take. Keep passwords private, sign out on a shared desk, and give each person only the role they need. Do not share a hospital login as a platform credential. The hospital record in the signed-in session is the scope of that desk.
A hospital or doctor subscription follows the plan quoted for that account. Prices are not shown on the public site until a catalog is configured. Cancellation is requested through Contact Us and takes effect as the quoted plan states. The live service can be paused for maintenance. No separate uptime percentage is published unless a written subscription says otherwise. Patient token advances, such as a JazzCash, EasyPaisa, or bank payment, follow the hospital's own verification rules.
ClinicTreat owns the software, the public site, the desk screens, and the custom components of this platform. A hospital keeps its own name, logo, and records. A subscription lets that hospital use the service. It does not transfer ownership of the software.
ClinicTreat is provided for queue, token, and practice workflow. It does not replace a clinician's judgement or a hospital's own record-keeping duty. We are not liable for a missed visit, a delayed message, a local power or network failure, a printer that is offline, or a loss that comes from a password that was shared. Where the law allows a limit, liability is limited to the subscription fees paid for the affected service in the previous month.
We collect the account details needed to run a desk or a patient account: name, email, phone or WhatsApp number, and a password hash. A booked token stores the patient name, phone, visit date, shift, token number, and payment reference that the patient sends. Clinic staff credentials stay with that hospital. WhatsApp Cloud API traffic is logged as a message kind and a short delivery hint, not as a copy of a private chat for any other purpose.
We use this information to issue and track tokens, print a receipt, schedule a visit, show a queue to the right hospital, and send the WhatsApp or email messages the product is built to send. We do not sell patient lists. A hospital sees only its own records.
Passwords are stored as hashes. Desk access uses a signed token. Hospital data is separated by the hospital on that token. The database is the configured store, which may be SQLite or PostgreSQL. A public deployment should use HTTPS. Staff should not put passwords or patient phone numbers into screenshots or shared notes.
WhatsApp messages go through the Meta WhatsApp Cloud API when that connection is configured. Hosting is the server where this application is deployed. Printing stays on the desk or printer the clinic chooses. Those services receive only what is needed for the message, the page, or the print. They are not a second patient record.
To ask for a copy of your account data, or to ask for the account to be deleted, use Contact Us and choose “Data export or account deletion”. Include the email on the account. We will use that request to export or delete the account data we can match. A hospital remains responsible for the clinical records it is required to keep.
Questions about these terms can go to Contact Us.