Cookie Policy

What are cookies?

A cookie is a small text file that may be placed on your device when you visit our sites.
When you next visit our websites, the cookie allows us to distinguish your device from other users’ devices.

For almost any website to work properly, it needs to collect certain information on its users. Cookies help make your experience of the Internet smoother and more interactive. These cookies are designed for different reasons, such as to allow the website to recognise users on subsequent visits, customise a website for a user, provide information to help us improve a user’s website experience, and to store the user’s preferences. They also help ensure that the advertisements that you see online are more relevant to you and your interests.

Why do we use cookies?

To allow our websites to work and help keep them safe and secure e.g. to load images and to allow you to log in securely.
To improve the performance of our websites by helping us analyse how they are used and understand which parts work well, and which don't.
To improve visitors experience on our websites and to personalise your experience.
To understand how effective our online advertising communications are.

What types of cookies do we use?

Depending on who owns the cookie, they are classified as:

First-party cookies: These are created by the website (domain) you are visiting. They allow us to collect customer analytics data, remember language settings, and carry out other useful functions that help provide a good user experience.
Third-party cookies: These are created by domains other than the one you are visiting. Third-party cookies are mostly used for tracking and online advertising purposes. If using incognito mode, browsers will not load third-party cookies. Note: We have no control over third-party cookies - you can turn them off, but not through us. You should read the privacy policy and / or cookie policy for each source.

Depending on the lifespan of the cookie, they are classified as:

Persistent cookies: Persistent cookies stay on your computer or device after your browser has been closed and last for a time specified in the cookie. The cookie will be automatically deleted when the cookie expires, or it can be deleted manually.
Session cookies: Session cookies only last as long as your online session, and disappear from your computer or device when you close your browser (like Google Chrome or Safari).

Depending on the purpose/function of the cookie, they are classified as:

Type of Cookie	Purpose
Strictly Necessary	Strictly necessary (sometimes called "essential") cookies are used only to transmit the data online and are needed to make the website operational. Without the use of these cookies, you may not be able to use some of the features of websites.
Functional	These help us recognise when you have visited our site previously so we can personalise content for you. For example, a cookie could help us remember your choice of language so you don't have to select this each time you visit our sites.
Performance	Performance cookies monitor website performance and collect data on how visitors use a website. These cookies provide information to help improve how a website works and are sometimes known as “statistical" or "analytical" cookies. For example, performance cookies can be used to gather data about visits to the website, including numbers of visitors and visits, length of time spent on the site, pages clicked on or where visitors have come from.
Advertising	Advertising (also known as "targeting") cookies are used to deliver advertisements more relevant to you, but can also limit the number of times you see an advertisement, and be used to chart the effectiveness of an ad campaign by tracking users’ clicks.

Other tracking technologies (web beacons)

A web beacon may also be known as a web bug, pixel tag or clear GIF. Web beacons are a clear graphic image (typically one pixel in size) that is delivered through a web browser or HTML e-mail. To a user this will be invisible.

A web beacon acts as a tag that records an end user’s visit to a particular web page or viewing of a particular e-mail. Web beacons are often used in conjunction with a cookie and provided as part of a third-party tracking service. Common usage scenarios for web beacons include file download monitoring, and ad campaign performance management. Web beacons also can report to the sender about which e-mails are read by recipients.

First-party cookies used by Untap

First party cookies used for https://www.untap.pe :

