Notifications HUB cookie policy

The Notifications HUB uses different types of cookies to provide the user with a more complete and personalized online experience. The different types of cookies we use and what we use them for are described below.

Cookies required

The notifications HUB uses cookies that are necessary for the user to be able to correctly use the functions and services of Icomm. Without these cookies, it is not possible to provide the service properly. These cookies do not collect any information that can be used to identify the user.

Functional cookies

Functional cookies serve to provide the user with a better online experience. These cookies do not collect or store any information that allows us to identify the user.

Performance Cookies

Performance cookies are used to understand how users use the Site. This allows us to keep our products and services up to date and relevant. We also use technologies similar to cookies, known as "web beacons", which are anonymous and are used for statistical purposes only, without collecting or containing information that identifies the user.

Security cookies

These cookies are only sent to the server with an encrypted request over the HTTPS protocol, to prevent cross-site scripting attacks. In this way we can guarantee the safety of the user's browsing.

Third party cookies

Notifications HUB may use third-party cookies on user websites that come from a different domain than the site the user is on. These cookies are mainly used for advertising and tracking on the site. In addition, the site may obtain third-party cookies as a result of contracts and/or services used by said third parties. The user understands and accepts that the notifications HUB does not have any type of control or possibility of modification over these cookies.

What cookies does the notifications HUB use on this Site?

In order to make full use of the functions and services that we offer in our notifications HUB, it is necessary for the user to accept the use of cookies. Thanks to them, we can provide certain features and improvements to the site. Although we set only some direct cookies, we also make use of external services that set their own cookies. We believe that it is essential that the user is informed about the cookies that are being used and the reason for their use. Below you can find a table that explains in detail the type of cookies that are being configured on our site.

It is important to note that although we audit the cookies used on our site, external services may make changes to their names and purposes. Not all cookies mentioned in our table may be stored on the user's device after visiting our site.

In our notifications HUB, we use the following cookies:

	Name	Purpose
	sdtp	Cache of information about the opt in and when to show it
	sdtpc	Indicator of active/inactive cache of information about the opt in
	sddh	Cache of information about the opt in html configured by the client, if applicable
	wdcc	Subscription status webhook information cache, if applicable
	cwdscc	Webhooks active/inactive cache indicator
	cus	Current user active/inactive subscription indicator cache
	TPIDC	Internal user identifier cookie
	wpnViewcount	Indicator of number of page views
	wpnLastDenial	Date (in timestamp format) of the last time the user clicked on 'no' within the opt in
	minPageViewsToShow	Cache of the client configuration with the minimum number of pages that the user must see before showing the opt in
	_wpnDestga	Indicator of whether the data has already been sent to the server for the user or not
	wpncotpc	Present cache indicator for chat buttons
	wpncotp	Cache data for chat buttons
	wpnhard	Data Lookup Retry Indicator
	wpnsdcachetp	Cache for A/B testing of site speed
	wpnsdcachetpcontrol_v2	Cache present indicator for A/B testing of site speed
	*us	Banner/popup indicator already seen by the user. Contains numeric data and ends in "us"
	wpneatouser	User Random Assignment for A/B Experiments
	_wpnlvusw	Last View Featured Feature Indicator
	_csrf-frontend	Code generated to avoid CSRF
	_identity-frontend	Logged in user data
	_advanced-frontend	Cookie with session data
	G_ENABLED_IDPS	Used to log in with Google
	gat, gid, _ga	Google Analytics Cookies

The user must understand and accept that the cookies used on our site may be constantly updated and vary depending on the service we offer. Therefore, they will be updated according to the availability and resources that we have in our notifications HUB.

Why does the Notifications HUB use cookies?

Notifications HUB uses cookies to understand site usage and improve the content and offerings on our service.

Cookie Settings

Cookie settings are an important task for users who wish to control their online experience. Modern browsers allow users to customize their cookie settings to accept all cookies, receive alerts when a website offers a cookie, or decline to receive cookies and delete existing cookies. It is important to note that if users block all cookies, some services will not work properly. To access all features and services, users must enable cookies.

If users do not configure their browser, the cookies provided by the website will be automatically accepted. Instead of blocking all cookies, users can choose to block only third-party cookies, which will allow the website to function properly as intended. In short, cookie settings are an important way for users to personalize their online experience and access all the services offered by the website.

Consult our article: Notifications HUB Guide for more details.

Updated on: 05/31/2023