Eronite • Insider-Magazin für Erwachsene seit 2006

Coo­kie policy

Coo­kie-Richt­li­nie

Wi­th this coo­kie po­li­cy, we would li­ke to ex­plain what coo­kies and coo­kie-li­ke tech­no­lo­gies are, how we and other ser­vice pro­vi­der use them on this web­site, what in­for­ma­ti­on they coll­ect, for how long and for what pur­po­ses we use them.

Ta­ble of contents

Con­trol­ler of the website

Ad­di­ti­on to the pri­va­cy policy

This coo­kie po­li­cy is a sup­ple­ment to this website's pri­va­cy po­li­cy. The coo­kie po­li­cy spe­ci­fies how a web­site uses coo­kies and what da­ta it coll­ects th­rough them, while the pri­va­cy po­li­cy is a mo­re com­pre­hen­si­ve over­view of all da­ta pro­ces­sing ac­ti­vi­ties on the web­site and beyond.

Coo­kies are small pie­ces of in­for­ma­ti­on si­mi­lar to text files that can be stored and read on the end de­vice. They ser­ve va­rious pur­po­ses, in­clu­ding main­tai­ning ba­sic func­tion­a­li­ties of the web­site, se­cu­ri­ty and pri­va­cy, pro­vi­ding op­tio­nal func­tions of the web­site, coll­ec­ting sta­tis­tic da­ta on vi­si­tor flows and pro­vi­ding mar­ke­ting sys­tems. Prac­ti­cal ex­amp­les of what can be stored in coo­kies are the sto­rage of log­in sta­tus in user ac­counts, the con­tent of shop­ping bas­kets in e‑commerce plat­forms, or a user ID for track­ing be­ha­vi­or on the web­site.

The in­for­ma­ti­on can tech­ni­cal­ly be stored in va­rious ways. The best-known ex­amp­les of this are HTTP coo­kies and coo­kie-li­ke tech­no­lo­gies li­ke lo­cal sto­rage, ses­si­on sto­rage or In­de­xedDB. Each ty­pe of sto­rage has dif­fe­rent pro­per­ties, which de­ter­mi­ne the tech­ni­cal hand­ling, ac­ces­si­bi­li­ty and con­trol­lers aut­ho­ri­zed to ac­cess the in­for­ma­ti­on. All the­se ty­pes of sto­rage are usual­ly sum­ma­ri­zed un­der the term "coo­kies" and are the­r­e­fo­re cal­led as such in this coo­kie policy.

The set­ting and re­a­ding of coo­kies in the Eu­ro­pean Uni­on (EU) and the Eu­ro­pean Eco­no­mic Area (EEA) is in ac­cordance wi­th Art. 5 (3) ePri­va­cy Di­rec­ti­ve and Re­ci­tal 66 ePri­va­cy Di­rec­ti­ve on­ly per­mit­ted if a user has gi­ven his con­sent on the ba­sis of com­pre­hen­si­ve in­for­ma­ti­on about the pur­po­ses of the pro­ces­sing. The web­site ope­ra­tor may al­so set coo­kies if they are strict­ly ne­ces­sa­ry to pro­vi­de you as a user wi­th the ex­press­ly re­ques­ted ser­vice, e.g. the ba­sic con­tent of this web­site or other strict­ly ne­ces­sa­ry coo­kies for ba­sic func­tion­a­li­ty of the web­site to be dis­play­ed to you wi­t­hout your con­sent.

The set­ting and re­a­ding of coo­kies in Switz­er­land is in ac­cordance wi­th Art. 45c (b) FMG (Fern­mel­de­ge­setz) on­ly per­mit­ted if a user has the op­ti­on to ob­ject the pro­ces­sing of da­ta on the ba­sis of com­pre­hen­si­ve in­for­ma­ti­on about the pur­po­ses of the pro­ces­sing. In ex­cep­tio­nal ca­ses, con­sent must be ob­tai­ned for the pro­ces­sing of per­so­nal da­ta in coo­kies in Switzerland.

