This repository was archived by the owner on Nov 10, 2023. It is now read-only.
Description What is this feature about? (1 sentence)
This removed Safe addresses from Google Analytics tracking for data protection reasons.
Why is it needed? What is the value? For whom do we build it?
Ethereum addresses are considered personal data ("personally identifiable information" or "PII"). This includes Safe addresses.
Due to GDPR, there are some restrictions in place regarding storage and usage of PII.
Hence we decided a while ago not to use it for tracking.
Issue:
Turns out we actually do track Safe addresses: In the "Created a safe" even and in the URL tracking.
Tasks
"Created a safe" event
This event currently uses the Safe address as value. Please leave the event in place but omit the value, i.e. do not track the Safe address.
"URL" tracking
Please omit the Safe address in any URL tracking (e.g. https://gnosis-safe.io/app/#/safes/0xA063Cb7CFd8E57c30c788A0572CBbf2129ae56B6/transactions ).
Instead please use an alternative URL like the following: https://gnosis-safe.io/app/#/safes/SAFE_ADDRESS/transactions . (If that's somehow not possible or you have other ideas, let's talk about it!)
Double check for PII
Please do a sanity check in the code whether the Safe address is tracked to Google Analytics somewhere else where I didn't check.
Reactions are currently unavailable