Name of Cookie	Session or Persistent (& Expiry)	Provider	Type of Cookie	Purpose
__cfruid	Session	CloudFlare (via HubSpot)	Strictly Necessary	Used to identify trusted web traffic and help detect malicious visitors to our website. Used in cases where multiple users are hidden behind the same client IP address. Each user will have a unique cookie to help prevent a case of rate limiting all users if one particular user hits the rate limit threshold.
__hs_initial_opt_in	Persistent 7 days	HubSpot	Strictly Necessary	This cookie is used to prevent the banner from always displaying when visitors are browsing in strict mode. It contains the string "yes" or "no".
__hs_opt_out	Persistent 13 months	HubSpot	Strictly Necessary	This cookie is used to remember not to ask the visitor to accept cookies again. It contains the string "yes" or "no".
__hs_do_not_track	Persistent 13 months	HubSpot	Strictly Necessary	This cookie can be set to prevent the tracking code from sending any information to HubSpot (note: it still allows anonymized information to be sent to HubSpot). It contains the string "yes.
hs-messages-is-open	Persistent 30 minutes	HubSpot	Strictly Necessary	This cookie is used to determine and save whether the chat widget is open for future visits. It resets to re-close the widget after 30 minutes of inactivity.
hs-messages-hide-welcome-message	Persistent 1 day	HubSpot	Strictly Necessary	This cookie is used to prevent the welcome message from appearing again for one day after it is dismissed.
hs_langswitcher_choice	Persistent 2 years	HubSpot	Strictly Necessary	This cookie is used to save the visitor’s selected language choice when viewing pages in multiple languages.
__hs_cookie_cat_pref	Persistent 13 months	HubSpot	Strictly Necessary	This cookie is used to record the categories a visitor consented to.
hs_ab_test	Session	HubSpot	Strictly Necessary	This cookie is used to consistently serve visitors the same version of an A/B test page they’ve seen before.
<id>_key	Persistent 14 days	HubSpot	Strictly Necessary	When visiting a password-protected page, this cookie is set so future visits to the page from the same browser do not require login again.
__hstc	Persistent 13 months	HubSpot	Performance	This cookie contains the domain, utk, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session).
hubspotutk	Persistent 13 months	HubSpot	Performance	This cookie keeps track of a visitor's identity. It is passed to HubSpot on form submission and used when deduplicating contacts. It contains an opaque GUID to represent the current visitor.
__hssc	Persistent	HubSpot	Performance	This cookie keeps track of sessions. This is used to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. It contains the domain, viewCount (increments each pageView in a session), and session start timestamp.
__hssrc	Session	HubSpot	Performance	Whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted their browser. If this cookie does not exist when HubSpot manages cookies, it is considered a new session. It contains the value "1" when present.
_hjid	Persistent 365 days	Hotjar	Performance	Hotjar cookie that is set when the customer first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.
_hjAbsoluteSessionInProgress	Persistent 30 minutes	Hotjar	Performance	This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie.
_hjIncludedInPageviewSample	Persistent 30 minutes	Hotjar	Performance	This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's pageview limit.
_gat	Persistent 1 minute	Google Analytics	Performance	To limit requests to Google Analytics (version GA3)
_gat_UA-XXXXXXXX-X	Persistent 1 minute	Google Analytics	Performance	To limit requests to Google Analytics (version GA4)
_ga	Persistent 2 years	Google Analytics	Performance	To identify unique users.
_gid	Persistent 24 hours	Google Analytics	Performance	To distinguish different users by a non-personal random number, instead of using personal information.
_ga_<container-id>	Persistent 2 years	Google Analytics	Performance	Used to persist session state.
_gcl_au	Persistent 3 months	Google Adsense	Advertising	Used by Google AdSense for experimenting with advertisement efficiency across web sites using their services. It’s for “Conversion Linker” functionality – it takes information in ad clicks and stores it in a first-party cookie so that conversions can be attributed outside the landing page.
messagesUtk	Persistent 13 months	HubSpot	Functional	This cookie is used to recognize visitors who use the chat option on our website. If we chat with a visitor who later returns to the website in the same browser, the messages tool will load their conversation history.

First party cookies used for https://app.exm.cloud
Note: Cookies may also show from https://funds.exm.cloud which is a specific module within UNTAP.

