Data Processing Agreement for customers.
Roles, instructions, safeguards, sub-processing, incidents, and data return for processing Nubo carries out on behalf of customers.
Controller and processor
For Nubo Cloud services and for projects where we access customer databases, the customer is controller and Nubo is processor: we process personal data solely on the controller’s documented instructions. For data about the commercial relationship itself, Nubo is controller.
- Subject matter: operation of the contracted platform and the services described in the SOW.
- Duration: for the term of the contract, plus the retrieval window.
- Nature: storage, backup, restore, observability, support, and evidence generation.
- Data subjects and data categories: determined by the customer through the workload it sends.
Limits on processing
Nubo does not process customer data for its own purposes, does not use it to train models, and does not monetise it. If an instruction appears to breach the LGPD, we say so before acting on it.
- No secondary use, no profiling, no data enrichment.
- Nubo personnel access is limited to what operation and support require, under confidentiality.
- Administrative access is written to an audit log available to the customer.
Technical and organisational measures
A minimum set of controls applies to every environment that handles customer data, reviewed whenever the architecture changes.
- Encryption: AES-256 at rest and TLS 1.3 in transit; customer-managed keys where contracted.
- Access: strong authentication, least privilege, per-tenant segregation, and periodic permission review.
- Resilience: replication across two Brazilian regions and periodic restore testing.
- Auditability: immutable records of backup, restore, access, and configuration change.
- People: confidentiality agreements plus security and privacy training.
Authorisation and changes
The customer authorises the sub-processors listed on the public Sub-processors page. Before adding a new sub-processor that will handle customer personal data, we give advance notice so a reasoned objection is possible.
- Advance notice: 30 days before the new sub-processor goes live.
- An unresolved reasoned objection entitles the customer to terminate the affected part without penalty.
- We impose protection obligations on sub-processors equivalent to those in this agreement.
International transfer
Nubo Cloud production workloads run in Brazilian regions. Where a sub-processor processes data outside Brazil, the transfer relies on the safeguards of LGPD arts. 33 and 35.
- The Sub-processors page states each provider’s country of processing.
- Contractual protection clauses are required of every provider processing abroad.
Incident notification
On confirming a security incident affecting customer personal data, we notify the controller without undue delay, so it can meet its own duties towards the ANPD and data subjects.
- Notification to the controller: within 48 hours of confirming the incident.
- Content: nature of the incident, data and subjects potentially affected, impact, containment, and remediation.
- We support the controller in notifying the ANPD and data subjects where required.
Supporting data subject rights
If a data subject contacts us directly about data under a customer’s control, we do not answer on the merits: we route the request to the controller and support them technically.
- Export and deletion tooling is made available to the controller.
- Support timelines are compatible with the controller’s statutory response deadline.
Audit and evidence
Customers may verify compliance with this agreement. We lead with documentary evidence so the multi-tenant environment is not exposed, and accept on-site audit where documentary evidence is insufficient.
- Evidence packs and restore reports available on demand through the portal.
- Assisted audit on reasonable notice, in business hours, under confidentiality.
- Return and deletion on termination: export within the agreed window, then deletion, with a deletion statement on request.