Effective date: July 28, 2018
How Old ("us", "we", or "our") operates the https://howold.date website (the "Service").
The Cookie text files comprise numbers and letters. The cookie files are saved into special areas in the memory of your computer or mobile device. Cookies stored here are called session cookies with cookies placed into the hard drive called persistent cookies.
The How Old cookie disclosure provides the user with information on which cookies are set when you visit an How Old website and how to reject or delete those cookies.
Please note that not all the cookies on our sites are set by us. Please see the section below on third party cookies.
Session cookies save website ’session’ credentials for visitors both logged in and not logged in. Once the browser is closed, the cookie is deactivated – and the session closed.
Analytical cookies collect visitor information, such as the number of visits, how our website was found, from where the visit came from, if via a marketing campaign etc. This information is extremely important to the business and helps us improve our website and further enhance visitor experience.
Functional cookies are specifically about visitor experience on the website. For example they ‘remember’ the open/closed status of pop up messages, what time zone or view state was set for the Economic Calendar, enabling access to information stored when registered with How Old and so on. Without these functional cookies, no settings information can be saved.
Third-party cookies are cookies that are set by a website other than the one you are currently on. For example an advertising service (ex: AdSense) can creates a third-party cookie to monitor which websites were visited by each user.
|Source||Name||Cookie Type||Life Time||Description||Impact|
|Google Analytics||_ga||1st Party||6 months||Used to distinguish users.||Edit Cookie Settings|
|Google Analytics||_ga||3rd Party||2 years||Used to distinguish users.||Edit Cookie Settings|
|Google Analytics||_gid||3rd Party||24 hours||Used to distinguish users.||Edit Cookie Settings|
|Google Analytics||_gat||3rd Party||1 minute||Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_ ||Edit Cookie Settings|
|Google Analytics||AMP_TOKEN||3rd Party||30 seconds to 1 year||Contains a token that can be used to retrieve a Client ID from AMP Client ID service. Other possible values indicate opt-out, inflight request or an error retrieving a Client ID from AMP Client ID service.||Edit Cookie Settings|
|Google Adsense||__gads||3rd Party||Various||Visitor statistics.||Edit Cookie Settings|
|Cloudflare||__cfduid||3rd Party||1 year||The __cfduid cookie is used to identify individual clients behind a shared IP address and apply security settings on a per-client basis. For example, if the visitor is in a coffee shop where there are a bunch of infected machines, but the specific visitor's machine is trusted (e.g. because they've completed a challenge within your Challenge Passage period), the cookie allows us to identify that client and not challenge them again. It does not correspond to any user ID in your web application, and does not store any personally identifiable information. This cookie is strictly necessary for Cloudflare's security features and cannot be turned off.||Essential Cookie|