Cookie Policy
Introduction
Our website uses cookies to distinguish you from other users of our website. This helps us to provide you with a good experience when you browse our website and also allows us to improve our site.
A cookie is a small file of letters and numbers that we store on your browser or the hard drive of your computer if you agree. Cookies contain information that is transferred to your computer’s hard drive.
We use the following cookies:
Strictly necessary cookies. These are cookies that are required for the operation of our website. They include, for example, cookies that enable you to log into secure areas of our website, use a shopping cart or make use of e-billing services.
Analytical or performance cookies. These allow us to recognise and count the number of visitors and to see how visitors move around our website when they are using it. This helps us to improve the way our website works, for example, by ensuring that users are finding what they are looking for easily.
Functionality cookies. These are used to recognise you when you return to our website. This enables us to personalise our content for you, greet you by name and remember your preferences (for example, your choice of language or region).
Targeting cookies. These cookies record your visit to our website, the pages you have visited and the links you have followed. We will use this information to make our website and the advertising displayed on it more relevant to your interests. We may also share this information with third parties for this purpose.
You can find more information about the individual cookies we use and the purposes for which we use them in the table below:
Full List Of WordPress Cookies
WordPress cookies can be divided into two categories: WordPress Users Cookie – “strictly necessary” cookies as WordPress will not be able to function without it. They are also session cookies as they expire once the user logs out or exits the page.
WordPress Commenters Cookie – not “strictly necessary” cookies and are set when users leave a comment on a post. These can also be classified as persistent cookies.
Note: those includes only cookies set by WordPress only – this doesn’t include cookies set by plugins.
You can find more information about the individual cookies we use and the purposes for which we use them in the table below:
WORDPRESS COOKIE NAME | DURATION | PURPOSE |
wordpress_{hash} | WordPress uses the login wordpress_{hash} cookie to store authentication details. Its use is limited to the Administration Screen area, /wp-admin/ | |
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. |
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. |
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 |
wp-settings-time-{user} | 1 year | Time at which wp-settings-{user} was set |
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. |
wp-postpass_{hash} | 10 days | Used to maintain session if a post is password protected |
wordpress_sec | There is not yet any general information about this cookie based on its name only. |
List Of WordPress Commenters Cookies
When visitors comment on your blog, they too get cookies stored on their computer. This is purely a convenience, so that the visitor won’t need to re-type all their information again when they want to leave another comment. Three cookies are set for commenters:
WORDPRESS COOKIE NAME | DURATION | PURPOSE |
comment_author_{HASH} | 347 days | Used to tracked comment author name, if “Save my name, email, and website in this browser for the next time I comment.” is checked |
comment_author_email_{HASH} | 347 days | Used to tracked comment author email, if “Save my name, email, and website in this browser for the next time I comment.” is checked |
comment_author_url_{HASH} | 347 days | Used to track comment author url, if “Save my name, email, and website in this browser for the next time I comment.” checkbox is checked |
V3 Software cookies
Cookie Name | Purpose | Duration |
Google reCaptcha | Encrypted Cookie by Google reCaptcha | Session |
Login | – “activuser” – ID of the user – “activdata” – Encrypted password of the user | Session |
MoxieCode FileManager Core Plugin | – When the MoxieCode File Manager opens the following cookie variable is being saved: – MCManager_ (this variable serves as an authenticator of the logged in users for using the MoxieCode FileManager) | Session |
MoxieCode FileManager FavoriteCookiePlugin | – This plugin triggers to save a cookie on the browser whenever a user uses its favorites functionality which is: – MCManagerFavoriteCookie_ | Session |
MoxieCode FileManager HistoryCookiePlugin | – This plugin triggers to save a cookie on the browser whenever a user uses its history functionality which is: – MCManagerHistoryCookie_ | Session |
MoxieCode ImageManager Core Plugin | – When the MoxieCode Image Manager opens the following cookie variable is being saved: – MCManager_ (this variable serves as an authenticator of the logged in users for using the MoxieCode ImageManager) | Session |
Mutiple Upload on ImageManager | – When the user uses mutiple upload of files in ImageManager it triggers to save a cookie to save to remember the files that were multiple selected to be uploaded. – plupload_ui_view | Session |
MoxieCode ImageManager FavoriteCookiePlugin | – This plugin triggers to save a cookie on the browser whenever a user uses its favorites functionality which is: – MCManagerFavoriteCookie_ | Session |
MoxieCode ImageManager HistoryCookiePlugin | – This plugin triggers to save a cookie on the browser whenever a user uses its history functionality which is: – MCManagerHistoryCookie_ | Session |
ServerResultURLCookieVariables From PaymentSense Payment Gateway | ||
Font Resize Functionality | Saves the cookie state of the sizes of the fonts of the website |
Please note that the following third parties may also use cookies, over which we have no control. These named third parties may include, for example, advertising networks and providers of external services like web traffic analysis services. These third party cookies are likely to be analytical cookies or performance cookies or targeting cookies:
To deactivate the use of third party advertising cookies, you may visit the consumer page to manage the use of these types of cookies [include link to consent management solution].
You can block cookies by activating the setting on your browser that allows you to refuse the setting of all or some cookies. However, if you use your browser settings to block all cookies (including essential cookies) you may not be able to access all or parts of our website.
Except for essential cookies, all cookies will expire after [365 days].