What the platform Klinika TES s.r.o. runs on does about security, stated by the software itself, followed by Klinika TES s.r.o.'s own measures. As of 2026-09-16.
The platform
- Sign-in only through the organisation's identity provider (Google or Microsoft), or a one-time code mailed to an existing account; no passwords are stored, and no sign-in path can create or promote an account.
- Role-based access with per-feature levels and per-person overrides; customer-side guests are walled off from sales, marketing, form-response and compliance data at the API, whatever their role.
- Every connection is encrypted in transit; API keys and sign-in codes are stored as hashes, calendar links and tokens are never returned once saved.
- A security trail records sign-ins, role changes and key lifecycle events and is never pruned; the activity log records what changed and by whom.
- Uploaded files are served as downloads, never as pages, and images are checked to be images — a file cannot become a script on the organisation's own address.
- Anything the platform fetches on the organisation's behalf (calendar feeds, webhook deliveries, images) is limited to public HTTPS addresses and never follows a redirect.
- Text sent to a model provider passes a redaction filter for credentials and card numbers first, and a model's answer is always a proposal a person confirms.
Retention in force
- Activity log, captured mail awaiting a decision, model runs: no period set — kept. The security trail is never pruned.
- Form responses: no period set — kept.
- Withdrawn consents and resolved data-subject requests: no period set — kept. Active consents and open requests are kept — they are the record.
- Public-page traffic: no identifier is stored; hit counts are pruned after 13 months.
Your rights
Ask Klinika TES s.r.o. for a copy of everything held about you, a correction or a deletion — the Privacy Center has the forms, and Klinika TES s.r.o. answers within a month.
Klinika TES s.r.o.'s own measures
Klinika TES s.r.o. has not added its own notes yet.
Where this instance is hosted
Hosting and its providers are the platform operator's; see the subprocessor list.