What rights does the web­site vi­si­tor have?

Ser­vices and their coo­kies can be set and read on the le­gal ba­sis of your con­sent or a le­gi­ti­ma­te in­te­rest. When you first vi­si­ted this web­site, you we­re as­ked for your con­sent and you had the op­por­tu­ni­ty to ob­ject to the use of cer­tain ser­vices. We ex­plai­ned which le­gal ba­sis is used for which ser­vice in our con­sent dia­log.

You have the right to view the histo­ry of your de­cis­i­ons, ch­an­ge your pri­va­cy set­tings, ob­ject to the use of ser­vices and re­vo­ke your con­sent at any time. Be­low you find pos­si­bi­li­ties to exer­cise your rights:

How to ma­na­ge coo­kies in a browser?

  • How to re­mo­ve coo­kies in a brow­ser: To re­mo­ve coo­kies from your de­vice, you can clear the brow­sing da­ta in the set­tings of your brow­ser. This ac­tion will re­mo­ve all coo­kies from all web­sites you've vi­si­ted, po­ten­ti­al­ly in­clu­ding sa­ved log­in de­tails and site pre­fe­ren­ces. In so­me brow­sers, you can just de­le­te the coo­kies and si­mi­lar da­ta wi­t­hout de­le­ting the who­le brow­sing history.
  • How to con­trol coo­kies in a brow­ser: For mo­re gra­nu­lar con­trol over coo­kies spe­ci­fic to cer­tain web­sites, na­vi­ga­te to the pri­va­cy and coo­kie set­tings wi­thin your used brow­ser. He­re, you can ad­just pre­fe­ren­ces re­la­ted to in­di­vi­du­al sites' coo­kie usage.
  • How to block coo­kies in a brow­ser: It's pos­si­ble to con­fi­gu­re most mo­dern brow­sers in their set­tings to block all coo­kies from be­ing pla­ced on your de­vice. But blo­cking coo­kies could lead to cer­tain ser­vices and func­tion­a­li­ties not func­tio­ning cor­rect­ly, e.g. log­ins as a user. You can al­so use ex­ten­si­ons for ma­ny brow­sers which can block the set­ting of coo­kies on websites.
  • How to ma­na­ge coo­kies on this web­site: To tail­or your pre­fe­ren­ces re­gar­ding coo­kies on this web­site, you can ch­an­ge your pre­fe­ren­ces at any time by cli­cking on the link in the sec­tion "Rights of the web­site visitor".

You can find mo­re in­for­ma­ti­on on the hand­ling of coo­kies de​vowl​.io/​r​c​b​/​c​o​o​k​i​e​-​h​a​n​d​l​i​ng/.

What ty­pes of coo­kies exist?

  • Es­sen­ti­al coo­kies are in­dis­pensable for the ba­sic func­tion­a­li­ty of a web­site and enable func­tions such as sa­ving log­in in­for­ma­ti­on or ac­cess to se­cu­re are­as of the site. The­se in­clude, for ex­am­p­le, se­cu­ri­ty coo­kies, which can iden­ti­fy a bot that is not wan­ted on the web­site by sto­ring an au­then­ti­ca­ti­on key in a cookie.
  • Func­tion­al coo­kies im­pro­ve the user ex­pe­ri­ence by sto­ring in­for­ma­ti­on and pre­fe­ren­ces such as lan­guage set­tings or ap­pearance set­tings of the web­site to pro­vi­de per­so­na­li­zed. This in­cludes, for ex­am­p­le, pre­fe­rence coo­kies that store the user's pre­fer­red vi­deo qua­li­ty on a website.
  • Sta­tis­tics coo­kies coll­ect da­ta about the use of a web­site to gain in­sights in­to user be­ha­vi­or and op­ti­mi­ze the per­for­mance of the site. This in­cludes, for ex­am­p­le, a ran­dom­ly as­si­gned user ID that makes it pos­si­ble to at­tri­bu­te whe­ther you have vi­si­ted a sub­page of the website.
  • Mar­ke­ting coo­kies are used to track user be­ha­vi­or across dif­fe­rent web­sites and to dis­play per­so­na­li­zed ad­ver­ti­sing ba­sed on the in­te­rests and sur­fing be­ha­vi­or of users. This in­cludes, for ex­am­p­le, ad­ver­ti­sing coo­kies that store an in­ter­ac­tion wi­th an ad­ver­ti­se­ment on the web­site and pass it on to ad­ver­ti­sers or a chat sys­tem for pre-sa­le ques­ti­ons and cus­to­mer support.

