Cookies Policy
Our Cookies Policy
Information About Our Use Of Cookies
Our website and mobile apps uses cookies and other software frameworks to distinguish you from other users of our website or mobile apps. This helps us to provide you with a better experience when you browse our website or use our apps, and also allows us to improve our service.
A cookie is a small software file that we download to, and store on, your device (if you agree). Software frameworks are used in our mobile apps and are necessary to use the app – you cannot opt in or out of using these.
We use the following cookies:
- Strictly necessary cookies. These are cookies that are required for the operation of our website. They include, for example, cookies that enable you to log into secure areas of our website, use a shopping cart or make use of e-billing services.
- Analytical/performance cookies. They allow us to recognise and count the number of visitors and to see how visitors move around our website when they are using it. This helps us to improve the way our website works, for example, by ensuring that users are finding what they are looking for easily.
- Functionality cookies. These are used to recognise you when you return to our website. This enables us to personalise our content for you, greet you by name and remember your preferences (for example, your choice of language or region).
- Targeting cookies. These cookies record your visit to our website, the pages you have visited and the links you have followed. We will use this information to make our website and the advertising displayed on it more relevant to your interests. We may also share this information with third parties for this purpose. have visited and the links you have followed. We will use this information to make our website and the advertising displayed on it more relevant to your interests. We may also share this information with third parties for this purpose.
You can find more information about the individual cookies we use and the purposes for which we use them in the table below:
YOYOWALLET.COM |
---|
COOKIE | NAME | PURPOSE | INFORMATION |
---|---|---|---|
csrftoken | Cross-Site Request Forgery Token | Security token to validate web requests and prevent malicious activity. | |
sessionid (1 month) | Session Token | Recognise you when you return to our site to prevent additional user log in. | |
ntercom-id-d3897k93 (1 year) | Intercom | Recognise you when you return to our site to use live chat feature. | |
_ga (2 years) | Google Analytics | Estimate our audience size and usage pattern. | https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage |
_gid (24 hours) | Google Analytics | Estimate our audience size and usage pattern. | https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage |
_gat (1 minute) | Google Analytics | Throttle request rate for Google Analytics | https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage_hstc(2 years) |
_hstc (2 years) |
Hubspot | Estimate our audience size and usage pattern. | https://knowledge.hubspot.com/articles/kcs_article/reports/what-cookies-does-hubspot-set-in-a-visitor-s-browser |
_hssrc (session) |
Hubspot | Estimate our audience size and usage pattern. | https://knowledge.hubspot.com/articles/kcs_article/reports/what-cookies-does-hubspot- set-in-a-visitor-s-browser_hssc(30 mins) |
_hssc (30 mins) |
Hubspot | Estimate our audience size and usage pattern. | https://knowledge.hubspot.com/articles/kcs_article/reports/what-cookies-does-hubspot-set-in-a-visitor-s-browser |
hubspotutk (10 years) | Hubspot | Estimate our audience size and usage pattern. | https://knowledge.hubspot.com/articles/kcs_article/reports/what-cookies-does-hubspot-set-in-a-visitor-s-browser |
_hjIncludedInSample (1 year) |
Hotjar | Estimate our audience size and usage pattern. | https://www.hotjar.com/legal/policies/cookie-information |
__consent (1 year) |
Adroll | Recognise visits to certain pages for ad tracking. | |
__adroll (1 year) |
Adroll | Recognise visits to certain pages for ad tracking. | |
_SL_C_23361dd035530_SID(1 year) |
Smartlook | Estimate our audience size and usage pattern. | https://help.smartlook.com/en/articles/6064963-cookies-in-smartlook |
We use the following 3rd party software frameworks that may store data on the device in our iOS and Android apps:
YOYO APP |
---|
NAME & OS | PRIMARY PURPOSE | MORE INFORMATION | PRIVACY |
---|---|---|---|
Branch (iOS and Android) | This is essential for our mobile application to create deep links that work when downloading the application from the App Store first. Branch is used for features like Voucher Sharing, | Security token to validate web requests and prevent malicious activity. | |
DeviceDNA (iOS and Android) | This is essential for our mobile application to process payments using JudoPay. | https://github.com/Judopay/DeviceDNA-iOS | Identifies devices using the JudoPay Genome Service to protect against fraud. |
Mixpanel (iOS and Android) | This enables us to monitor our audience size and usage pattern. | https://github.com/mixpanel/mixpanel-swift | Likely to store session and profile data onto the mobile device, and sends user data to Yoyo for triggering messages and data analysis. |
Realm (iOS) | This is essential for our mobile application to persist data which enables offline access. | https://github.com/realm/realm-cocoa | Stores user and transaction data from us for offline use of the app. |
Crashlytics (iOS and Android) | This enables crash reporting, and allows us monitor to our audience size and usage patterns | https://fabric.io/kits/ios/crashlytics | Likely to store data onto the mobile device such as crash reports and session identifiers. |
Facebook (iOS and Android) | This enables us to allow users to register and login to the mobile application with their Facebook account. | https://developers.facebook.com/docs/ios/ | Likely to store user data onto the mobile device. |
Fabric (iOS) | This enables us monitor our audience size and usage patterns. | https://docs.fabric.io/apple/fabric/overview.html | Likely to store data onto the mobile device such as session identifiers and device profiles. |
Taplytics (iOS and Android) | This is essential for our mobile application to allow us to remotely enable/disable functionality for testing and stability. | https://taplytics.com/docs/ios-sdk/getting-started | Likely to store user profile and activity data onto the mobile device. |
Zendesk (iOS and Android) | This enables us to allow users to raise support tickets from the mobile application. | https://developer.zendesk.com/embeddables/docs/ios/welcome | Likely to store Yoyo user ID and region onto the mobile device. |
Google Play Services (Android) | Used for Google services e.g. Google Maps | https://developers.google.com/android/guides/overview | Likely to store data relating to user consents on the device |
Please note that third parties (including, for example, advertising networks and providers of external services like web traffic analysis services) may also use cookies, over which we have no control. These cookies are likely to be analytical/performance cookies or targeting cookies.
You can block cookies or change the way they work by changing the settings on your browser or changing the preferences on your mobile device. However, if you block all cookies (including essential cookies) you may not be able to access all or parts of our site.
You are unable to block the use of 3rd party software frameworks that are used in our apps, as they are essential to the use of the app.