Cookie Policy

RushDublin.com (“we” / “our”) use cookies to operate our website, analyse our web traffic and integrate social media features.

This policy outlines our use of cookies (both first- and third-party) and how the end user (“you” / “your”) can change and/or restrict cookies in your web browser.

What is a cookie?

A cookie is a small dataset sent by a website’s server to the end-user’s web browser on their device.

Use and purpose of cookies

We use cookies to:

operate our website;
log your use of our website to analyse traffic; and
provide social media integration, e.g., to allow you to share content from our website to your social media feeds and access and interact with our associated social media pages through plugins.

None of the cookies on RushDublin.com are essential or deemed ‘strictly necessary’. However, by clicking “Accept” on the pop-up banner, you are acknowledging this cookie policy and consenting to use of both first- and third-party cookies present on our website as outlined in this policy.

By opting not to accept cookies (i.e., by not clicking “Accept” on the pop-up banner) you may still use our website, however some features (in particular, social media integration and plugins) may not function correctly or at all.

First-party cookies

RushDublin.com stores one first-party cookie on your device.

Name	thb-werkstatt-cookiebar
Value(s)	show (default); hide
Domain	.rushdublin.com
Expiration	12 months
Purpose	To disclose our use of cookies and display a link to our cookie policy upon the end-user’s visit to our website.

Third-party cookies

Facebook.com stores five cookies and Twitter.com stores two cookies on your device.

Please note: Some personal and identifiable information and/or personalised data may be collected and sent to the third-party domains listed in the tables below.

For information on how to block third-party cookies, please see the links in the “Further information” section of this policy.

Name	datr
Value(s)	Autogenerated
Domain	.facebook.com
Expiration	2 years
Purpose	To identify the web browser used on the end-user’s device.

Name	locale
Value(s)	Autogenerated
Domain	.facebook.com
Expiration	1 week
Purpose	To identify the language and region settings of the web browser on the end-user’s device.

Name	oo
Value(s)	Autogenerated
Domain	.facebook.com
Expiration	5 years
Purpose	To deliver third-party advertisements on Facebook.

Name	sb
Value(s)	Autogenerated
Domain	.facebook.com
Expiration	2 years
Purpose	To deliver third-party advertisements on Facebook.

Name	wd
Value(s)	Autogenerated
Domain	.facebook.com
Expiration	1 week
Purpose	To identify the screen resolution of the web browser on the end-user’s device and optimise the Facebook feed plugin on our index page according to it.

Name	guest_id
Value(s)	Autogenerated
Domain	.twitter.com
Expiration	12 months
Purpose	To display our Twitter feed plugin on our index page. Note: This cookie will only be used if the end user is not currently signed in to an account on Twitter.com.

Name	personalization_id
Value(s)	Autogenerated
Domain	.twitter.com
Expiration	9 months
Purpose	To display our Twitter feed plugin on our index page.

Further information

For further information on understanding and managing cookies in your web browser, please see the following links:

Desktop browsers

Clear, enable and manage cookies in Chrome (Google Chrome)
Protect your privacy: Cookies and cache (Mozilla Firefox)
Manage cookies and website data in Safari on Mac (Apple Safari)
How to manage cookies in Opera (Opera)
Delete Cookies in Microsoft Edge (Microsoft Edge)

Mobile browsers

Android

- - Clear, enable, and manage cookies in Chrome (Google Chrome)
  - Clear your browsing history and other personal data on Firefox for Android (Mozilla Firefox for Android)

iOS

- - Clear, enable, and manage cookies in Chrome (Google Chrome)
  - Clear browsing history in Firefox for iOS (Mozilla Firefox)
  - Clear the history and cookies from Safari on your iPhone, iPad, or iPod touch (Apple Safari)

For other devices, operating systems and web browsers (both desktop and mobile), please consult the manufacturers’ and/or developers’ support.

Last updated: 16 February 2022