Security & data protection
This page is not marketing copy. It describes Klivance's data-security and clinical-safety model as it is — what we store and how, what we never process, and where our limits are. The full legal framework is in the privacy notice.
At a glance
| Patient identity (name, national ID, chart no) | Your choice — you may use a pseudonym code or enter a real name in a patient record; if you enter a name, informing the patient is the physician’s duty |
| Patient files (labs/reports) | Encrypted at the application layer (AES-based) — stored in the database, never on disk in the clear |
| Card details | Never reach us — payment is taken on iyzico's secure page with 3-D Secure |
| Passwords | Argon2id hash — plain text is never stored |
| In transit | All traffic is encrypted with HTTPS/TLS |
| Deletion | Files: content removed immediately · Accounts: permanently deleted within 30 days |
Patient data: the physician decides
You can open every patient record under a pseudonym code (e.g. K-2041); the age band — or, if you prefer, the exact age — chronic conditions and medication list attach to that code. You may also enter your patient’s real name — that is a choice, not a requirement.
Exact age is optional: for dosing and renal assessment it is clinically more useful than a band, but if you leave it empty the record keeps working with the age band alone. If you do enter it, decide knowing that it makes the record more identifiable.
The consequences of that choice are straightforward:
- If you use a pseudonym code: the records contain no patient identity; only you know the identity, in your own records.
- If you enter a real name: the record becomes health data relating to an identified person — special-category personal data under Article 6 of the KVKK. Informing your patient and obtaining any consent required from them is your duty as the physician; Klivance does not obtain that consent on your behalf and does not verify that it exists.
- Either way: your patient files are stored encrypted (see below) and, if you close your account, permanently deleted within 30 days at most.
⚠ Enter only what is clinically necessary. We recommend redacting identity and contact details you do not need from lab/report files before uploading them (data minimisation).
Encryption and account security
- Patient files: every file is encrypted at the application layer with AES-based encryption plus integrity verification (HMAC) and stored encrypted in the database; no plain copy is kept on disk. The encryption key lives outside the database, and key rotation is supported.
- Passwords: irreversibly hashed with Argon2id; a plain-text password is never stored. You can also sign in without a password, via your Google account.
- Sessions: server-side; your browser holds only a random session token (HttpOnly + SameSite cookie; HTTPS-only in production).
- In transit: all traffic is encrypted with TLS (HTTPS).
Deletion and retention
- Deleting a file: when you delete a file, its encrypted content and extracted text are removed immediately; the remaining record trace is fully deleted within 30 days at most.
- Deleting your account (right to be forgotten): request deletion from your Account page; during a 30-day grace period you can sign in and cancel. When the period ends, the account and all linked clinical data are deleted permanently.
- Financial records: invoice and payment records are retained for 10 years as required by Turkish tax law.
The full retention schedule is in the privacy notice.
AI processing
Your questions, the clinical notes in your patient records and the documents you upload are processed on the AI infrastructure we use to generate the answer. Under the applicable provider policy, data processed through the API is not used to train models by default. This data is used solely to generate a clinical decision-support answer for you; it is not used for marketing and is not sold.
Payment security
Your card details are never collected on Klivance pages. Payment is taken on the secure payment page of iyzico, a licensed payment institution based in Türkiye, with 3-D Secure verification; your card data is processed by iyzico only — it never reaches us at any stage.
Clinical safety design
- It does not diagnose. Klivance is not a medical device; it lays the evidence and reasoning in front of you with citations — the decision is yours.
- If it can't ground a claim, it says so. Every claim links to a named source; when the evidence is thin or missing, the answer states that plainly.
- It asks first on risky actions. When the safety of a stated decision depends on a missing piece of information, a clarifying question comes before the full answer (included in your subscription).
- Safety layers are never placed behind the paywall. The dose double-check and red-flag screening are included in your subscription and keep working even after your trial ends. These layers don't decide — they flag for your review.
- Not for emergencies. Klivance is not designed for time-critical emergency decision-making; in an emergency, call your local emergency number.
What we don't do
- We don't collect ID or diploma images; entering patient identity is never required.
- We don't send marketing e-mail — you receive transactional messages only (verification, receipts).
- We don't sell your data to third parties for marketing.
- We don't store card details — we never even see them.
Honest limits
We don't yet hold an independent security certification (ISO 27001, SOC 2) — we are early-stage, and instead of certification badges we prefer to state our concrete design decisions openly on this page. Questions: info@klivance.com.
Vulnerability disclosure
If you believe you've found a security vulnerability, write to info@klivance.com. Good-faith reports are welcome and answered quickly.