Cookies

Last Updated: [12.6.23]

This Cookies Policy explains how newecoact.wpenginepowered.com (“we,” “us,” or “our”) uses cookies and similar technologies to collect and store information when you visit our website. Necessary cookies are those that will be used as a minimum, because they are necessary for the website to function correctly. The remaining cookies will only be set if you specifically indicate your consent for that type of cookie to be used. Please note that choosing only necessary cookies may limit some optional website functionality and personalisation.

What are Cookies?

Cookies are small text files that are placed on your computer or mobile device when you visit a website. They are widely used to make websites work more efficiently, enhance user experience, and provide information to the website owners.

How We Use Cookies

We use cookies for the following purposes:

Necessary Cookies:

Cookiebot:
- Name: CookieConsent
- Purpose: Stores the user’s cookie consent state for the current domain.
- Expiry: 1 year
- Type: HTTP
Google:
- Name: test_cookie
- Purpose: Used to check if the user’s browser supports cookies.
- Expiry: 1 day
- Type: HTTP
HubSpot:
- Name: __cf_bm
- Purpose: This cookie is used to distinguish between humans and bots, enabling valid reports on the use of the website.
- Expiry: 1 day
- Type: HTTP
LinkedIn:
- Name: li_gc
- Purpose: Stores the user’s cookie consent state for the current domain.
- Expiry: 180 days
- Type: HTTP
LinkedIn:
- Name: bscookie
- Purpose: Used to identify the visitor through an application, allowing login through the LinkedIn application.
- Expiry: 1 year
- Type: HTTP
YouTube:
- Name: CONSENT
- Purpose: Used to detect if the visitor has accepted the marketing category in the cookie banner for GDPR compliance.
- Expiry: 2 years
- Type: HTTP
elementor:
- Name: [name]
- Purpose: Used in context with the website’s WordPress theme, allowing real-time content implementation or changes by the website owner.
- Expiry: Persistent
- Type: HTML

Preference Cookies:

LinkedIn:
- Name: lidc
- Purpose: Registers which server-cluster is serving the visitor, optimizing user experience through load balancing.
- Expiry: 1 day
- Type: HTTP
wp-wpml_current_language:
- Name: [name]
- Purpose: Designates the country code calculated based on the user’s IP address, determining the language for the visitor.
- Expiry: Session
- Type: HTTP

Statistics Cookies:

Google:
- Name: _ga
- Purpose: Registers a unique ID to generate statistical data on how the visitor uses the website.
- Expiry: 2 years
- Type: HTTP
Google:
- Name: ga#
- Purpose: Collects data on the number of times a user has visited the website, along with first and most recent visit dates.
- Expiry: 2 years
- Type: HTTP
Google:
- Name: _gat
- Purpose: Used by Google Analytics to throttle request rate.
- Expiry: 1 day
- Type: HTTP
Google:
- Name: _gid
- Purpose: Registers a unique ID to generate statistical data on how the visitor uses the website.
- Expiry: 1 day
- Type: HTTP
HubSpot:
- Name: __hssc
- Purpose: Identifies if the cookie data needs to be updated in the visitor’s browser.
- Expiry: 1 day
- Type: HTTP
HubSpot:
- Name: __hssrc
- Purpose: Used to recognize the visitor’s browser upon reentry on the website.
- Expiry: Session
- Type: HTTP
HubSpot:
- Name: __hstc
- Purpose: Sets a unique ID for the session, obtaining data on visitor behavior for statistical purposes.
- Expiry: 180 days
- Type: HTTP
HubSpot:
- Name: hubspotutk
- Purpose: Sets a unique ID for the session, obtaining data on visitor behavior for statistical purposes.
- Expiry: 180 days
- Type: HTTP

Marketing Cookies:

