Skip to content
Talk to us
Menu

Salvus

Security and privacy

What IT, information security and legal teams usually ask, with what Salvus already publishes. Where there is no published document, we say so and answer in the technical conversation.

Talk to the technical team (opens in a new tab)Get the committee kit

What IT asks

Each answer comes from a policy, term or page already published. Those marked “technical conversation” have no published document, and we prefer to say so rather than invent an answer.

Where is the data hosted and in which region?

Hosting, data region and the data protection officer follow each client’s policy. That is why the answer is agreed by contract and confirmed in the technical conversation, rather than being one rule for everyone.

The data region of each deployment follows the client’s policy and is confirmed in writing in the technical conversation.

On the corporate website, data is kept in an operational environment that is not publicly accessible, and Salvus states that third-party services may transfer data to other countries. The details are in the website privacy policy.

Who accesses what? How do profiles work?

In HAI, access is by profile, with authentication and separation between organizations. Registration depends on permission from the organization that licenses the platform, and that organization selects and registers its professionals.

Each person signs in with their own login and password. The terms ask the organization to safeguard passwords, guide its professionals and adopt good information security practices.

Whether the health plan or the hospital accesses the data directly depends on the agreed design. We confirm the scope in the conversation, before any commitment.

Is there an access log (audit trail)?We answer in the technical conversation

We answer in the technical conversation. This page does not state what is not yet documented for publication.

How do backup and service continuity work?We answer in the technical conversation

We answer in the technical conversation. For the ATAS O2 device, connection contingency is described in the ATAS O2 block, further down.

Is data encrypted in transit and at rest?We answer in the technical conversation

We answer in the technical conversation. The policies and terms describe technical and organizational security measures, without detailing algorithms.

How does integration with our systems work?

In HAI, integrations connect the operation’s sources, preserving origin and identity, and are defined in each deployment, after assessment and validation.

In ATAS O2, the integration with the medical record runs on a virtual machine at the hospital, connected to the Salvus environment, with access to the record’s test database. Remote access by our team follows the hospital’s policy. An integration done at one hospital does not count as compatibility at another: each one goes through validation.

Does Salvus have a security certification or seal?

Salvus is not ISO/IEC 27001 certified. It uses the good practices of the ABNT NBR ISO/IEC 27001 standard as a reference, without certification. This page does not claim a seal or a standard met. For HAI, privacy and security documentation is available on request. What is not yet documented we answer in the technical conversation.

How does Salvus report a security incident?

The Brazilian General Data Protection Law (LGPD, art. 48) provides for reporting a security incident to the ANPD (the national data protection authority) and to the data subject when there is relevant risk or harm. In HAI, Salvus is the operator, and the organization that licenses the platform controls the health information.

When an incident may cause relevant risk or harm, Salvus notifies the client within 3 business days, the same period that Resolution CD/ANPD No. 15/2024 sets for reporting to the ANPD and to data subjects. Questions about personal data go to the data protection officer.

How long is data kept?

Patient care records follow the medical record law: they are kept for at least 20 years from the last entry (Law No. 13,787/2018, art. 6). Website data, such as contacts and forms, is kept for as long as needed for its purposes or as the law requires.

ATAS O2 on the hospital network

ATAS O2 combines the device at the point of use, software, connectivity, integration, implementation, training and maintenance. What the hospital IT team follows:

  • Connectivity. The devices communicate with the system through gateways installed in the hospital. Network signal and telemetry are checked at installation, bed by bed.
  • What IT prepares. A virtual machine for the integration, access to the medical record’s test database and remote access by our team through the means the hospital’s policy accepts. The full requirements are in the integration documentation.
  • Validation in four steps. Virtual machine and test database released by IT; connection to the Salvus environment and end-to-end tests; test with a simulated device, followed by IT and the clinical team; real devices at the beds and a technical acceptance statement.
  • Contingency. Validation tests connection loss and reconnection before use at the bed. The device display signals low pressure, low battery and technical failure.
  • Maintenance. Inventory, serial number and maintenance of each device are recorded. Maintenance, replacement and contingency are defined in the contract and in the implementation.
  • Device software update. We answer in the technical conversation

