The database is on your machine
When installed locally, the PostgreSQL database sits on the computer you installed it on, along with the files — scans, photographs, x-rays. No copy is sent anywhere, and we have no access to it.
The short answer: on the computer you installed the software on, unless you asked us to host it. The long answer, including what we do not do and what we do not claim, is below.
The essentials
When installed locally, the PostgreSQL database sits on the computer you installed it on, along with the files — scans, photographs, x-rays. No copy is sent anywhere, and we have no access to it.
A button in Settings writes the whole database to a plain SQL file. Copy it to a USB stick; any competent database person can read it without our software. Nothing holds your records hostage.
All three can back themselves up on a schedule, keeping the newest. KlickClinic goes further: once a day it offers the first admin who opens it a one-click copy, and once a week the larger backup that includes the images.
Ready-made roles, each module set to hidden, view or edit, plus separate switches for the sensitive things — patient phone numbers, the practice’s whole books.
Passwords are hashed with bcrypt, every server action re-checks the signed-in user and their permission rather than trusting the browser, and repeated wrong passwords are slowed down.
Removed treatments and visits wait in a list for 90 days and come back complete, with their sessions and their money. An activity log records what changed, who changed it and when.
If we host it
If you choose hosting, your data is not on your machine — it is on a cloud provider’s servers outside Iraq. Each hosted clinic gets a wholly separate project with its own database and its own file storage; no two customers ever share a database.
We pull a verified offsite backup for each hosted clinic, mirror it to a second location, and prove the dumps really restore by restoring them into a scratch database. The last such verification covered all six on 15 September 2026.
If it matters to you that the records sit on hardware you own — and for most clinics it does — choose the local installation. That is the way the software is primarily built to run.
Plainly
Every line here is something we could have left unsaid, or phrased vaguely enough to imply the opposite. This is the list a careful adviser would ask you about, answered before they ask.
There is no insurer billing, no claims, no eligibility checking and no co-pay splitting anywhere in KlickClinic. If your practice runs on insurance work, this is not the program for you today.
KlickClinic does not send WhatsApp or SMS reminders to patients. It produces the recall list — who is due and when — and your staff make the calls. Anyone who tells you otherwise is reading an old README; we removed the claim rather than the feature, because the feature was never there.
Nothing in any of the three programs analyses an OPG, proposes a treatment, or assists with a diagnosis. Prescription templates are suggested by matching the treatment and the conditions you recorded — that is a lookup, not a judgement, and it is the only thing in the software that could be mistaken for one.
There is no multi-branch management from a single login. A clinic is one database and one installation. Two branches means two installations, and they do not share a patient list.
If you run both, they do not synchronise. They are two full installations with two databases, and a backup file is carried between them by hand. KlickLab is the one exception, and only in one direction: the lab PC owns the data and the online copy is a read-only mirror refreshed from it.
A copy installed on your own PC is updated by running the new setup file on that PC. There is no background updater that changes the software under your staff mid-morning — which is also why nothing changes on the day you are busiest unless you choose it.
Every account in KlickClinic is a staff account. Patients do not log in, do not book their own appointments and do not see their records.
We do not claim HIPAA, GDPR or ISO compliance, because we have not been audited against any of them. What we can tell you is exactly where your data sits, who can reach it and how to take a complete copy — and those are on this page.
It is at version 0.2.0 and in daily production use in one company — the owner’s own. Its money arithmetic is covered by 394 automated tests and 133 written business rules, and it is genuinely used every day. It has fewer years behind it than KlickClinic or KlickLab, and you should weigh that.
When a lab invoices a clinic, that cost lands on the clinic’s books and on the dentists’ commission. It never appears on a patient’s balance, and disputing a lab bill in the software does not send anything to the lab — you still telephone them.
This list is not necessarily complete, but it is not a curated selection either. It came out of a review whose explicit job was to try to refute every claim on this site against the programs’ own source — and what did not survive was deleted rather than softened. What survived is the feature list.
Ask it. Questions of this kind get a specific answer, not a reassurance.