How Google uses cookies

Google · Official agreement

Read the agreement

4 of 39 cards in Security & Safeguards

Security & Safeguards · Company practice

Google uses cookies for security: authenticating users, protecting against spam, fraud and abuse, and tracking outages

Google says it uses cookies and similar technologies for security purposes to protect you as you interact with a service. The four uses it names are authenticating users, protecting against spam, fraud and abuse, and tracking outages.

Supporting quotations

Google uses cookies and similar technologies for security purposes to protect you as you interact with a service by authenticating users, protecting against spam, fraud and abuse, and tracking outages.

Security & Safeguards · Company practice

SID and HSID cookies hold signed, encrypted records of your Google Account ID and latest sign-in time for 2 years

Google says the cookies used to authenticate users help ensure that only the actual owner of an account can access that account. The cookies SID and HSID contain digitally signed and encrypted records of a user's Google Account ID and most recent sign-in time. Together they let Google block many types of attack, such as attempts to steal the content of forms submitted in Google services. These cookies last 2 years.

Supporting quotations

cookies called ‘SID’ and ‘HSID’ contain digitally signed and encrypted records of a user’s Google Account ID and most recent sign-in time.
The combination of these cookies allows Google to block many types of attack, such as attempts to steal the content of forms submitted in Google services. These cookies last for 2 years.

Qualifications & exceptions

  • The page says the combination of the two cookies allows blocking "many types" of attack, not all attacks.

Security & Safeguards · Company practice

pm_sess and YSC cookies check that requests in a session come from you, not other sites

Google says some cookies and similar technologies are used to detect spam, fraud and abuse. The pm_sess and YSC cookies ensure that requests within a browsing session are made by the user and not by other sites, preventing malicious sites from acting on a user's behalf without the user's knowledge. pm_sess lasts 30 minutes; YSC lasts for the duration of a user's browsing session.

Supporting quotations

the ‘pm_sess’ and ‘YSC’ cookies ensure that requests within a browsing session are made by the user, and not by other sites. These cookies prevent malicious sites from acting on behalf of a user without that user’s knowledge.
The ‘pm_sess’ cookie lasts for 30 minutes, while the ‘YSC’ cookie lasts for the duration of a user’s browsing session.
Also annotated in the same passage (1)

Security & Safeguards · Company practice

__Secure-YENID, __Secure-YEC and AEC cookies help detect invalid ad activity and protect advertisers and creators

Google says the __Secure-YENID, __Secure-YEC and AEC cookies are used to detect spam, fraud and abuse, to help ensure that advertisers are not incorrectly charged for fraudulent or otherwise invalid impressions or interactions with ads, and that YouTube creators in the YouTube Partner Program are remunerated fairly. AEC lasts 6 months; __Secure-YENID and __Secure-YEC last 13 months.

Supporting quotations

The ‘__Secure-YENID,’ ‘__Secure-YEC,’ and ‘AEC’ cookies are used to detect spam, fraud, and abuse to help ensure advertisers are not incorrectly charged for fraudulent or otherwise invalid impressions or interactions with ads, and that YouTube creators in the YouTube Partner Program are remunerated fairly.
The ‘AEC’ cookie lasts for 6 months and the ‘__Secure-YENID’ and ‘__Secure-YEC’ cookies last for 13 months.

Qualifications & exceptions

  • The creator-payment purpose is stated only for creators in the YouTube Partner Program.

Not stated here

  • The page also says __Secure-YENID replaces __Secure-YEC, yet lists both here with the same 13-month lifetime; it does not say whether both are set.

Cross-references

Also annotated in the same passage (1)