Security and privacy
Security by design, at every layer
The health data are among the most sensitive that exist, so security cannot be a feature that is added at the end: it is part of every design decision, every technological choice, and every data flow.
In the UbitelCare architecture, each layer has protective measures according to their function: authentication and authorization centralized, systematic encryption of data in transit and at rest, and access control by roles, so that each user only accesses what their role requires.
He GDPR compliance It's not a checklist, but a design criterion.
The goal is a secure system in a sustained manner and with continuous improvement, not just at launch.

How the security model works
Four layers of protection that work in a coordinated manner.
01
Identity and authentication
Centralized identity management that verifies each user before granting access. It operates with access and refresh tokens, transparent permission renewal, and automatic error recovery. Every login is logged and traceable.
02
Role-based authorization
Each role only has access to what is relevant to it: the cardiologist to the patients of their institution, the patient to their information, the administrator to their organization. No one has access outside their designated area.
03
Data encryption
Sensitive data is protected in two states: in transit, all communications travel encrypted by HTTPS; at rest, the database applies encryption that preserves confidentiality even in the event of unauthorized access to the storage.
04
Cloud infrastructure security
Cloud infrastructure provides its own layers of protection: firewalls, intrusion detection, continuous monitoring, and regular audits. UbitelCare inherits these measures and combines them with those implemented in the system design.

The GDPR as a design criterion
Compliance with Regulation (EU) 2016/679 is not a post-development step: it has guided the platform's design decisions from the outset. Personal data flows have been assessed to minimize the exposure of sensitive information.
- Pseudo-anonymization: identity is separated from physiological data
- Right to limit access and request account deletion
- Health data processed with enhanced safeguards and a legitimate basis
- Privacy built into the architecture, not added later
What we don't claim
Our framework for healthcare software is Regulation (EU) 2017/745 (MDR) and the associated medical software quality and lifecycle standards.
UbitelCare does not claim security certifications it does not possess. The ISO 27001, ISO 27017, ISO 27018, ISO 27701, IEC 81001, ENS, and HIPAA standards belong to other industry stakeholders; attributing them to us would be incorrect. The framework described on this page reflects the measures actually implemented and documented in our system, without claiming external certifications we do not hold.
An evolution-oriented model
The measures described on this page are not an end point. They form the basis of a model that is reviewed and strengthened as the platform and its environment change.
Security is not a state that is achieved, but an ongoing process. UbitelCare's model evolves as the system grows, new solutions and data sources are incorporated, and the threat landscape changes. The use of world-class cloud infrastructure ensures that the infrastructure layer remains constantly up-to-date.
Do you have specific security requirements for your organization?
If you represent a healthcare institution, operator, or integrator with specific security requirements, the UbitelCare technical team can provide detailed documentation of the security model under a confidentiality agreement.