More details on the ATAS O2 page for hospitals. Do not send patient data by email or message.

HAI: profile-based access and patient data

  • Profiles and organizations. Access is by profile, with authentication and separation between organizations. Who accesses what depends on configuration and deployment.
  • Health data. Treated as sensitive personal data, to the minimum necessary for the purpose.
  • Login and password. Each person signs in with their own login and password, and the organization that licenses HAI registers its professionals.
  • Files. Files exchanged between the organization and the health professional are restricted and do not appear to other users.
  • Visit record. Each visit leaves a traceable record, according to the profile and the operation’s configuration. This record supports checking and auditing; analysis and decision remain with whoever audits.

LGPD, roles and data protection officer

Who decides about the data

On the website, Salvus acts as controller or operator, depending on the flow. On the HAI platform and app, Salvus is the operator: the organizations that license HAI and the health professionals hold control of the health information, under professional secrecy rules.

Data protection officer

Salvus’s data protection officer (DPO) is Sião Governança em Privacidade de Dados e Segurança da Informação Ltda. The officer is the channel between Salvus, data subjects and the ANPD. In contracts with hospitals and health plans, hosting, data region and the data protection officer follow each client’s policy.

dpo.juridico@salvus.me Subject: “Meus Dados Pessoais” (Portuguese for “My Personal Data”)

Data subject rights

  1. Write to dpo.juridico@salvus.me with the subject “Meus Dados Pessoais” (Portuguese for “My Personal Data”) and say what you need.
  2. To protect your data, Salvus may ask for information that confirms your identity before responding.
  3. The website policy provides for a reply to legitimate requests within 15 calendar days. If the request is complex or numerous, Salvus informs you and keeps you updated on progress.

The rights set out in the policies follow article 18 of the Brazilian General Data Protection Law (Law No. 13,709/2018): confirmation that processing exists, access, correction, anonymization, blocking or deletion, portability, information about whom the data was shared with, and withdrawal of consent. Some data may be kept when the law requires it or to defend Salvus’s rights; the policies explain each case.

Read the website privacy policy (in Portuguese) and the HAI privacy policy (in Portuguese).

What the website collects

  • When you fill in a form: name, email, phone, company, field of work and role. This data is used to reply to your contact and, if you choose, to send material and the newsletter.
  • Automatically: device and browsing data, such as IP address with date and time and pages visited, through cookies and similar technologies. You can delete or block cookies in your browser. Read the cookies section (in Portuguese).
  • Data is kept in an operational environment that is not publicly accessible and is only stored for as long as needed for the purposes or by law.
  • Salvus does not directly transfer data collected in Brazil to other countries, but third-party services it uses may do so. Salvus states that it seeks third parties with adequate privacy standards.

Security incident: how we report

The LGPD (art. 48) provides for reporting to the ANPD and to the data subject when an incident may cause relevant risk or harm. In HAI, Salvus is the operator and control of the health information belongs to the organization that licenses the platform, which guides who notifies whom.

When an incident may cause relevant risk or harm, Salvus notifies the client within 3 business days, the same period that Resolution CD/ANPD No. 15/2024 sets for reporting to the ANPD and to data subjects. Questions about personal data reach the data protection officer, at the email above.

What we do not promise

Salvus adopts technical and organizational security measures, but the policies and terms state clearly that no system is free of vulnerabilities and that no transmission over the internet is completely secure. That is why this page carries no seal, certification or promise of absolute security.

Where to read the documents

Take it to the committee

For the meeting with IT, security and legal, talk to the technical team or get the kit for the product the committee is assessing.

Talk to the technical team (opens in a new tab)Get the committee kit: ATAS O2 (in Portuguese)Get the committee kit: HAI (opens in a new tab)

Other questions: contato@salvus.me. Do not send patient data by email or message.