Please log in to continue
WalkMe stores your data in the region chosen during account setup.
We have data centers in the US and EU that follow local privacy and compliance laws. If you're not sure which region to select, check with your admin.
This solution hashes the end user identifier client side before any information is sent to our analytics servers so that the end user is anonymized within the WalkMe analytics platform, Insights. This is implemented on a system by system basis, meaning it is possible to apply a different hashing function for each system if needed.
For all analytics events that are sent to WalkMe, the user identifier is attached as a property so that events can be tied back to a user's activity in WalkMe Insights.
In order to add an additional layer of security to the collection of the end user identifier, the value of this identifier can be configured to be hashed. WalkMe supports SHA256 base 64 + SALT.
SALT is a random data that is used as an additional input to a one-way function that hashes data, a password or passphrase. Salts are used to safeguard passwords in storage. WalkMe will store this SALT on the client-side for use in hashing the identifier.
When no SALT is defined, the feature will use the regular SHA256 hashing algorithm. The original end user identifier will not appear or be stored anywhere within the WalkMe infrastructure. The hashing function is run client-side on the end-users web browser, and all communication from their browser to the WalkMe infrastructure only sends the hashed UUID value.
Applying the end user ID hashing does not impact the WalkMe architecture, and the same rules and configuration apply.
The feature applies as part of the WalkMe Player that is running on the client-side machine. When this feature is applied, the WalkMe Player executes the hashing algorithm. Every analytics event sent to the WalkMe server will be sent with the unique hashed unique user identifier.