Cookie Policy

This page was last changed on August 19, 2026, last checked on August 19, 2026 and applies to citizens and legal permanent residents of the United States.

1. Introduction

Our website, https://artemissecurity.com (hereinafter: “the website”) uses cookies and other related technologies (for convenience all technologies are referred to as “cookies”). Cookies are also placed by third parties we have engaged. In the document below we inform you about the use of cookies on our website.

2. Cookies

When you visit our website it can be necessary to store and/or read certain data from your device by using technologies such as cookies.

2.1 Technical or functional cookies

Some cookies ensure that certain parts of the website work properly and that your user preferences remain known. By placing functional cookies, we make it easier for you to visit our website. This way, you do not need to repeatedly enter the same information when visiting our website and, for example, the items remain in your shopping cart until you have paid. We may place these cookies without your consent.

2.2 Statistics cookies

We use statistics cookies to optimize the website experience for our users. With these statistics cookies we get insights in the usage of our website.

2.3 Advertising cookies

On this website we use advertising cookies, enabling us to gain insights into the campaign results. This happens based on a profile we create based on your behavior on https://artemissecurity.com. With these cookies you, as website visitor, are linked to a unique ID but these cookies will not profile your behavior and interests to serve personalized ads.

You can object to the tracking by these cookies by clicking the “Manage Consent” button.

2.4 Marketing/Tracking cookies

Marketing/Tracking cookies are cookies or any other form of local storage, used to create user profiles to display advertising or to track the user on this website or across several websites for similar marketing purposes.

2.5 Social media

On our website, we have included content from LinkedIn and X (Formerly Twitter) to promote web pages (e.g. “like”, “pin”) or share (e.g. “tweet”) on social networks like LinkedIn and X (Formerly Twitter). This content is embedded with code derived from LinkedIn and X (Formerly Twitter) and places cookies. This content might store and process certain information for personalized advertising.

Please read the privacy statement of these social networks (which can change regularly) to read what they do with your (personal) data which they process using these cookies. The data that is retrieved is anonymized as much as possible. LinkedIn and X (Formerly Twitter) are located in the United States.

3. Placed cookies

Most of these technologies have a function, a purpose, and an expiration period.

  1. A function is a particular task a technology has. So a function can be to “store certain data.”

  2. Purpose is “the Why” behind the function. Maybe the data is stored because it is needed for statistics.

  3. The expiration period shows the length of the period the used technology can “store or read certain data.”

Google Tag Manager (Marketing, Statistics)

Usage: We use Google Tag Manager for website statistics. Read more about Google Tag Manager

Sharing data: For more information, please read the Google Tag Manager Privacy Statement.

Marketing

  • _mdb_mdb_pxl_01KHRA6S12GGAZYARHSKFGA8D4 Function: MDB pixel tracking identifier stored via Google Tag Manager.

Statistics

  • _mdb_vid Expiration: 1 year. Function: Stores a unique visitor ID for analytics tracking via Google Tag Manager.

HubSpot (Marketing, Statistics, Functional, Preferences)

Usage: We use HubSpot for marketing automation (automated email marketing). Read more about HubSpot

Sharing data: For more information, please read the HubSpot Privacy Statement.

Marketing

  • 6977fed26a84090011d7058b_canTrack Function: Stores whether the visitor has consented to HubSpot tracking.

  • 6977fed26a84090011d7058b_eventQueue Function: Queues HubSpot tracking events before sending to HubSpot.

  • hubspotutk Expiration: 13 months. Function: Store and track a visitor’s identity.

  • __hstc Expiration: 13 months. Function: Store time of visit.

Statistics

  • __hssrc Expiration: session. Function: Store a unique session ID.

Functional

  • __hssc Expiration: 30 minutes. Function: Store anonymized statistics.

  • __hs_cookie_cat_pref Expiration: 6 months. Function: Store cookie consent preferences.

  • *_key Expiration: 2 weeks. Function: Store logged in users.

  • hs_ab_test Expiration: session. Function: Store ID’s of experiments and sessions for A/B testing.

  • __hs_do_not_track Expiration: 6 months. Function: Store ‘do not track’ signals.

Preferences

  • messagesUtk Expiration: 13 months. Function: Store browser details.

  • __hsmem Expiration: 1 week. Function: Store logged in users.

  • hs-messages-is-open Expiration: 30 minutes. Function: Store if a message has been shown.

Leadfeeder (Statistics, Marketing)

Usage: We use Leadfeeder for advertising. Read more about Leadfeeder

Sharing data: For more information, please read the Leadfeeder Privacy Statement.

Statistics

  • _reb2butk Expiration: 2 years. Function: Stores a unique tracking key for Leadfeeder.

  • _reb2bref Expiration: Session. Function: Stores the referrer URL of the visitor.

  • _reb2buid Expiration: 2 years. Function: Stores a unique visitor ID for Leadfeeder.

  • _reb2bli Expiration: 2 years. Function: Stores a unique ID to identify returning visitors.

  • _reb2bsha Expiration: 2 years. Function: Stores a hashed value to identify visitors.

  • _reb2btd Expiration: Session. Function: Tracks session data for Leadfeeder.

  • _reb2bgeo Expiration: Session. Function: Stores geographic location data for the visitor.

  • _reb2bsessionID Expiration: Session. Function: Stores a unique session ID for Leadfeeder tracking.

  • _leadgenie_session Expiration: Session. Function: Session cookie used by Leadfeeder to track visitor sessions on aplo-evnt.com.

