somdn-pro
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php on line 6121woocommerce-services
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php on line 6121woocommerce-conditional-shipping-and-payments
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php on line 6121woocommerce-eu-vat-number
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php on line 6121woocommerce-memberships
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php on line 6121woocommerce-order-status-control
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php on line 6121woocommerce-sequential-order-numbers-pro
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php on line 6121imca-website-2020
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php on line 6121IMCA takes your privacy and trust seriously. The following statement sets out the information we collect, how we use it and details on \u2018cookies\u2019 used by this website. Please contact us if you have any questions regarding our privacy policy and use of your data.<\/p>
We do not collect personally identifiable details about you unless you choose to submit them \u2013 via a membership application, event registration, publications order or other form of contact. Where we do this, we collect the information we need for that process and only use it for that purpose.<\/p>
We use Google Analytics to look at how our website is used, based on aggregated visitor data. This analysis does not identify individual users, but lets us see trends such as popular content, visitor countries, browsers\/devices used, etc. We can then use this data to help improve the website.<\/p>
Forms on this website are protected with Google ReCAPTCHA, to ensure human submission and reduce spam. The Google Privacy Policy<\/a> and Terms of Service<\/a> apply to the ReCAPTCHA elements of the site.<\/p> IMCA does not collect credit card details and where they are submitted, they are deleted from IT systems (or physically destroyed, as appropriate). For your security, all card payments are collected via PayPal or Stripe using their secure servers. Card details are provided directly to those services and not made available to IMCA \u2013 we receive data relevant to the purchase being made, but not card details or other card data that, if intercepted, could pose a security risk to you.<\/p> Our web site uses a technology known as cookies to store small amounts of data on our visitors\u2019 computers or devices. Cookies are small pieces of text data that can be placed on a visitor\u2019s computer, normally to provide enhanced functionality and\/or improved relevancy of information.<\/p> First party cookies<\/strong> (our website creates these):<\/p> Details are provided in tables below, listing various cookies that are set for users of stores with the WooCommerce <\/p> If you wish to dismiss the notice about cookies, a separate cookie will be placed on your computer for the sole purpose of hiding the notice on future visits. This cookie will expire in 365 days, or when this privacy policy changes, whichever is sooner.<\/p> Third party cookies<\/strong> (may be added by a service provider we use, subject to your browser settings):<\/p> Google Analytics:<\/p> IMCA takes your privacy and trust seriously. The following statement sets out the information we collect, how we use it and details on \u2018cookies\u2019 used by this website. Please contact […]<\/p>\n","protected":false},"author":11,"featured_media":0,"parent":3,"menu_order":0,"comment_status":"closed","ping_status":"open","template":"","meta":{"inline_featured_image":false,"_EventAllDay":false,"_EventTimezone":"","_EventStartDate":"","_EventEndDate":"","_EventStartDateUTC":"","_EventEndDateUTC":"","_EventShowMap":false,"_EventShowMapLink":false,"_EventURL":"","_EventCost":"","_EventCostDescription":"","_EventCurrencySymbol":"","_EventCurrencyCode":"","_EventCurrencyPosition":"","_EventDateTimeSeparator":"","_EventTimeRangeSeparator":"","_EventOrganizerID":[],"_EventVenueID":[],"_OrganizerEmail":"","_OrganizerPhone":"","_OrganizerWebsite":"","_VenueAddress":"","_VenueCity":"","_VenueCountry":"","_VenueProvince":"","_VenueState":"","_VenueZip":"","_VenuePhone":"","_VenueURL":"","_VenueStateProvince":"","_VenueLat":"","_VenueLng":"","_VenueShowMap":false,"_VenueShowMapLink":false,"footnotes":""},"class_list":["post-126496","page","type-page","status-publish","hentry"],"acf":[],"yoast_head":"\nPayment Data<\/h3>
Use of Cookies<\/h2>
Cookie Name<\/th> Duration<\/th> Purpose<\/th><\/tr> woocommerce_cart_hash <\/td> session <\/td> Helps WooCommerce determine when cart contents\/data changes.<\/td><\/tr> woocommerce_items_in_cart <\/td> session <\/td> Helps WooCommerce determine when cart contents\/data changes.<\/td><\/tr> wp_woocommerce_session_ <\/td> 2 days<\/td> Contains a unique code for each customer so that it knows where to find the cart data in the database for each customer.<\/td><\/tr> store_notice[notice id] <\/td> session <\/td> Allows customers to dismiss the Store Notice.<\/td><\/tr><\/tbody><\/table><\/figure> Cookie Name<\/th> Duration<\/th> Purpose<\/th><\/tr> __utma<\/td> 2 years from set\/update <\/td> Used to distinguish users and sessions. The cookie is created when the JavaScript library executes and no existing __utma cookies exists. The cookie is updated every time data is sent to Google Analytics.<\/td><\/tr> __utmt<\/em> <\/td> 10 minutes <\/td> Used to throttle request rate.<\/td><\/tr> __utmb<\/td> 30 mins from set\/update <\/td> Used to determine new sessions\/visits. The cookie is created when the JavaScript library executes and no existing __utmb cookies exists. The cookie is updated every time data is sent to Google Analytics.<\/td><\/tr> __utmz<\/td> 6 months from set\/update <\/td> Stores the traffic source or campaign that explains how the user reached your site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics.<\/td><\/tr> __utmv <\/td> 2 years from set\/update <\/td> Used to store visitor-level custom variable data. This cookie is created when a developer uses the _setCustomVar method with a visitor level custom variable. This cookie was also used for the deprecated _setVar method. The cookie is updated every time data is sent to Google Analytics.<\/td><\/tr><\/tbody><\/table><\/figure>","protected":false},"excerpt":{"rendered":"