lcp

Use of cookies

How does Tie-Me-Up use some of your personal data (e.g. IP) and how is it used?

Tie-Me-Up uses cookies.

What are they? Cookies are small files that a website or service provider transfers to the computer's hard drive via the web browser (only if you give your consent).

They allow the website systems or the service provider to recognise your browser and to capture and remember information. Examples: a) they help us remember and process the items in your shopping cart; b) they are useful for understanding your preferences based on previous or current site activity, which allows us to offer you improved services; c) they help us produce aggregated data about site traffic and interaction, so we know in which directions we need to develop, build and improve the site; d) for user identification; e) to retain users' personalised preferences; f) to help users carry out actions on the site without having to re-enter information when navigating from one page to another or when visiting the site later; g) for behavioural online targeted advertising and relevant ads for users.

How are they used?

The web server that serves the web page can store a cookie module on the user's computer or mobile device. An external web server that manages files included or referenced in the web page can also store cookies. All these cookie modules are called HTTP header cookies.

Another way to store cookies is through JavaScript code contained in or referenced from that page.

Each time the user requests a new page, the web server can receive the cookie values it has previously set and return the page with content related to those values. Similarly, JavaScript code is able to read a cookie that belongs to its domain and/or carry out an action accordingly.

What are the different types of cookies?

A cookie can be classified by its lifetime and the domain it belongs to. By lifetime, a cookie is either: a) a session cookie — deleted when the user closes the browser; or b) a persistent cookie, which remains on the user's computer/device for a predefined period.

Regarding the domain it belongs to, there are either: a) first-party cookies, which are set by the web server of the visited page and share the same domain; b) third-party cookies, stored by a domain different from the domain of the visited page. This can happen when the web page references a file, such as JavaScript, located outside its domain.

Cases in which you do not need to confirm or give your consent for cookies:

  • When a cookie is used exclusively for the purpose of transmitting a communication that is strictly necessary for the provider of an information-society service to provide a service explicitly requested by the user.

  • Cookies introduced by the user (session ID), such as first-party cookies, to keep track of users' input when filling in online forms, shopping carts etc., for the duration of a session.

  • Authentication cookies, to identify the user once they have logged in, for the duration of a session.

  • User-centred security cookies, used to detect authentication abuses, for a limited persistent duration.

  • Multimedia content cookies used to store technical data to play video or audio content, for the duration of a session.

  • Load-balancing cookies, for the duration of a session.

  • User interface personalisation cookies, such as language or font preferences, for the duration of a session.

  • Third-party content-sharing cookies for logged-in members of a social network.

  • You can choose to have your computer warn you every time a cookie module is sent, or you can choose to disable all cookies. You do this through your browser settings. As each browser is slightly different, consult your browser's Help menu to learn the correct way to modify cookie modules.

  • If you disable cookie modules, some of the features that make your experience more efficient may not work correctly.

What types of cookies does the PrestaShop platform (used by our online shop) use?

There are, in general, four categories of cookies: "Strictly Necessary", "Performance", "Functionality" and "Targeting". We use all four categories of cookies.

  • Strictly necessary cookies. These cookies are essential, as they allow you to be informed about our products and services.

  • Performance cookies. These cookies collect information about how you have used information related to the unique user name you provided, so that less pressure is placed on our back-end infrastructure. These cookies can also be used to let us know you have logged in, so we can offer you fresher content than for a user who has never logged in. We also use cookies to track aggregate use of the services and to experiment with new features and changes to the service. The information collected is used to improve the operation of the services offered on the site.

  • Functionality cookies. These cookies allow us to remember how you are logged in, whether you have chosen not to see ads any more, whether you have made an edit to an article in the Service while logged out, when you logged in or out, the status or history of the service tools you have used. These cookies also allow us to tailor the Service to deliver improved features and content for you and to remember how you have customised the Service in other ways, such as personalising the toolbars we offer in the right column of each page. The information these cookies collect can be anonymous and is not used to track our customers' browsing activity on other sites or services.

  • How are cookie modules targeted? Our advertising partners or other third-party partners may use these types of cookies to deliver advertising relevant to your interests. These cookie modules can remember that your device has visited a site or service and can also track your device's browsing activity on other sites or services. This information can be shared with organisations outside the site, such as advertisers and/or advertising networks, to deliver advertising and help measure the effectiveness of an advertising campaign, or with other business partners for the purpose of providing aggregated service-usage statistics and aggregated testing services.

Where do we use cookies?

  • Authentication. We use cookie modules to verify your account and determine when you are logged in, so we can give you easier access to our site and provide you with the appropriate experience and features. Cookies also help us remember your browser, so you do not have to register and can log in more easily to our site.

  • Security. We use cookies to help us keep the account and data safe. For example, cookie modules can help us identify and impose additional security measures when someone tries to access your account without authorisation. We also use cookie modules to store information that allows us to recover your account if you forget your password, or if you need additional authentication if you tell us that your account has been hacked. Cookies help us combat spam and phishing attacks by allowing us to identify computers used to create a large number of fake accounts.

  • Improving site features and services. We use cookie modules to help us store preferences, know when you have viewed or interacted with the content of our products, and provide you with personalised content and experiences. For example, cookies allow us to make suggestions to personalise content on third-party sites that integrate our social plugins. We also use cookie modules to offer you relevant content, so that you see the site in your preferred language.

  • Performance. We use cookie modules to give you the best possible experience.

  • Analytics and research. We use cookie modules to better understand how users use our products, so we can improve them. Cookie type used:
    https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage

