Cookie Policy
Last updated: February 14, 2023
Hale Ola Pono / Magic Isle uses cookies on this website. By using the website, you consent to the use of cookies.
Our Cookies Policy explains what cookies are, how we use cookies, how third-parties we may partner with may use cookies on the website, your choices regarding cookies and further information about cookies.
What are cookies?
Cookies are small pieces of text sent by your web browser by a website you visit. A cookie file is stored in your web browser and allows the Service or a third-party to recognize you and make your next visit easier and the Service more useful to you.
Cookies can be "persistent" or "session" cookies.
How Hale Ola Pono / Magic Isle uses cookies:
When you use and access this website, we may place a number of cookies files in your web browser. We use cookies for the following purposes: to enable certain functions of the Service, to provide analytics and to store your preferences. We use both session and persistent cookies on the website and we use different types of cookies to run the website:
- Essential cookies. We may use essential cookies to authenticate users and prevent fraudulent use of user accounts.
-Third-party cookies. In addition to our own cookies, we may also use various third-parties cookies to report usage statistics of the website, and so on.
What are your choices regarding cookies?
If you'd like to delete cookies or instruct your web browser to delete or refuse cookies, please visit the help pages of your web browser. Please note, however, that if you delete cookies or refuse to accept them, you might not be able to use all of the features we offer, you may not be able to store your preferences, login, and some of our pages might not display properly.
Which cookies we use:
Google Analytics
_ga, _gat, _gid, _gtag_UA_XXXXXXXX_X, _gac_UA-XXXXXXXX-X
These cookies are set by Google Analytics, which allow us to analyze user experience on the website.
ShareThis
_unam, _utma, _utmv, __utmz, _stid
These cookies are set as part of the ShareThis service and monitors "click-stream" activity, e.g. web pages viewed, navigation from page to page, time spent on each page etc. The ShareThis service only personally identifies you if you have separately signed up with ShareThis for a ShareThis account and given them your consent. You can read the ShareThis privacy policy here. This page also explains how you can opt out of the tracking aspects of the ShareThis Service if you wish to.
Stripe
__stripe_mid, __stripe_orig_props, __stripe_sid, cid, country, __stripe-js-v3-features__ (local storage)
These cookies are set by Stripe. Stripe is used to make credit card payments. Stripe uses a cookie to remember who you are and to enable us to process payments without storing any credit card information on its own servers.
WordPress
wordpress_[hash], wordpress_logged_in_[hash], wp-settings-2, wp-settings-time-2
These cookies are set by wordpress so you can login to your account on the website. On login, wordpress uses the wordpress_[hash] cookie to store your authentication details. Its use is limited to the admin console area, /wp-admin/
After login, wordpress sets the wordpress_logged_in_[hash] cookie, which indicates when you're logged in, and who you are, for most interface use.
WordPress also sets a few wp-settings-{time}-[UID] cookies. The number on the end is your individual user ID from the users database table. This is used to customize your view of admin interface, and possibly also the main site interface.
WooCommerce
woocommerce_cart_hash, woocommerce_items_in_cart, wp_woocommerce_session_
The first two cookies contain information about the cart as a whole and helps WooCommerce know when the cart data changes. The final cookie (wp_woocommerce_session_) contains a unique code for each customer so that it knows where to find the cart data in the database for each customer. No personal information is stored within these cookies.
Wordfence
Wfwaf-authcookie-(hash)
This cookie is used by the Wordfence firewall to perform a capability check of the current user before WordPress has been loaded. This is only set for users that are able to log into WordPress. It allows the Wordfence firewall to detect logged in users and allow them increased access. It also allows Wordfence to detect non-logged in users and restrict their access to secure areas. The cookie also lets the firewall know what level of access a visitor has to help the firewall make smart decisions about who to allow and who to block.
Where can your find more information about cookies:
You can learn more about cookies and the following third-party websites:
• AllAboutCookies: http://www.allaboutcookies.org/
• Network Advertising Initiative: http://www.networkadvertising.org/