Dispatch and Destination User Privacy


Due to the recent requirements of GDPR, we have enabled a new feature in SCORM Cloud. You can now choose to make all user names and IDs obfuscated in the database and in all reports with a one-way hash. This feature can only be enabled on newly created Dispatches and is set at the Destination or Dispatch levels.

This feature makes it easy to create a new Destination with this setting enabled so that when you create new Dispatches using this Destination, the user information will be obfuscated.


You can also set this enabled at the Dispatch level by creating a new Dispatch with the checkbox enabled.


Note that once set, all launches of the Dispatch will be affected and it cannot be reversed once recorded in the database. Even if you disable it on a Dispatch, those users that launched it during the time it was enabled will be obfuscated in all reports.


LearnerID = destination name_280116f51d487926b4fabad9c5a0e7d7e0207a1b12abcdde565024f

First Name = 48d14f2c95d124710121a0c69a6fa3e9ceed2bfad9a4ea0c5f17398ae69fbb64

Last Name = 2d1e830624b2572adc05351a7cbee2d3aa3f6a52b34fa38a260c9c78f96fcd07

Please make sure you have a requirement to use this feature before enabling it and if you have any questions, please send a message to

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


  • Avatar
    Jon Hughes

    Does this setting need to be enabled in order to be GDPR compliant? Or is that up to the end user's organisation to agree with us as data processors?

  • Avatar
    Ryan Donnelly

    Hi Jon - It would be a piece of GDPR compliance. With this option enabled, Learner PII is hashed. Sometimes this is all an organization needs. However, they may require a larger agreement. If you have any further questions, please send an email to

Powered by Zendesk