WHAT DO I NEED TO KNOW ABOUT COOKIES?
Cookies are small files that are stored locally on your device when you visit a website. They are used for a variety of reasons:
- Storing information about users, so users don’t have to repeatedly type their information.
- Ensuring that you stay signed in when you leave and re-enter a website.
- Improving the user experience on a website by learning how users are navigating a site and accessing its functionality.
- Delivering relevant adverts to
- Ensuring that content is tailored to each user and their preferences.
To do all this, multiple types of cookies can be used:
First-party
These are cookies that are set by the website you are using. Only that website can create them for you to store. They can be used for reasons such as ensuring you stay logged on when you leave and re-enter a site.
Third-party
These are cookies that are set by an external websites and services. Websites might include content from other sources like Facebook or YouTube. Such systems may set their own cookies to display better content and further improve their services.
Session
These are cookies that are only set whilst your online session persists. They are removed from your device when your browser is closed.
Persistent
These are cookies that remain on your device after your session ends. They are used on sites that need to remember you and your preferences across multiple online sessions.
Functional
These are cookies that are utilised by websites to extend or improve the features and functionality within a website. For example, a website might utilise functional cookies to remember your preferences of content in order to recommend and display relevant articles or blog posts, or to remember you have visited the site before and messages/popups for first-time visitors should therefore not be displayed. Functional cookies can also aid in making sites accessible, as accessibility preferences like grayscale colour palette or increased font size selections can be remembered.
Strictly necessary
These are cookies that are required by the website to display certain content or provide certain functionality. Without them, users would not be able to experience a website to its fullest extent. Examples of such cookies include those that are stored when you sign into a website, or when you select your security preferences.
Advertising
These are cookies that are utilised to target visitors with relevant advertising. They are often connected to advertising platforms that track users across different websites to establish what their interests are. This is how you are displayed adverts relevant to you specifically.
Performance
These are cookies that help administrators ensure that a website is working efficiently and performing as it should for users.
HOW WE USE COOKIES
At steam-packet.com we use cookies to keep track of booking progress, and to remember you when you return to our site.
To make a booking on steam-packet.com, you need to have cookies enabled. If you don't wish to enable cookies, you'll still be able to browse the site, but you will not be able to make a booking. Most web browsers have cookies enabled by default, but you are able to disable them in your browser settings.
Please note that the cookies steam-packet.com utilise can't harm your computer. We don't store personally identifiable information such as credit card details in cookies we create, but we do use encrypted information gathered from them to help improve your experience on the site. For example, they help us to identify and resolve errors and to monitor site usage through analytics.
We do have relationships with carefully selected and monitored suppliers who may also set cookies during your visit to be used for remarketing purposes while using other websites - in other words to show you different offers based on what you appear to be interested in.
We're giving you this information as part of our initiative to comply with government legislation, and to make sure we're transparent about your privacy when using our website. We know you'd expect nothing less from us.
OUR COOKIES POLICY
To make full use of the online booking system and personalised features on steam-packet.com, your computer, tablet or mobile device will need to accept cookies, as certain personalised features of this website rely on them.
Our cookies don't store sensitive information such as your name, address or payment details: they simply hold the 'key' that, once you're signed in, is associated with this information. However, if you'd prefer to restrict, block or delete cookies from steam-packet.com, or any other website, you can use your browser settings to do this. Each browser is different, so check the 'Help' menu of your particular browser to learn how to change your cookie preferences.
COOKIES USED ON OUR WEBSITE
|
Cookie Domain
|
Name of Cookie
|
What do they do?
|
Duration
|
|
Steam Packet
|
fw-session
|
Used to store the “SessionID” for the current user’s session. This is used for server-side tracking of a user’s session across multiple requests.
|
End of session
|
|
Steam Packet
|
RequestVerificationToken
|
Used to hold a “Cross-Site Request Forgery” (CSRF) protection value to aid in the protection against malicious CSRF attacks.
|
End of session
|
|
Steam Packet
|
authinfo
|
Encrypted authentication details to store authentication info when a user is logged into the site for the duration of their session.
|
End of session
|
|
Steam Packet
|
bookingpreferences
|
Used to store and restore serialised form values for the “Book a Sailing” form. This will restore the users entered values into the form if the user were to return to the “Book a Sailing” form after clicking the “Check Availability” button.
|
1 day
|
|
Steam Packet
|
Timeduseriomresident
|
Stores the users answer to the “Do you live on the Isle of Man?” popup box question upon first visit to the site or if the cookie doesnt exist/has expired. The answer to that question is used to display different content/information to the user in appropriate places.
|
6 months
|
|
Steam Packet
|
ARRAffinity
|
This cookie is set by websites run on the Windows Azure cloud platform. It is used for load balancing to make sure the visitor page requests are routed to the same server in any browsing session.
|
End of session
|
|
Cloudflare
|
cfduid
|
The cookie is set by CloudFare. The cookie is used to identify individual clients behind a shared IP address and apply security settings on a per-client basis. It does not correspond to any user ID in the web application and does not store any personally identifiable information.
|
4 weeks
|
|
DoubleClick
|
test_cookie
|
This cookie is set by doubleclick.net. The purpose of the cookie is to determine if the users' browser supports cookies.
|
15 minutes
|
|
Google
|
ga
|
This cookie distinguishes users by assigning a randomly generated number as an identifier. It is used to calculate visitor, session and campaign data for the site’s analytics reports.
|
2 years
|
|
Google
|
gid
|
Responsible for counting and tracking page views in a standard Google Analytics session.
|
24 hours
|
|
Google
|
gcl_au
|
This cookie is used by Google AdSense for experimenting with advertisement efficiency.
|
90 days
|
|
Google
|
gcl_dc, gcl_aw
|
These cookies track and attribute campaign success from Google AdWords by creating unique hashed IDs based on page visits from ads.
|
90 days
|
|
Google
|
utma
|
Used to distinguish users and sessions. The cookie is created when the javascript library executes and no existing __utma cookies exists. The cookie is updated every time data is sent to Google Analytics.
|
2 years
|
|
Google
|
utmb
|
Used to determine new sessions/visits. The cookie is created when the javascript library executes and no existing __utmb cookies exists. The cookie is updated every time data is sent to Google Analytics.
|
30 mins
|
|
Google
|
utmc
|
Not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit.
|
End of session
|
|
Google
|
utmz
|
Stores the traffic source or campaign that explains how the user reached your site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics.
|
6 months
|
|
Google
|
utmv
|
Used to store visitor-level custom variable data. This cookie is created when a developer uses the _setCustomVar method with a visitor level custom variable. This cookie was also used for the deprecated _setVar method. The cookie is updated every time data is sent to Google Analytics.
|
2 years
|
|
Quantcast
|
qca
|
Collects information about our website ranking and targeted advertising.
|
13 months
|
|
Facebook
|
fbp
|
Facebook advertiser cookies are used for reporting on social campaigns, troubleshooting campaign set up and building aggregated pools of audiences for targeting based on behaviour trends.
Privacy policy: facebook.com/policies
|
2 months
|
|
Facebook
|
fr
|
The cookie is set by Facebook to show relevant advertisements to the users and measure and improve the advertisements. The cookie also tracks the behaviour of the user across the web on sites that have Facebook pixel or Facebook social plugin.
|
2 months
|
|
Hotjar
|
_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.
|
1 year
|
|
Hotjar
|
_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.
|
1 year
|
|
Hotjar
|
_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).
|
End of session
|
|
Hotjar
|
_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.
|
End of session
|
|
Hotjar
|
_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.
|
End of session
|
|
Hotjar
|
_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.
|
End of session
|
|
Hotjar
|
_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.
|
Under 100ms
|
|
Hotjar
|
_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.
|
30 minutes
|
|
Hotjar
|
_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.
|
30 minutes
|
|
Hotjar
|
_hjAbsoluteSessionInProgress
|
This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie.
|
30 minutes
|
|
Hotjar
|
_hjFirstSeen
|
This is set to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions.
|
End of session
|
|
Hotjar
|
hjViewportId
|
This stores information about the user viewport such as size and dimensions.
|
End of session
|
|
Hotjar
|
_hjRecordingEnabled
|
This is added when a recording starts and is read when the recording module is initialized to see if the user is already in a recording in a particular session.
|
End of session
|
| Teads |
TT_Viewer |
This is set by Teads to collect current URL, auctid parameter (sent through click-through URL), device, browser, OS. No personal information is collected. |
1 year
|
Google Analytics
Our website uses Google Analytics, a web analysis service provided by Google.
Google Analytics uses cookies that are stored locally on a user’s computer to facilitate an analysis of user behaviour and site performance. The information generated by such cookies (time, place and frequency of visits to our site), including user IP addresses, is stored by Google and used by Isle of Man Steam Packet Company Limited to better understand site usage, user experience and customer behaviour.
Google may also transfer information to third parties where required to do so by law or where such third parties process data on Google’s behalf. Google states that it will in never associate user IP addresses with other data held by Google. You can change how cookies are installed and/or stored by changing your website browser settings. For more information about changing cookie settings on your browser, please see the ‘Managing Cookies’ page on About Cookies UK. You should be aware, however, that by doing so you may not be able to make full use of all the functions of our website.
Google Analytics also offers an ‘Opt-out’ browser add-on, which is compatible with most modern browsers and can be downloaded here. This can help users restrict and manage what data Google can collect. The add-on effectively blocks the tracking script used by Google Analytics to collect information about website visits.
It should be noted, however, that the Google Opt-out add-on offered by Google does not affect other cookies or third-party tools this site may utilise in order to analyse usage and improve user experience.
For the cases in which personal data is transferred to the US, Google has self-certified pursuant to the EU-US Privacy Shield.
Google Tag Manager (GTM)
Our website also uses Google Tag Manager (GTM), a tag management system provided by Google that deploys JavaScript and HTML tags to improve the accuracy and relevance of tracking and analytics on websites.
Tags are small code elements that are used to measure traffic and visitor behaviour by tracking events. Such events are triggered and recorded when users carry out predefined actions.
GTM helps us to understand the reach and engagement of our online advertising and social channels; to configure remarketing; to better target relevant demographic groups; and to test and optimise our websites by integrating with Google Analytics as detailed above.
If you have performed deactivation, GTM takes this deactivation into account.
More information about GTM’s privacy practices can be found on Google’s Policies Page and Google’s Tag Manager Terms of Service.
Facebook
We use Facebook, the world’s largest social networking service, for advertising purposes. If you have an account with Facebook you will likely be shown ads based on your visits and purchases with us.
The data collected by Facebook when you visit our site may later be used to display Steam Packet ads on other third-party accounts with similar interests to you.
Hotjar
We use Hotjar in order to better understand our users’ needs and to optimise this service and experience.
Hotjar is a technology service that helps us better understand our users’ experience (e.g. how much time they spend on which pages, which links they choose to click, what users do and don’t like, etc.) and this enables us to build and maintain our service with user feedback. Hotjar uses cookies and other technologies to collect data on our users’ behaviour and their devices. This includes a device's IP address (processed during your session and stored in a de-identified form), device screen size, device type (unique device identifiers), browser information, geographic location (country only), and the preferred language used to display our website.
Hotjar stores this information on our behalf in a pseudonymized user profile.
Hotjar is contractually forbidden to sell any of the data collected on our behalf.
For further details, please see the ‘About Hotjar’ section of Hotjar’s support site.
MANAGING COOKIES
If cookies aren't enabled on your computer, it will mean that your booking experience on our website will be limited to browsing; you won't be able make a booking or use the ‘My Account’ section.
If you're not sure of the type and version of your web browser, or how to change your cookie settings, the following website is a useful resource: https://www.whatismybrowser.com
