Security & Data Protection
Klynic is designed to operate on a modern, secure architecture with per-clinic separation, protecting each customer's business, financial and operational information.
Last updated: June 2026
Cloud infrastructure
Klynic relies on modern cloud services such as Google Cloud and Firebase for availability, scalability and secure operation.
Encryption
Communication with the platform is protected via HTTPS/TLS and security measures applied by the cloud infrastructure.
Role-based access
Information is organized by clinic, user, permissions and branch to reduce improper access.
1. Security approach
Klynic applies reasonable technical and organizational measures to protect users' information against unauthorized access, loss, alteration, disclosure or misuse. No system can guarantee absolute security, but we design the platform with an architecture oriented toward reducing risk.
2. Infrastructure
The platform runs on modern cloud services, including Google Cloud Platform and Firebase technologies. This infrastructure allows scaling resources, applying security controls, managing authentication and keeping services reliably available.
3. Encryption and secure communications
The site and platform use HTTPS/TLS connections to protect data transmission between the user's browser and Klynic's services. Protection at rest depends on the security mechanisms offered by the cloud infrastructure and the providers used.
4. Separation by clinic
Klynic is designed to separate information by clinic or organization. Access is managed through users, memberships, roles and permissions, preventing a user from viewing information that does not belong to their clinic.
5. Roles and permissions
The platform may include roles such as owner, administrator, manager or operational user. These roles allow limiting sensitive actions such as financial configuration, user management, treatment plans, patients, costs and reports.
6. Backups and continuity
Cloud infrastructure may provide backup, redundancy and disaster recovery mechanisms. Klynic works to keep the service available, although interruptions may occur due to maintenance, external incidents or causes beyond our control.
7. Activity logging and monitoring
Klynic may log technical events, user activity, errors and operational metrics to improve security, detect incidents, investigate failures and maintain the stability of the service.
8. User responsibility
Security also depends on the user. We recommend using strong passwords, not sharing credentials, controlling who has access to the clinic, logging out on shared devices and reporting any suspicious activity.
9. External providers
To operate Klynic we may use infrastructure, payment, analytics, communication and support providers. We look for reliable providers suitable for the technical processing of information, in accordance with our Privacy Policy .
10. Security contact
To report a vulnerability, incident or security question, write to us at info@klynic.co.
Questions about this document?
Write to us and we will get back to you as soon as possible.