Privacy policy

1. Who is responsible

The controller of your personal data is [to be completed], [to be completed]. For any question about your data, write to [to be completed].

2. Patient data stays on your device

Everything you enter about patients — names, findings, reports — and your clinic settings are stored only in your own browser (local storage). They are never sent to our servers, and we cannot see them.

An encrypted backup is created in your browser and protected with a password that only you know. We never receive the backup file or the password, so we cannot open or restore it.

3. What we store about you

• your email address and whether it has been confirmed;
• a one-way hash of your password, if you sign in with a password (never the password itself);
• if you sign in with Google: your Google account identifier and email address — we do not request or store your name or photo, and we do not keep Google access tokens;
• the date your account was created;
• active sessions: a random session token and its expiry date — no IP address and no device information.

We do not ask for your name, phone number, address or any payment data.

4. Why we process it and on what legal basis

• to create your account, let you sign in and send you the emails needed for that (confirmation, password reset, deletion notice) — performance of a contract, Art. 6(1)(b) GDPR;
• to protect the service against automated abuse (bot check, limits on sign-in attempts) — our legitimate interest in security, Art. 6(1)(f) GDPR.

We do not use your data for advertising or profiling, we do not sell it, and the service contains no analytics or advertising trackers.

5. Service providers

• Cloudflare Turnstile — the bot check on the sign-in, registration and password-reset pages. When these pages load, Cloudflare processes technical data such as your IP address and browser characteristics to tell people from bots (cloudflare.com/privacypolicy).
• Google — only if you choose “Continue with Google”; Google confirms your identity and tells us your email address (policies.google.com/privacy).
• Our email delivery provider — to send confirmation, password-reset and account-deletion emails.
• Our hosting provider — runs the server and stores the account database.

Where a provider processes data outside the European Economic Area, this happens on the basis of the safeguards required by the GDPR (for example the EU Standard Contractual Clauses or an adequacy decision).

6. Cookies and local storage

We use one strictly necessary cookie to keep you signed in, plus short-lived technical cookies during sign-in with Google. Your browser’s local storage holds your examinations, clinic settings, interface language and theme.

All of these are needed for the service to work, so no consent banner is shown. We use no tracking or advertising cookies.

7. How long we keep data

• account data — until you delete your account;
• sessions — until you sign out, or at most 7 days without activity;
• confirmation and password-reset links — they expire after 1 hour (unused ones are deleted with your account);
• IP addresses used to limit sign-in attempts — only in the server’s memory, for a few minutes; never written to the database.

8. Your rights

You have the right to access your data, to have it corrected or deleted, to restrict or object to its processing and to data portability. You can delete your account yourself at any time in Settings → Account; for anything else write to [to be completed].

You also have the right to lodge a complaint with a data protection supervisory authority, in particular in the EU country where you live or work.

9. Deleting your account

When you delete your account, your email, password hash, Google link and all sessions are removed from our database immediately and permanently. We send one final email to confirm the deletion.

Examinations stored in your browser are not touched unless you choose to delete them as well. Backup files you have downloaded remain yours.

10. Security

Passwords are stored only as a salted, slow one-way hash. Connections are encrypted (HTTPS), sign-in pages are protected by a bot check and the number of attempts is limited.

11. Changes to this policy

If we change how we handle your data, we will update this page and the date at the top. Significant changes will be announced in the service.