Security and data
In short: the data stays in a database in the client's name, each person only sees what their role requires, secret keys never live in the browser, there's a backup every week outside the server and, if the client leaves, they take everything.
Where the data is stored
Each system uses its own database, separate from other clients'. The database runs on a managed cloud database service (managed PostgreSQL), with data stored encrypted by the provider.
Technical detail: managed PostgreSQL (Supabase), always connected over HTTPS.
Who has access
Each team member has their own login. What they see depends on their role: the front desk doesn't need to see finances, and finance doesn't need to see every detail of the records. Phone numbers and other data can appear masked for those who don't need them.
Access rules live in the database itself, not just on screen. Even if someone tries to query the data outside the system, the database only returns what that login is allowed to see.
Technical detail: row-level rules in the database (Row Level Security), applied to every query.
Keys and integrations
Integrations with payments, WhatsApp and artificial intelligence use secret keys. These keys are stored on the automation server, never in the browser, the app or the website code. The page the team uses only loads a public key, which on its own gives no access to any data.
Backups
Every week a full copy of the data is made and stored outside the server where the system runs. If something goes wrong, the data can be restored from the latest copy.
Data protection: who is responsible for what
The client is the data controller: they decide what is collected and why. NESSO is the data processor: it processes data only to make the system work, following the client's instructions and the contract. In clinics, health data is sensitive data, and access to it follows the principle of least privilege.
If something goes wrong
If there is an incident that could put the data at risk, we notify the client without delay, with what happened and what was done, so they can notify the data subjects and the relevant data protection authority, when applicable.
If the client leaves
The contract can be ended with 30 days' notice. The data is exported and handed over to the client within 30 days, in a format that can be opened in a spreadsheet or imported into another system. After delivery, at the client's request, the copies kept by NESSO are deleted.
For your IT team or data protection officer
If your company needs a security questionnaire answered or more technical details, write to contato@nessosistemas.com. See also the website's privacy policy.