Updated by Joakim Stenberg
We use localStorage for storing and accessing information on a user's device.
How can users prevent data from being stored or accessed from localStorage?
We are currently in the process of registering for the TCF v2.0 Global Vendor List and will require a TCF v2.0 consent before storing or accessing information from localStorage.
We do not store or access any information on a user's device in case the browser setting Do Not Track has been enabled.
What information is stored and accessed from localStorage?
abRange. Widget variation (design variation of a placement) user was last exposed to in case a widget A/B test is active. A widget A/B test helps us evaluate which design of a widget works best. We store information in localStorage in order to always show the same variation to the same user. We do so ensure a consistent experience even when a widget A/B test is active. By storing this information in localStorage we avoid collecting information about the user, what widget variation to show is determined client side.
uid. User ID set by Smart AdServer. To avoid storing any information related to an individual user on our servers we store this information in localStorage. In conjunction with a valid consent string the user ID is included in our ad calls to Smart AdServer handling the provided user ID according to the provided consent string.
session. Collection of time spent, scroll depth, session time and number of page views. Information is stored in localStorage, accessed by our script and sent to our servers in such a way that we can collect content metrics without any information about individual users.