Name of Cookie	Session or Persistent (& Expiry)	Provider	Type of Cookie	Purpose
JSESSIONID	Session	Untap	Strictly Necessary	Stores the ID of the session opened in Untap's application server to attend requests fired by the user.
id_token	Persistent 10 hours	Untap	Strictly Necessary	Stores the JSON Web Token (JWT) that holds user’s credentials once authenticated
access_token	Persistent 10 hours	Untap	Strictly Necessary	Stores the JSON Web Token (JWT) client applications use to get access to Untap’s API services.
expires_at	Persistent 10 hours	Untap	Strictly Necessary	Stores the expiration date for the user in the authentication server.
https%3A%2F%2Fapp.exm.cloud%2Fcom.etask.etaskweb.ETaskWeb%2Ftheme	Session	Untap	Strictly Necessary	Stores the visual theme used to render the application to the user.
hydra_returnTo	Session	Untap	Strictly Necessary	Used to know the URL of the page to show users after logging out.

First party cookies used for https://www.exm.support:

Name of Cookie	Session or Persistent (& Expiry)	Provider	Type of Cookie	Purpose
__cfruid	Session	CloudFlare (via Zendesk)	Strictly Necessary	Used to identify trusted web traffic and help detect malicious visitors to our website. Used in cases where multiple users are hidden behind the same client IP address. Each user will have a unique cookie to help prevent a case of rate limiting all users if one particular user hits the rate limit threshold.
__cf_bm	Persistent 30 minutes	CloudFlare (via Zendesk)	Strictly Necessary	This cookie helps manage incoming traffic that matches criteria associated with bots.
_zendesk_session	Persistent 8 hours	Zendesk	Strictly Necessary	Stores account ID, route for internal service calls and the cross-site request forgery token.
zendesk_thirdparty_test	Persistent 8 hours	Zendesk	Strictly Necessary	Used during sign in on host mapped accounts for cookie-restricted browsers.
_zendesk_shared_session	Persistent 8 hours	Zendesk	Strictly Necessary	Authentication cookie - set to be anonymous. Holds session information for sharing across Zendesk applications.
_zendesk_authenticated	Session	Zendesk	Strictly Necessary	This is a flag set when a user is authenticated to display the most up to date content.
_zendesk_cookie	Persistent 1 year	Zendesk	Strictly Necessary	Saves arbitrary preference settings. Two factor authentication features and device tracking will not work without it.
bime_subdomain	Persistent 20 years	Zendesk	Strictly Necessary	Holds the subdomain name of the Untap account used for Zendesk services.
__zlcmid	Persistent 1 year	Zendesk	Strictly Necessary	Store visitor's machine-id for the Chat widget's authentication
_app_market_session	Session	Zendesk	Strictly Necessary	Stores the session key for the managing of Apps.
_help_center_session	Session	Zendesk	Strictly Necessary	Stores unique session key for Help Center product.
__stripe_mid	Persistent 1 year	Stripe (via Zendesk)	Functionality	Cookie used to provide fraud prevention.
_voice_session	Session	Zendesk	Functionality	Sessions for Voice.
_pendo_meta.PENDO_API_KEY	Persistent 100 days	Pendo (via Zendesk)	Performance	Analytics - Associates metadata with site visitors
_pendo_accountId.PENDO_API_KEY	Persistent 100 days	Pendo (via Zendesk)	Performance	Analytics -Grouping of site visitor metadata
_pendo_visitorId.PENDO_API_KEY	Persistent 100 days	Pendo (via Zendesk)	Performance	Analytics - Identifies site visitors
_pendo_launcher-closed.PENDO_API_KEY	Persistent 10 days	Pendo (via Zendesk)	Performance	Analytics - Application launcher
optimizelyEndUserId	Persistent 6 months	Optimizely (via Zendesk)	Performance	Optimizely uses cookies and localStorage to uniquely identify visitors, track and attribute their actions to experiments and personalization campaigns, and deliver consistent experiences across page loads and visitor sessions. This cookie stores a visitor's unique Optimizely identifier. It's a combination of a timestamp and random number.
_biz_nA, _ biz_pendingA, biz_ABTestA, _biz_uid _biz_flagsA	Persistent 1 year	Zendesk	Performance	Used for A/B testing.
__ncuid	Persistent 1 year	Zendesk	Performance	Cookie allows Zendesk to count visits and traffic sources, to measure and improve the performance of the site.
_gat	Persistent 1 minute	Google Analytics (via Zendesk)	Performance	Used to gain insights into the use of the help centre - by limiting requests to Google Analytics (version GA3)
_gid	Persistent 1 day	Google Analytics (via Zendesk)	Performance	Used to gain insights into the use of the help centre - by distinguishing different users by a non-personal random number, instead of using personal information.
_ga	Persistent 2 years	Google Analytics (via Zendesk)	Performance	Used to gain insights into the use of the help centre - by identifying unique users.
_uetvid	Persistent 1 year	Microsoft (via Zendesk)	Performance	Used to track visitors on multiple websites.
ajs_anonymous_id	Persistent 1 year	Zendesk	Advertising	These cookies are generally used for Analytics and help count how many people visit a certain site by tracking if you have visited before.
ajs_group_id	Persistent 1 year	Zendesk	Advertising	These cookies track visitor usage and events within the website.
ajs_user_id	Persistent 1 year	Zendesk	Advertising	This cookie helps track visitor usage, events, target marketing, and can also measure application performance and stability.

