This Policy explains which personal data nuvem.team processes, for what purpose, who we share it with, how long we keep it and how you exercise your rights, under Brazilian Law No. 13,709/2018 (the General Personal Data Protection Law, LGPD).
nuvem.team is a product of NUVEM.ONLINE LTDA, CNPJ 32.676.503/0001-78, headquartered at
Av. Brigadeiro Luís Antônio, 2367, Jardim Paulista, São Paulo/SP, CEP 01401-000, Brazil
("Nuvem.Online", "we"). It brings together on-call, alert management and incident response on the
nuvem.team website, the app.nuvem.team web application, the ingest.nuvem.team ingestion
endpoint and the official apps for macOS, Windows, iOS and Android.
1. Who decides about your data
nuvem.team is used by organizations (our customers) to receive the alerts from their own monitoring, page whoever is on call and respond to incidents. That is why there are two roles:
| Data | Who is the controller | Nuvem.Online's role |
|---|---|---|
| An organization's operational data: members, roles and invitations; events and alerts received from integrations, with the content its monitoring sends; incidents and the conversation of each one; teams, on-call schedules, coverage calendar and escalation policies | The organization | Processor: processes the data on the organization's behalf, only to provide the service |
Personal account, subscription, acceptance of the terms, registered devices and the delivery receipts of the notifications sent to them, notification preferences, access logs and visits to the nuvem.team website | Nuvem.Online | Controller |
If you use nuvem.team through an organization, such as the company you work for, requests about operational data should be made to that organization first. We will support it in handling them.
2. Which data we process
2.1. Account and subscription
- Personal account: name, email and the account identifier at Nuvem.Online's identity provider. The account is the same across all Nuvem.Online products, such as nuvem.works, nuvem.cash and Dorsal.
- Sign in with Google, Microsoft or Apple: optional. If you choose one of them, the provider confirms your identity and shares the account data needed to sign in, such as name and email.
- Subscription: country, the organization's tax ID (CNPJ or CPF), the organization's name and identifier (slug), who subscribed and the plan. On the Team plan, also the legal name and the billing address and email. The payment method stays with the payment processor, not with Nuvem.Online.
- Acceptance of the terms: product, accepted version, the person who accepted, date, time and IP address.
2.2. Operational data
On the organization's behalf, we process what is needed to page the right people and record the response to each incident:
- Members and invitations: who is a member of the organization and each one's role, and the email of whoever was invited, while the invitation is pending. People who don't have an account yet receive the invitation by email.
- Events and alerts: what the organization's integrations send to the ingestion endpoint, stored as received, with the full content, and the results of the HTTP monitor. The organization decides what its monitoring sends; if that content includes personal data, it is stored along with the event.
- Incidents and conversation: the history of each incident and its conversation, with the messages and actions of whoever took part and each author's name. The conversation is seen by everyone who sees the incident: there are no private messages.
- On-call: teams and their members, on-call schedules, the coverage calendar and escalation policies.
The Nuvem.Online team accesses operational data to operate the platform, provide support and, when the organization subscribes, deliver NOC as a Service or assisted setup. Its messages and actions in an incident stay in the conversation, with the name of whoever acted, like those of any member.
What we don't collect: metrics, logs and traces from the organization's systems, which stay in its own infrastructure.
2.3. Devices and notifications
To page you, we register each device where you receive notifications, whether an official app or the browser:
- the device type, the browser or operating system name and the language;
- the installation identifier;
- the push token from the Apple Push Notification service, on iOS, or from Firebase Cloud Messaging, on Android, or, in the browser, the Web Push endpoint and keys;
- the conditions still missing for the device to ring, such as a denied permission;
- the registration, confirmation and last-use dates.
We also keep the delivery receipts of each notification and your notification preferences.
The notification content is end-to-end encrypted (RFC 8291) and carries only the minimum to ring and show on the screen: the organization, the severity, the incident number and title, and a delivery token that lets you Acknowledge without unlocking the device. The push services that carry the notification to the device cannot read that content. On the lock screen, what appears follows your system's preview setting, and opening the incident requires unlocking.
2.4. Web application and official apps
The macOS, Windows, iOS and Android apps keep the session credentials in the operating system's own vault: the Keychain (macOS and iOS), the Android Keystore and the Windows Credential Manager. In the web application, the session is kept in encrypted cookies, which the page's scripts cannot read and which are needed to keep you signed in; the language choice is also kept in a cookie.
The apps ask for permission to show notifications. So that paging for a critical or high incident rings even with the device in silent mode or battery saving, they also ask for:
- on Android: full-screen notification, like an alarm clock's; a foreground service, to ring in a loop; vibration; keeping the screen on; access to the Do Not Disturb policy; and an exception from battery optimization;
- on iOS: time-sensitive notifications and, once Apple approves them, Critical Alerts.
The apps don't use the camera, microphone, location, contacts, photos or advertising identifier, and have no analytics or crash-reporting SDK.
The nuvemteam CLI, which ships with the desktop app, uses the same session as the app. When a
member uses it with their own AI agent, what that agent reads goes to the AI provider chosen by the
person or the organization, under their responsibility.
2.5. Website visits
We measure visits to the nuvem.team website with Umami, an open-source analytics tool that we
host ourselves. It doesn't use cookies, doesn't store your IP address and doesn't build a
profile of visitors. We record the pages viewed, where the visit came from (referring site and
campaign parameters), the approximate country and the type of browser, operating system and device.
We also measure clicks on "Start free", on "Talk about your on-call" and on the WhatsApp
button, without knowing who clicked.
Because it uses no cookies and doesn't identify you, this measurement doesn't require a consent
banner.
2.6. Contact through WhatsApp
The website's WhatsApp button is optional. If you click it, the conversation takes place on WhatsApp, a Meta service, subject to its own rules. We use your number and what you write only to reply and follow up on the conversation. nuvem.team doesn't send alerts or notifications through WhatsApp.
3. What we use the data for and on which legal basis
| Purpose | Legal basis (LGPD, art. 7) |
|---|---|
| Create and maintain the account, including through sign-in with Google, Microsoft or Apple, and subscribe and operate the organization | Performance of a contract |
| Receive events from integrations, open incidents and page whoever is on call | Performance of a contract and the organization's legitimate interest in responding to its own incidents |
| Register devices and deliver notifications | Performance of a contract |
| Keep delivery receipts, to show whether the paging arrived | Performance of a contract and the organization's legitimate interest in following its pages |
| Bill the Team plan | Performance of a contract and compliance with a legal obligation |
| Keep access logs of the application | Compliance with a legal obligation (Brazilian Internet Civil Framework, art. 15) |
| Record the acceptance of the terms | Performance of a contract and regular exercise of rights |
| Keep the platform secure and prevent abuse, such as excessive events at ingestion or use of the HTTP monitor against third parties | Legitimate interest |
| Measure website visits, without identifying visitors | Legitimate interest |
| Reply to contacts through WhatsApp | Preliminary procedures to a contract, at the data subject's request |
We don't sell personal data and don't use it for advertising.
4. Who we share data with
We use providers to operate the service, who process the data only for that purpose:
- Oracle Cloud Infrastructure — platform hosting, in the São Paulo region, Brazil.
- Cloudflare — DNS for the domains (application and ingestion traffic doesn't go through it).
- Apple Push Notification service and Google's Firebase Cloud Messaging — delivery of notifications in the iOS and Android apps. They receive the device token and the encrypted notification.
- Browser push service — in the browser, the notification goes, also encrypted, through its push service, such as Google's in Chrome, Mozilla's in Firefox, Apple's in Safari and Microsoft's in Edge.
- Google, Microsoft and Apple — sign-in, only for those who choose to sign in with one of them.
- Meta (WhatsApp) — only when you choose to talk to us there.
The macOS and Windows apps receive notifications straight from the platform, with no push service in between. The identity provider, email delivery, such as the invitation's, and the website analytics run on infrastructure operated by Nuvem.Online itself, on Oracle Cloud Infrastructure.
nuvem.team doesn't currently send data to artificial intelligence providers.
We may also share data when the law requires it or by order of a competent authority.
5. International transfer
All platform data stays in Brazil. The push services of Apple, Google and the browsers, the sign-in providers, Cloudflare and Meta may process data outside the country; in those cases, the transfer follows art. 33 of the LGPD.
6. How long we keep data
| Data | Retention |
|---|---|
| Operational data of an active organization | While the organization exists |
| Operational data of a closed organization | Erased within 30 days |
| Removed device | Erased within 30 days |
| Notification delivery receipts | 12 months |
| Application access logs | 12 months (the Brazilian Internet Civil Framework requires at least 6 months) |
| Account, subscription and acceptance of the terms | While the contract lasts and, afterwards, for the period needed to exercise rights, of up to 5 years. If you delete your account earlier, it is removed right away and the acceptance is kept for the same period |
| Pending invitation | The invitation is valid for 12 hours. Once expired, the reserved role is erased and the invitation stays in the administrator's list, with the email, until they resend or cancel it |
| Website analytics | No data that identifies visitors |
7. How we protect data
- All platform data stays in Brazil.
- Notification content is end-to-end encrypted and carries only the minimum to ring.
- The apps' session credentials are kept in the operating system's vault.
- Each organization's data is kept separate: each member sees only the organizations they belong to, with the access of their role.
- Each integration has a rate limit at ingestion.
- The HTTP monitor blocks private destinations, so it cannot reach internal networks.
- The apps use no advertising identifier and no analytics or crash-reporting SDK.
If a security incident involving personal data occurs, under art. 48 of the LGPD, that may bring relevant risk or harm, we will notify the affected organizations and the ANPD within the deadlines set by regulation.
8. Your rights
As a data subject, you may request at any time:
- confirmation that we process your data and access to it;
- correction of incomplete, inaccurate or outdated data;
- anonymization, blocking or erasure of unnecessary data or data processed in breach of the LGPD;
- data portability;
- information about who we share your data with;
- review of decisions made solely on the basis of automated processing;
- objection to processing based on legitimate interest, where applicable.
Requests about an organization's operational data, such as an incident's conversation, are forwarded to that organization, which is the controller. To delete your account, see Account and data deletion. You may also file a complaint with the Brazilian National Data Protection Authority (ANPD).
9. Data protection officer
- Name: Wallacy Santos Ferreira
- Email: wallacy@nuvem.online
- Phone: +55 11 4210-1289
- Data subject request form: nuvem.online/privacy
10. Children and teenagers
nuvem.team is a service for organizations and is not intended for anyone under 18.
11. Changes to this Policy
We may update this Policy. The current version is always on this page, with the date of the last update. Relevant changes will be announced in the product itself.