Trust
Security, access control and data rights for an aesthetic clinic
Each clinic is isolated in the database itself, not just on screen. Each team member sees what their role allows, sign-in has two-step verification, and every relevant change is written to an audit trail.
Records, clinical photos and appointment history are sensitive data. The right question is not whether a system promises security — it is where security is enforced, and here the answer is: in the database layer, not in the page's JavaScript.
- Per-clinic isolation enforced in the database
- Role-based access: each person sees their own
- Two-step verification to sign in
- Passwords stored with a password-specific algorithm, never as text
- Audit trail with who changed what and when
- Sensitive data is redacted before reaching any log
Isolation where it counts
Separation between clinics is enforced by the database itself, with row-level policy. A query reaching for another clinic's data does not come back empty out of interface politeness: it does not reach. That is the difference between hiding and preventing.
Who can do what
Every route that changes something requires a compatible role, checked on the server. Hiding a button is not access control — the check happens again on the side that decides, even if someone calls the address directly.
A trail instead of trust
A relevant change records who did it, on which record, and how the data looked before. When someone asks why a record changed, the answer is a query, not a reconstruction from memory.
Sensitive data does not leak through logs
Before any technical record, content is redacted. That is the route clinical data usually escapes through in a poorly built system: not the screen, but the log nobody reads until the day of the incident.
What does not exist yet
Stated because it is true, and you should know before signing:
- Data export and deletion for a data subject exist as a service, but **have no button in the dashboard yet** — today they go through support
- There is no published formal certification: what exists is what is described here, verifiable in the product
- The system does not replace the clinic's own data protection officer
- There is no electronic signature of consent inside the product
Frequently asked
Questions about security
Can another clinic see my data?
No. Isolation is enforced in the database with row-level policy, so separation does not depend on the screen filtering correctly.
Does my receptionist see finance?
Only if her role allows it. The check happens on the server for every operation, not only when rendering the menu.
How does deleting a client's data work?
The service exists and runs today through support, because there is no dashboard button yet. It is in the limits above on purpose.
See where security is enforced
Create the account, invite the team and watch access control work.
Meet Bia