Cookies list
Below is a list of the cookies that we use. We have tried to ensure this is complete and up to date, but if you think that we have missed a cookie or there is any discrepancy, please let us know.
Analytical/performance
We use the following analytical/performance cookies:
| Cookie Name | Expiration Time | Description |
|---|---|---|
| _ga | 2 years | Used to distinguish users. |
| _gid | 24 hours | Used to distinguish users. |
| _gat | 1 minute | Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_<property-id>. |
| AMP_TOKEN | 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. |
| _gac_<property-id> | 90 days | Contains campaign related information for the user. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you opt-out. |
Functionality
We use the following functionality cookies:
| WORDPRESS COOKIE NAME | DURATION | PURPOSE | LOGGED-IN USERS ONLY? |
|---|---|---|---|
| wordpress_{hash} | | WordPress uses the login wordpress_{hash} cookie to store authentication details. Its use is limited to the Administration Screen area, /wp-admin/ | Yes |
| wordpress_logged_in_{hash} | Session | Remember User session. WordPress sets the after login wordpress_logged_in_{hash} cookie, which indicates when you’re logged in, and who you are, for most interface use. | Yes |
| wordpres_test_cookie | Session | Test if cookie can be set. WordPress also sets wordpress_test_cookie cookie to check if the cookies are enabled on the browser to provide appropriate user experience to the users. This cookie is used on the front-end, even if you are not logged in. | No |
| wp-settings-{user_id} | 1 year | Customization cookie. Used to persist a user’s wp-admin configuration. The ID is the user’s ID. This is used to customize the view of admin interface, and possibly also the main site interface. | Yes |
| wp-settings-time-{user} | 1 year | Time at which wp-settings-{user} was set | Yes |
| wp-saving-post | 1 day | Auto-saving cookie: wp-saving-post is a WordPress cookie created when auto-saving a post in the editor. Used to track if there is saved post exists for a post currently being edited. If exists then let user restore the data. | Yes |
| wp-postpass_{hash} | 10 days | Used to maintain session if a post is password protected | No |
| COOKIE NAME | EXPIRATION TIME | DESCRIPTION |
|---|---|---|
| dtCookieConsent | 2 months | Used to check if the user agreed to our use of cookies. |
| PHPSESSID | Will expire when the browser is closed | PHP Session cookie used to establish a user session |
in English
Cookies list
Below Is A List Of The Cookies That We Use. We Have Tried To Ensure This Is Complete And Up To Date, But If You Think That We Have Missed A Cookie Or There Is Any Discrepancy, Please Let Us Know.
Analytical/performance
We Use The Following Analytical/performance Cookies:
| Cookie Name | Expiration Time | Description |
|---|---|---|
| _ga | 2 Years | Used To Distinguish Users. |
| _gid | 24 Hours | Used To Distinguish Users. |
| _gat | 1 Minute | Used To Throttle Request Rate. If Google Analytics Is Deployed Via Google Tag Manager, This Cookie Will Be Named _dc_gtm_<property-id>. |
| AMP_TOKEN | 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. |
| _gac_<property-id> | 90 Days | Contains Campaign Related Information For The User. If You Have Linked Your Google Analytics And Google Ads Accounts, Google Ads Website Conversion Tags Will Read This Cookie Unless You Opt-out. |
Functionality
We Use The Following Functionality Cookies:
| WORDPRESS COOKIE NAME | DURATION | PURPOSE | LOGGED-IN USERS ONLY? |
|---|---|---|---|
| wordpress_{hash} | | WordPress Uses The Login WordPress_{hash} Cookie To Store Authentication Details. Its Use Is Limited To The Administration Screen Area, /wp-admin/ | Yes |
| wordpress_logged_in_{hash} | Session | Remember User Session. WordPress Sets The After Login WordPress_logged_in_{hash} Cookie, Which Indicates When You’re Logged In, And Who You Are, For Most Interface Use. | Yes |
| wordpres_test_cookie | Session | Test If Cookie Can Be Set. WordPress Also Sets WordPress_test_cookie Cookie To Check If The Cookies Are Enabled On The Browser To Provide Appropriate User Experience To The Users. This Cookie Is Used On The Front-end, Even If You Are Not Logged In. | No |
| wp-settings-{user_id} | 1 Year | Customization Cookie. Used To Persist A User’s Wp-admin Configuration. The ID Is The User’s ID. This Is Used To Customize The View Of Admin Interface, And Possibly Also The Main Site Interface. | Yes |
| wp-settings-time-{user} | 1 Year | Time At Which Wp-settings-{user} Was Set | Yes |
| wp-saving-post | 1 Day | Auto-saving Cookie: Wp-saving-post Is A WordPress Cookie Created When Auto-saving A Post In The Editor. Used To Track If There Is Saved Post Exists For A Post Currently Being Edited. If Exists Then Let User Restore The Data. | Yes |
| wp-postpass_{hash} | 10 Days | Used To Maintain Session If A Post Is Password Protected | No |
| COOKIE NAME | EXPIRATION TIME | DESCRIPTION |
|---|---|---|
| dtCookieConsent | 2 Months | Used To Check If The User Agreed To Our Use Of Cookies. |
| PHPSESSID | Will Expire When The Browser Is Closed | PHP Session Cookie Used To Establish A User Session |
Cookies Policy in Other Translations
Add to favorites