--- title: "Cookie policy" canonical_url: "https://www.smoltek.com/cookie-policy/" date: 2025-06-14 author: "Thomas Barregren" --- # Cookie policy # Cookie policy With this cook­ie pol­i­cy, we would like to explain what cook­ies and cook­ie-like tech­nolo­gies are, how we and oth­er ser­vice provider use them on this web­site, what infor­ma­tion they col­lect, for how long and for what pur­pos­es we use them. ## Table of contents - [Con­troller of the website](https://www.smoltek.com#controller-of-the-website) - [Addi­tion to the pri­va­cy policy](https://www.smoltek.com#diff-to-privacy-policy) - [What are cook­ies and sim­i­lar technologies?](https://www.smoltek.com#cookie-technology) - [What is the legal basis for setting/​reading cookies?](https://www.smoltek.com#legal-basis) - [What rights does the web­site vis­i­tor have?](https://www.smoltek.com#rights-of-visitor) - [How to man­age cook­ies in a browser?](https://www.smoltek.com#manage-cookies) - [What types of cook­ies exist?](https://www.smoltek.com#types-of-cookies) - [Who can set cook­ies on this website?](https://www.smoltek.com#cookies-origin) - [Which cook­ies are used on this website?](https://www.smoltek.com#list-of-services) ## Controller of the website - **Provider:** Smoltek, Swe­den - **Email:** [info@smoltek.com](mailto:info@smoltek.com) - **Phone:** [+46 317 01 03 05](tel:+46%20317%2001%2003%2005) - **Con­tact form:** [www.smoltek.com/contact/](https://www.smoltek.com/contact/) ## Addition to the privacy policy This cook­ie pol­i­cy is a sup­ple­ment to this web­site’s [pri­va­cy pol­i­cy](https://www.smoltek.com/privacy-policy/). The cook­ie pol­i­cy spec­i­fies how a web­site uses cook­ies and what data it col­lects through them, while the pri­va­cy pol­i­cy is a more com­pre­hen­sive overview of all data pro­cess­ing activ­i­ties on the web­site and beyond. ## What are cookies and similar technologies? Cook­ies are small pieces of infor­ma­tion sim­i­lar to text files that can be stored and read on the end device. They serve var­i­ous pur­pos­es, includ­ing main­tain­ing basic func­tion­al­i­ties of the web­site, secu­ri­ty and pri­va­cy, pro­vid­ing option­al func­tions of the web­site, col­lect­ing sta­tis­tic data on vis­i­tor flows and pro­vid­ing mar­ket­ing sys­tems. Prac­ti­cal exam­ples of what can be stored in cook­ies are the stor­age of login sta­tus in user accounts, the con­tent of shop­ping bas­kets in e‑commerce plat­forms, or a user ID for track­ing behav­ior on the web­site. The infor­ma­tion can tech­ni­cal­ly be stored in var­i­ous ways. The best-known exam­ples of this are HTTP cook­ies and cook­ie-like tech­nolo­gies like local stor­age, ses­sion stor­age or Indexed­DB. Each type of stor­age has dif­fer­ent prop­er­ties, which deter­mine the tech­ni­cal han­dling, acces­si­bil­i­ty and con­trollers autho­rized to access the infor­ma­tion. All these types of stor­age are usu­al­ly sum­ma­rized under the term “cook­ies” and are there­fore called as such in this cook­ie policy. ## What is the legal basis for setting/​reading cookies? The set­ting and read­ing of cook­ies in the Euro­pean Union (EU) and the Euro­pean Eco­nom­ic Area (EEA) is in accor­dance with Art. 5 (3) ePri­va­cy Direc­tive and Recital 66 ePri­va­cy Direc­tive only per­mit­ted if a user has giv­en his con­sent on the basis of com­pre­hen­sive infor­ma­tion about the pur­pos­es of the pro­cess­ing. The web­site oper­a­tor may also set cook­ies if they are strict­ly nec­es­sary to pro­vide you as a user with the express­ly request­ed ser­vice, e.g. the basic con­tent of this web­site or oth­er strict­ly nec­es­sary cook­ies for basic func­tion­al­i­ty of the web­site to be dis­played to you with­out your consent. ## What rights does the website visitor have? Ser­vices and their cook­ies can be set and read on the legal basis of your con­sent or a legit­i­mate inter­est. When you first vis­it­ed this web­site, you were asked for your con­sent and you had the oppor­tu­ni­ty to object to the use of cer­tain ser­vices. We explained which legal basis is used for which ser­vice in our con­sent dia­log. You have the right to view the his­to­ry of your deci­sions, change your pri­va­cy set­tings, object to the use of ser­vices and revoke your con­sent at any time. Below you find pos­si­bil­i­ties to exer­cise your rights: - [Change pri­va­cy settings](https://www.smoltek.com#consent-change) - [Pri­va­cy set­tings history](https://www.smoltek.com#consent-history) - [Revoke con­sents](https://www.smoltek.com#consent-revoke) ## How to manage cookies in a browser? - **How to remove cook­ies in a brows­er:** To remove cook­ies from your device, you can clear the brows­ing data in the set­tings of your brows­er. This action will remove all cook­ies from all web­sites you’ve vis­it­ed, poten­tial­ly includ­ing saved login details and site pref­er­ences. In some browsers, you can just delete the cook­ies and sim­i­lar data with­out delet­ing the whole brows­ing history. - **How to con­trol cook­ies in a brows­er:** For more gran­u­lar con­trol over cook­ies spe­cif­ic to cer­tain web­sites, nav­i­gate to the pri­va­cy and cook­ie set­tings with­in your used brows­er. Here, you can adjust pref­er­ences relat­ed to indi­vid­ual sites’ cook­ie usage. - **How to block cook­ies in a brows­er:** It’s pos­si­ble to con­fig­ure most mod­ern browsers in their set­tings to block all cook­ies from being placed on your device. But block­ing cook­ies could lead to cer­tain ser­vices and func­tion­al­i­ties not func­tion­ing cor­rect­ly, e.g. logins as a user. You can also use exten­sions for many browsers which can block the set­ting of cook­ies on websites. - **How to man­age cook­ies on this web­site:** To tai­lor your pref­er­ences regard­ing cook­ies on this web­site, you can change your pref­er­ences at any time by click­ing on the link in the sec­tion “Rights of the web­site visitor”. You can find more infor­ma­tion on the han­dling of cook­ies [devowl.io/rcb/cookie-handling/](https://devowl.io/rcb/cookie-handling/). ## What types of cookies exist? - **Essen­tial cook­ies** are indis­pens­able for the basic func­tion­al­i­ty of a web­site and enable func­tions such as sav­ing login infor­ma­tion or access to secure areas of the site. These include, for exam­ple, secu­ri­ty cook­ies, which can iden­ti­fy a bot that is not want­ed on the web­site by stor­ing an authen­ti­ca­tion key in a cookie. - **Func­tion­al cook­ies** improve the user expe­ri­ence by stor­ing infor­ma­tion and pref­er­ences such as lan­guage set­tings or appear­ance set­tings of the web­site to pro­vide per­son­al­ized. This includes, for exam­ple, pref­er­ence cook­ies that store the user’s pre­ferred video qual­i­ty on a website. - **Sta­tis­tics cook­ies** col­lect data about the use of a web­site to gain insights into user behav­ior and opti­mize the per­for­mance of the site. This includes, for exam­ple, a ran­dom­ly assigned user ID that makes it pos­si­ble to attribute whether you have vis­it­ed a sub­page of the website. - **Mar­ket­ing cook­ies** are used to track user behav­ior across dif­fer­ent web­sites and to dis­play per­son­al­ized adver­tis­ing based on the inter­ests and surf­ing behav­ior of users. This includes, for exam­ple, adver­tis­ing cook­ies that store an inter­ac­tion with an adver­tise­ment on the web­site and pass it on to adver­tis­ers or a chat sys­tem for pre-sale ques­tions and cus­tomer support. ## Who can set cookies on this website? On this web­site, both the oper­a­tor of the web­site and third-par­ty ser­vices which are used on this web­site may set cook­ies and access its con­tent. Who can access which cook­ies and their con­tent dif­fers between first-par­ty and third-par­ty cook­ies. First-par­ty cook­ies are cre­at­ed by the vis­it­ed web­site and can only be read by the web­site oper­a­tor and inte­grat­ed third-par­ty ser­vices on this web­site. Third-par­ty cook­ies are set by usu­al­ly third-par­ty ser­vices on oth­er domains, can be read on all web­sites on which the ser­vice that con­trols the domain is embed­ded and, for exam­ple, used by adver­tis­ing net­works to track user behav­ior across dif­fer­ent web­sites and offer per­son­al­ized advertising. ## Which cookies are used on this website? | Cat­e­go­ry | Tech­ni­cal cook­ie name | Tech­ni­cal cook­ie host | Ser­vice | Dura­tion | Type | Pur­pose | |--------------|--------------------------------------------------------------|---------------------------|--------------------------------|-----------|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Essen­tial | real\_​cookie\_​banner* | .smoltek.com | Real Cook­ie Banner | 365 days | HTTP Cook­ie | Unique iden­ti­fi­er for the con­sent, but not for the web­site vis­i­tor. Revi­sion hash for set­tings of cook­ie ban­ner (texts, col­ors, fea­tures, ser­vice groups, ser­vices, con­tent block­ers etc.). IDs for con­sent­ed ser­vices and ser­vice groups. | | Essen­tial | real\_cookie\_banner\*-tcf | .smoltek.com | Real Cook­ie Banner | 365 days | HTTP Cook­ie | Con­sents col­lect­ed under TCF stored in TC String for­mat, includ­ing TCF ven­dors, pur­pos­es, spe­cial pur­pos­es, fea­tures, and spe­cial features. | | Essen­tial | real\_cookie\_banner\*-gcm | .smoltek.com | Real Cook­ie Banner | 365 days | HTTP Cook­ie | Con­sents into con­sent types (pur­pos­es) col­lect­ed under Google Con­sent Mode stored for all Google Con­sent Mode com­pat­i­ble services. | | Essen­tial | real\_­cook­ie\_ban­ner-test | .smoltek.com | Real Cook­ie Banner | 365 days | HTTP Cook­ie | Cook­ie set to test HTTP cook­ie func­tion­al­i­ty. Delet­ed imme­di­ate­ly after test. | | Essen­tial | real\_​cookie\_​banner* | https://www.smoltek.com | Real Cook­ie Banner | \- | Local Stor­age | Unique iden­ti­fi­er for the con­sent, but not for the web­site vis­i­tor. Revi­sion hash for set­tings of cook­ie ban­ner (texts, col­ors, fea­tures, ser­vice groups, ser­vices, con­tent block­ers etc.). IDs for con­sent­ed ser­vices and ser­vice groups. Is only stored until con­sent is doc­u­ment­ed on the web­site server. | | Essen­tial | real\_cookie\_banner\*-tcf | https://www.smoltek.com | Real Cook­ie Banner | \- | Local Stor­age | Con­sents col­lect­ed under TCF stored in TC String for­mat, includ­ing TCF ven­dors, pur­pos­es, spe­cial pur­pos­es, fea­tures, and spe­cial fea­tures. Is only stored until con­sent is doc­u­ment­ed on the web­site server. | | Essen­tial | real\_cookie\_banner\*-gcm | https://www.smoltek.com | Real Cook­ie Banner | \- | Local Stor­age | Con­sents col­lect­ed under Google Con­sent Mode stored in con­sent types (pur­pos­es) for all Google Con­sent Mode com­pat­i­ble ser­vices. Is only stored until con­sent is doc­u­ment­ed on the web­site server. | | Essen­tial | real\_­cook­ie\_ban­ner-con­sent-queue* | https://www.smoltek.com | Real Cook­ie Banner | \- | Local Stor­age | Local caching of selec­tion in cook­ie ban­ner until serv­er doc­u­ments con­sent; doc­u­men­ta­tion peri­od­ic or at page switch­es attempt­ed if serv­er is unavail­able or overloaded. | | Func­tion­al | \_​ga\_​BZBL1GE94X | .spotlightstockmarket.com | Spot­light Stock­mar­ket Graph | 1 year | HTTP Cook­ie | \- | | Func­tion­al | \_​ga | .spotlightstockmarket.com | Spot­light Stock­mar­ket Graph | 1 year | HTTP Cook­ie | \- | | Func­tion­al | \_​gcl\_​au | .spotlightstockmarket.com | Spot­light Stock­mar­ket Graph | Ses­sion | HTTP Cook­ie | \- | | Func­tion­al | SIDCC | .google.com | YouTube | 1 year | HTTP Cook­ie | \- | | Func­tion­al | SIDCC | .youtube.com | YouTube | 1 year | HTTP Cook­ie | \- | | Func­tion­al | VISITOR\_​INFO1\_​LIVE | .youtube.com | YouTube | 7 months | HTTP Cook­ie | \- | | Func­tion­al | LOGIN\_​INFO | .youtube.com | YouTube | 13 months | HTTP Cook­ie | \- | | Func­tion­al | CONSENT | .youtube.com | YouTube | 9 months | HTTP Cook­ie | \- | | Func­tion­al | CONSENT | .google.com | YouTube | 9 months | HTTP Cook­ie | \- | | Func­tion­al | OTZ | www.google.com | YouTube | 1 day | HTTP Cook­ie | \- | | Func­tion­al | yt-remote-device-id | https://www.youtube.com | YouTube | \- | Local Stor­age | Unique device ID, time of cre­ation and expi­ra­tion of the object | | Func­tion­al | yt-fuller­screen-edu-but­ton-shown-count | https://www.youtube.com | YouTube | \- | Local Stor­age | \- | | Func­tion­al | yt-remote-con­nect­ed-devices | https://www.youtube.com | YouTube | \- | Local Stor­age | List of devices asso­ci­at­ed with a YouTube account, time of cre­ation and expi­ra­tion of the object | | Func­tion­al | yt-play­er-band­width | https://www.youtube.com | YouTube | \- | Local Stor­age | Infor­ma­tion on the band­width util­i­sa­tion of the YouTube play­er, time of cre­ation and expi­ra­tion of the object | | Func­tion­al | LogsDatabaseV2:\*\|\| | https://www.youtube.com | YouTube | \- | Indexed­DB | \- | | Func­tion­al | Ser­vice­Work­er­Logs­Data­base | https://www.youtube.com | YouTube | \- | Indexed­DB | \- | | Func­tion­al | Ytldb­Meta | https://www.youtube.com | YouTube | \- | Indexed­DB | \- | | Func­tion­al | yt-play­er-qual­i­ty | https://www.youtube.com | YouTube | \- | Local Stor­age | Out­put video qual­i­ty for YouTube videos, time of cre­ation and expi­ra­tion of the object | | Func­tion­al | yt-play­er-per­for­mance-cap | https://www.youtube.com | YouTube | \- | Local Stor­age | \- | | Func­tion­al | Per­sis­ten­tEn­ti­ty­S­toreDb:\*\|\| | https://www.youtube.com | YouTube | \- | Indexed­DB | \- | | Func­tion­al | yt-idb-pref-stor­age:\*\|\| | https://www.youtube.com | YouTube | \- | Indexed­DB | \- | | Func­tion­al | yt.innertube::nextId | https://www.youtube.com | YouTube | \- | Local Stor­age | \- | | Func­tion­al | yt.innertube::requests | https://www.youtube.com | YouTube | \- | Local Stor­age | \- | | Func­tion­al | yt-html5-player-modules::subtitlesModuleData::module-enabled | https://www.youtube.com | YouTube | \- | Local Stor­age | \- | | Func­tion­al | yt-remote-ses­sion-app | https://www.youtube.com | YouTube | SESSION | Ses­sion Storage | Appli­ca­tion used for the ses­sion and time of object creation | | Func­tion­al | yt-remote-cast-installed | https://www.youtube.com | YouTube | SESSION | Ses­sion Storage | Sta­tus of instal­la­tion of the ‘remote-cast’ func­tion and time of object creation | | Func­tion­al | yt-remote-ses­sion-name | https://www.youtube.com | YouTube | SESSION | Ses­sion Storage | Name of the active ses­sion and time of object creation | | Func­tion­al | yt-remote-cast-avail­able | https://www.youtube.com | YouTube | SESSION | Ses­sion Storage | Sta­tus of avail­abil­i­ty of the ‘remote-cast’ func­tion and time of object creation | | Func­tion­al | yt-remote-fast-check-peri­od | https://www.youtube.com | YouTube | SESSION | Ses­sion Storage | Time of object cre­ation as a deter­mi­na­tion of whether the remote-cast func­tion can be accessed | | Func­tion­al | \*\|\|::yt-player::yt-player-lv | https://www.youtube.com | YouTube | \- | Local Stor­age | \- | | Func­tion­al | swpush­no­ti­fi­ca­tions­db | https://www.youtube.com | YouTube | \- | Indexed­DB | \- | | Func­tion­al | yt-play­er-local-media:\*\|\| | https://www.youtube.com | YouTube | \- | Indexed­DB | \- | | Func­tion­al | yt-it-response-store:\*\|\| | https://www.youtube.com | YouTube | \- | Indexed­DB | \- | | Func­tion­al | \_\_HOST-GAPS | accounts.google.com | YouTube | 13 months | HTTP Cook­ie | \- | | Func­tion­al | OTZ | accounts.google.com | YouTube | 1 day | HTTP Cook­ie | \- | | Func­tion­al | \_\_Se­cure-1PSID­CC | .google.com | YouTube | 1 year | HTTP Cook­ie | \- | | Func­tion­al | \_\_Se­cure-1PA­PISID | .google.com | YouTube | 1 year | HTTP Cook­ie | \- | | Func­tion­al | \_\_Se­cure-3PSID­CC | .youtube.com | YouTube | 1 year | HTTP Cook­ie | \- | | Func­tion­al | \_\_Se­cure-1PA­PISID | .youtube.com | YouTube | 13 months | HTTP Cook­ie | \- | | Func­tion­al | \_\_Se­cure-1PSID | .youtube.com | YouTube | 13 months | HTTP Cook­ie | \- | | Func­tion­al | \_\_Se­cure-3PSID­CC | .google.com | YouTube | 1 year | HTTP Cook­ie | \- | | Func­tion­al | \_\_Se­cure-ENID | .google.com | YouTube | 13 months | HTTP Cook­ie | \- | | Func­tion­al | \_\_Se­cure-1PSID | .google.com | YouTube | 13 months | HTTP Cook­ie | \- | | Func­tion­al | ytGe­f­Con­fig:\*\|\| | https://www.youtube.com | YouTube | \- | Indexed­DB | \- | | Func­tion­al | \_\_Host-3PLSID | accounts.google.com | YouTube | 13 months | HTTP Cook­ie | \- | | Func­tion­al | LSID | accounts.google.com | YouTube | 13 months | HTTP Cook­ie | \- | | Func­tion­al | ACCOUNT\_​CHOOSER | accounts.google.com | YouTube | 13 months | HTTP Cook­ie | \- | | Func­tion­al | \_\_Host-1PLSID | accounts.google.com | YouTube | 13 months | HTTP Cook­ie | \- | | Func­tion­al | \_\_Se­cure-3PA­PISID | .google.com | YouTube | 13 months | HTTP Cook­ie | \- | | Func­tion­al | SAPISID | .google.com | YouTube | 13 months | HTTP Cook­ie | \- | | Func­tion­al | APISID | .google.com | YouTube | 13 months | HTTP Cook­ie | \- | | Func­tion­al | HSID | .google.com | YouTube | 13 months | HTTP Cook­ie | \- | | Func­tion­al | \_\_Se­cure-3PSID | .google.com | YouTube | 13 months | HTTP Cook­ie | \- | | Func­tion­al | \_\_Se­cure-3PA­PISID | .youtube.com | YouTube | 13 months | HTTP Cook­ie | \- | | Func­tion­al | SAPISID | .youtube.com | YouTube | 13 months | HTTP Cook­ie | \- | | Func­tion­al | HSID | .youtube.com | YouTube | 13 months | HTTP Cook­ie | \- | | Func­tion­al | SSID | .google.com | YouTube | 13 months | HTTP Cook­ie | \- | | Func­tion­al | SID | .google.com | YouTube | 13 months | HTTP Cook­ie | \- | | Func­tion­al | SSID | .youtube.com | YouTube | 13 months | HTTP Cook­ie | \- | | Func­tion­al | APISID | .youtube.com | YouTube | 13 months | HTTP Cook­ie | \- | | Func­tion­al | \_\_Se­cure-3PSID | .youtube.com | YouTube | 13 months | HTTP Cook­ie | \- | | Func­tion­al | SID | .youtube.com | YouTube | 13 months | HTTP Cook­ie | \- | | Func­tion­al | VISITOR\_​PRIVACY\_​METADATA | .youtube.com | YouTube | 7 months | HTTP Cook­ie | \- | | Func­tion­al | PREF | .youtube.com | YouTube | 1 year | HTTP Cook­ie | Unique ID to set pre­ferred page set­tings and play­back set­tings such as explic­it auto­play options, con­tent ran­domi­sa­tion and play­er size | | Func­tion­al | YSC | .youtube.com | YouTube | Ses­sion | HTTP Cook­ie | Unique ses­sion ID to recog­nise that requests with­in a brows­er ses­sion orig­i­nate from the user and not from oth­er websites | | Func­tion­al | SOCS | .youtube.com | YouTube | 9 months | HTTP Cook­ie | Set­tings for users to con­sent to Google ser­vices stor­ing their preferences | | Func­tion­al | SOCS | .google.com | YouTube | 13 months | HTTP Cook­ie | Set­tings for users to con­sent to Google ser­vices stor­ing their preferences | | Func­tion­al | NID | .google.com | YouTube | 7 months | HTTP Cook­ie | Unique ID to store pre­ferred set­tings such as lan­guage, num­ber of results on the search results page or acti­va­tion of the Google Safe­Search filter | | Func­tion­al | IDE | .doubleclick.net | YouTube | 9 months | HTTP Cook­ie | Unique iden­ti­fi­ca­tion tokens for per­son­al­is­ing ads on all sites using the Google adver­tis­ing network | | Func­tion­al | yt-play­er-head­ers-read­able | https://www.youtube.com | YouTube | \- | Local Stor­age | State of tech­ni­cal read­abil­i­ty of the YouTube play­er head­er, time of cre­ation and expi­ra­tion of the object | | Func­tion­al | \_\_Se­cure-YEC | .youtube.com | YouTube | 1 year | HTTP Cook­ie | Unique iden­ti­fi­er used to detect spam, fraud, and abuse | | Func­tion­al | yt-play­er-vol­ume | https://www.youtube.com | YouTube | \- | Local Stor­age | Sound set­tings for the YouTube play­er, time of cre­ation and expi­ra­tion of the object | | Func­tion­al | yt-play­er-vol­ume | https://www.youtube.com | YouTube | SESSION | Ses­sion Storage | Sound set­tings for the YouTube play­er, time of cre­ation of the object | | Func­tion­al | AEC | .google.com | YouTube | 6 months | HTTP Cook­ie | Unique iden­ti­fi­er used to detect spam, fraud, and abuse | | Func­tion­al | ytidb::LAST\_RESULT\_ENTRY\_KEY | https://www.youtube.com | YouTube | \- | Local Stor­age | \- | | Func­tion­al | test\_​cookie | .doubleclick.net | YouTube | 1 day | HTTP Cook­ie | Tests whether cook­ies can be set | | Mar­ket­ing | lang | .linkedin.com | LinkedIn Insight-Tag | Ses­sion | HTTP Cook­ie | \- | | Mar­ket­ing | lidc | .linkedin.com | LinkedIn Insight-Tag | 1 day | HTTP Cook­ie | \- | | Mar­ket­ing | bcook­ie | .linkedin.com | LinkedIn Insight-Tag | 13 months | HTTP Cook­ie | \- | | Mar­ket­ing | Ana­lyt­ic­sSyn­cHis­to­ry | .linkedin.com | LinkedIn Insight-Tag | 1 month | HTTP Cook­ie | \- | | Mar­ket­ing | User­Match­His­to­ry | .linkedin.com | LinkedIn Insight-Tag | 1 month | HTTP Cook­ie | \- | | Mar­ket­ing | lang | .ads.linkedin.com | LinkedIn Insight-Tag | Ses­sion | HTTP Cook­ie | \- | | Mar­ket­ing | li\_​gc | .linkedin.com | LinkedIn Insight-Tag | 6 months | HTTP Cook­ie | \- | | Mar­ket­ing | li\_​mc | .linkedin.com | LinkedIn Insight-Tag | 23 months | HTTP Cook­ie | \- | | Mar­ket­ing | liap | .linkedin.com | LinkedIn Insight-Tag | 3 months | HTTP Cook­ie | \- | | Mar­ket­ing | li\_​sugr | .linkedin.com | LinkedIn Insight-Tag | 3 months | HTTP Cook­ie | \- | The cook­ie pol­i­cy was last updat­ed on July 12, 2025.