Who can set coo­kies on this website?

On this web­site, bo­th the ope­ra­tor of the web­site and third-par­ty ser­vices which are used on this web­site may set coo­kies and ac­cess its con­tent. Who can ac­cess which coo­kies and their con­tent dif­fers bet­ween first-par­ty and third-par­ty coo­kies. First-par­ty coo­kies are crea­ted by the vi­si­ted web­site and can on­ly be read by the web­site ope­ra­tor and in­te­gra­ted third-par­ty ser­vices on this web­site. Third-par­ty coo­kies are set by usual­ly third-par­ty ser­vices on other do­mains, can be read on all web­sites on which the ser­vice that con­trols the do­main is em­bedded and, for ex­am­p­le, used by ad­ver­ti­sing net­works to track user be­ha­vi­or across dif­fe­rent web­sites and of­fer per­so­na­li­zed advertising.

Which coo­kies are used on this website?

Ca­te­go­ryTech­ni­cal coo­kie na­meTech­ni­cal coo­kie hostSer­viceDu­ra­ti­onTy­pePur­po­se
Es­sen­ti­alreal_​cookie_​banner*.ero​ni​te​.comRe­al Coo­kie Banner365 daysHTTP Coo­kieEin­deu­ti­ger Iden­ti­fi­ka­tor für die Ein­wil­li­gung, aber nicht für den Web­site-Be­su­cher. Re­vi­si­ons­hash für die Ein­stel­lun­gen des Coo­kie-Ban­ners (Tex­te, Far­ben, Funk­tio­nen, Ser­vice­grup­pen, Diens­te, Con­tent Blo­cker usw.). IDs für ein­ge­wil­lig­te Ser­vices und Service-Gruppen.
Es­sen­ti­alreal_cookie_banner*-tcf.ero​ni​te​.comRe­al Coo­kie Banner365 daysHTTP Coo­kieIm Rah­men von TCF ge­sam­mel­te Ein­wil­li­gun­gen, die im TC-String-For­mat ge­spei­chert wer­den, ein­schließ­lich TCF-Ven­do­ren, ‑Zwe­cke, ‑Son­der­zwe­cke, ‑Funk­tio­nen und ‑Son­der­funk­tio­nen.
Es­sen­ti­alreal_cookie_banner*-gcm.ero​ni​te​.comRe­al Coo­kie Banner365 daysHTTP Coo­kieDie im Goog­le Con­sent Mo­de ge­sam­mel­ten Ein­wil­li­gun­gen in die ver­schie­de­nen Ein­wil­li­gungs­ty­pen (Zwe­cke) wer­den für al­le mit dem Goog­le Con­sent Mo­de kom­pa­ti­blen Ser­vices gespeichert.
Es­sen­ti­alre­al_­coo­kie_­ban­ner-test.ero​ni​te​.comRe­al Coo­kie Banner365 daysHTTP Coo­kieCoo­kie, der ge­setzt wur­de, um die Funk­tio­na­li­tät von HTTP-Coo­kies zu tes­ten. Wird so­fort nach dem Test gelöscht.
Es­sen­ti­alreal_​cookie_​banner*https://​www​.ero​ni​te​.comRe­al Coo­kie Banner-Lo­cal StorageEin­deu­ti­ger Iden­ti­fi­ka­tor für die Ein­wil­li­gung, aber nicht für den Web­site-Be­su­cher. Re­vi­si­ons­hash für die Ein­stel­lun­gen des Coo­kie-Ban­ners (Tex­te, Far­ben, Funk­tio­nen, Ser­vice-Grup­pen, Ser­vices, Con­tent Blo­cker usw.). IDs für ein­ge­wil­lig­te Ser­vices und Ser­vice-Grup­pen. Wird nur so­lan­ge ge­spei­chert, bis die Ein­wil­li­gung auf dem Web­site-Ser­ver do­ku­men­tiert ist.
Es­sen­ti­alreal_cookie_banner*-tcfhttps://​www​.ero​ni​te​.comRe­al Coo­kie Banner-Lo­cal StorageIm Rah­men von TCF ge­sam­mel­te Ein­wil­li­gun­gen wer­den im TC-String-For­mat ge­spei­chert, ein­schließ­lich TCF Ven­do­ren, Zwe­cke, be­son­de­re Zwe­cke, Funk­tio­nen und be­son­de­re Funk­tio­nen. Wird nur so­lan­ge ge­spei­chert, bis die Ein­wil­li­gung auf dem Web­site-Ser­ver do­ku­men­tiert ist.
Es­sen­ti­alreal_cookie_banner*-gcmhttps://​www​.ero​ni​te​.comRe­al Coo­kie Banner-Lo­cal StorageIm Rah­men des Goog­le Con­sent Mo­de er­fass­te Ein­wil­li­gun­gen wer­den für al­le mit dem Goog­le Con­sent Mo­de kom­pa­ti­blen Ser­vices in Ein­wil­li­gungs­ty­pen (Zwe­cke) ge­spei­chert. Wird nur so­lan­ge ge­spei­chert, bis die Ein­wil­li­gung auf dem Web­site-Ser­ver do­ku­men­tiert ist.
Es­sen­ti­alre­al_­coo­kie_­ban­ner-con­sent-queue*https://​www​.ero​ni​te​.comRe­al Coo­kie Banner-Lo­cal StorageLo­ka­le Zwi­schen­spei­che­rung (Caching) der Aus­wahl im Coo­kie-Ban­ner, bis der Ser­ver die Ein­wil­li­gung do­ku­men­tiert; Do­ku­men­ta­ti­on pe­ri­odisch oder bei Sei­ten­wech­seln ver­sucht, wenn der Ser­ver nicht ver­füg­bar oder über­las­tet ist.
Es­sen­ti­al_​_​cf_​bm.ero​ni​te​.comCloud­fla­re30 mi­nu­tesHTTP Coo­kieIden­ti­fi­ziert und ent­schärft Bot-Verkehr
Es­sen­ti­alcf_​ob_​info.ero​ni​te​.comCloud­fla­re30 se­condsHTTP Coo­kieStellt Da­ten für den Al­ways-On­line-Dienst be­reit (Er­satz­in­hal­te bei ei­nem Ser­ver­aus­fall) und holt Res­sour­cen aus dem Cache
Es­sen­ti­alcf_​use_​ob.ero​ni​te​.comCloud­fla­re30 se­condsHTTP Coo­kieStellt Da­ten für den Al­ways-On­line-Dienst be­reit (Er­satz­in­hal­te bei ei­nem Ser­ver­aus­fall) und holt Res­sour­cen aus dem Cache
Es­sen­ti­al_​_​cfwaitingroom.ero​ni​te​.comCloud­fla­reSes­si­onHTTP Coo­kieVer­folgt Be­su­cher im War­te­raum bei ho­hem Ver­kehrs­auf­kom­men und Serverüberlastung
Es­sen­ti­al_​_​cfseq.ero​ni​te​.comCloud­fla­reSes­si­onHTTP Coo­kieVer­folgt An­fra­ge­se­quen­zen und Zeitplanung
Es­sen­ti­al_​_​cfruid.ero​ni​te​.comCloud­fla­reSes­si­onHTTP Coo­kieUn­ter­stützt die Ra­ten­be­gren­zung durch die Ver­wal­tung des Da­ten­ver­kehrs und die Ver­fol­gung der Her­kunft der Anfragen
Es­sen­ti­al_​cfuvid.ero​ni​te​.comCloud­fla­reSes­si­onHTTP Coo­kieIden­ti­fi­ziert ein­zel­ne Be­nut­zer, die die­sel­be IP-Adres­se haben.
Es­sen­ti­alcf_​clearance.ero​ni​te​.comCloud­fla­re30 mi­nu­tesHTTP Coo­kieSpei­chert den Be­weis für die be­stan­de­ne Anti-Bot-Herausforderung
Es­sen­ti­alcf_​chl_​rc_​i.ero​ni​te​.comCloud­fla­reSes­si­onHTTP Coo­kieIn­ter­ne Ver­wen­dung zur Er­mitt­lung von Produktionsproblemen
Es­sen­ti­alcf_​chl_​rc_​ni.ero​ni​te​.comCloud­fla­reSes­si­onHTTP Coo­kieIn­ter­ne Ver­wen­dung zur Er­mitt­lung von Produktionsproblemen
Es­sen­ti­alcf_​chl_​rc_​m.ero​ni​te​.comCloud­fla­reSes­si­onHTTP Coo­kieIn­ter­ne Ver­wen­dung zur Er­mitt­lung von Produktionsproblemen
Es­sen­ti­al_​_​cflb.ero​ni​te​.comCloud­fla­reSes­si­onHTTP Coo­kieHält den Be­nut­zer wäh­rend sei­ner Sit­zung mit dem­sel­ben Ser­ver verbunden
Es­sen­ti­alele­men­torhttps://​www​.ero​ni​te​.comEle­men­tor-Lo­cal Storage-
Es­sen­ti­alele­men­torhttps://​www​.ero​ni​te​.comEle­men­torSES­SI­ONSes­si­on Storage-
Func­tion­alSIDCC.goog​le​.comYou­Tube1 yearHTTP Coo­kie-
Func­tion­alSIDCC.you​tube​.comYou­Tube1 yearHTTP Coo­kie-
Func­tion­alVISITOR_INFO1_LIVE.you​tube​.comYou­Tube7 monthsHTTP Coo­kie-
Func­tion­alLOGIN_INFO.you​tube​.comYou­Tube13 monthsHTTP Coo­kie-
Func­tion­alCON­SENT.you​tube​.comYou­Tube9 monthsHTTP Coo­kie-
Func­tion­alCON­SENT.goog​le​.comYou­Tube9 monthsHTTP Coo­kie-
Func­tion­alOTZwww​.goog​le​.comYou­Tube1 dayHTTP Coo­kie-
Func­tion­alyt-re­mo­te-de­vice-idhttps://​www​.you​tube​.comYou­Tube-Lo­cal StorageEin­deu­ti­ge Ge­rä­te-ID, Zeit­punkt der Er­stel­lung und Ab­laufs des Objekts
Func­tion­alyt-play­er-hea­ders-re­a­da­blehttps://​www​.you​tube​.comYou­Tube-Lo­cal StorageTech­ni­sche Les­bar­keit vom You­Tube-Play­er-Hea­der, Zeit­punkt der Er­stel­lung und Ab­laufs des Objekts
Func­tion­alytidb::LAST_RESULT_ENTRY_KEYhttps://​www​.you​tube​.comYou­Tube-Lo­cal StorageMög­lich­keit des Zu­griffs auf den You­Tube-Da­ten­bank-Cache, Zeit­punkt der Er­stel­lung und Ab­laufs des Objekts
Func­tion­alyt-ful­ler­screen-edu-but­ton-shown-counthttps://​www​.you​tube​.comYou­Tube-Lo­cal Storage-
Func­tion­alyt-re­mo­te-con­nec­ted-de­viceshttps://​www​.you​tube​.comYou­Tube-Lo­cal StorageLis­te mit Ge­rä­ten, die mit ei­nem You­Tube-Kon­to ver­bun­den sind, Zeit­punkt der Er­stel­lung und Ab­laufs des Objekts
Func­tion­alyt-play­er-band­widthhttps://​www​.you​tube​.comYou­Tube-Lo­cal StorageIn­for­ma­tio­nen zur Band­brei­ten­nut­zung des You­Tube-Play­ers, Zeit­punkt der Er­stel­lung und Ab­laufs des Objekts
Func­tion­alLogsDatabaseV2:*||https://​www​.you​tube​.comYou­Tube-In­de­xedDB-
Func­tion­alSer­vice­Wor­ker­LogsDa­ta­ba­sehttps://​www​.you​tube​.comYou­Tube-In­de­xedDB-
Func­tion­alYtldb­Me­tahttps://​www​.you​tube​.comYou­Tube-In­de­xedDB-
Func­tion­altest_​cookie.dou​ble​click​.netYou­Tube1 dayHTTP Coo­kie-
Func­tion­alyt-play­er-qua­li­tyhttps://​www​.you​tube​.comYou­Tube-Lo­cal StorageAus­ga­be-Vi­deo­qua­li­tät für You­Tube-Vi­de­os, Zeit­punkt der Er­stel­lung und Ab­laufs des Objekts
Func­tion­alyt-play­er-per­for­mance-caphttps://​www​.you​tube​.comYou­Tube-Lo­cal Storage-
Func­tion­alyt-play­er-vo­lu­mehttps://​www​.you​tube​.comYou­Tube-Lo­cal StorageIn­for­ma­tio­nen zu den Ton-Ein­stel­lun­gen des You­Tube-Play­ers, Zeit­punkt der Er­stel­lung und Ab­laufs des Objekts
Func­tion­alPer­sis­ten­tEn­ti­ty­S­to­reDb:*||https://​www​.you​tube​.comYou­Tube-In­de­xedDB-
Func­tion­alyt-idb-pref-sto­rage:*||https://​www​.you​tube​.comYou­Tube-In­de­xedDB-
Func­tion­alyt.innertube::nextIdhttps://​www​.you​tube​.comYou­Tube-Lo­cal Storage-
Func­tion­alyt.innertube::requestshttps://​www​.you​tube​.comYou­Tube-Lo­cal Storage-
Func­tion­alyt-html5-player-modules::subtitlesModuleData::module-enabledhttps://​www​.you​tube​.comYou­Tube-Lo­cal Storage-
Func­tion­alyt-re­mo­te-ses­si­on-apphttps://​www​.you​tube​.comYou­TubeSES­SI­ONSes­si­on StorageGe­nutz­te Ap­pli­ka­ti­on für die Sit­zung und Zeit­punkt der Er­stel­lung des Objekts
Func­tion­alyt-re­mo­te-cast-in­stal­ledhttps://​www​.you​tube​.comYou­TubeSES­SI­ONSes­si­on StorageSta­tus der In­stal­la­ti­on der "remote-cast"-Funktion und Zeit­punkt der Er­stel­lung des Objekts
Func­tion­alyt-play­er-vo­lu­mehttps://​www​.you​tube​.comYou­TubeSES­SI­ONSes­si­on StorageIn­for­ma­tio­nen zu den Ton-Ein­stel­lun­gen des You­Tube-Play­ers und Zeit­punkt der Er­stel­lung des Objekts
Func­tion­alyt-re­mo­te-ses­si­on-na­mehttps://​www​.you​tube​.comYou­TubeSES­SI­ONSes­si­on StorageNa­men der ak­ti­ven Sit­zung und Zeit­punkt der Er­stel­lung des Objekts
Func­tion­alyt-re­mo­te-cast-availablehttps://​www​.you​tube​.comYou­TubeSES­SI­ONSes­si­on StorageSta­tus der Ver­füg­bar­keit der "remote-cast"-Funktion und Zeit­punkt der Er­stel­lung des Objekts
Func­tion­alyt-re­mo­te-fast-check-pe­ri­odhttps://​www​.you​tube​.comYou­TubeSES­SI­ONSes­si­on StorageZeit­punkt der Er­stel­lung des Ob­jekts als Fest­stel­lung, ob "remote-cast"-Funktion er­reich­bar ist
Func­tion­al*||::yt-player::yt-player-lvhttps://​www​.you​tube​.comYou­Tube-Lo­cal Storage-
Func­tion­alsw­push­no­ti­fi­ca­ti­ons­dbhttps://​www​.you​tube​.comYou­Tube-In­de­xedDB-
Func­tion­alyt-play­er-lo­cal-me­dia:*||https://​www​.you​tube​.comYou­Tube-In­de­xedDB-
Func­tion­alyt-it-re­spon­se-store:*||https://​www​.you​tube​.comYou­Tube-In­de­xedDB-
Func­tion­al__HOST-GAPSac​counts​.goog​le​.comYou­Tube13 monthsHTTP Coo­kie-
Func­tion­alOTZac​counts​.goog​le​.comYou­Tube1 dayHTTP Coo­kie-
Func­tion­al__­Se­cu­re-1P­SIDCC.goog​le​.comYou­Tube1 yearHTTP Coo­kie-
Func­tion­al__­Se­cu­re-1PA­PISID.goog​le​.comYou­Tube1 yearHTTP Coo­kie-
Func­tion­al__­Se­cu­re-3P­SIDCC.you​tube​.comYou­Tube1 yearHTTP Coo­kie-
Func­tion­al__­Se­cu­re-1PA­PISID.you​tube​.comYou­Tube13 monthsHTTP Coo­kie-
Func­tion­al__­Se­cu­re-1P­SID.you​tube​.comYou­Tube13 monthsHTTP Coo­kie-
Func­tion­al__­Se­cu­re-3P­SIDCC.goog​le​.comYou­Tube1 yearHTTP Coo­kie-
Func­tion­al__­Se­cu­re-EN­ID.goog​le​.comYou­Tube13 monthsHTTP Coo­kie-
Func­tion­al__­Se­cu­re-1P­SID.goog​le​.comYou­Tube13 monthsHTTP Coo­kie-
Func­tion­alyt­GefCon­fig:*||https://​www​.you​tube​.comYou­Tube-In­de­xedDB-
Func­tion­al__Host-3PLS­IDac​counts​.goog​le​.comYou­Tube13 monthsHTTP Coo­kie-
Func­tion­alLS­IDac​counts​.goog​le​.comYou­Tube13 monthsHTTP Coo­kie-
Func­tion­alACCOUNT_CHOOSERac​counts​.goog​le​.comYou­Tube13 monthsHTTP Coo­kie-
Func­tion­al__Host-1PLS­IDac​counts​.goog​le​.comYou­Tube13 monthsHTTP Coo­kie-
Func­tion­al__­Se­cu­re-3PA­PISID.goog​le​.comYou­Tube13 monthsHTTP Coo­kie-
Func­tion­alSA­PI­SID.goog​le​.comYou­Tube13 monthsHTTP Coo­kie-
Func­tion­alAPISID.goog​le​.comYou­Tube13 monthsHTTP Coo­kie-
Func­tion­alHS­ID.goog​le​.comYou­Tube13 monthsHTTP Coo­kie-
Func­tion­al__­Se­cu­re-3P­SID.goog​le​.comYou­Tube13 monthsHTTP Coo­kie-
Func­tion­al__­Se­cu­re-3PA­PISID.you​tube​.comYou­Tube13 monthsHTTP Coo­kie-
Func­tion­alSA­PI­SID.you​tube​.comYou­Tube13 monthsHTTP Coo­kie-
Func­tion­alHS­ID.you​tube​.comYou­Tube13 monthsHTTP Coo­kie-
Func­tion­alSSID.goog​le​.comYou­Tube13 monthsHTTP Coo­kie-
Func­tion­alSID.goog​le​.comYou­Tube13 monthsHTTP Coo­kie-
Func­tion­alSSID.you​tube​.comYou­Tube13 monthsHTTP Coo­kie-
Func­tion­alAPISID.you​tube​.comYou­Tube13 monthsHTTP Coo­kie-
Func­tion­al__­Se­cu­re-3P­SID.you​tube​.comYou­Tube13 monthsHTTP Coo­kie-
Func­tion­alSID.you​tube​.comYou­Tube13 monthsHTTP Coo­kie-
Func­tion­alVISITOR_PRIVACY_METADATA.you​tube​.comYou­Tube7 monthsHTTP Coo­kie-
Func­tion­alNID.goog​le​.comYou­Tube7 monthsHTTP Coo­kieEin­deu­ti­ge ID, um be­vor­zug­te Ein­stel­lun­gen wie z. B. Spra­che, Men­ge der Er­geb­nis­se auf Such­ergeb­nis­sei­te oder­Ak­ti­vie­rung des Saf­eSe­arch-Fil­ters von Google
Func­tion­alPREF.you​tube​.comYou­Tube1 yearHTTP Coo­kieEin­deu­ti­ge ID, um be­vor­zug­te Sei­ten­ein­stel­lun­gen und Wie­der­ga­be­ein­stel­lun­gen wie ex­pli­zi­te Au­to­play-Op­tio­nen, zu­fäl­li­ge Wie­der­ga­be von In­hal­ten und Play­er­grö­ße festzulegen
Func­tion­alIDE.dou​ble​click​.netYou­Tube9 monthsHTTP Coo­kieEin­deu­ti­ge Iden­ti­fi­ka­ti­ons­to­ken zur Per­so­na­li­sie­rung von An­zei­gen auf Web­sites, die nicht Goog­le betreibt
Func­tion­al__­Se­cu­re-YEC.you​tube​.comYou­Tube1 yearHTTP Coo­kieEin­zig­ar­ti­ge In­for­ma­tio­nen zur Er­ken­nung von Spam, Be­trug und Missbrauch
Func­tion­alYSC.you​tube​.comYou­TubeSes­si­onHTTP Coo­kieEin­deu­ti­ge Sit­zungs-ID, um zu er­ken­nen, dass An­fra­gen in­ner­halb ei­ner Brow­ser­sit­zung vom Be­nut­zer und nicht von an­de­ren Web­sites stammen
Func­tion­alAEC.goog​le​.comYou­Tube6 monthsHTTP Coo­kieEin­deu­ti­ge In­for­ma­ti­on zur Er­ken­nung von Spam, Be­trug und Missbrauch
Func­tion­alSOCS.you​tube​.comYou­Tube9 monthsHTTP Coo­kieEin­stel­lun­gen zur Ein­wil­li­gung von Nut­zern zu Goog­le-Diens­ten, um de­ren Prä­fe­ren­zen zu speichern
Func­tion­alSOCS.goog​le​.comYou­Tube13 monthsHTTP Coo­kieEin­stel­lun­gen zur Ein­wil­li­gung von Nut­zern zu Goog­le-Diens­ten, um de­ren Prä­fe­ren­zen zu speichern
Sta­tis­tic_​ga.ero​ni​te​.comGoog­le Analytics24 monthsHTTP Coo­kieBe­nut­zer-ID zur Ana­ly­se des all­ge­mei­nen Be­nut­zer­ver­hal­tens auf ver­schie­de­nen Websites
Sta­tis­tic_​ga_​*.ero​ni​te​.comGoog­le Analytics24 monthsHTTP Coo­kieBe­nut­zer-ID zur Ana­ly­se des Be­nut­zer­ver­hal­tens auf die­ser Web­site für Be­rich­te über die Nut­zung der Website

The coo­kie po­li­cy was last up­dated on 16. Ju­ne 2026.

Bit­te le­sen Sie auch un­se­re Da­ten­schutz­hin­wei­se, das Im­pres­sum, die Ju­gend­schutz­be­stim­mun­gen, die Nut­zungs­be­din­gun­gen, un­se­ren Re­dak­ti­ons- und Pres­se­co­dex und Teil­nah­me­be­din­gun­gen für Gewinnspiele/​Umfragen.

Cookie Consent with Real Cookie Banner