Understanding tracking with Cookiedatabase.org



Cookie is placed by:

The functionality is:

The purpose is:

This period shows the length of the period at which a service can store and/or read certain data from your computer by using a cookie, a pixel,  an API, cookieless tracking, or other resources. 

This describes if this specific cookie , localStorage or other resource is responsible for sharing, collecting or storing direct or indirect personal data.

You can use this data to update your cookie policy, screen services that set specific cookies or contribute to our effort in creating internet transparency.  Data passport: To see this, just click on the name of the service.

This is the number of times a website requested information from cookiedatabase about this particular “cookie” used on their website.  

One Response

  1. When a load balancer first receives a request from a client, it routes the request to a target (based on the chosen algorithm), and generates a cookie named AWSALB. It encodes information about the selected target, encrypts the cookie, and includes the cookie in the response to the client. The load balancer generated cookie has its own expiry of 7 days which is non-configurable.

    With cross-origin resource sharing (CORS) requests, some browsers require SameSite=None; Secure to enable stickiness. In this case, the load balancer generates a second stickiness cookie, AWSALBCORS, which includes the same information as the original stickiness cookie plus the SameSite attribute. Clients receive both cookies.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Scan your website with iubenda

Get your free compliance report to find out if you have compliance issues and how to solve them.


The Privacy Suite for WordPress. With Cookiedatabase.org API

Burst Statistics

Privacy Friendly Analytics for WordPress

Really Simple SSL

Improve Security for WordPress