GDPR checklist for monitoring tools.
Monitoring tools receive logs, errors and request details, which can include identifiers and IP addresses. Compare 4 common tools and see what to check for each.
Compared at a glance
| Tool | Usual role | Data location | Agreement |
|---|---|---|---|
 Sentry | Usually a processor | Set per account or project | Published by the vendor |
 Better Stack | Usually a processor | Set per account or project | Published by the vendor |
 Datadog | Usually a processor | Set per account or project | Published by the vendor |
 New Relic | Usually a processor | Set per account or project | Published by the vendor |
What to check for monitoring tools
- Check what is sent by default, and scrub personal data from logs and error payloads.
- Set a retention period that matches how long you need the logs.
- Record the region where events are stored.
- List the tool as a recipient if user identifiers reach it.
All monitoring tools
Questions, answered.
What should I check before using a monitoring tool under the GDPR?
Check what is sent by default, and scrub personal data from logs and error payloads. Set a retention period that matches how long you need the logs. Record the region where events are stored. List the tool as a recipient if user identifiers reach it.
Do I need a data processing agreement with a monitoring provider?
If the provider handles personal data on your behalf, yes: Article 28 of the GDPR requires a written contract. Some providers publish the text, others give it to you inside your account. Providers that decide their own purposes may act as independent controllers instead, so check the role.
Which monitoring tools does Privacyboard cover?
Sentry, Better Stack, Datadog, New Relic. Each has a page with its agreement, usual role and data location, checked on 1 November 2026.
Other categories
Privacyboard is not affiliated with these vendors. Checked on 1 November 2026. This is guidance, not legal advice.