Cookies policy

Mars 2021

BRANNET MARKET COMPANY, S. L., hereafter Brannet Market, is the owner, and thus responsible, of the projects indicated below, including any of their subdomains and sections, hereafter “Website”:

 

In this document we provide you with information about cookies, both in a general way and about the ones we use in particular.

1. GENERAL INFORMATION ABOUT COOKIES

What are cookies?

“Cookies” are small compressed text files that allow us to save data specifically related to the user’s device while he is visiting our website.

Generally, when referring to “cookies” on the Internet, reference is also made to other technologies used for similar purposes: for instance, through the technical configuration of your device, or your IP address when you download complete images or simply a “pixel”, data are being collected. This allows us to recognize you when you visit our website again, to know your approximate location, the connection time, the device from which you access (fixed or mobile), the operating system and browser used, the most visited pages, the number of clicks made, among others.

How to manage Cookies?

Web browsers usually allow you to disable the use of cookies; limit them to specific web pages or configure the browser to notify you when a cookie is placed in the device. You can also delete them at any time from your computer’s hard drive (file: “cookies”).

In most cases, a website can be accessed even if the use of cookies has been blocked in the browser settings or when they have not been accepted.

However, typically, when you block the placement of cookies, you can suffer limitations in the presentation of the website and your user interface.

To obtain more detailed information about the cookies installed on your device and how to manage and delete them, please click the link corresponding link in your web browser:

Additional information is also available at the following link:

2. SPECIFIC INFORMATION ABOUT COOKIES USED ON OUR WEBSITES

Brannet Market only displays advertisements to its free users: if you become a “premium” user we will not show you advertisements. To show you this advertising, for example, we use cookies.

Brannet Market only hires tier-1 service providers (such as OneTrust) and advertising providers (such as IAB vendors, Google).

Regarding the control and management of cookies and similar technologies, we use One Trust “cookie compliance” technology, based on IAB Europe “Transparency and Consent Framework”.

Through our cookie setting panel (powered by One Trust) you can consent or reject, granularly, the use of our cookies and those of third parties, as well as certain data processing carried out by third parties based on their legitimate interests. By selecting “Reject all” you will also block said data processing.

Cookies (and similar technologies) help us better understand what interests and helps our users most, and to improve our services.

You can find extended information and clarification about each category of cookies used on our websites through our cookie settings panel, to which you access by clicking on “Cookie setting”, located at the bottom of all our webs, in section “Legal”.

Please find below the description of some of them:

Session and persistent cookies

We use the so-called “session cookies”, which are stored exclusively during the time of your visit to any of our websites.

In addition, we and our partners use “persistent cookies” to withhold information about those users who repeatedly access any of our websites.

Analytical, advertising cookies…

We use personalized advertising cookies (which we will talk about below) and web analytics cookies, to know the number of visitors to the different pages and sections of our website, their interactions and duration of their visits, place of entry and exit, to try to improve our content and its capacity to generate interaction.

We use Google Analytics, Hubspot and Hotjar cookies to measure the results of visits and customer acquisition, and to analyze traffic and, for example, detect potentially malicious “bots”.

Cookies can also be “first-party” or “third-party” cookies

“First-party” cookies are those that are sent to the user’s terminal equipment from a device or domain managed by Brannet Market as editor of the website from which the services requested by the user are provided.

“Third-party” cookies are those that are sent to the user’s terminal equipment from a device or domain that is not managed by Brannet Market, but by another organization, which processes the data obtained through such cookies.

You can find out complete information about the data processing carried out by these third parties (lawful bases, international data transfers carried out, retention periods, exercise of rights of access, erasure, restriction of processing, portability and rectification, and how exercise your rights, … in their respective policies linked in this text and in the cookie tables).

