Cookies
We use cookies to provide you with a better service and a better browsing experience, as well as to be able to show you advertising based on your browsing habits. We are responsible for the installation of the cookies we use and what we do with the data we obtain from them, whether they are our own or third-party cookies.
In the following table, you will find links to facilitate access to the points of this policy that are of interest to you. However, we recommend that you read it in its entirety:
- What are cookies and what other things are stored in the browser?
- Are they dangerous?
- What technical cookies do we use and for what?
- What preference cookies do we use and for what?
- What statistical cookies do we use and why?
- What marketing cookies do we use and what for?
- What other elements are stored in the browser and for what?
- How can I manage or disable cookies?
- Modifications to this Cookies Policy
1. What are cookies and what other things are stored in the browser?
Cookies are small text files that are stored in your browser when you visit our website. These files contain information about your browsing and interaction with our website, with the purpose of making your user experience more efficient and showing you advertising based on your browsing habits. Some cookies are essential for the proper functioning of our website, such as technical or user interface personalisation cookies, and others, such as analysis cookies or behavioural advertising (or marketing) cookies, require that we inform you and that you give us your consent before we can use them.
LocalStorage and SessionStorage are two of several different data storage spaces that can be located in your device's browser and, like cookies, can be first-party (when created by our own website) or third-party (when created by our service providers or our partners). The difference between the two spaces is that LocalStorage stores information indefinitely or until you decide to clear the browser data, while SessionStorage stores information for as long as the tab where our website is being used remains open and, once closed, the information is deleted. The difference with cookies is that these two spaces allow storing more information than cookies without impacting the performance of our website.
You can get more information here.
Finally, we inform you that although the purpose of the third-party cookies we use, for which we are responsible, is indicated in the tables in the following sections, these third parties may dedicate the data collected by their cookies to other purposes which they are solely responsible for. In the case of third-party cookies, our responsibility for the purposes of the third parties is limited to the download of the cookies into your device (what we do for the stated purpose). You can find out more information about the purposes of these third parties, and whether or not they make transfers to third countries in their corresponding privacy policies (see the links in the tables below).
2. Are they dangerous?
In general, the level of risk posed by cookies depends on the type of cookies and whether they are first-party or third-party. Most cookies are not dangerous. Specifically:
Technical and preference cookies have more benefits than risks
The article 29 working party (former WP29 and current European Data Protection Board) in its Opinion 4/2012, "on the exemption from the consent requirement of cookies", considers that they do not pose a risk for you and exempt from the obligation to obtain consent prior to their use to all cookies that:
- are necessary for communications to be transmitted through a network between the user and the servers that host the website, and to all those that
- are necessary to provide a specific functionality explicitly requested by the user.
This exemption from the obligation to base the legality of its use on your consent, so as not to represent a risk for you, is also reflected in the cookie guides published by most of the Data Protection Agencies of the EU countries (for example, in the case of Spanish, it is included in section 4.1 of the guide on the use of cookies, of July 2020).
WP29 even defined the purposes that it explicitly considers to have more benefits than risks for you.
Purposes of cookies explicitly excluded from informed consent
With regard to its purpose, WP29 explicitly excludes the following cookies from the obligation to obtain the informed consent of the visitor:
- Cookies called "user input", which are usually used to track the user's actions when he fills in the online forms of an http(s) session, or to remember the shopping basket that he 'user has selected in an e-commerce,
- Session cookies that are used for user authentication or identification, which store a kind of token (witness that the user is who he claims to be and has already been authenticated) to prevent this user from having to give his/her username or password on each page he/she request and has restricted access control,
- User security cookies, introduced specifically to strengthen the security of the service explicitly requested by the user. For example, to detect erroneous and repeated attempts to connect to a website, or abuse,
- Media player session cookies,
- Session cookies to balance the load on information systems,
- User interface personalization cookies, such as to remember your preferred language, and
- Certain plug-in cookies to exchange social content.
In general, in those cases in which a website offers its visitors a service, when the website uses cookies exclusively for the purposes for which it is not necessary to obtain consent, listed above, whether they are first-party or third-party cookies, it will not be necessary for the website controller to inform the visitor of their use or to obtain his/her consent.
Statistical cookies ALSO do not pose an appreciable risk
Regarding the processing of data collected through analysis cookies, the aforementioned opinion of the current European Data Protection Board stated that, although controllers located in the UE, which are obligated subjects of 2002/58/CE Directive are not exempt from the duty to obtain consent for their use, it is unlikely they represent a risk to users' privacy as long as they are first-party cookies that process aggregated data with a strictly statistical purpose, that provide information on their uses and include the possibility for data subjects to express their negative about its use.
Switzerland is not subject to this directive, and allows legitimate interest to be used for the processing of statistical cookies, which is why they appear pre-marked in the cookie settings.
First-party cookies also usually do not pose an appreciable risk for you
First-party cookies are generated by our website, while third-party cookies are generated by services or providers independent of us, and they are these independent providers who define the purposes and means of the processing they carry out.
Our only responsibility regarding third-party cookies is the necessary collaboration of our website in the placement of these cookies on your device, placement to which we will normally be obliged as it is necessary to be able to use the services provided to us by said third-parties (for example, to check that you are not a robot of these that are so abundant on the Internet, and thus avoid that the requests or comments that could be sent to us through the forms on our website harm our attention over the authentic ones).
3. What technical cookies do we use and for what?
Technical cookies are those that allow the user to navigate through a website, platform or application as well as the use of the different options or services that exist therein, including the management and operation of the website and the enabling of its functions and services (for example, identifying your session, accessing parts of the web that have restricted access, remembering the elements that make up your purchase order, carrying out the purchase process of your order, managing your payment, etc.). The website, platform or app cannot function properly without these cookies, as they are considered necessary.
In our specific case, we use the following:
| Cookie | Supplier | Purpose | Duration |
|---|---|---|---|
| callbackUrl | Olyverse | It is used to return the user to a specific URL (from where you have decided to register or log in session). | Session |
| Secure-next-auth.session-token | Olyverse | Session cookie for connection with backend API. | 24 hours |
| Secure-next-auth.callback-url | Olyverse | It is used to return the user to the page where I was when logged in or add a URL to redirect it after the start of the session. | Session |
| Host-next-auth.csrf-token | Olyverse | Necessary to prevent attacks Cross-Site-Request-Forgery. | Session |
| referer_code | Olyverse | It is used to detect with what referer code a user is registered with coming from a link shared by a referer. | Session |
| referer_channel | Olyverse | It is used to detect from which referer channel is registered a user coming from a link shared by a referer. | Session |
| urlPostLoginOauth | Olyverse | It is used to return the user to a specific URL (from where you have decided to register or log in session with Oauth). | Session |
| urlPostLogin | Olyverse | It is used to return the user to a specific URL (from where you have decided to register or log in session). | Session |
| ethSecretBuyer | Olyverse | It is used in the minting process directly for the “Registered Buyers”. | 24 hours |
| ethSecret | Olyverse | It is used in the normal minting process to store the information back once the minting is performed. | 24 hours |
| orderPusherMintedOly | Olyverse | It is used in the minting process with OLY to subscribe to the event from pusher and refresh the page according to the minting process. | 24 hours |
| olySecret | Olyverse | It is used in the minting process with OLY to store the information back once the minting is performed. | 24 hours |
| stripeSecret | Olyverse | It is used in the minting process via stripe to store the information back in the minting process. | 24 hours |
| waitlist-coming-soon | Olyverse | It is used in the process of registration/login that comes from a Click on a waitlist. | Session |
4. What preference cookies do we use and for what?
Preference or personalization cookies allow our website to remember information that changes the way our pages behave or look in order to differentiate your experience from that of other users. As an example, it usually remembers the language in which you want to view our website. If you are the one who voluntarily chooses these features, for example, by marking the flag or letters that identify the language, it is considered a service expressly requested by you as long as the cookies obey exclusively for the purpose of personalization, so in this case it would not be necessary to ask you for an explicit consent.
Specifically, our website uses the following preference cookies:
| Cookie | Supplier | Purpose | Duration |
|---|---|---|---|
| localConsent | Olyverse |
It is generated when the user saves their cookie preferences which are stored in String format, and indicates whether you have accepted statistical cookies and or marketing cookies. |
365 days |
5. What statistical cookies do we use and why?
Statistical or analysis cookies are those that allow us to understand how visitors interact with the pages of our website and thus carry out a statistical analysis of the services we provide. The information collected is used to measure activity on our site in order to introduce improvements in the products and services we offer you.
We will use analysis cookies exclusively if you authorize us to do so, by pressing the corresponding button on the cookie banner or through the cookie’s configuration menu.
Specifically, our website uses the following analysis cookies:
| Cookie | Supplier | Purpose | Duration |
|---|---|---|---|
| ln_or | Used to determine if Oribi analytics can be carried out on a specific domain | 1 day | |
| _gid | Used to differentiate unique visitors | 1 day | |
| _ga_# | Used by Google Analytics to store and count page views | 2 years | |
| _ga | Used by Google Analytics to record a unique identity for the visitor | 2 years | |
| _clsk | Microsoft (Clarity) | Connects multiple page views by a user into a single Clarity session recording. | 1 day |
| _clck | Microsoft (Clarity) | Stores information about how visitors use the website and helps to create an analytics report on how the website is performing. | 1 year |
| _gat_gtag_UA_# | Used by Google Analytics to uniquely identify the visitor | 1 minute |
6. What marketing cookies do we use and what for?
Marketing or behavioural advertising cookies store information on user behavior obtained through continuous observation of your browsing habits, which allows developing a specific profile to show relevant and attractive ads to each individual user, and to thus, more value to third-party advertisers.
We will use marketing cookies exclusively if you authorize us to do so by pressing the corresponding button on the cookie banner or through the cookie’s configuration menu.
Specifically, our website uses those indicated in the table below:
| Cookie | Supplier | Purpose | Duration |
|---|---|---|---|
| _ttp | TikTok | To measure and improve the performance of advertising campaigns and to personalize the user's experience (including ads) on TikTok. | 13 months |
| _tt_enable_cookie | TikTok | Advertising | 13 months |
| _fbp | Advertising and Analytics | 90 days | |
| _gcl_au | Campaign Manager, Display & Video 360, Google Ads, Search Ads 360 | 90 days |
7. What other elements are stored in the browser and for what?
We reserve space in the user's browser using LocalStorage objects. The following table describes the variables that the owner of that space stores in your browser.
| Variable/label | Owner | Purpose | Duration |
|---|---|---|---|
| guest_id_marketing | Twitter.com | They are used for advertising on X (former Twitter) when session closes | 1 year |
| guest_id_ads | Twitter.com | 1 year | |
| guest_id | Twitter.com | It is used by X (former Twitter) for authentication | 1 year |
| loglevel:http-help-rs | Unknown |
Log levels are essentially labels that indicate the severity or urgency of the various events in our application. Their primary purpose is to separate messages that are merely informational (meaning that the system is working normally) from those that describe a problem or potential problem, such as when recurring errors are detected in the system. Log levels also provide a way to regulate the amount of log data generated by your application so that only the relevant and necessary information is recorded, minimizing the storage requirements and ensuring efficient log management |
Persistent |
| wc@2:core:0.3//key | walletconnect.com | Variables used by walletconnect.com (tool that we use so that users can use their wallet linked to walletconnect in their mobile application) | Persistent |
| WCM_VERSION | Persistent | ||
| WCM_WALLETCONNECT_CLIENT_ID | Persistent | ||
| loglevel:openlogin | web3auth.io | Variable used by web3auth.io (tool we use so that users with only their email could have a wallet on our website) | Persistent |
| loglevel:web3auth-logger | Persistent | ||
| openlogin_store | Persistent | ||
| nextauth.message | Olyverse | Variable used to display messages during the login process. | Persistent |
| wallet | Olyverse | Have the wallet address saved to be able to make queries to the API to show data to the user. | Persistent |
| loglevel:broadcast-channel | Olyverse | Variable used to communicate information through different windows, iframes, via a push notification channel. | Persistent |
8. How can I manage or disable cookies?
You can administer, manage and deactivate the cookies used by our website at any time from your browser, for example, to withdraw your consent, following the instructions provided by the manufacturer of your browser:
- Instructions for Microsoft Edge
- Instructions for Google Chrome
- Instructions for Google Android
- Instructions for Internet Explorer 11
- Instructions for Mozilla Firefox
- Instructions for Opera
- Instructions for Safari
If you disable the installation of cookies in your browser, you will be able to continue accessing our website with it, but your navigation may not be optimal and some of the services offered may not work properly.
9. Modifications to this Cookies Policy
We will update this Cookies Policy whenever necessary to reflect changes in our website.
If there are substantial changes to this policy, we will notify you before they come into effect by publishing a prominent notice in the cookie banner. In any case, we recommend that you periodically review this Cookie Policy to find out which ones we use and how we use them.
Last updated: August 29, 2024