Sign up for our newsletter!

Subscribe form (en)

No spam. Simply good reading. Get your free subscription to Smoltek Newsletter infrequently delivered straight to your inbox.

Your data will be handled in compliance with our privacy 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

Controller of the website

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. 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.

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.

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:

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/.

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­ryTech­ni­cal cook­ie nameTech­ni­cal cook­ie hostSer­viceDura­tionTypePur­pose
Essen­tialreal_​cookie_​banner*.smoltek.comReal Cook­ie Banner365 daysHTTP Cook­ieUnique 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­tialreal_cookie_banner*-tcf.smoltek.comReal Cook­ie Banner365 daysHTTP Cook­ieCon­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­tialreal_cookie_banner*-gcm.smoltek.comReal Cook­ie Banner365 daysHTTP Cook­ieCon­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­tialreal_­cook­ie_ban­ner-test.smoltek.comReal Cook­ie Banner365 daysHTTP Cook­ieCook­ie set to test HTTP cook­ie func­tion­al­i­ty. Delet­ed imme­di­ate­ly after test.
Essen­tialreal_​cookie_​banner*https://www.smoltek.comReal Cook­ie Banner-Local Stor­ageUnique 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­tialreal_cookie_banner*-tcfhttps://www.smoltek.comReal Cook­ie Banner-Local Stor­ageCon­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­tialreal_cookie_banner*-gcmhttps://www.smoltek.comReal Cook­ie Banner-Local Stor­ageCon­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­tialreal_­cook­ie_ban­ner-con­sent-queue*https://www.smoltek.comReal Cook­ie Banner-Local Stor­ageLocal 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.comSpot­light Stock­mar­ket Graph1 yearHTTP Cook­ie-
Func­tion­al_​ga.spotlightstockmarket.comSpot­light Stock­mar­ket Graph1 yearHTTP Cook­ie-
Func­tion­al_​gcl_​au.spotlightstockmarket.comSpot­light Stock­mar­ket GraphSes­sionHTTP Cook­ie-
Func­tion­al_​osm_​locationwww.openstreetmap.orgOpen­StreetMap14 monthsHTTP Cook­ieLat­i­tude and lon­gi­tude as well as zoom lev­el of the loca­tion select­ed on the map
Func­tion­al_​osm_​sessionwww.openstreetmap.orgOpen­StreetMapSes­sionHTTP Cook­ieUnique ID for the session
Func­tion­al_​osm_​totp_​token.openstreetmap.orgOpen­StreetMap2 hoursHTTP Cook­ie-
Func­tion­al_​pk_​id.*www.openstreetmap.orgOpen­StreetMap1 monthHTTP Cook­ieUnique ID for rec­og­niz­ing the user for tracking
Func­tion­al_​pk_​ref.*www.openstreetmap.orgOpen­StreetMap8 daysHTTP Cook­ieReferred URL
Func­tion­al_​pk_​ses.*www.openstreetmap.orgOpen­StreetMap32 min­utesHTTP Cook­ie-
Func­tion­alSIDCC.google.comYouTube1 yearHTTP Cook­ie-
Func­tion­alSIDCC.youtube.comYouTube1 yearHTTP Cook­ie-
Func­tion­alVISITOR_​INFO1_​LIVE.youtube.comYouTube7 monthsHTTP Cook­ie-
Func­tion­alLOGIN_​INFO.youtube.comYouTube13 monthsHTTP Cook­ie-
Func­tion­alCONSENT.youtube.comYouTube9 monthsHTTP Cook­ie-
Func­tion­alCONSENT.google.comYouTube9 monthsHTTP Cook­ie-
Func­tion­alOTZwww.google.comYouTube1 dayHTTP Cook­ie-
Func­tion­alyt-remote-device-idhttps://www.youtube.comYouTube-Local Stor­ageUnique device ID, time of cre­ation and expi­ra­tion of the object
Func­tion­alyt-fuller­screen-edu-but­ton-shown-counthttps://www.youtube.comYouTube-Local Stor­age-
Func­tion­alyt-remote-con­nect­ed-deviceshttps://www.youtube.comYouTube-Local Stor­ageList of devices asso­ci­at­ed with a YouTube account, time of cre­ation and expi­ra­tion of the object
Func­tion­alyt-play­er-band­widthhttps://www.youtube.comYouTube-Local Stor­ageInfor­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­alLogsDatabaseV2:*||https://www.youtube.comYouTube-Indexed­DB-
Func­tion­alSer­vice­Work­er­Logs­Data­basehttps://www.youtube.comYouTube-Indexed­DB-
Func­tion­alYtldb­Metahttps://www.youtube.comYouTube-Indexed­DB-
Func­tion­alyt-play­er-qual­i­tyhttps://www.youtube.comYouTube-Local Stor­ageOut­put video qual­i­ty for YouTube videos, time of cre­ation and expi­ra­tion of the object
Func­tion­alyt-play­er-per­for­mance-caphttps://www.youtube.comYouTube-Local Stor­age-
Func­tion­alPer­sis­ten­tEn­ti­ty­S­toreDb:*||https://www.youtube.comYouTube-Indexed­DB-
Func­tion­alyt-idb-pref-stor­age:*||https://www.youtube.comYouTube-Indexed­DB-
Func­tion­alyt.innertube::nextIdhttps://www.youtube.comYouTube-Local Stor­age-
Func­tion­alyt.innertube::requestshttps://www.youtube.comYouTube-Local Stor­age-
Func­tion­alyt-html5-player-modules::subtitlesModuleData::module-enabledhttps://www.youtube.comYouTube-Local Stor­age-
Func­tion­alyt-remote-ses­sion-apphttps://www.youtube.comYouTubeSESSIONSes­sion StorageAppli­ca­tion used for the ses­sion and time of object creation
Func­tion­alyt-remote-cast-installedhttps://www.youtube.comYouTubeSESSIONSes­sion StorageSta­tus of instal­la­tion of the ‘remote-cast’ func­tion and time of object creation
Func­tion­alyt-remote-ses­sion-namehttps://www.youtube.comYouTubeSESSIONSes­sion StorageName of the active ses­sion and time of object creation
Func­tion­alyt-remote-cast-avail­ablehttps://www.youtube.comYouTubeSESSIONSes­sion StorageSta­tus of avail­abil­i­ty of the ‘remote-cast’ func­tion and time of object creation
Func­tion­alyt-remote-fast-check-peri­odhttps://www.youtube.comYouTubeSESSIONSes­sion StorageTime 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-lvhttps://www.youtube.comYouTube-Local Stor­age-
Func­tion­alswpush­no­ti­fi­ca­tions­dbhttps://www.youtube.comYouTube-Indexed­DB-
Func­tion­alyt-play­er-local-media:*||https://www.youtube.comYouTube-Indexed­DB-
Func­tion­alyt-it-response-store:*||https://www.youtube.comYouTube-Indexed­DB-
Func­tion­al__HOST-GAPSaccounts.google.comYouTube13 monthsHTTP Cook­ie-
Func­tion­alOTZaccounts.google.comYouTube1 dayHTTP Cook­ie-
Func­tion­al__Se­cure-1PSID­CC.google.comYouTube1 yearHTTP Cook­ie-
Func­tion­al__Se­cure-1PA­PISID.google.comYouTube1 yearHTTP Cook­ie-
Func­tion­al__Se­cure-3PSID­CC.youtube.comYouTube1 yearHTTP Cook­ie-
Func­tion­al__Se­cure-1PA­PISID.youtube.comYouTube13 monthsHTTP Cook­ie-
Func­tion­al__Se­cure-1PSID.youtube.comYouTube13 monthsHTTP Cook­ie-
Func­tion­al__Se­cure-3PSID­CC.google.comYouTube1 yearHTTP Cook­ie-
Func­tion­al__Se­cure-ENID.google.comYouTube13 monthsHTTP Cook­ie-
Func­tion­al__Se­cure-1PSID.google.comYouTube13 monthsHTTP Cook­ie-
Func­tion­alytGe­f­Con­fig:*||https://www.youtube.comYouTube-Indexed­DB-
Func­tion­al__Host-3PLSIDaccounts.google.comYouTube13 monthsHTTP Cook­ie-
Func­tion­alLSIDaccounts.google.comYouTube13 monthsHTTP Cook­ie-
Func­tion­alACCOUNT_​CHOOSERaccounts.google.comYouTube13 monthsHTTP Cook­ie-
Func­tion­al__Host-1PLSIDaccounts.google.comYouTube13 monthsHTTP Cook­ie-
Func­tion­al__Se­cure-3PA­PISID.google.comYouTube13 monthsHTTP Cook­ie-
Func­tion­alSAPISID.google.comYouTube13 monthsHTTP Cook­ie-
Func­tion­alAPISID.google.comYouTube13 monthsHTTP Cook­ie-
Func­tion­alHSID.google.comYouTube13 monthsHTTP Cook­ie-
Func­tion­al__Se­cure-3PSID.google.comYouTube13 monthsHTTP Cook­ie-
Func­tion­al__Se­cure-3PA­PISID.youtube.comYouTube13 monthsHTTP Cook­ie-
Func­tion­alSAPISID.youtube.comYouTube13 monthsHTTP Cook­ie-
Func­tion­alHSID.youtube.comYouTube13 monthsHTTP Cook­ie-
Func­tion­alSSID.google.comYouTube13 monthsHTTP Cook­ie-
Func­tion­alSID.google.comYouTube13 monthsHTTP Cook­ie-
Func­tion­alSSID.youtube.comYouTube13 monthsHTTP Cook­ie-
Func­tion­alAPISID.youtube.comYouTube13 monthsHTTP Cook­ie-
Func­tion­al__Se­cure-3PSID.youtube.comYouTube13 monthsHTTP Cook­ie-
Func­tion­alSID.youtube.comYouTube13 monthsHTTP Cook­ie-
Func­tion­alVISITOR_​PRIVACY_​METADATA.youtube.comYouTube7 monthsHTTP Cook­ie-
Func­tion­alPREF.youtube.comYouTube1 yearHTTP Cook­ieUnique 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­alYSC.youtube.comYouTubeSes­sionHTTP Cook­ieUnique 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­alSOCS.youtube.comYouTube9 monthsHTTP Cook­ieSet­tings for users to con­sent to Google ser­vices stor­ing their preferences
Func­tion­alSOCS.google.comYouTube13 monthsHTTP Cook­ieSet­tings for users to con­sent to Google ser­vices stor­ing their preferences
Func­tion­alNID.google.comYouTube7 monthsHTTP Cook­ieUnique 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­alIDE.doubleclick.netYouTube9 monthsHTTP Cook­ieUnique 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­alyt-play­er-head­ers-read­ablehttps://www.youtube.comYouTube-Local Stor­ageState 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.comYouTube1 yearHTTP Cook­ieUnique iden­ti­fi­er used to detect spam, fraud, and abuse
Func­tion­alyt-play­er-vol­umehttps://www.youtube.comYouTube-Local Stor­ageSound set­tings for the YouTube play­er, time of cre­ation and expi­ra­tion of the object
Func­tion­alyt-play­er-vol­umehttps://www.youtube.comYouTubeSESSIONSes­sion StorageSound set­tings for the YouTube play­er, time of cre­ation of the object
Func­tion­alAEC.google.comYouTube6 monthsHTTP Cook­ieUnique iden­ti­fi­er used to detect spam, fraud, and abuse
Func­tion­alytidb::LAST_RESULT_ENTRY_KEYhttps://www.youtube.comYouTube-Local Stor­age-
Func­tion­altest_​cookie.doubleclick.netYouTube1 dayHTTP Cook­ieTests whether cook­ies can be set
Mar­ket­inglang.linkedin.comLinkedIn Insight-TagSes­sionHTTP Cook­ie-
Mar­ket­inglidc.linkedin.comLinkedIn Insight-Tag1 dayHTTP Cook­ie-
Mar­ket­ingbcook­ie.linkedin.comLinkedIn Insight-Tag13 monthsHTTP Cook­ie-
Mar­ket­ingAna­lyt­ic­sSyn­cHis­to­ry.linkedin.comLinkedIn Insight-Tag1 monthHTTP Cook­ie-
Mar­ket­ingUser­Match­His­to­ry.linkedin.comLinkedIn Insight-Tag1 monthHTTP Cook­ie-
Mar­ket­inglang.ads.linkedin.comLinkedIn Insight-TagSes­sionHTTP Cook­ie-
Mar­ket­ingli_​gc.linkedin.comLinkedIn Insight-Tag6 monthsHTTP Cook­ie-
Mar­ket­ingli_​mc.linkedin.comLinkedIn Insight-Tag23 monthsHTTP Cook­ie-
Mar­ket­ingliap.linkedin.comLinkedIn Insight-Tag3 monthsHTTP Cook­ie-
Mar­ket­ingli_​sugr.linkedin.comLinkedIn Insight-Tag3 monthsHTTP Cook­ie-

The cook­ie pol­i­cy was last updat­ed on June 14, 2025.