Google Analytics cookies:

Google Analytics is a simple, easy-to-use tool that helps website owners measure how users interact with the website content. As a user navigates between web pages, Google Analytics provides website owners with JavaScript tags (libraries) to record information about the page a user has viewed, for example the page URL. The Google Analytics JavaScript libraries use HTTP cookies. Cookies were designed as a secure mechanism for websites to remember information or to record users' browsing activity and to "remember" what a user did on previous pages / in other interactions with the website.

The information generated by the cookie about the use of this site (including your IP address) is transmitted and stored on a Google server.

Google Analytics supports two JavaScript libraries (tags) for website measurement:

  • Using analytics.js cookies

The analytics.js JavaScript library is part of Universal Analytics and uses first-party cookies to:

- Distinguish unique users

- Throttle the request rate

When using the recommended JavaScript snippet, analytics.js sets cookies at the highest level of the domain. For example, if your website address is blog.example.co.uk, analytics.js will set the cookie domain to .example.co.uk. Setting cookies at the highest level of the domain allows users to be tracked across subdomains without any other configuration.

  • Using ga.js cookies

The ga.js JavaScript library uses first-party cookies to:

Determine which domain to measure.

Distinguish unique users.

Throttle the request rate.

Remember the number and time of previous visits.

Remember traffic source information.

Determine the start and end of a session.

Remember the value of visitor-level custom variables.

By default, this library sets cookies on the domain specified in the browser's document.host property and sets the cookie path at the root level.

Authentication cookies

Cookie authentication uses HTTP cookies to authenticate client requests and maintain session information. It works as follows:

The client sends a login request to the server.

On successful authentication, the server response includes the Set-Cookie header containing the cookie name, value, expiry time and other information.

The client must send this cookie in the Cookie header on all subsequent requests to the server.

On logout, the server sends back a Set-Cookie header that causes the cookie to expire.


USE OF FACEBOOK PIXEL

  • This site uses the Facebook Pixel, a small piece of JavaScript code added to the site to optimise ads, report the success of advertising campaigns across all devices, and display ads targeted to the audience. The Facebook Pixel sends information about your browsing session via HTTP headers to Facebook, including IP address, information about the web browser, page location, document, referrer and web-browser user agent. Pixel-specific data includes pixel identification data and Facebook cookie data to link events to a specific Facebook ad account and match them to a person known to Facebook. Facebook checks whether the person has previously seen or interacted with an ad from our account, or whether the person matches an audience rule, and prepares an analytical report containing anonymous or aggregated data. Facebook retains information collected from pixels for 180 days.

  • Google Tag Manager

For transparency reasons, please note that we use Google Tag Manager. Google Tag Manager does not collect personal data. It facilitates the integration and management of our tags. Tags are small elements of code used to measure traffic and visitor behaviour, to detect the impact of online advertising, or to test and optimise our websites. For more information about Google Tag Manager visit: https://www.google.com/intl/de/tagmanager/use-policy.html

  • Google Dynamic Remarketing

    We use Google Dynamic Remarketing to advertise over the Internet, in particular on the Google Display Network. Dynamic remarketing will show you ads based on which parts of websites you have viewed, by placing a cookie in your browser. This cookie module does not identify you in any way or allow access to your computer or mobile device. The cookie is used to tell other websites that "This user has visited a certain page, so show them ads related to that page." Google Dynamic Remarketing allows us to adapt our marketing to better suit customers' needs.

If you do not want to see ads from our site, you can opt out of Google's use of cookie modules by accessing Google Ads Settings. For further information, visit the Google Privacy Policy.

  • Google remarketing

    Following your visit to our online shop, as a result of the integration of a Google remarketing code, Google can see that you have accessed certain pages of ours (for example, initiating the ordering process). Subsequently, if you perform searches on Google or see ads from the Google network on other websites, we have the possibility to show you targeted ads for our products (known as remarketing). If you have a Google account, Google can link this data to your Google account.

You can find information about Google's data protection and how remarketing works in the Google Privacy Policy, as well as in the Google Remarketing Notes.

You can object to remarketing by configuring your browser so that it does not accept cookie modules. However, you will be able to use our site only in a restricted way.

In addition, you can disable interest-based ads from Google in Google Ads Settings using the following link: https://www.google.com/settings/u/0/ads/authenticated?hl=en

  • Google AdWords conversion tracking

We use the online advertising programme "Google AdWords" and conversion tracking within the scope of Google AdWords. Google conversion tracking is an analytical service. When you click on an ad placed by Google, a conversion-tracking cookie device is placed on the device. These cookies expire after 30 days, do not contain personal data and cannot be used for personal identification.

PrestaShop standard cookies

Tie-Me-Up, through PrestaShop, uses encrypted cookies to store all session information, both for visitors/customers and for employee administrators.