-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[GDPR] Ip Anonymisation #322
Comments
Hi @rolebi This feature is coming very soon. The choice between all these options will be available in Datadog's interface. |
Great : ) |
Very interested by this as well. We would love to use RUM and Logs, but because we can't anonymise IPs to be GDPR compliant we are not using it. |
Is there any news on this ? we're also looking to anonymize or have an option to remove network details altogether. |
We would also love to have this feature. What we did to make it work right now is:
Hope this will be helpful for the others. |
Hi @tchock thanks a lot for raising this. Apologies for the delay! Here is the situation for now: RUM Browser Logs The vast majority of users actually need the IP address and geoIP data, which is why it is enabled by default. On logs specifically, we are stuck with how integrations pipelines work: there's no simpler way to customize them. Once again thank you for the patience here. I will answer with the appropriate documentation links once it's live. |
Any updates on this? :D |
+1 for updates. There's mention of the workaround above being documented. Did this ever happen? Many thanks |
any news ? |
Update? |
Hi, @hdelaby Any updates on the feature? |
Hello, The situation is still the same, to remove IP addresses from RUM data, you need to go through support@datadoghq.com. We'll let you know here if we have any update on the topic. |
@bcaudan , we don't use RUM, but we still want to avoid logging IP/geo in the regular browser intake. We've contacted support, and they've only linked us to Any recommendation? Is that something support is able to solve similar to for RUM? |
@johnkors for browser logs, did you tried the mentioned workaround? |
@bcaudan Not sure how that would work for browser logs. We're never sending anything related to network. It's appended at datadog servers. |
One workaround to ensure that the IP/Geo information is never forwarded from the clients to Datadog regardless of whether it's stored or not (would still show up in access logs etc) is to setup a simple HTTP proxy between your clients and Datadog. |
@henningms Hi ;) Yeah, that's our last resort. |
Hi! 😂 It's quickly becoming my default in the projects 😅 Allows us to control what is sent and eases the minds of the legal/GDPR team |
The mentionned workaround allow you to customize what is done by datadog servers. |
Sorry, I misread "cloning" as a code change in this repo (as in a fork). My fault. I'll try out the pipeline mods. Thanks. |
Any update on this request? Seems like a feature that many would find useful. The workaround mentioned above might not be viable for everyone. |
Hello, Here is the current state: RUM Logs
You can anonymise the IP by:
|
Hi,
Is there a way to anonymise the IP address that is stored with each log ? It is a requirement to be compliant with privacy regulations in Europe (GDPR/E-Privacy).
The full IP shouldn't be available at all in the source data and shouldn't be used for GeoIP resolution. Only the "pseudo-anonymized" IP can be stored and used for GeoIP resolution.
For a lack of official sources I redirect you to the GA documentation: https://support.google.com/analytics/answer/2763052?hl=en
The text was updated successfully, but these errors were encountered: