Tiers uses sub-processors to assist with the provision of our services to our customers. These sub-processors may process customer data. The identity, processing activity, contact information, and processing location of each sub-processor is listed below. We update this list from time to time. We encourage you to periodically review this statement for the latest information.
Sub-Processor Name | Permitted Sub-Processor Activities | Data Protection Officer Contact Details | Address | Processing Location(s) |
---|---|---|---|---|
Amazon Web Services | Infrastructure | aws-EU-privacy@amazon.com | 410 Terry Avenue North. Seattle, WA, USA | Washington, USA |
Cloudflare | Infrastructure | privacyquestions@cloudflare.com | 106 E. 6th Street Suite 350. Austin, TX 78701, USA | California, USA |
You will find all the cookies used on our websites in this list. These are sorted by the purposes mentioned in the Cookie Statement.
We use different Technologies to ensure that our website functions well and is easy to use.
Host | Cookie name | Purpose | Lifetime of technology | Shared with third parties |
---|---|---|---|---|
Tiers | cookieConsent | Used to identify that the user gave consent to using cookies. | 1 week | Not shared |
Tiers | strictly-necessary-cookies | Used to identify that the user gave consent to using Stricly Necessary cookies. | 1 week | Not shared |
Tiers | marketing-cookies | Used to identify that the user gave consent to using Marketing cookies. | 1 week | Not shared |
Cloudflare | __cf_bm | Cloudflare’s bot products identify and mitigate automated traffic to protect our website from bad bots. Cloudflare places the __cf_bm cookie on end-user devices that access customer sites protected by Bot Management or Bot Fight Mode. The __cf_bm cookie is necessary for these bot solutions to function properly. This cookie expires after 30 minutes of continuous inactivity by the end user. The cookie contains information related to the calculation of Cloudflare’s proprietary bot score and, when Anomaly Detection is enabled on Bot Management, a session identifier. The information in the cookie (other than time-related information) is encrypted and can only be decrypted by Cloudflare. A separate __cf_bm cookie is generated for each site that an end user visits, as Cloudflare does not track users from site to site or from session to session. The __cf_bm cookie is generated independently by Cloudflare, and does not correspond to any user ID or other identifiers in a customer’s web application. | 30 minutes | Shared with Cloudflare |
_GRECAPTCHA | Used for risk analysis to mitigate the risk of spam via our contact form. | 6 months | Shared with Google | |
tawk.to | twk_idm_key | Used for the session management of the user with the chat. | Session | Shared with tawk.to |
tawk.to | twk_uuid_* | Used to identify the user in the chat. | 6 months | Shared with tawk.to |
We use Technologies that deliver adverts relevant to a visitor’s interests.
Host | Cookie name | Purpose | Lifetime of technology | Shared with third parties |
---|---|---|---|---|
Tiers | _ga | Used in context with identifying visitors to the website. The cookie collects the behavioral data of all visitors. The cookie registers data such as IP addresses, visitor sources, time spent on the website, and page requests for the visit. | 2 years | Shared with Google |
We may update this technology list from time to time in response to changing legal, technical or business developments.
If you have any further questions or comments, please contact us via our contact page.
We encourage you to periodically review this list for the latest information. We will keep prior versions of our technology list in an archive for your review.
This technology list may be modified and was last modified on 8 February 2023.