Last updated · 2026-11-04
Cookie Policy
Region: EU · Version: 2.1 · Effective date: 4 November 2026
This Cookie Policy, together with our Privacy Notice, describes how we use cookies and similar technologies when you visit our website, available at rumos.eu (formerly www.cryptounity.org and cryptounity.eu) (the "Site"), use the Rumos mobile application (the "Mobile App"), or interact with our services, content or communications (collectively, the "Services").
This Cookie Policy explains what these technologies are, how and why we use them, and the choices available to you regarding their use.
For the purposes of this Cookie Policy, "we", "us" or "our" refer to CU EUROPE, digitalne storitve, d.o.o., a company incorporated under the laws of the Republic of Slovenia, with its registered seat in Slovenia (full postal address: see our Impressum at https://rumos.eu/legal/impressum), registration number 7591802000, which operates the Site and the Mobile App under the Rumos brand (until 4 November 2026: "CryptoUnity"). Until 22 October 2026, the Site and the Mobile App were operated by CU, trgovanje z virtualnimi valutami, d.o.o., Ljubljana.
We act as the controller for the use of cookies and similar technologies on the Services, except where third-party providers act as independent controllers, as indicated below.
We use cookies and similar technologies, including local storage, session storage and software development kits ("SDKs"), to operate, improve and secure our Services. These technologies allow us to remember your preferences, keep the Services working, analyse usage and, where you consent, measure the effectiveness of our communications.
Where these technologies collect information that qualifies as personal data, that processing is governed by our Privacy Notice.
If you have questions regarding this Cookie Policy or our use of cookies, you may contact us at info@rumos.eu.
1. General
Cookies are small text files that are placed on your device when you visit a website. They allow us and our service providers to recognise your browser or device and to store certain information for the purposes described in this Policy.
Local storage and session storage are browser technologies that store data on your device. Data in local storage remains until you delete it; data in session storage is deleted when you close the browser tab.
SDKs are code components integrated into our Mobile App that provide functions such as notifications, crash reporting, identity verification and usage analysis, and that may collect information about the device and network used to access the Services.
These technologies may be set by us (first-party) or by third-party service providers.
We do not use advertising cookies or pixels on the Site.
2. Categories of Cookies and Other Tracking Technologies
We classify cookies and similar technologies into the following categories:
(i) Strictly necessary. These technologies are essential for the operation of the Services, including remembering your consent choices, account login, security and fraud prevention. Because they are required for the Services to function, they do not require your consent.
(ii) Functionality. These technologies remember choices you make (such as language, region or display theme) and are set when you make that choice. They are used only to provide the function you requested.
(iii) Analytics and performance. These technologies help us understand how users interact with the Services, for example pages visited, errors encountered and overall usage patterns, so that we can improve them.
(iv) Marketing and attribution. These technologies help us understand which campaigns or links brought a visitor to the Services and to the app stores.
In the European Union and the European Economic Area, we obtain your prior consent before placing or reading non-essential cookies or similar technologies on your device, including analytics and marketing technologies, except where this Policy states otherwise and the law permits it. Our cookie consent tool allows you to accept, reject or manage your preferences before such technologies are used.
3. Legal Basis for Processing (EU/EEA Users)
- Strictly necessary and functionality technologies: storing or accessing information on your device is permitted without consent because it is strictly necessary to provide the service you request. Any related processing of personal data is based on our legitimate interest in providing secure and functional Services.
- All other technologies (including analytics and marketing): based on your consent.
You may withdraw your consent at any time through the cookie settings on the Site or through your browser settings. Withdrawal does not affect the lawfulness of processing before withdrawal.
The use of cookies is subject to the EU ePrivacy Directive (2002/58/EC) as implemented in national law; in Slovenia, Article 225 of the Electronic Communications Act (Zakon o elektronskih komunikacijah, ZEKom-2; Uradni list RS, No. 130/22, as amended). Where the General Data Protection Regulation (GDPR) applies to data collected through these technologies, that processing is governed by our Privacy Notice.
4. List of Cookies and Similar Technologies
4.1 Site (rumos.eu)
| Name | Type | Provider | Purpose | Category | Duration |
|---|---|---|---|---|---|
cu-consent |
Cookie and local storage | CU EUROPE (first-party) | Stores your cookie consent choices | Strictly necessary | Cookie: 12 months; local storage: until deleted |
cu-lang |
Cookie | CU EUROPE (first-party) | Remembers the language you selected | Functionality | 12 months |
cu-theme |
Local storage | CU EUROPE (first-party) | Remembers your light or dark display setting | Functionality | Until deleted |
cu-region-choice |
Local storage | CU EUROPE (first-party) | Remembers your choice in the region (EU / US site) banner | Functionality | Until deleted |
cu-banner-dismissed-v1 |
Local storage | CU EUROPE (first-party) | Remembers that you closed an announcement banner | Functionality | Until deleted |
| Workshop progress keys | Local storage | CU EUROPE (first-party) | Saves your progress in interactive workshops | Functionality | Until deleted |
cu-logo-intro |
Session storage | CU EUROPE (first-party) | Shows the logo animation only once per visit | Functionality | Until the tab is closed |
cu-app-noredirect, cu-app-redirected |
Session storage | CU EUROPE (first-party) | Controls the automatic redirect from the download page to the app store | Functionality | Until the tab is closed |
cu_utm, cu_attr |
Session storage | CU EUROPE (first-party) | Stores campaign parameters (for example utm_source, gclid, fbclid) and the type of referring site, so that a download can be attributed to the campaign that brought you | Marketing and attribution (only after you accept analytics cookies) | Until the tab is closed |
_ga |
Cookie | Google Ireland Limited (third-party) | Google Analytics 4: distinguishes visitors to produce usage statistics; IP addresses are anonymised | Analytics (only with consent) | 2 years |
_ga_<container-id> |
Cookie | Google Ireland Limited (third-party) | Google Analytics 4: maintains the session state | Analytics (only with consent) | 2 years |
| Umami analytics | No cookies or device storage | Our web-hosting provider (servers in the EU), on our behalf | Cookieless measurement of page views, referring sites, browser, device type and country, without identifying you | Analytics (no consent needed: cookieless first-party measurement that stores nothing on and reads nothing from your device) | No storage on your device; statistics kept on the server for 14 months |
| Session recording and heatmaps | None: no cookies, local storage or session storage are used | Umami, self-hosted on our behalf by our web-hosting provider (servers in the EU) | Records how visitors interact with pages (for example clicks and scrolling) in pseudonymised form, to find usability problems; all form inputs are masked | Analytics (only after you accept analytics cookies) | Recordings are kept on the server for up to 30 days |
Google Analytics is loaded only after you accept analytics cookies, and never when the Site is opened inside the Mobile App. For information on how Google uses data, see https://policies.google.com/technologies/partner-sites.
4.2 Mobile App
| SDK | Provider | Purpose | Category |
|---|---|---|---|
| Identity-verification SDK (Sumsub) | Used in BitGo's onboarding flow; the data is collected by and for BitGo Europe GmbH. CU EUROPE no longer uses its own Sumsub account for new checks; that account only keeps earlier verification records (see the Privacy Notice) | Document, liveness or video identification during BitGo onboarding | Strictly necessary |
| Stripe SDK | Stripe, Inc., for CU Global, Inc. (USA), which sells the subscriptions | Card payments for subscriptions | Strictly necessary |
| Firebase Cloud Messaging | Google Ireland Limited | Delivers push notifications, including notices and statements routed from BitGo | Strictly necessary |
| Firebase Crashlytics | Google Ireland Limited | Crash reports to keep the Mobile App stable and secure | Strictly necessary (security and stability: crash and stability data only; not used for advertising; no user identifiers beyond what crash diagnosis needs) |
| Firebase Analytics (Google Analytics for Firebase) | Google Ireland Limited | Usage statistics for the Mobile App | Analytics (in app version 1.18 and later only if you opt in, see Section 5) |
| Google Play Install Referrer (Android only) | Google Ireland Limited (Google Play) | Read once after installation (a) to pick up a referral code if you installed the Mobile App through another user's referral link, so that the referral can be credited under the referral programme (Terms of Service, Section 11); and (b) for install attribution: the full referrer and the Google Play click and install times are sent once per installation to our own servers, so that we can see which campaign or link the installation came from. We store this ourselves and do not pass it to Meta or Google | (a) Functionality (referral programme); (b) Analytics: from app version 1.18 only if you allow usage analytics (see Section 5); versions before 1.18 send it without asking |
| Apple AdServices attribution token (iOS only) | Apple | Read once after installation for install attribution: the Mobile App sends the token to our servers, which exchange it with Apple for Apple Search Ads attribution data (which ad or campaign the installation came from). We store the result ourselves and do not pass it to Meta or Google | Analytics: from app version 1.18 only if you allow usage analytics (see Section 5); versions before 1.18 send it without asking |
5. Managing and Disabling Cookies
You can manage your choices at any time through the cookie settings on the Site. You can also manage or delete cookies and local storage through your browser settings:
- Firefox: https://support.mozilla.org/en-US/kb/enable-and-disable-cookies-website-preferences
- Chrome: https://support.google.com/chrome/answer/95647
- Microsoft Edge: https://support.microsoft.com/en-us/windows/delete-and-manage-cookies-168dab11-0753-043d-7c16-ede5947fc64d
- Safari: https://support.apple.com/guide/safari/manage-cookies-and-website-data-sfri11471/mac
In the Mobile App (version 1.18 and later), usage analytics (Firebase Analytics) and install attribution (Section 4.2) are off until you agree to them through a separate opt-in that is not pre-ticked (shown when you accept the Terms or after you log in); accepting the Terms does not switch them on. You can withdraw your agreement at any time in the app settings. Crash reports (Firebase Crashlytics) are strictly necessary for the security and stability of the Mobile App and are sent without opt-in; they contain only crash and stability data and are not used for advertising. You manage notifications in your device settings.
Earlier app versions: versions of the Mobile App before 1.18 do not have this opt-in. They send usage statistics (Firebase Analytics) to Google, as our processor, from the first launch, and install-attribution data (Section 4.2) once per installation to our own servers. We use this data only for the purposes described in our Privacy Notice (section 4.12), never for advertising. To stop it, update the Mobile App to version 1.18 or later as soon as it is available to you; you can also ask us at info@rumos.eu to delete the analytics data linked to your app installation or account.
Disabling strictly necessary or functionality technologies may affect the functionality of the Services.
6. Third-Party Technologies
Where we use third-party technologies (see Section 4), the third party may receive information about your use of the Services, such as pages visited, device information and interactions.
Google Ireland Limited acts as our processor for Google Analytics and Firebase, subject to Google's data processing terms; information may be transferred to Google LLC in the United States on the basis of the EU-U.S. Data Privacy Framework or standard contractual clauses; Google signals are switched off, Google Analytics 4 does not log or store IP addresses, and the data is kept for 14 months. Further information is available in our Privacy Notice.
Where required by applicable law, we obtain your consent before using non-essential third-party technologies.
7. Updates to This Cookie Policy
We may update this Cookie Policy to reflect changes in our practices, technologies or legal requirements. Where required by applicable law, we will notify you of material changes, for example by a notice on the Site or in the Mobile App, and ask for your consent again where needed.
The current version of this Cookie Policy is always available on the Site, together with its effective date.
8. Contact Information
If you have any questions about this Cookie Policy or our use of cookies and similar technologies, you may contact us at:
CU EUROPE, digitalne storitve, d.o.o., Slovenia (full postal address: see our Impressum at https://rumos.eu/legal/impressum) Email: info@rumos.eu
9. Your Cookie Choices
You can manage your cookie preferences at any time through our cookie consent tool or your browser settings.
Where you have given consent to non-essential technologies, you may withdraw it at any time with effect for the future.
For more information, please refer to our Privacy Notice.
Effective date: 4 November 2026 · Version: 2.1
