Cookies by party
First-party cookies are stored directly on the domain or website the user visits. They collect data for analytical purposes, and remember user settings, including sign-in details, online shopping cart items, and website settings, such as language. First-party cookies cannot be used to track user activities on other websites.
Third-Party Cookies are stored under a different domain than you are currently visiting. Third-Party Cookies are used to track users between websites, and between devices, and help to display more relevant ads between websites.
Cookies by category
Strictly necessary cookiesare essential for websites to function normally or to access particular features, such as the ability to sign in, add items to your cart in an online store, or purchase stuff on the internet. Strictly necessary cookies usually are first-party cookies, and they do not require user consent.
Performance cookies monitor site performance and follow user actions, They can count page visits, examine how much time a user has spent on a website, as well as analyze loading speeds to improve website performance. Performance cookies can be both first-party and Third-Party Cookies.
Functionality cookies are used to enhance the performance of a website as without them certain functions may not be available. They allow remembering user preferences and settings. Functional cookies can be both first-party and Third-Party Cookies.
Targeting cookieshelp to build user profiles and attract customers with targeted ads. They can be shared with other advertisers so that the performance of such ads can be monitored and measured. Targeting cookies are almost always third-party cookies.
Cookies by security
HttpOnly cookies carry a cookie flag that tells the server that the information contained in the flagged cookies should not be transferred beyond the server. These cookies could be accidentally or intentionally revealed to a third party, and they are used when cookies contain sensitive information about the user.
SameSite cookies act as a cookie attribute and are used to control how cookies are submitted in cross-site requests. In other words, the SameSite cookie attribute is used by browsers to identify how first-party and third-party cookies should be handled.
Secure cookies have the secure cookie attribute, and they could be transmitted only through a secure channel when an HTTP request is submitted. Typically, such a channel is HTTPS. The secure cookies attribute protects cookies from being observed by parties that do not have the right to see them.