/
How is the anonymity of the user guaranteed?
Usercentrics - PUBLIC
How is the anonymity of the user guaranteed?
We assign randomly created but unique IDs to reliably assign Consent data to a user. These IDs are therefore already pseudonyms and are created by the client-side code of the CMP. To pseudonymise the user consent ID, we use the hash procedure SHA-256. A single consent document also receives a unique ID, which is created with a double hash procedure from the user ID and other non-user-specific IDs to increase data integrity and thus also represents a pseudonym. The double hash is created on the server side.
Do you need further help?
Related content
Is there a Best-Practice Guideline as to which options are recommended for a GDPR-compliant integration?
Is there a Best-Practice Guideline as to which options are recommended for a GDPR-compliant integration?
Read with this
How is user anonymity guaranteed?
How is user anonymity guaranteed?
More like this
How does Usercentrics recognize the country from which the user accesses your website?
How does Usercentrics recognize the country from which the user accesses your website?
Read with this
Wie wird die Anonymisierung des Nutzers gewährleistet?
Wie wird die Anonymisierung des Nutzers gewährleistet?
More like this
What does the deleting concept of Usercentrics look like?
What does the deleting concept of Usercentrics look like?
Read with this
If I integrate the CMP via the Google Tag Manager, should the GTM be categorized as "essential"?
If I integrate the CMP via the Google Tag Manager, should the GTM be categorized as "essential"?
Read with this
Usercentrics - PUBLIC