Note: If a provider (other than Untap) has been listed above - further information can be found in the 'Third-party cookies used by Untap' section.

Third-party cookies (and external providers) used by Untap

Third Party	Purpose	Useful Links
Auth0 (part of Okta, Inc group) via https://auth.hydra.cloud	Auth0 is for user authentication and authorization. For example, when a user logs in to our application https://app.exm.cloud, this includes when customers log in using SSO (single sign on).	https://auth0.com/privacy
CloudFlare (used by sites hosted by HubSpot and Zendesk)	Single cookie used to identify trusted web traffic and help detect malicious visitors to our website.	https://www.cloudflare.com/privacypolicy/
HubSpot	We use HubSpot to host our website https://www.untap.pe. HubSpot is used to manage the content on our Site, conduct web analytics and optimize the position of our website in search engines.	https://legal.hubspot.com/privacy-policy https://knowledge.hubspot.com/reports/what-cookies-does-hubspot-set-in-a-visitor-s-browser https://knowledge.hubspot.com/account/hubspot-cookie-security-and-privacy
HotJar (used by HubSpot and Zendesk)	We use Hotjar to personalize our website, collect your feedback and analyze website traffic.	https://www.hotjar.com/privacy https://help.hotjar.com/hc/en-us/articles/115011789248-Hotjar-Cookie-Information
Google Analytics	Google Analytics allows us to measure and thoroughly analyze the traffic on our website. It also enables us to estimate whether we earned back the investment for particular ad campaigns and measure its outcome.	https://policies.google.com/privacy https://developers.google.com/analytics/devguides/collection/gajs/Cookie-usage
DoubleClick (owned by Google)	DoubleClick is a company owned by Google, which services we use to manage advertising campaigns on web, including on our website.	https://www.google.com/policies/technologies/ads/
Google AdWords	Google AdWords is a tool that we use to personalize and maximize the effects of our advertising campaigns. Google AdWords impact on our ad campaigns and actions includes adjusting such campaigns for our visitors within web browsers.	https://www.google.com/policies/technologies/ads/
LinkedIn	We like to connect with people on our social media accounts and visitors to our site can share pages, such as blog posts, to their own social media accounts.	https://www.linkedin.com/legal/privacy-policy https://www.linkedin.com/legal/l/cookie-table
Twitter		https://twitter.com/en/privacy https://help.twitter.com/en/rules-and-policies/twitter-cookies#
Power BI (part of Microsoft)	We use PowerBI so our customers can get reporting from the data entered into our systems Cookies set by PowerBI are needed to Used to distribute traffic to the website on several servers in order to optimise response times and to store data on the time spent on the website and its sub-pages, during the current session.	https://privacy.microsoft.com/en-gb/privacystatement
Bing.com (part of Microsoft)	If maps are displayed within your PowerBI reports, additional cookies may be needed from bing.com to support the map features.
Microsoft Ads (used by Zendesk)	Used by Zendesk for performance cookies to track visitors to our site.
Zendesk (Note: includes other 3rd parties such as Pendo and Optimizely)	Zendesk is used to run our support site - https://www.exm.support and allows us to communicate with customers through channels such as web chat. The link on the right lists each cookie by name, shows the type and explains the purpose, so this third-party have not been listed under each heading to avoid duplication as the link will specify this information.	https://www.zendesk.co.uk/company/agreements-and-terms/cookie-policy/ https://www.pendo.io/legal/privacy-policy/ https://www.pendo.io/legal/cookiepolicy/ https://help.optimizely.com/Set_Up_Optimizely/Cookies_and_localStorage_in_the_Optimizely_snippet
YouTube (owned by Google)	Untap uses multiple sources, as listed on the left, for video hosting. Examples of video content we may display could be instructional videos to support customers using our application or client testimonials explaining how our product has helped support their business. More information about the cookies used by each third-party can be found using the links provided on the right hand side.	https://policies.google.com/privacy?hl=en-GB https://www.youtube.com/intl/ALL_uk/howyoutubeworks/user-settings/privacy/
Vimeo		https://vimeo.com/privacy https://vimeo.com/cookie_policy
Vidyard		https://www.vidyard.com/privacy/ https://www.vidyard.com/cookies/

