FusPay Cookies Policy
FusPay Technologies Inc. (“FusPay” or “we”, “our”, “us” and any other derivative in any jurisdiction) 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 them to 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 to log in, and they show us where you might be having trouble with our products. Without them, we would have no way to remember anything about you, such as whether you’re logged in.
In this policy, we have explained how and why we use cookies, and what each of them do. We have broken them down into four groups:
Strictly necessary cookies. We need these cookies to run our website — they let us save your cookie preferences and keep the site secure. They are always 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 web browser. We will 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 — Instance, for example. They help us 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 more on 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 purpose of 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
Cloudflare
We use the __cfduid cookie to identify individual clients behind a shared IP address and apply security settings. This helps us to stop malicious traffic and spam across our site.
We also use the __cfruid cookie for our rate-limiting policies.
__cfduid cookie 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.
Persistent
1 year
Cloudflare
https://www.cloudflare.com/privacypolicy/
Gid
This cookie helps us uniquely identify visitors so that new features on the site are consistently displayed each time they visit. Without this use, new features will not function correctly.
Persistent
1 year
No third parties involved
id_tmp
This cookie helps us identify users for our 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
No third parties involved
JSESSIONID
The jsessionid cookie helps us to monitor the reliability of our service and manage login sessions by preserving user states across page requests.
Session
New relic
https://newrelic.com/termsandconditions/privacy
Oauth
The userToken, oauthToken cookies let us to authenticate each subsequent login request to our site by a customer.
Session
24 hours
No third parties involved
rc::c
We use the rc::c cookie to help us distinguish between humans and bots.
Session
Veriff
We use the #cid cookie 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 laws and regulations.
Session
One year
Veriff
https://www.veriff.com/privacy-policy
We use the cacheID 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 which helps us comply with laws and regulations.
Persistent
twCookieConsent
This is essential for letting us remember your choice of cookie consent.
Persistent
6 months
No third parties involved
twCookieConsentGTM
This is essential for letting us remember your choice of cookie consent.
Persistent
6 months
No third parties involved
selectedProfileID
We use the selected-profile-id-userid cookie to store the selected profile on your device.
_mp_opt_in_out#
The _mp_out_in_out# localStorage item is essential for remembering your choice of cookie consent, specifically for Mixpanel.
Persistent
N/A
Mixpanel
localeData
We use the localeData cookie to store your language preference and provide you with customised regional content. This helps us to show content translated into your preferred language, a key part of making our service accessible to an international audience.
Persistent
1 year
countryOfResidence
We use the countryOfResidence cookie to ensure that you’re only shown products which are available in your country.
Session
N/A
No third parties involved
signupToken
We use this cookie to allow customers to complete a signup if it’s interrupted.
Session
N/A
No third parties involved
tw-ref
We use tw-ref cookies as part of the referral program to help identify a host / guest. These let us link hosts to guests that sign up, and help us to apply a discount for first-time invited customers.
Persistent
1 month
No third parties involved
tw-ref-invite-source-code
We use tw-ref cookies as part of the referral program to help identify a host / guest. These let us link hosts to guests that sign up, and help us to apply a discount for first-time invited customers.
Persistent
1 month
No third parties involved
tw-ref-user-id
We use tw-ref cookies as part of the referral program to help identify a host / guest. These let us link hosts to guests that sign up and help us to apply a discount for first-time invited customers.
Persistent
1 month
No third parties involved
tw-ref-user
tWe use tw-ref cookies as part of the referral program to help identify a host / guest. These let us link hosts to guests that sign up and help us to apply a discount for first-time invited customers.
Persistent
1 month
No third parties involved
tw-ref-user-name
We use tw-ref cookies as part of the referral program to help identify a host / guest. These let us link hosts to guests that sign up and help us to apply a discount for first-time invited customers.
Persistent
1 month
No third parties involved
tw-coupon
This helps us to apply a discount for eligible customers.
Persistent
1 month
No third parties involved
accountDetailsReferralCode
This cookie allows us to modify the account details onboarding experience for users referred from known affiliates.
Session
N/A
No third parties involved
rate-alerts-token
We need the sessionStorage value to keep the user logged in to the Rate Alerts service, and to manage their saved rate alerts.
Session
N/A
No third parties involved
deviceTokenTW
This is a required token to keep your account safe.
Persistent
1 year
No third parties involved
appToken
We use the appToken cookie to identify which client is using our services and products.
Persistent
24 hours
No third parties involved
rememberedDevice
We use this cookie to record that a user has successfully logged in with SMS or app-based second factor authentication on the device previously, and we will only require first factor authentication (e.g. password) in order to login again on that same device for the next 90 days.
Persistent
90 days
No third parties involved
rememberThisDevice
We use this cookie to retain the user’s previous decision for the ‘Remember this device’ checkbox each time they login.
Persistent
1 year
No third parties involved
tell-me-more-banner
The purpose of this cookie is to let us remember your choice to not see banners on our website.
Persistent
90 days
No third parties involved
beta-banner
The purpose of this cookie is to let us remember your choice to not see banners on our website.
Persistent
90 days
No third parties involved
currency-converter-app-banner
The purpose of this cookie is to let us remember your choice to not see banners on our website.
Persistent
90 days
No third parties involved
switch-salary-banner
The purpose of this localStorage item is to remember your choice to not see banners on our website.
Persistent
N/A
No third parties involved
has-agreed-owners-disclaimer
The purpose of this cookie is to help us remember that you have accepted the disclaimers in our Terms and Conditions.
Persistent
40 days
No third parties involved
interstitialDismissed
The purpose of this cookie is to help us decide if we should show you an interstitial modal on our home page.
Persistent
90 days
No third parties involved
get-paid-voting
The purpose of this localStorage item is to remember your choice to not see banners on our website.
Persistent
N/A
No third parties involved
ASP.NET_SessionId
ASP Dot Net uses this cookie to record the users current session between page requests.
Session
1 Session
ASP Dot Net, Investis Digital
https://www.investisdigital.com/privacy-policy
mymca-banner
The purpose of this cookie is to let us remember your choice to not see banners on our website.
Session
90 days
No third parties involved
COOKIES THAT GIVE YOU A BETTER BROWSING EXPERIENCE
usr
This cookie stores a value that identifies you after logging in. It lets us deliver relevant content to you on our homepage.
Persistent
1 year
No third parties involved
hasClickedOnSignUpOrLogin
This lets us customise your experience so that it is easier for you to log in, such as replacing the register button with a login button.
Persistent
90 days
No third parties involved
est.cookie
We use the test.cookie to check if the user’s browser supports cookies.
Persistent
1 day
Doubleclick.net
https://policies.google.com/technologies/ads?hl=en-US
rate-alerts-route
This localStorage value saves your most recent choice of currency to currency route on the rate alerts page.
Persistent
N/A
No third parties involved
profileType
This cookie is used to save the user profile type at Register page as a cookie to reuse it at on-boarding flows.
Session
1 Session
No third parties involved
COOKIES THAT HELP US IMPROVE OUR PRODUCTS AND SERVICES
Analytics
This cookie lets us see how you interact with our products in the backend. It contains information on your profile and whether or not you’ve registered in the past.
Session
1 session
No third parties involved
Google Analytics
The _gat and gat# cookies are installed by Google Universal Analytics to throttle the request rate to limit the collection of data on high traffic sites.
Session
1 minute
Google
https://support.google.com/analytics/answer/6004245
We use the _gid cookie to store information on how visitors use a website and helps in creating analytics report of how the website is doing. The data includes the number of visitors, where they came from, and the pages visited in an anonymous form.
Persistent
1 day
We use _ga cookie to calculate visitor, session, campaign data and keep track of site usage for the site’s analytics report. It stores information anonymously and assigns a randomly generated number to identify unique visitors.
Persistent
2 years
We use the _dc_gtm_UA# to limit the number of requests that we make to Google Analytics.
Session
We use the collect cookie to see which devices and marketing channels you’re using. We send this information to Google Analytics to learn about your device and behaviour.
Session
HotJar
We use the _hjid cookie to see your behaviour for our own statistical and monitoring purposes.
Persistent
1 year
HotJar
https://www.hotjar.com/legal/policies/privacy
This cookie lets us 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 you’ve scrolled down a page and where you may 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 helps us identify subconscious thought patterns users have, which helps us pin-point where customers might struggle in our product.
We set the _hjClosedSurveyInvites cookie once a visitor interacts with a survey invitation modal popup. We use it to ensure that the same invite does not reappear if it has already been shown.
We set the _hjDonePolls cookie once a visitor completes a poll using the Feedback Poll widget. We use it to ensure that the same poll does not reappear if it has already been filled in.
We set the _hjMinimizedPolls cookie once a visitor minimises a Feedback Poll widget. We use it to ensure that the widget stays minimised when the visitor navigates through our site.
We set the _hjDoneTestersWidgets cookie once a visitor submits their information in the Recruit User Testers widget. We use it to ensure that the same form does not reappear if it has already been filled in.
We set the _hjIncludedInSample cookie to let Hotjar know whether that visitor is included in the sample, which lets us generate funnels.
We set the _hjShownFeedbackMessage cookie when a visitor minimizes or completes Incoming Feedback. We do this so that the form will be minimised immediately if they navigate to another page where it is set to show.
The _hjRecordingLastActivity cookie should be found in sessionStorage (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).
We use the hjTLDTest cookie when the Hotjar script executes and we try to determine the most generic cookie path we should use, instead of the page hostname. We do this 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.
We use the _hjUserAttributesHash cookie as user attributes are 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.
We set the _hjIncludedInPageviewSample cookie to determine if a user is included in the data sampling defined by your site’s pageview limit.
The _hjCachedUserAttributes 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.
iz_sd_ss and iz_uh_ps
We use the iz_sd_ss cookie 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 FusPay 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.
Session -1 year
Informizely
https://www.informizely.com/data-protection
We use the iz_uh_ps cookie 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.
Persistent – N/A
Mixpanel
The mp_#_mixpanel cookie is an analytical cookie that helps us understand how you move 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 dropoffs 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 FusPay 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/
userSecurityData
The purpose of the userSecurityData cookie is to keep track of how many times we have shown a user the option to enable security features after they log in.
Persistent – N/A
No third parties involved
gid
This cookie is used to count unique visitors arriving on our website and measure usage of our products.
Persistent
1 year
No third parties involved
If you don’t want this cookie to persist and do not wish to be recognised as a return visitor, you can delete this cookie within your browser settings.
_dc_gtm_UA-#
This cookie is used to control how a Google Analytics script tag loads. This is a HTTP cookie whose data is deleted after a session.
Persistent -1 minute
Google Tag Manager
https://policies.google.com/privacy
_cltk
Registers statistical data on users’ behaviour on the website. Used for internal analytics by the website operator.
Session -1 minute
Clarity
_pk_id#
This cookie is used to enable collection of statistics on user visit to the website anonymously. Information collected include pages read, average time spent and the number of visits.
Session – 1 year
Piwik Analytics Platform
https://piwik.pro/privacy-policy/
_pk_ses#
This cookie is used to track the pages requested by the visitor in a session for use by Piwik Analytics Platform.
Session -30 minutes
Piwik Analytics Platform
https://piwik.pro/privacy-policy/
X-AB
This cookie is used by the website’s operator in context with multi-variate testing. This is a tool used to combine or change content on the website. This allows the website to find the best variation/edition of the site.
Session -1 day
Snap
COOKIES THAT KEEP OUR MARKETING COSTS DOWN
Facebook
The fr, _fbp, _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 our website, the cookie will share with Facebook encrypted emails used to register with FusPay 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 FusPay. 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 FusPay 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 up to FusPay when they have already done so.
Persistent -3 months
Facebook
https://en-gb.facebook.com/policy.php
g_airpr_recent_visist
We use the g_airpr_recent_visit cookie 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
Google Ads
We use the _gcl_au cookie 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.
Persistent
90 days
Google
The ads/ga-audiences cookie is used by Google Adwordsinorder to re-engage visitors based on their online behaviour across various websites.
Session
We use the NID cookie to assign a unique ID number to a returning user’s device. This unique ID number is used for targeting advertisements to the user.
Persistent
MUID and MUIDB
The MUID and MUIDB (bat.bing.com) cookies let us track users by synchronising the Microsoft User Identifier (MUID) across many domains and counting 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
Twitter
We use the personalization_id cookie to store data about visitors and users and measure advertising effectiveness, show relevant advertising and exclude irrelevant advertising.
Persistent, session
30 days
Twitter
Twitter Cookie Policy
Yahoo
The B cookie lets us 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.
Persistent
2 years
Yahoo
https://policies.yahoo.com/xa/en/yahoo/privacy/index.htm
The XB andpagead/conversion/1001035224 cookie is used by Yahoo to enable it to track Yahoo conversions.
Persistent/Session
6 days
How to block cookies
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 our sites, products and services. Your browser settings also allow you to delete all cookies stored on your device whenever you wish.
How to control cookies
Where you are from the United Kingdom, the UK Information Commissioner’s Office has provided the following guidance on controlling cookies:
A number of websites provide detailed information on cookies, including AboutCookies.org and AllAboutCookies.org.
The European Interactive Digital Advertising Alliance website Your Online Choices allows you to install opt-out cookies across different advertising networks. Google has developed a browser add-on to allow users to opt-out of Google Analytics across all websites which use it. This is also available in the Chrome web store.
Some browsers include a feature known as ‘Do Not Track’ or DNT. This allows you to indicate a preference that websites should not track you. However, whilst DNT is available in many browsers, websites are not required to recognise its request, so it may not always work. You can get help on how to use DNT in Microsoft Edge, Microsoft Internet Explorer, Mozilla Firefox, Google Chrome and Opera.
For more information on how private browsing works as well as its limitations, visit the support pages for your browser: Microsoft Edge, Microsoft Internet Explorer, Mozilla Firefox, Google Chrome, Safari (IOS mobile and desktop) and Opera.
If you are concerned about online tracking, then we can recommend you:
Install a privacy-friendly browser on your device, such as Mozilla Firefox, Firefox Focus or Brave; Install anti-tracking and ad-blocking plug-ins on that browser, such as uBlock, Ghostery or PrivacyBadger; and
Use privacy-friendly web search engines, such as DuckDuckGo or Qwant.
If you have any questions about the cookies or similar technologies in use on our site, products or services, please send an email to [email protected]