Marketing

  • _lfa

  • _lfa_* Expiration: 2 years. Function: Store and track audience reach.

  • _lc2_fpi

  • _lc2_fpi_js

Google Adsense (Statistics, Marketing)

Usage: We use Google Adsense for showing advertisements. Read more about Google Adsense

Sharing data: For more information, please read the Google Adsense Privacy Statement.

Statistics

  • _gcl_ls Function: Store and track interaction.

Marketing

  • _gcl_au Expiration: persistent. Function: Store and track conversions.

  • google_adsense_settings Expiration: persistent. Function: Provide ad delivery or retargeting.

LinkedIn (Marketing, Functional, Statistics, Preferences)

Usage: We use LinkedIn for display of recent social posts and/or social share buttons. Read more about LinkedIn

Sharing data: For more information, please read the LinkedIn Privacy Statement.

Marketing

  • _li_duid

  • li_adsId Expiration: 30 days. Function: Stores a LinkedIn advertising identifier.

  • lms_ads Expiration: 30 days. Function: Store and track visits across websites.

  • _guid Expiration: 90 days. Function: Store and track a visitor’s identity.

  • li-oatml Expiration: 1 month. Function: Provide ad delivery or retargeting.

  • li_sugr Expiration: 90 days. Function: Store and track a visitor’s identity.

  • UserMatchHistory Expiration: 30 days. Function: Provide ad delivery or retargeting.

Purpose pending investigation

  • _li_dcdm_c

Functional

  • sdsc Expiration: session. Function: Provide load balancing functionality.

  • li_gc Expiration: 6 months. Function: Store cookie consent preferences.

  • BizographicsOptOut Expiration: 10 years. Function: Store privacy preferences.

Statistics

  • lms_analytics Expiration: 30 days. Function: Store and track a visitor’s identity.

  • AnalyticsSyncHistory Expiration: 30 days. Function: Store and track visits across websites.

Preferences

  • li_alerts Expiration: 1 year. Function: Store if a message has been shown.

  • bcookie Expiration: 1 year. Function: Store browser details.

  • lidc Expiration: 1 day. Function: Provide load balancing functionality.

  • bscookie Expiration: 1 year. Function: Store logged in users.

PostHog (Statistics)

Usage: We use PostHog for analytics. Read more about PostHog

Sharing data: For more information, please read the PostHog Privacy Statement.

Statistics

  • ph_*_posthog Expiration: 1 year. Function: PostHog analytics tracking cookie.

Apollo (Statistics)

Usage: We use Apollo for advertising. Read more about Apollo

Sharing data: For more information, please read the Apollo Privacy Statement.

Statistics

  • apolloAnonId Expiration: 1 year. Function: Stores an anonymous visitor ID for Apollo analytics.

YouTube (Marketing)

Usage: We use YouTube for video display. Read more about YouTube

Sharing data: For more information, please read the YouTube Privacy Statement.

Purpose pending investigation

  • _li_ss

Marketing

  • GPS Expiration: session. Function: Store location data.

  • VISITOR_INFO1_LIVE Expiration: 6 months. Function: Provide ad delivery or retargeting.

  • YSC Expiration: session. Function: Store and track interaction.

  • PREF Expiration: 8 months. Function: Store user preferences.

Google Analytics (Statistics)

Usage: We use Google Analytics for website statistics. Read more about Google Analytics

Sharing data: For more information, please read the Google Analytics Privacy Statement.

Statistics

  • _ga Expiration: 2 years. Function: Store and count pageviews.

  • _ga_* Expiration: 1 year. Function: Store and count pageviews.

WordPress (Functional)

Usage: We use WordPress for website development. Read more about WordPress

Sharing data: This data is not shared with third parties.

Functional

  • wp-settings-* Expiration: persistent. Function: Store user preferences.

  • wp-settings-time-* Expiration: 1 year. Function: Store user preferences.

  • wordpress_logged_in_* Expiration: persistent. Function: Store logged in users.

  • wordpress_test_cookie Expiration: session. Function: Read if cookies can be placed.

  • wp_lang Expiration: session. Function: Store language settings.

CloudFlare (Functional)

Usage: We use CloudFlare for content distribution network (CDN) services. Read more about CloudFlare

Sharing data: For more information, please read the CloudFlare Privacy Statement.

Functional

  • __cf_bm Expiration: 30 minutes. Function: Read and filter requests from bots.

  • _cfuvid Expiration: Session. Function: Identifies individual clients behind a shared IP for Cloudflare rate limiting on hubspot.com.

Google Fonts (Marketing)