Google:
- Name: IDE
- Purpose: Used by Google DoubleClick to register and report the website user’s actions after viewing or clicking one of the advertiser’s ads, measuring ad efficacy and presenting targeted ads.
- Expiry: 1 year
- Type: HTTP
Google:
- Name: pagead/landing
- Purpose: Collects data on visitor behavior from multiple websites to present more relevant advertisements and limit the number of times they are shown the same ad.
- Expiry: Session
- Type: Pixel
Google:
- Name: _gcl_au
- Purpose: Used by Google AdSense to experiment with advertisement efficiency across websites using their services.
- Expiry: 3 months
- Type: HTTP
Google:
- Name: pagead/1p-user-list/#/
- Purpose: Pending
- Expiry: Session
- Type: Pixel
HubSpot:
- Name: __ptq.gif
- Purpose: Sends data to the marketing platform HubSpot about the visitor’s device and behavior, tracking them across devices and marketing channels.
- Expiry: Session
- Type: Pixel
LinkedIn:
- Name: bcookie
- Purpose: Used by LinkedIn for tracking the use of embedded services.
- Expiry: 1 year
- Type: HTTP
LinkedIn:
- Name: li_sugr
- Purpose: Collects data on user behavior and interaction to optimize the website and make advertisements more relevant.
- Expiry: 3 months
- Type: HTTP
LinkedIn:
- Name: UserMatchHistory
- Purpose: Ensures visitor browsing-security by preventing cross-site request forgery, essential for the security of the website and visitor.
- Expiry: 30 days
- Type: HTTP
Twitter:
- Name: i/adsct
- Purpose: Used by Twitter.com to determine the number of visitors accessing the website through Twitter advertisement content.
- Expiry: Session
- Type: Pixel
LinkedIn:

Name: muc_ads
Purpose: Collects data on user behavior and interaction to optimize the website and make advertisements more relevant.
Expiry: 2 years
Type: HTTP

YouTube:

Name: LAST_RESULT_ENTRY_KEY
Purpose: Used to track the user’s interaction with embedded content.
Expiry: Session
Type: HTTP

LogsDatabaseV2:V#||LogsRequestsStore:

Name: [name]
Purpose: Pending
Expiry: Persistent
Type: IDB

YouTube:

Name: remote_sid
Purpose: Necessary for the implementation and functionality of YouTube video content on the website.
Expiry: Session
Type: HTTP

TESTCOOKIESENABLED:

Name: [name]
Purpose: Used to track the user’s interaction with embedded content.
Expiry: 1 day
Type: HTTP

YouTube:

Name: VISITOR_INFO1_LIVE
Purpose: Estimates the user’s bandwidth on pages with integrated YouTube videos.
Expiry: 180 days
Type: HTTP

YouTube:

Name: YSC
Purpose: Registers a unique ID to keep statistics of the YouTube videos the user has seen.
Expiry: Session
Type: HTTP

YouTube:

Name: ytidb::LAST_RESULT_ENTRY_KEY
Purpose: Used to track the user’s interaction with embedded content.
Expiry: Persistent
Type: HTML

YtIdbMeta#databases:

Name: [name]
Purpose: Used to track the user’s interaction with embedded content.
Expiry: Persistent
Type: IDB

YouTube:

Name: yt-remote-cast-available
Purpose: Stores the user’s video player preferences using embedded YouTube video.
Expiry: Session
Type: HTML

YouTube:

Name: yt-remote-cast-installed
Purpose: Stores the user’s video player preferences using embedded YouTube video.
Expiry: Session
Type: HTML

YouTube:

Name: yt-remote-connected-devices
Purpose: Stores the user’s video player preferences using embedded YouTube video.
Expiry: Persistent
Type: HTML

YouTube:

Name: yt-remote-device-id
Purpose: Stores the user’s video player preferences using embedded YouTube video.
Expiry: Persistent
Type: HTML

YouTube:

Name: yt-remote-fast-check-period
Purpose: Stores the user’s video player preferences using embedded YouTube video.
Expiry: Session
Type: HTML

YouTube:

Name: yt-remote-session-app
Purpose: Stores the user’s video player preferences using embedded YouTube video.
Expiry: Session
Type: HTML

YouTube:

Name: yt-remote-session-name
Purpose: Stores the user’s video player preferences using embedded YouTube video.
Expiry: Session
Type: HTML

Please note that third-party cookies may be used by external services mentioned above. We recommend reviewing their respective privacy policies for more information on how they use cookies and the data collected.

Managing Cookies

You can change your cookies preferences at any time by clicking on the icon located at the bottom left of each website page. Please note that disabling or blocking certain cookies may impact the functionality of our website.

Updates to the Cookies Policy

We may update this Cookies Policy from time to time to reflect changes in technology, legal requirements, or our business practices. Any updates or revisions will be posted on this page, and the revised policy will be effective upon posting.