When you visit our web pages, different types of data are stored locally on your device via your web browser. "Locally stored data" can be used to adapt the content and functions of the services and thus make your visit better organized and more meaningful for you. The most common type of local data storage is cookies. These are small text files that are stored on your device (computer, mobile phone or tablet). These files allow us to recognize your browser.In addition to cookies, we also use other similar technologies such as pixel tags. This is technology that recognizes cookies and identifiers and helps third parties place cookies on your device. Albert does not store any data locally on your device, but third parties may do, so when you use our service or visit our website (more on this below).
For what does our third party use local data storage?
Deliver and customize our website and information for the device and browser you use.
Provide the most tailored information and knowledge experience possible when using one of our applications.
Improve Albert and make sure things work as well as possible.
Customize which advertisements you see.
In the browser settings you will usually find an overview of all cookies that are stored. There you can also delete unwanted cookies, specify whether you accept the storage of cookies from the websites you visit, from third parties connected to the websites and if you want to be notified each time a new cookie is saved. More information about cookies and how you can manage them can be found on the the Information Commissioner's Office ('ICO') website.
Below are instructions on how to handle cookies in different browsers. Note that the process for this may change and that the descriptions below will not always be updated.
Below are examples of cookies, scripts and locally stored data that we use to better deliver and adapt content and ensure that things work as well as possible.
|Examples of cookies and scripts for data storage||Actor||Used for|
|CM, CM14, Digitrust.v1.identity, TPC, _qca, gcl_au, adtrc, uid, C, OMITelenor_TNSE, cid||Adform||Used to track traffic from advertising. Information that is stored is used to keep track of whether a visitor has seen certain advertisements or not and ensure that the same advertisements are not displayed again. Disable Adform here.|
|DSID, IDE, _gads, gfp64b||Double-click (Google)||Used to measure the effect of the Google advertising network from e.g. Display advertising.|
|Act, c_user, datr, fr, m_pixel_ratio, presence, sb, spin, wd, xs, Facebook SDK||Used to measure the impact of Facebook's ad network. Also used so that you can easily log in to our application with your Facebook account.|
|1P_JAR, AID, ANID, APISID, CONSENT, HSID, NID, OGPC, S, SAPSID, SID, SID, SSID, DV, UULE||Google Analytics||Used to analyse and to adapt the information on our website based on which device, operating system and browser you use.|
|PHPSSESSID, lc.visitorid.8746731, utmx (x), _fbp, _ga, gat, gclau, _gid, emailAddr, landingpage, letsdealcamp||Albert||Script to be able to identify customers' subscriptions and possible offers in order to be able to provide the best possible customer service for all customers.|
|lc_visitor, _mid, _orig, country, lang, machineid, merchant, session, csrf, user||Stripe||Script used to be able to link a purchase on the website to a PLUS account in our application.|
|Firebase SDK||Firebase||Helps us to see what technical errors occur in the app and how we can best fix them. Also helps us to be able to test new functionality and to launch new things in a controlled way. Finally, used to analyse the traffic.|
|Mixpanel SDK||Mixpanel||Used to be able to analyse user and consumer behaviour in our application in order to make Albert better and ensure that things work as well as possible.|