---
title: "Privacy and Real User Monitoring (Help Center / Privacy & security / Monitoring)"
ai_context: "Use this article for questions about privacy in RUMvision Real User Monitoring, visitor-level RUM data, GDPR, data minimisation and the distinction between monitoring data and account/application data. It explains that RUMvision measures technical website performance for real visitors, does not use RUM data for advertising or behavioural targeting, does not fingerprint visitors or recognise them across unrelated websites, and is not intended to collect direct identifiers such as names, email addresses, account IDs, payment data or form contents. Relevant for questions about what RUMvision collects, whether RUM data can still qualify as personal data, cookie consent, browser storage, optional monitoring features, website-operator responsibilities, privacy safeguards and where to find more detailed monitoring privacy documentation."
canonical: "https://www.rumvision.com/help-center/privacy-security/monitoring/privacy-rum/"
---

Breadcrumbs: [Home](https://www.rumvision.com/?format=md) > [Help Center](https://www.rumvision.com/help-center/?format=md) > [Privacy & security](https://www.rumvision.com/help-center/privacy-security/?format=md) > [Monitoring](https://www.rumvision.com/help-center/privacy-security/monitoring/?format=md) > Privacy and rum

# Privacy and Real User Monitoring

RUMvision measures how your website performs for real visitors. Our monitoring is designed to collect the technical information needed for performance analysis while minimising the amount of information processed about the people using your website.

We do not use visitor-level RUM data for advertising or behavioural targeting, do not fingerprint visitors, and do not recognise visitors across unrelated websites. Our baseline monitoring is also not intended to collect names, email addresses, account identifiers, payment information or form contents.

Some technical RUM data can still qualify as personal data under the GDPR, even when it does not directly identify someone. We therefore treat relevant RUM data accordingly rather than simply describing everything we collect as anonymous.

## Monitoring privacy topics

You can find more detail about each part of our monitoring setup here:

- [**Data collection**](https://www.rumvision.com/help-center/privacy-security/monitoring/what-data-does-rumvision-collect/?format=md) - what the RUMvision snippet collects and why
- [**Cookie consent**](https://www.rumvision.com/help-center/privacy-security/monitoring/consent-before-placing-rumvision/?format=md) - whether consent is required and how browser storage can be configured
- [**Enabling optional features**](https://www.rumvision.com/help-center/privacy-security/monitoring/optional-features-enablement/?format=md) - what changes when you enable additional monitoring capabilities
- [**Your responsibilities**](https://www.rumvision.com/help-center/privacy-security/monitoring/your-responsibilities/?format=md) - what you should review and configure as the website operator
 
## What about personal data in the RUMvision application?

The monitoring running on your website is separate from the RUMvision application used by you and your team.

The application may process personal data such as names, business email addresses, account information, billing information and support history where necessary to provide and manage your RUMvision subscription.

[Read about personal data in the RUMvision application](https://www.rumvision.com/help-center/privacy-security/application/pii-data/?format=md)