Cookie Policy
1. WHAT IS A COOKIE?
Cookies are small pieces of text used to store information on web browsers. Cookies are used to store and receive identifiers and other information on computers, cell phones, and other devices. Other technologies, including data we store on your web browser or device, identifiers associated with your device, and other software, are used for similar purposes. In this document, we refer to all these technologies as “Cookies.” The term Cookies also include similar technologies for collecting and storing information, such as local shared objects (commonly referred to as "flash cookies"), web beacons or web bugs (including transparent or clear gifs). For further information about our cookie policy, please contact us at [email protected]
2. WHY DO WE USE COOKIES?
Cookies allow our servers to anonymously compile usage information (including IP address) to generate statistical information about the general operation and use of our websites. Cookies may also be used to recognize you as a returning website visitor or Priyo consumer, and allow us to provide information that may benefit you or best match your defined preferences. We also use Cookies to identify you as a valid user who has logged into our website, so that you will not be forced to re-enter your password multiple times while using our websites. In addition, we use Cookies if you have a Priyo account or use Priyo products.
3. COOKIES MANAGED BY DIFFERENT COMPANIES
First-party Cookies. These Cookies are sent to your computer or device from a computer or domain that is managed by Priyo.
Third-party Cookies. These Cookies are sent to your computer or device from a computer or domain that may or may not be managed by Priyo. In these cases, a third party will process the data obtained by the Cookies.
4. COOKIES WITH DIFFERENT DURATIONS
4.1 Persistent Cookies
These Cookies remain on your device for the period specified in the cookie, ranging from a few minutes to several years. They are activated each time you visit the website that created that particular cookie.
4.2 Session Cookies
These are Cookies designed to collect and store data when you access a website or an app. They are used to store data that is only relevant for providing the service on a one-off basis. Once you close the browser, all session Cookies are deleted.
5. WHAT TYPE OF COOKIES WE USE AND WHY?
The specific Cookies used on our site are generally categorised as follows:
- Required Cookies;
- Functional Cookies;
- Advertising Cookies;
- Performance Cookies.
6. SPECIFIC COOKIES WE USE ON money.priyo.com
6.1 Required Cookies
| Cookie Name | Cookie Type | Purpose | Session |
| Cloudflare | 3rd Party (Cloud Flare) | 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. 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. | 1 Year |
| localeData | No Third Party Involved | 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. | 1 Year |
| countryOfResidence | No Third Party Involved | We use the countryOfResidence cookie to ensure that you’re only shown products which are available in your country. | |
| deviceToken | No Third Party Involved | This is a required token to keep your account safe. | 1 Year |
| appToken | No Third Party Involved | We use the appToken cookie to identify which client is using Priyo services. | 3 Months |
| gid | No Third Party Involved | 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. | 1 Year |
| gid_tmp | No Third Party Involved | 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. | 1 Year |
| JSESSIONID | New Relic | The jsessionid cookie helps us to monitor the reliability of our service and manage login sessions by preserving user states across page requests. | |
| Oauth | The userToken, oauthToken cookies let us to authenticate each subsequent login request to our site by a customer. | ||
| rc::c | We use the rc::c cookie to help us distinguish between humans and bots. | ||
| Veriff | 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 EU laws and regulations. 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 EU laws and regulations. | |
| CookieConsent | This is essential for letting us remember your choice of cookie consent. | 6 months | |
| rememberMe | This is essential to store user's consent to remember their device to skip 2FA for their next login. | 1 Month | |
| CookieConsentGTM | This is essential for letting us remember your choice of cookie consent. | 6 Months |