Last Updated: 13 December 2019
TransferWise uses small files (known as cookies) to see how you use our site and products. We put them on your computer when you visit our site, and use themto recognise you and store information in between visits.
With cookies we can give you a better browsing experience, improve the quality of our products, and keep our marketing costs down. They let us make it easier tolog in, and they show us where you might be having trouble with our products. Without them, we’d have no way to remember anything about you, such as whetheryou’re logged in.
Strictly necessary cookies. We need these cookies to run our website — they let us save your cookie preferences, and keep the site secure. They’realways on.
Cookies that give you a better browsing experience. These let us tailor the site to your needs, like displaying it in the same language as your webbrowser. We’ll sometimes refer to them as functionality cookies.
Cookies that help us improve our products. These let us use tools that show us how you interact with our products — Mixpanel, for example. They helpus find and fix problems for our customers, and they’re also known as analytical or performance cookies.
Cookies that keep our marketing costs down. These improve our marketing — helping us to spend less on sites like Google and Facebook, and moreon charging as little as we can. When our costs go down, so do our prices. We share this information in aggregate form with third parties, for the purposeof advertising.
You can see each cookie we use and our reasons for using them below.
|Technology||Purpose||Session or Persistent||Lifespan||Third Parties||Privacy information|
|STRICTLY NECESSARY COOKIES|
The __cfduid cookie is used to identify individual clients behind a shared IP address and apply security settings. It is used to stop malicious traffic and spam across our site.
Cloudflare provides web optimisation and security services that we use to improve and protect our websites, including a reverse proxy, pass-through security service, and a content distribution network.
|cookie_notice_closed||The cookie_notice_closed is used to persist the action of hiding the cookie banner on transferwise.com between sessions.||Persistent||90 Days|
|Feature_gdpr_consent_policy||This cookie is used to store your cookie consent preferences and protect your rights under EU data protection legislation.||Persistent||90 Days|
|Gid||This cookie is used to identify users. This is only used forTransferWise's own internal purposes. By recognising unique browsers, we can more accurately measure the total number of users visiting our site from different locations on the web.||Persistent||1 year|
|JSESSIONID||The JSESSIONID cookie is used to monitor the reliability of our service and helps us manage login sessions by preserving user states across page requests.||Session||New Relic||https://newrelic.com/termsandconditions/privacy|
|Oauth||The userToken, oauthToken cookies are used by TransferWise to authenticate each subsequent login request to our site by a customer.||Session||24 hours|
|rc::c||The rc::c cookie is used to help us distinguish between humans and bots.||Session|
The #cid cookie is used to gather all information relating to a browser in order to detect any fraudulent or unlawful activity of a user. This is a strictly necessary cookie in order to keep us be compliant with applicable EU laws and regulations.
The cacheID cookie is used to gather all information relating to a browser in order to detect any fraudulent or unlawful activity of a user. This is a strictly necessary cookie in order to keep us compliant with applicable EU laws and regulations.
|Session and Persistent||1 Year||Veriff||https://www.veriff.com/privacy-policy|
|LocaleData||The localeData cookie is used in order to store the user's language preference and provide the user with customised regional content. By doing this, we can ensure we show content translated into the preferred language. This is a key part of making our service accessible to an international audience.||Persistent||1 Year|
Retains the user’s previous decision for the ‘Remember this device for 30 days’ checkbox each time they login.
Remembering the device means we record that the customer has successfully logged in with second factor authentication (such as SMS or Push) on that device previously, and we will only require first factor authentication (e.g. password) in order to login again on that same device in the next 30 days.
This rememberMe cookie only records true/false whether or not the checkbox was ticked, and so whether or not it should be ticked next time.
If rememberMe was selected, the fxuser cookie stores a unique value on that device used to approve skipping 2fa for that user
1 year (rememberMe)
35 days (fxuser)
|Test.cookie||The test.cookie cookie is used to check if the user's browser supports cookies.||Persistent||1 day||Doubleclick.net||https://policies.google.com/technologies/ads?hl=en-US|
The _gat, cookie is installed by Google Universal Analyticsto throttle the request rate to limit the collection of data onhigh traffic sites.
The _gid cookie is used to store information on how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected includes the number of visitors, the source where they have come from, and the pages visited in an anonymous form.
The _ga cookie is used to calculate visitor, session,campaign data and keep track of site usage for the site'sanalytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors.
The _dc_gtm_UA# cookie is used to limit the number of requests that we make to Google Analytics.
The collect cookie is used to track the user across devices and marketing channels. This data is sent to GoogleAnalytics about the user’s device and behaviour.
|Session, Persistent, Persistent, Session, Session||1 Minute, 1 Day, 2 Years||https://support.google.com/analytics/answer/6004245|
The _hjid cookie is used to obtain data on users’ behaviourfor our own statistical and monitoring purposes.
This cookie enables us to identify which users have been randomly selected to take part in a sample to monitor those users’ behaviour on our site.
Hotjar also provides us with a heatmap of the site which allows us to monitor, for example, how far a user has scrolled down a page and where on a page they have hovered.
With session and screen recording, we’re able to get more context for complicated problems - by observing users going through our flows in an uninterrupted manner, in their real life setting. This aids us in identifying subconscious thought patterns users have, which helps us pin-point where customers might struggle in our product.
|_iz_sd_ss_ and _iz_uh_ps_||
The _iz_sd_ss_ cookie is used to store data about a visitor in order to make decisions about when to show a survey, like the number of site visits and survey views. We ask users to complete a survey from time to time in order to help TransferWise improve its pages and services. For example, we might ask users whether they could find the information they were looking for, or ask users what products and services they are interested in. We use survey responses in order to make content on our site more relevant and helpful to the individual user. We do not study individuals during this process.
The_iz_uh_ps_ cookie is used to store data about a user relating to the number of site visits and survey views, which enables us to make a decision about whether we should undertake a survey about the use of our site.
|Session, Persistent||1 year||Informizely||https://www.informizely.com/data-protection|
|MixPanel||The mp_mixpanel cookie is an analytical cookie and is used to help us understand how the user moves through the website. This data is shared with Mixpanel in order to help us improve our site. With it we can measure visits to parts of our site, track the success of flows within our site, understand where the failures or drop offs are, and measure the success of changes to the site. As well as referral source information, it contains a randomly assigned number in order to associate events belonging to the same session, and if logged in, the TransferWise customer number. It also allows us to determine the customer numbers of a group of users that may have been affected by a fault of our site. Access to separate internal tools would be needed to query customer information from that customer number.||Persistent||1 year||Mixpanel||https://mixpanel.com/legal/privacy-policy/|
|COOKIES THAT KEEP OUR MARKETING COSTS DOWN|
The _fr, _fbbp, _tr, AA003 and ATN cookies are used by Facebook to obtain encrypted data about visitors and users of our website for the purposes of measuring advertising effectiveness, showing relevant advertising to certain groups of users and excluding other groups of users from seeing irrelevant advertising.
For example, if a user registers on TransferWise.com, the cookie will share with Facebook encrypted emails used to register with TransferWise in the form of a hash. If you have an account with Facebook, Facebook will be able to identify you as the same user on Facebook that has registered for TransferWise. If you don’t have an account, this hash renders useless, and as such ‘new’ information previously unknown to Facebook is not shared with Facebook.
In this example, we can measure the effectiveness of our Facebook advertising. It helps us understand how many users have registered with TransferWise via Facebook. This is important as it means we can make informed investment decisions about our advertising. This may help us contribute to our overall mission of reducing prices for customers over time.
This can also help us prevent advertising irrelevant content to users, e.g. advertisements encouraging users to sign upto TransferWise when they have already done so.
|g_airpr_recent_visist||The g_airpr_recent_visit cookie is used to store data about visitors in order to match the unique identifier with visits to digital media outlets so we can understand the effectiveness of our communications.||Persistent||1 day||Onclusive||https://onclusive.com/legal/gdpr-dataprocessingaddendum/|
The _gcl_au cookie is used to link Google advertisements to conversions made on our site. This cookie is also used by Google AdSense for experimenting with advertising efficiency across websites using their service.
The ads/ga-audiences cookie is used by Google Adwordsin order to re-engage visitors based on their online behaviour across various websites.
The NID cookie is used to assign a unique ID number to are turning user’s device. This unique ID number is used for targeting advertisements to the user.
|Persistent, Session, Persistent||90 days, 90 days|
|MUID and MUIDB||The MIUD and MUIDB (bat.bing.com) cookie enables us to track users by synchronising the Microsoft User Identifier (MUID) across many domains and helps us count the number of valid clicks. This helps us better understand user behaviour and has the potential to increase efficiency in our marketing spend.||Persistent||1 year||Microsoft||https://about.ads.microsoft.com/en-gb/resources/policies/microsoft-advertising-click-measurement-description-of-methodology|
The personalization_id cookie is used to store data about visitors and users in order to measure advertising effectiveness, show relevant advertising and exclude irrelevant advertising.
The i/adsct cookie is used by Twitter to determine the number of visitors accessing the website through Twitter advertising content.
The _B cookie allows us to store data about a user in order to log conversions made from clicks on advertisements. In particular, this cookie enables us to collect statistical data related to the user's website visits, such as the number of visits, average time spent on a website and what pages have been loaded. This helps us better understand user behaviour and has the potential to increase efficiency in our marketing spend.
The XB and pagead/conversion/1001035224 cookie is used by Yahoo to enable it to track Yahoo conversions.
|Persistent, Persistent/Session||2 year, 6 days||Yahoo||https://policies.yahoo.com/xa/en/yahoo/privacy/index.htm|
|Facebook Integrations||We use the Facebook button on our website in order to link users to our Facebook profile. We may use Facebook'sadvertising services. In providing these services Facebook may collect certain information about our website visitors.||https://developers.facebook.com/docs/facebook-pixel/implementation/gdpr/|
|Google AdWords||We may use Google's advertising services which may include remarketing, re-engagement or similar audience features in Google Ads that would allow us to reach people who previously visited our website, and match the right people with the right message. Google may display ads about our website or our services when you are browsing other websites. In providing these services Google may collect certain information about our website visitors.||https://policies.google.com/privacy|
|Youtube Integrations||We use Youtube to embed videos on our website. In providing this service Google may collect certain information about our website visitors.||Youtube||https://policies.google.com/privacy?hl=en&gl=uk|
You can choose to block cookies by activating the settings on your browser that allow you to refuse the setting of all or some cookies. However, if you use your browser settings to block all cookies (including essential cookies) you may not be able to access parts of the website. Your browser settings also allow you to delete all cookies stored on your device whenever you wish.
The UK Information Commissioner’s Office has provided the following guidance on controlling cookies:
If you are concerned about online tracking then we can recommend you:
If you have any questions about the cookies or similar technologies in use on our website, please send an email to firstname.lastname@example.org.