Web beacons used by Untap

Untap uses web beacons through our website https://www.untap.pe which is hosted by HubSpot.
We typically use web beacons in emails. They help us to:

Measure if an email campaign is successful. For example, if we launch a new brochure or provide white papers, we can see if the emails have been read.
Keep track of users who do not engage with the content we send out to visitors who have subscribed to our mailing lists, so HubSpot can make decisions if future content may still be useful to you.

Note: Web beacons, clear gifs, tracking pixels and similar technologies can also be used by some third parties, such as Google Analytics or LinkedIn.

Do I have to accept cookies?

You do not have to accept cookies to use Untap. However, you should be aware if you do reject cookies, certain features of our websites may not work properly (or at all) and you may have a poor user experience as a result.

How can I opt out or adjust the settings?

Although most browsers are set to accept cookies, you can change your browser settings. To read more click the link for your browser below.

Please note that opt-out mechanisms described above generally rely on cookies to retain your opt-out preferences. So if you reject or erase all cookies, your opt-out choices may not function properly. You can find more information about how you can manage your privacy settings and cookies at the All About Cookies and Your Online Choices websites.

Do you have any information for opting out of third-parties?

Google Analytics:
https://tools.google.com/dlpage/gaoptout

DoubleClick (Google):
https://support.google.com/dfp_premium/answer/2839090?hl=en

Google Ads:
https://support.google.com/ads/answer/2662922

Hotjar:
https://www.hotjar.com/opt-out

To opt-out of interest-based advertising by third parties, please visit:

Digital Advertising Alliance (DAA)’s self-regulatory opt-out page (http://optout.aboutads.info/) and mobile application-based “AppChoices” download page (https://youradchoices.com/appchoices) and / or Network Advertising Initiative (NAI)’s self-regulatory opt-out page (http://optout.networkadvertising.org/) if you are located in the United States.
European Interactive Digital Advertising Alliance (EDAA)’s consumer opt-out page (http://youronlinechoices.eu) if you are located in Europe.

How can I avoid web beacons (or similar tracking technologies)?

Web beacons are designed to be unobtrusive but you can normally render them ineffective by switching off cookies in your browser.
There are also browser add-ons and extensions that specifically block web beacons.

To avoid web beacons in emails, you can turn off images in your email service.
Check your email’s help section to find out how.

Who do I contact if I still have questions?

For general enquiries, you can email us via info@untap.pe.

If you have any concerns or questions about how Untap use cookies, you can contact:
Data Protection Officer: Manfredi Bargioni
Telephone: +44 (0)1252 302 354
e-mail: Manfredi.bargioni@untap.pe

Postal Address:
Untap Software Limited
Suite 8, The Hub,
Farnborough Business Park,
Farnborough,
Hampshire,
GU14 7JP

We would always ask that you raise any concerns with us first. To make a complaint about the way Untap Software Limited work with cookies, you can contact the Information Commissioner’s Office (ICO) by visiting https://ico.org.uk/make-a-complaint/cookies/.