Usage: We use Google Fonts for display of webfonts. Read more about Google Fonts

Sharing data: For more information, please read the Google Fonts Privacy Statement.

Marketing

  • Google Fonts API Expiration: expires immediately. Function: Read user IP address.

Complianz (Functional)

Usage: We use Complianz for cookie consent management. Read more about Complianz

Sharing data: This data is not shared with third parties. For more information, please read the Complianz Privacy Statement.

Functional

  • cmplz_functional Expiration: 365 days. Function: Store cookie consent preferences.

  • cmplz_statistics Expiration: 365 days. Function: Store cookie consent preferences.

  • cmplz_preferences Expiration: 365 days. Function: Store cookie consent preferences.

  • cmplz_marketing Expiration: 365 days. Function: Store cookie consent preferences.

  • cmplz_saved_categories Expiration: 365 days. Function: Store cookie consent preferences.

  • cmplz_saved_services Expiration: 365 days. Function: Store cookie consent preferences.

  • cmplz_id Expiration: 365 days. Function: Store cookie consent preferences.

  • cmplz_user_data Expiration: 365 days. Function: Read to determine which cookie banner to show.

  • cmplz_cookie_data Expiration: 365 days. Function: Store information about cookies that have been detected on the site.

  • cmplz_consented_services Expiration: 365 days. Function: Store cookie consent preferences.

  • cmplz_policy_id Expiration: 365 days. Function: Store accepted cookie policy ID.

  • cmplz_banner-status Expiration: 365 days. Function: Store if the cookie banner has been dismissed.

  • __test__ Expiration: Session. Function: Used to check if cookies can be placed on artemissecurity.com.

Miscellaneous (Purpose pending investigation)

Sharing data: Sharing of data is pending investigation

Purpose pending investigation

  • ph_phc_aZky1n1pccVJCjHmMhyK13P0bYoPDTwha5Qq3ToVklU_primary_window_exists

  • WP_PREFERENCES_USER_1

  • WP_DATA_USER_1

  • ppma_settings_active_tab

  • wpEmojiSettingsSupports

  • googlesitekit_1.177.0_2609584902e9c61e43e87cdcc2359a18_core::site::ads-measurement-status

  • googlesitekit_1.177.0_2609584902e9c61e43e87cdcc2359a18_core::user::survey

  • googlesitekit_notification_seen

  • googlesitekit_1.177.0_2609584902e9c61e43e87cdcc2359a18_core::site::notifications

  • WP_DATA_USER_14

  • WP_PREFERENCES_USER_14

  • _twpid

  • _rdt_uuid

  • ph_phc_aZky1n1pccVJCjHmMhyK13P0bYoPDTwha5Qq3ToVklU_session_registered_properties

  • googlesitekit_1.184.0_eaf69a0a3e7dc91a43d8e180fbc41039_core::user::tracking

  • _rdt_cfg

  • _twsid

  • googlesitekit_1.184.0_53108864394f10df52e4aaf9ef7d5078_core::user::tracking

  • _reb2bfxf

  • _dflt_attr

  • vector_pixel_89c23b71-2ba2-4fb3-90b6-e77270348967_visitor_uuid

  • vector_pixel_89c23b71-2ba2-4fb3-90b6-e77270348967_visitor_id

  • vector_pixel_89c23b71-2ba2-4fb3-90b6-e77270348967_synced_at

  • _dflt_aid

  • vector_visitor_id

  • art_attr

  • _dflt_sid

  • _dflt_la

4. Browser and Device based Consent

When you visit our website for the first time, we will show you a pop-up with an explanation about cookies. You do have the right to opt-out and to object against the further use of non-functional cookies.

4.1 Manage your opt-out preferences

5. Enabling/disabling and deleting cookies

You can use your internet browser to automatically or manually delete cookies. You can also specify that certain cookies may not be placed. Another option is to change the settings of your internet browser so that you receive a message each time a cookie is placed. For more information about these options, please refer to the instructions in the Help section of your browser.

Please note that our website may not work properly if all cookies are disabled. If you do delete the cookies in your browser, they will be placed again after your consent when you visit our website again.

6. Your rights with respect to personal data

You have the following rights with respect to your personal data:

  • you may submit a request for access to the data we process about you;

  • you may object to the processing;

  • you may request an overview, in a commonly used format, of the data we process about you;

  • you may request correction or deletion of the data if it is incorrect or not or no longer relevant, or to ask to restrict the processing of the data.

To exercise these rights, please contact us. Please refer to the contact details at the bottom of this Cookie Policy. If you have a complaint about how we handle your data, we would like to hear from you.

For more information about your rights with respect to personal data, please refer to our Privacy Statement

7. Contact details

For questions and/or comments about our Cookie Policy and this statement, please contact us by using the following contact details:

Artemis Global Technologies, Inc.
109 West 27th, New York, NY 10001
United States
Website: https://artemissecurity.com
Email: privacy@artemissecurity.com
Phone number: 6469220780

This Cookie Policy was synchronized with cookiedatabase.org on November 5, 2026.

Table of contents

Section title