You will find detailed information about all cookies used on each of our websites (www.Brannet Market.com; www.bemockup.com; in the cookie table at the end of this text.

Information on the processing of data shared with our advertising partners
Preliminary information

In the field of online advertising, cookies and other similar technologies allow website visitors to be recognized or singled out (but not identified in the traditional sense of the word, that is, by their names, surnames, ID number or email address) and classified into groups or “audiences” based on their interests.

Knowing your interests and personalizing the advertising displayed to you in accordance with them is possible thanks to the use of these cookies and similar technologies.

Third-parties advertising

We allocate the exploitation of our advertising spaces to companies that market them to third parties who then insert their advertisements on our website, depending on your habits and interests.

Consequently, Brannet Market offers its advertising spaces based on real-time biddings through two channels or platforms:

  • Google AdManager and
  • Various platforms that also market our advertising spaces among their own partners through header bidding techniques (Rubicon Project, Index Exchange, DistrictM, Amazon APS, OpenX).

Through these real-time biddings, companies interested in our advertising spaces, bid to display their ads on our website, customizing their advertising based on the user.

Brannet Market logically benefits from the advertising displayed, enables the collection of user information through cookies and captures their consent to this extent through its websites. But here is where our intervention and responsibility ends.

Brannet Market cannot and indeed does not control the advertisements displayed, nor does it participate in the data processing operations carried out on these platforms to select the user receiving the ads and the advertiser placing such ads.

For these purposes, and to guarantee the quality of both the advertising and the advertisers, Brannet Market only markets its advertisement space with the leading platforms worldwide (IAB those others mentioned in the cookies policy), as previously stated.

You can learn more about Google AdManager and the Header Bidding service providers, in their respective links as provided below.

You can browse the full list of IAB Europe partners (advertisers) here.

You can prevent targeted advertising from being specifically shown to you on Brannet Market websites in the following ways:

Through our cookie setting panel: by granularly accepting or rejecting the different categories of cookies used, you can authorize or not the processing of your data for the purposes of profiling you, the placing of personalized advertising, and the rest of the processing operations described hereby.

You can also disable cookies in your browser by installing a plug-in as Ghostery or Privacy Badger or through a rejection system (“opt-out”) provided by some third parties that install cookies on our website, as Google (behavioral advertising) (requires Google log-in).

Adobe’s advertising

Brannet Market, in turn, offers third-party advertising (Adobe), and tracks its users through Google Analytics when they click on its advertising banners, to check the performance in terms of conversion rate on that advertiser’s website.

Brannet Market advertising

Brannet Market contracts “affiliate” advertising services on different platforms that will redirect its users to our website when they click on our banners or advertisements (through Awin, Reddit and Naver). These platforms also install cookies on our websites in order to verify and track the performance of their ads.

Moreover, Brannet Market contracts personalized advertising services of various social media platforms (such as Facebook and other third parties) to attract potential new users to our websites who have been profiled by such platforms according to their interests. Brannet Market selects, among these profiles, those who we understand may be interested in our products (for example, those users who had visited our websites, or users within a determined age or geographical location).

These platforms integrate “cookies” and other technologies (from Facebook for example) on our website. These technologies allow them, after you have provided consent, to track, for example, whether their users have only accessed Brannet Market’s websites to just quit, they have downloaded any products or have become Premium users.

Then, they provide us with this information in an aggregated and anonymous way to bill us accordingly, allowing us to better understand the price and profitability of our advertising campaigns on each platform.

Furthermore, we may show advertisements to visitors who have left our website, for example without registering, to try to convince them to do so (remarketing techniques).

Regarding these data processing operations, Brannet Market is a “joint controller” together with each of those platforms, in relation to (i) the selection of the interests of its users to whom we request our advertising is displayed; (ii) their monitoring and observation on our websites; and (iii) the provision of statistical and aggregated data to Brannet Market on the result of these campaigns, that is, the conversion rate , if applicable, into our clients.

All these processing operations are carried out without Brannet Market being able to identify you: we only identify you when you register as a free or premium user.

Otherwise, Brannet Market does not participate in and therefore is not a controller of the processing operations that advertisers and platforms carry out for their own purposes, either prior or subsequent to those other processing operations carried out together with Brannet Market.

Brannet Market has adhered to Facebook´s standard Joint Controllership Addendum , by virtue of which we have defined the scope of our shared processing operations. We provide you with the link to Facebook Ireland privacy policy, where information is provided on the legally mandatory aspects. We also inform you that Facebook Ireland is responsible for granting your data protection rights (arts. 15 to 20 General Data Protection Regulation) in relation to the personal data stored by Facebook Ireland after our joint processing.

International data transfers

Regarding Brannet Market advertising, by using Facebook and Google services, we participate in the international transfer of personal data to countries with a potentially lower level of protection than that imposed by the General Data Protection Regulation. These international transfers are therefore based on standard contractual clauses.

In relation to third-party advertising, Brannet Market’s controllership is limited to the duties of providing information and obtaining our website visitors’ consent for the purpose of using their cookies to show personalized advertising.

Additional Information

Below, and in the corresponding cookie tables, Brannet Market provides you with the links to the information offered by each of these companies and platforms regarding the joint controllership situations already described and their own processing operations (lawful bases, international data transfers carried out, retention periods or the exercise of a right of access, erasure, restriction of processing, portability and rectification).

We remind you again that you can exercise your rights of access, restrictions of processing and / or erasure in relation to the processing of your personal data carried out jointly with the aforementioned platforms:

  • Through our email [email protected], if you are a registered user of Brannet Market.
  • And otherwise, before the platforms in which you have a user account (because we will not be able to identify you).

PinterestPrivacy Policy and Cookies Policy

CriteoPrivacy Policy and Cookies Policy

FacebookPrivacy PolicyCookies Policy and Joint processing annex

TwitterPrivacy Policy and Cookies Policy

GooglePrivacy Policy and Cookies Policy

Microsoft BingPrivacy Policy and Cookies Policy

NaverPrivacy Policy and Cookies Policy

RedditPrivacy Policy and Cookies Policy

Brannet Market Company’s cookie table

In the table below you will find detailed information about all cookies used on Brannet Market’s web pages.

First-party cookies on the websites owned by Brannet Market Company

PURPOSE

EXPIRY DATE

DOMAIN

Develops statistics about Premium services advertisements

1 hour

Brannet Market

Stores URL to redirect the user after finishing the registration or login process

10 minutes

Brannet Market

Collects information about visits

2 years

Brannet Market, Bemockup

Checks if internal promotions are shown to the user

2 days

Brannet Market

Avoids CSRF attacks in forms

2 hours

Brannet Market

Test about payment data. Selection of payment, subscription to Premium

3 days

Brannet Market

Remembers user’s personal ID each time they log on. This cookie is only created if the user agrees to be remembered

30 days

Brannet Market

Stores information on marketing campaigns in which the User has participated

30 days

Brannet Market
Bemockup

Test about search activity. Analysis of searches run by the user

30 days

Brannet Market

Measures data collected from searches

30 days

Brannet Market

Used in the payment process to redirect the user to the payment platform in case they are logged off

7 days

Brannet Market

Language detection. Helps us to collect information about the language preferences of the User to provide visitors with information in their preferred language

Session

Brannet Market, Bemockup

User login. Used to manage and store information about the user login

Session

Brannet Market, Bemockup

Checks if cookies compliance messages are visible on the Website

Session

Brannet Market, Bemockup

They allow the operation and navigation through the website, as well as the use of the different options or services that exist in it, including those that the editor uses to allow the management and operation of the website and enable its functions and services, such as, for example, control traffic and data communication, identify the session, access restricted access parts, remember the elements that make up an order, carry out the purchase process of an order, manage payment, control fraud linked to the security of the service, make the request for registration or participation in an event, use security elements while browsing, enable dynamic content (for example, animation of loading a text or image) or share content through social networks

Session

Bemockup

They store information to allow the users to access the service with certain characteristics that can differentiate their experience from that of other users, such as, for example, the language, the type of user (anonymous, registered or premium), the appearance or content of the service, depending on the type of browser through which the users accesses the service or the region from which they access the service, etc.

Session

Bemockup

Third-party cookies in www.brannetmarket.com

THIRD PARTY

COOKIE

DESCRIPTION

Google Analytics (Performance)+ info

We collect information of how users interact with the content of the web. When a user browses the pages of a website, information about the page the user has viewed is colected; for example, URL, time spent on the website, number of pages viewed. It allows us to generate labels or objectives to know if you have bought, what item, how many times … It also collects demographic and navigation data, that is; where does the user come from, how does he get to our website or what campaign does he come from

Hotjar (Performance)+ info

_hjClosedSurveyInvites

Hotjar cookie that is set once a visitor interacts with an External Link Survey invitation modal. It is used to ensure that the same invite does not reappear if it has already been shown.

_hjDonePolls

Hotjar cookie that is set once a visitor completes a survey using the On-site Survey widget. It is used to ensure that the same survey does not reappear if it has already been filled in.

_hjMinimizedPolls

Hotjar cookie that is set once a visitor minimizes an On-site Survey widget. It is used to ensure that the widget stays minimized when the visitor navigates through your site.

_hjShownFeedbackMessage

Hotjar cookie that is set when a visitor minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if the visitor navigates to another page where it is set to show.

_hjid

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.

_hjRecordingLastActivity

This should be found in Session storage (as opposed to cookies). This gets updated when a visitor recording starts and when data is sent through the WebSocket (the visitor performs an action that Hotjar records).

_hjTLDTest

When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed.

_hjUserAttributesHash

User Attributes sent through the Hotjar Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to be updated.

_hjCachedUserAttributes

This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. These attributes will only be saved if the user interacts with a Hotjar Feedback tool.

_hjLocalStorageTest

This cookie is used to check if the Hotjar Tracking Script can use local storage. If it can, a value of 1 is set in this cookie. The data stored in_hjLocalStorageTest has no expiration time, but it is deleted almost immediately after it is created.

_hjIncludedInPageviewSample

This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site’s pageview limit.

_hjIncludedInSessionSample

This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site’s daily session limit.

_hjAbsoluteSessionInProgress

This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie.

Zendesk (Performance)+ info

_cf_bm

This Cloudflare cookie helps manage incoming traffic that matches criteria associated with bots.

_cfruid

Cloudflare cookie used in cases were 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.

_cfduid

Cloudflare cookie used for security restrictions

_zendesk_shared_session

Authentication cookie – set to be anonymous

_zendesk_authenticated

This is a flag set when a user is authenticated to display the most up to date content.

Adpone (Advertising)+ info

Recognize and analyze inventory available in our advertising spaces to offer our users advertising of interest. Campaign optimization, segmentation, frequency.

Adform (Advertising)+ info

Allows personalized advertising to be shown

RichAudience (Advertising)+ info

Allows personalized advertising to be shown

Smartadserver (Advertising)+ info

Allows personalized advertising to be shown

Sovrn (Advertising)+ info

Allows personalized advertising to be shown

Pinterest (Performance / Advertising)+ info

We will impact users who have visited the website or are registered on it with an advertising banner, we will use the data of registered users so as not to impact campaigns whose objective is premium subscription and we will look for users with similar online behavior to registered users or who have visited the web. This set of data will be used both to reach our target audience through online campaign segmentation and to measure their results.

Criteo (Performance / Advertising)+ info

We will impact users who have visited the website or are registered on it with an advertising banner, we will use the data of registered users so as not to impact campaigns whose objective is premium subscription and we will look for users with similar online behavior to registered users or who have visited the web. This set of data will be used both to reach our target audience through online campaign segmentation and to measure their results.

Facebook (Performance / Advertising)+ info

We collect data from visitors to our pages to analyze behavior and impact them with our ads if they finally do not register or do not subscribe. Also, to be able to impact users similar to those who visit us or similar to those registered or subscribed that are not clients.

Instagram (Performance / Advertising)+ info

We collect data from visitors to our pages to analyze behavior and impact them with our ads if they finally do not register or do not subscribe. Also, to be able to impact users similar to those who visit us or similar to those registered or subscribed that are not clients.

Twitter (Performance / Advertising)+ info

We collect data from visitors to our pages to analyze behavior and impact them with our ads if they finally do not register or do not subscribe. Also, to be able to impact users similar to those who visit us or similar to those registered or subscribed that are not clients.

Google Ads (Performance / Advertising)+ info

We collect data from visitors to our pages to analyze behavior and impact them with our ads if they finally do not register or do not subscribe. Also, to be able to impact users similar to those who visit us or similar to those registered or subscribed that are not clients.

Bing Ads (Performance / Advertising)+ info

We collect data from visitors to our pages to analyze behavior and impact them with our ads if they finally do not register or do not subscribe. Also, to be able to impact users similar to those who visit us or similar to those registered or subscribed that are not clients.

AWIN (Performance / Advertising)+ info

Advertising Activity: Business Transaction Tracking and Results Measurement

Naver (Performance / Advertising)+ info

Advertising Activity: Business Transaction Tracking, Conversion Rate and Results Measurement

Reddit (Performance / Advertising)+ info

We collect quantitative data from the users who have seen or clicked on our ads published on the platform to measure the performance of advertising actions: visits, registrations and subscriptions. This data is quantitative and does not link or provide the details of the users’ account or personal data (they are agregated and do not identify the user)

RTB Mind (Performance / Advertising)+ info

Traffic Pixel: Conversion and intermediate actions (it measures if the user has visited the price page but has not converted, etc). It is also identified by pixel if users are premium so as not to impact them with our campaigns

Google (Performance / Advertising)+ info

NID

Used by Google to personalize the ads displayed in the website

_ga

Used by Google to store a unique customer identifier

_gid

Used by Google to distinguish users

1P_JAR

Google uses this cookie to personalize ads that may be of your interest

hsid

Security cookie to authenticate users, avoid fraudulent use of login credentials and protect user data against unauthorized third parties

sidcc

Security cookie to authenticate users, avoid fraudulent use of login credentials and protect user data against unauthorized third parties

sidcc

Used by Google to obtain anonymous information about browsing

sapisid

It is created when you log into a Google account in order to remain connected to that same Google account when using its services again

apisid

It is created when you log into a Google account in order to remain connected to that same Google account when using its services again

ssid

It is created when you log into a Google account in order to remain connected to that same Google account when using its services again

dsid

Used by Google to display more relevant ads

ide

Used by Google to display more relevant ads

anid

Used by Google to personalize the ads displayed in the website

Hubspot (Performance / Functionality)+ info

_hs_opt_out

This cookie is used by the opt-in privacy policy to remember not to ask the visitor to accept cookies again

__hs_do_not_track

This cookie can be set to prevent the tracking code from sending any information to HubSpot.

__hs_initial_opt_in

This cookie is used to prevent the banner from always displaying when visitors are browsing in strict mode

hs_ab_test

This cookie is used to consistently serve visitors the same version of an A/B test page they’ve seen before

__cfduid

This cookie is set by HubSpot’s CDN provider, Cloudflare. It helps Cloudflare detect malicious visitors to your website and minimizes blocking legitimate users

__cfruid

This cookie is set by HubSpot’s CDN provider because of their rate limiting policies.

__hstc

The main cookie for tracking visitors. It 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

This cookie keeps track of a visitor’s identity. It is passed to HubSpot on form submission and used when deduplicating contacts.

__hssc

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

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.

OpenX (Advertising)+ info

i

Records anonymized user data, such as IP address, geographic location, visited websites and which ads the user has clicked on, in order to optimize the display of ads based on the user’s navigation on websites that use the same advertising network

pd

Collect information about visitor behavior on various websites. This information is used on the website to optimize the relevance of advertising

DistrictM (Advertising)+ info

Allows personalized advertising to be shown

AppNexus (Advertising)+ info

uuid2

This cookie contains a unique randomly-generated value that enables the Platform to distinguish browsers and devices. It is matched against information – such as advertising interest segments and histories of ads shown in the browser or device – provided by clients or other third parties and stored on the Platform. This information is used by clients to select advertisements for delivery by the Platform, and to measure the performance of, and attribute payment for, those advertisements. In addition, we use this cookie to enable clients to use data which does not reveal or use an Internet user’s real-world identity or data they collect outside of the Platform or acquire from other third parties. This cookie is also sometimes matched to clients’ or other third parties’ cookies so that they can use data they collect outside of the Platform to serve more relevant advertisements to Internet users. When a user opts out of having the Platform used to select ads based on online behavior, the unique value in uuid2 is deleted and replaced with the non-unique value “-1”.

anj

The anj cookie contains data denoting whether a cookie ID is synced with our partners.

icu

The icu cookie is used to select ads and limit the number of times a user sees a particular ad. It contains information such as the number of times an ad has been shown, how recently an ad has been shown, or how many total ads have been shown.

Amazon APS (Advertising)+ info

ad-id

Used by Amazon Advertising to record user actions and target website content based on ad clicks on a different website

ad-privacy

Used by Amazon Advertising to record user actions and target website content based on ad clicks on a different website

Rubicon Project (Advertising)+ info

trp_optout

Log Preferences: Cookie indicating that a user has opted-out of behavioral targeting marketing.

FPTrust

Log Preferences: These cookies support the opt-out process via the Network Advertising Initiative (NAI).

Khaos

Platform Operations: Internal user identifier used for analytics.

rsid

Platform Operations: Session cookie that contains information about a device, including region (derived from IP address, not geolocation data), operating System, browser, etc., that is used during the ad inventory sale process.

rpx, rpx_*

Platform Operations: Contains expiration dates for information in the rpb cookie.

fcap

Platform Operations: Number of times we have shown an ad on a per user basis.

put_*

Platform Operations: Bidder identifiers placed at the request of a bidder, to sync a bidder’s independent information about an end user with Rubicon Project, to allow the bidder (not Rubicon Project) to bid on ads through the Rubicon Project advertising exchange based on behavioral targeting information known only to the bidder (i.e., the user identifier will be transmitted in a bid request to the bidder that caused this cookie to be placed).

pux

Platform Operations: Dates for when information in the put_* and sput cookies expires and should be refreshed.

rpb

Analytics: Publisher and partner-owned audience segments used for private marketplaces and audience-based planning and forecasting in Orders.

sput, sput_*

Analytics: Contains multiple bidder identifiers (i.e., data that would be stored in multiple put_* cookies) in a smaller number of cookies.

ses*

Analytics: Indicates number of times Rubicon Project has served a user an advert for this particular unit of inventory.

vis*

Analytics: Indicates number of times a user action has precipitated an ad request for this particular unit of inventory.

cd

Analytics: Indicates whether cookies are disabled for the device.

cimg*

Analytics: Contains information about served ads (timestamp, site, internal identifiers for the publisher, buyer, advertiser, and displayed advertisement).

audit

Analytics: Used to record cookie consent data.

Google Tag Manager (Performance / Advertising)+ info

Google Tag Manager is a tag management system that allows third parties to add functionality to websites, video content, and mobile applications. Examples of such solutions include web analytics, campaign analytics, audience measurement, personalization, allows you to quickly and easily update tags and code snippets on a website or your mobile applications, such as those intended for analytics traffic and optimize marketing campaigns. You can add and update custom, third-party or AdWords tags, Google Analytics, Firebase Analytics and Floodlight, Facebbok Ads, Twitter Ads, Hotjar. It is used in order to manage the different conversion codes of the online Marketing and retargeting tools

Index Exchange (Advertising)+ info

CMPS

Identify the main server for quick responses to the user’s page

CMTS

Identify backup server for quick responses to user page

CMGO

Indicates if the user’s primary server has changed

CMTEST

Confirm if cookies can be created for the user

CMID

Recognize web users that IndexExchange has seen before by browser. This is the cookie that is used to allow personalized advertising, among other uses

CMPRO

Identify server profile for quick responses to user page

CMRUM3

It contains a table that maps the IDs of Index Exchange’s users with those of our bidding partners

CMDD

Measures how many unique pages a user has interacted with on a web property

CMST

Contains the duration of a session in a session

CMSC

Contains the start time of a user in a session

CMO

Indicates if the web user has chosen not to participate using behavioral advertising opt-out tools

Improve Digital (Advertising)+ info

tuuid

To enable bidding process

tuuid_lu

To enable bidding process

pvt

Tracks views to measure conversions

ih

To limit number of advertisements you see (frequency capping)

fh

Impression counter

um

To enable bidding process

umeh

To enable bidding process

sh

To limit number of advertisements you see (frequency capping)

lcri5m

Load creative

lcai9h

Load campaign impressions

3. CHANGES IN THE COOKIE POLICY

We recommend that you review this cookie policy each time you connect to our Websites. Brannet Market reserves the right to modify its content at any given time.

In any case, Brannet Market will notify or announce the new content and the dates on which a revision of these terms occurs, for the information of its users.

Last edited: December 2020