> For the complete documentation index, see [llms.txt](https://docs.powermonitor.com.br/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.powermonitor.com.br/en/useful-links/politica-de-privacidade.md).

# Privacy Policy

This Privacy Policy describes how **Power Monitor**, a **Power Tuning** product, collects, uses, and protects the information obtained while you use the platform.

### Data collected

Power Monitor collects only **metadata** from your Microsoft 365 tenant through official Microsoft APIs, with read-only permissions. The data collected includes:

* **Inventory metadata**: names of workspaces, reports, datasets, dataflows, notebooks, pipelines, capacities, and gateways
* **Operational status and history**: refresh status, execution logs, capacity usage, gateway availability
* **Configuration data**: configured alerts, notification preferences, connected tenants
* **User and permission metadata**: user names, access groups, workspace permissions (when enabled)

Power Monitor **does not collect**:

* Content of reports or dashboards
* Data stored in datasets or data sources
* Access credentials for data sources

### Use of data

The data collected is used exclusively to:

* Provide the Power Monitor monitoring and alerting service
* Generate the inventory, performance, and permission reports displayed in the portal
* Send alerts and notifications configured by the user
* Continuously improve the platform's services

The data **is not sold or shared** with third parties for advertising or marketing purposes.

### Storage and security

The data is stored on Power Tuning infrastructure in **Microsoft Azure**, with the following protections:

* Encrypted communication over HTTPS/TLS in transit
* Encrypted data at rest
* Access control restricted to each customer's data
* Power Tuning does not access customer data without explicit authorization, except when required for authorized technical support

### Data retention

* Historical monitoring data (alert history, execution logs) is retained for as long as the customer maintains an active account
* After the account is canceled, the data is retained for 30 days and then permanently deleted

### Your rights

As the data subject, you have the right to:

* Access the data collected by Power Monitor about your environment
* Request correction of inaccurate data
* Request early deletion of the data
* Revoke Power Monitor's access to your tenant at any time (through Microsoft Entra ID)

To exercise these rights or ask questions about privacy, contact us on [WhatsApp](https://powermonitor.com.br/whatsapp) or through the Power Tuning email.

### LGPD compliance

Power Tuning is committed to complying with the **Brazilian General Data Protection Law (LGPD)** (Law No. 13,709/2018) and with the applicable data protection legislation.

### Changes to this policy

Power Tuning may update this Privacy Policy periodically. Significant changes will be communicated to customers by email.

***

*Last updated: April 2026*

*Power Monitor is a product of* [*Power Tuning*](https://powertuning.com.br/)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.powermonitor.com.br/en/useful-links/politica-de-privacidade.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.