Privacy Policy
What we collect, why, where it lives and for how long. No fog.
Last updated: 2026-10-01
This document describes how the system actually behaves. Before relying on it legally, have a lawyer review it — especially if you serve patients in the EU.
| Data | Why | How long |
|---|---|---|
| Email and clinic name | Signing in, addressing you, getting in touch | While the account exists |
| Clinic profile and price list | Perla answers patients from exactly this data | While the account exists |
| Patient conversations | So the clinic can see what was asked and answered | Until the clinic deletes them |
| Booking requests | So the front desk can call back and confirm a time | Until the clinic deletes them |
Who the controller is
The Perla service is provided by Vladyslav Kutsyn, Mladá Boleslav, Czechia. Data questions: hello@getperla.eu.
Two roles matter here. For clinic account data we are the controller. For the content of patient conversations the clinic is the controller and we act as a processor on its instructions.
What is collected
Account data: email, clinic name, password (stored only as a hash — we never see it).
Clinic profile: address, opening hours, doctors, services with prices, insurers, hand-off rules. This is what the clinic enters itself, and what Perla answers from.
Patient conversations: message and reply text, timestamps, language, and the page the chat was opened from.
Booking requests: the name and phone number the patient gave, plus a preferred time and reason for the visit.
What we deliberately don't collect
Perla never asks a patient for card numbers, identity documents, insurance policy numbers or medical history. The assistant is instructed not to ask, and there are no payments in the chat at all.
We use no advertising trackers and pass nothing to ad networks.
Legal basis
Account and profile data are processed to perform the contract with the clinic. Patient conversations are processed on the clinic's instructions as a processor. Technical logs rest on the legitimate interest of keeping the service running and protected from abuse.
Where it is stored
Database and authentication run on Supabase, region EU — Ireland (eu-west-1). The application itself runs on a server in Nuremberg, Germany (netcup).
Messages are sent to OpenAI to generate a reply. OpenAI processes them as a data processor and, under their API terms, does not use API request content to train their models.
How long it is kept
Account and profile data for as long as the account exists. When an account is deleted, related data is deleted along with it.
Conversations and booking requests are kept until the clinic deletes them or closes the account. A custom retention period can be agreed on the Network plan.
Your rights
You have the right to obtain a copy of your data, correct it, delete it, restrict processing and object to it. Write to hello@getperla.eu — we reply within 30 days, as GDPR requires.
If you are a patient and want a conversation deleted, contact the clinic directly: the clinic controls that data. We will act on its request.
Security
All traffic runs over HTTPS. Access to clinic data is constrained at the database level by Row Level Security — a clinic technically cannot read another clinic's data even by tampering with the request. The widget's public key permits exactly one action: chatting as its own clinic.
Who data is shared with
Only these services, and only as far as the work requires. There is no list of advertising or analytics partners.
Message text is encrypted before it is written to the database (AES-256-GCM). The key lives only in the application environment and is never stored in the database, so the tables hold no readable text. This is not end-to-end encryption: the model has to read a message in order to answer it, so we remain technically able to decrypt. Claiming otherwise would not be true.
- Supabase Inc.database, authenticationEU (AWS) · account, clinic profile, conversations, requests
- OpenAI Ireland Ltd.generating chat repliesEU / USA · patient messages and the clinic profile sent as context
- Resend, Inc.sending notification email to the clinicUSA · patient name, phone, reason for the visit
- Telegram FZ-LLCclinic notifications and the patient bot — only if the clinic connects itUAE · patient name, phone, and their messages
- netcup GmbHserver hostingNuremberg, Germany · everything in transit; no patient data stored on disk
- Zoho Corporationmailbox for hello@getperla.euEU (Zoho EU data centre) · correspondence sent to us, including data subject requests
