Introduction
This Cookie Policy (hereinafter referred to as "Policy") outlines the use of cookies and similar tracking technologies on the cryptocurrency trading platform (hereinafter referred to as "Platform") operated by Rampnow sp. z o.o., a company duly registered in the Polish company register (KRS) under number 0001025453, with its registered office at ul. Uniwersytecka 13, Katowice, 40-007, Poland (hereinafter referred to as "Rampnow", "we", "us" or "our").
It is designed to comply with the General Data Protection Regulation (GDPR), formally known as Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC.
This Policy provides transparency regarding the types of cookies used, their purposes and options for managing preferences. The use of cookies is integral to ensuring the functionality, security and usability of the Platform while complying with applicable privacy regulations.
It is designed to comply with the General Data Protection Regulation (GDPR), formally known as Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC.
This Policy provides transparency regarding the types of cookies used, their purposes and options for managing preferences. The use of cookies is integral to ensuring the functionality, security and usability of the Platform while complying with applicable privacy regulations.
What are Cookies?
Cookies are small text files stored on a computer or other internet-connected device by a web browser when a website is visited. They enable the collection and storage of information about browsing activity and preferences. Cookies serve a variety of purposes, such as remembering login credentials, language settings, or the time and date of visits, and tracking key visitor metrics to enhance functionality and user experience.
Cookies are inherently secure and cannot run programs or transmit harmful software, such as viruses, to a device. They function as a passive tool to support seamless navigation and improve website performance.
In addition to cookies, other technologies like local storage and session storage may be used. These technologies offer similar capabilities but store data differently to meet specific objectives, such as ensuring security, optimizing performance, or personalizing content.
Cookies are inherently secure and cannot run programs or transmit harmful software, such as viruses, to a device. They function as a passive tool to support seamless navigation and improve website performance.
In addition to cookies, other technologies like local storage and session storage may be used. These technologies offer similar capabilities but store data differently to meet specific objectives, such as ensuring security, optimizing performance, or personalizing content.
Purpose of using Cookies
Cookies are utilized on the Platform to enhance functionality, analyze visitor behavior and ensure a seamless user experience. These technologies serve several specific purposes, which include:
- Statistical analysis:
Cookies help collect and analyze aggregated data about website traffic and usage patterns, providing insights into how visitors interact with the Platform. - Identifying individual visitors:
Cookies assign a unique identifier to each visitor, enabling the Platform to distinguish between users and analyze their interactions effectively. - Tracking visitor behavior:
Cookies monitor user actions, such as navigation patterns and interactions with different website elements. This helps in understanding preferences and optimizing content. - Experiment management:
Cookies determine if a visitor is part of an active experiment, track engagement with specific variations and ensure consistent delivery of variations across visits. - Goal tracking:
Cookies measure completed actions, such as conversions or specific milestones, to evaluate the effectiveness of Platform features and experiments. - Improving efficiency:
By storing relevant information, cookies help accelerate future interactions, making the website faster and more intuitive for returning visitors. - Data storage for enhanced functionality:
Cookies and related technologies, such as local storage, store different sets of data to support functionalities without affecting website loading times or performance.
Categories of Cookies used
The following cookies and storage mechanisms are used to monitor and analyze website visitor activity:
First-party cookies are set directly by the domain being visited. These cookies store data in the web browser associated with the specific domain and are used to support functionalities, track user activity, and analyze interactions within that same domain.
Below is a list of the first-party cookies used on the Platform, along with their purposes and details.
2. Third-Party Cookies
Third-party cookies identify recurring visitors in a web browser across multiple domains. These cookies store data under external domains associated with services integrated into the Platform.
Below is a list of third-party cookies used, including their purposes and details.
3. Local Storage
These store visitor data locally within the visitor's browser.
4. Session Storage
These store visitor data for a session as long as a web browser is open or the web page is refreshed.
- First-Party Cookies
- Third-Party Cookies
- Local Storage
- Session Storage
First-party cookies are set directly by the domain being visited. These cookies store data in the web browser associated with the specific domain and are used to support functionalities, track user activity, and analyze interactions within that same domain.
Below is a list of the first-party cookies used on the Platform, along with their purposes and details.
Cookie Name | Information Stored | Generation State | Expiry Period | Purpose |
|---|---|---|---|---|
| zab_g_{exp_key}(stores a random alphanumeric string of length 7 or 32) | This cookie stores details such as the experiment key, variation key, and additional user data (such as browser used, user agent info, etc.) for your a/b test. | Sets when the a/b test is configured with a custom or pageview goal into it. | Expires once the session is over (when the website tab is closed). | Used to track successful custom/pageview goal conversions obtained in the same domain. |
| zabUserID | This cookie stores a unique user key for every visitor reaching the website. | Sets when a user visits for the first time. | 1 year | Used for identifying individual visitors along with the status of new and returning visitors. |
| zabVisitID | This cookie stores a unique visit key every time a user returns to the web page. | Sets every time a user visits. | 1 year | Used for identifying every visit made by the user on the web page. |
| zabSplit | This cookie stores details like experiment key, variation key, and additional user data (such as browser used, user agent info, etc.) for your Split URL experiments. | Sets when the experiment URL and variation URL are from the same domain. And, when a particular variation is selected for the split URL experiment. | 5 secs | Used for sending the experiment and visitor information to the server upon redirection. |
| zabBucket | This cookie stores details like experiment key and its corresponding variation key for you a/b or split URL experiments. | Sets when the user's URL matches with the experiment URL. And if the target audience is satisfied. | 1 year | Used to consistently serve visitors the same variation of the test they've seen before. |
| zabHMBucket | This cookie stores the experiment key for your heatmap experiments. | Sets when the user's URL matches with the experiment URL. | 1 year | Used for identifying the exact heatmap experiment to be tracked on the web page. |
| zpsfa_{exp_key}(stores a random alphanumeric string of length 7 or 32) | This cookie stores a visit key for the first-time visitor landing in a funnel analysis experiment. | Sets when the user's URL matches with the experiment URL or when the custom event of a funnel step is triggered. | 1 month | Used for deriving the path taken by the visitor and the number of visitors that dropped off while traversing through the funnel. |
| zfa{exp_key}(stores a random alphanumeric string of length 7 or 32) | This cookie stores details like experiment key and user data (such as browser used, user agent info, etc.) for your form analytics experiments. | Sets when the experiment URL and conversion URL are from the same domain. | 1 hour | Used for tracking actual user conversions. |
| zsr {expkey}(stores a random alphanumeric string of length 7 or 32) | This cookie stores a session key for your session recording experiments. | Sets when a user's URL matches with the experiment URL. | 2 hours | Used for mapping all the user actions performed within a session. |
| zabme | This cookie stores the experiment key of your a/b or split URL experiment chosen from a mutually exclusive group. | Sets once a mutually exclusive group is created. | 1 year | Used for serving the same experiment within a mutually exclusive group, the user has seen before. |
| zsd{sessionId} (stores a random alphanumeric string of length 32) | This cookie stores the session's metadata for your session recording experiments. | Sets once after the user start interacting on a web page's session. | 2 hours | Used for identifying the start time, last interacted time, and number of pages visited for a session. |
| ps_payloadSeqId: | This cookie stores the sequence key for your session recording experiments. | Sets once the user starts interacting on a web page's session. | 2 hours | Used to keep track of duplicate payloads (session data). |
| zabPZBucket | This cookie stores the experience key for your personalization experiments. | Sets when the experience is selected in a personalization experiment and is of type redirection | 1 year | Used to consistently serve visitors the same experience they have seen before. |
| zPersonalization | This cookie stores details like the experiment key, experience key, and user data (such as browser used, user agent info, etc.) for your personalization experiments. | Sets when the experiment URL and experience URL are from the same domain and is of type redirection. | 1 year | Used for sending the experiment and visitor information to the server upon redirection. |
| zia_ {projectkey} | This cookie stores the identity API details of individual visitors on your website. | Sets once the website owner provides the user's information. | 1 year | Used to avoid sending the same visitor data multiple times to the server. |
| zpc< projectkey> | This cookie stores the visitors' response to the website's privacy policy. | Sets when the visitor makes a choice of privacy consent. | 1 year | Used to ensure that the banner does not reappear to the same visitor on your website. |
| zps_permission_status | This cookie stores the granted and denied permission value of the visitor for your web push notification experiments. | Sets when the user lands on the website with push notification enabled in it. | 1 year | Used to identify and update the push notification status of the subscriber on your website. |
| {exp_id}+"popup"(stores a random alphanumeric string of length 7 or 32) | This cookie stores details like the number of times a popup is displayed, the time when the cookie was created, and the popup completion status by individual visitors on your website. | Sets when the user's URL matches with the URL type configured in your popup experiment. | 1 year | Used to track user impressions and whether they respond to a popup. |
| zps-tgr-dts | This cookie stores the session's metadata on your website | Sets when a user visits your site for the first time. | 1 year | Used for activating your experiment based on a given trigger condition. |
| zpspolls_" +{exp_id} | This cookie stores details like the number of times a poll was shown, whether the poll was completed, and the time it was created for your polls experiment. | Sets when the user's URL matches with the poll URL. | 1 year | Used for tracking user actions such as impressions, answered/unanswered polls, and other poll parameters. |
| zpsPollsBucket | This cookie stores the experiment key for your polls experiments. | Sets when the user's URL matches with the poll URL. | 1 year | Used for identifying the polls experiment to be served on the web page. |
| "zpspb" + {exp_id} | This cookie stores details like the number of times a popup was displayed, the time when the cookie was created, and the popup completion status by individual visitors on your website. | Sets when the user's URL matches with the popup URL. | 1 year | Used for tracking user actions like impressions and answered/unanswered popups. |
| zpsPopupBucket | This cookie stores the experiment key for your popup experiment. | Sets when the user's URL matches with the popup URL. | 1 year | Used for identifying the popup experiment to be served on the web page. |
| "zpssr" + {current time in milliseconds} | This cookie stores the same cookie name and cookie value for your session recording experiment. | Sets when the session recording experiment is running on the website. | Gets deleted immediately after identification of the top level domain. | Used to identify the top level domain in your session recording experiment. |
2. Third-Party Cookies
Third-party cookies identify recurring visitors in a web browser across multiple domains. These cookies store data under external domains associated with services integrated into the Platform.
Below is a list of third-party cookies used, including their purposes and details.
Cookie Name | Information Stored | Generation State | Expiry Period | Purpose |
|---|---|---|---|---|
| zab_g_{exp_key} (stores a random alphanumeric string of length 7 or 32) | This cookie stores details such as the experiment key, variation key, and additional user data (such as browser used, user agent info, etc.) for your a/b tests. | Sets when the a/b test is configured with a custom or pageview goal into it. | 1 year | Used to track successful custom/pageview goal conversions obtained across different domains. |
| {variation_url} | This cookie stores experiment details like experiment key, variation key, and additional user data (such as browser used, user agent info, etc.) for your Split URL tests. | Sets when the variations are from different domains. And, when a particular variation is selected in the split URL experiment. | 1 year | Used for identifying the exact split experiment and its corresponding variation URL for returning visitor. |
| zab_ {expkey} | This cookie stores details like the experiment key and user data (such as browser used, user agent info, etc.) for your form analytics experiments. | Sets when the experiment URL and confirmation URL are from different domains. And, if the user submits the form. | 1 hour | Used for tracking actual form conversions. |
| {zps_push} | This cookie stores text content like bannerpopup, sidepopup, and nopopup when push notifications are enabled in PageSense's project. | Sets when the user lands on the website with the push notification. | Used for deciding whether to show or hide the notification box and maintain its position on a website. | |
| zPersonalization | This cookie stores details like the experiment key, experience key, and user data (such as browser used, user agent info, etc.) for your personalization experiment. | Sets when the experience URL and experience URL are from different domains. And, if the audience parameter matches with the respective personalization experience. | 1 year | Used for identifying and redirecting users to consistently show the same experience. |
| {expId} (stores a random alphanumeric string of length 7 or 32) | This cookie stores experiment key and additional user data (such as browser used, user agent info, etc.) on a local storage system for your session recording experiments. | Sets once the user starts interacting on a web page. | No expiry | Used for identifying and keeping track of a visitor's data during a session. |
3. Local Storage
These store visitor data locally within the visitor's browser.
4. Session Storage
These store visitor data for a session as long as a web browser is open or the web page is refreshed.
Cookie Name | Information Stored | Generation State | Expiry Period | Purpose |
|---|---|---|---|---|
| tabUid | This cookie stores the tab ID for your session recording experiments. | Sets when a user visits for the first time. | Cleared once after the browser tab is closed. | Used for mapping all the user actions performed within the respective tabs for a session. |
Cookie management
Cookies used on the Platform comply with the requirements of the General Data Protection Regulation (GDPR), ensuring that non-essential cookies are only deployed after obtaining explicit user consent. Upon accessing the Platform, a cookie banner is displayed, offering the following options:
Opt-Out options: For experiments involving session recordings, Rampnow provides an option to "opt-in" or "opt-out" of cookie-based tracking. This ensures that users are informed and can choose whether to allow session recording cookies that track and collect specific data about their interactions on the Platform.
- Accept all cookies: Enables all cookies, including essential, functional, and non-essential cookies,
- Decline non-essential cookies: Allows only essential cookies necessary for the Platform's basic functionality,
- Customize preferences: Provides an option to select specific cookie categories based on individual preferences.
Opt-Out options: For experiments involving session recordings, Rampnow provides an option to "opt-in" or "opt-out" of cookie-based tracking. This ensures that users are informed and can choose whether to allow session recording cookies that track and collect specific data about their interactions on the Platform.
- Applicable limitations: The opt-out option is available exclusively for session recording experiments. For other functionalities or tests, cookies are automatically set to collect the necessary user information without an opt-out choice.
- Recommended practice: Providing transparency and choice for session recording is strongly recommended as a best practice to ensure compliance and maintain user trust.
Policy updates
This Cookie Policy is subject to periodic updates to reflect changes in legal requirements, industry best practices, technological advancements, or modifications to the operation of the Platform. Updates may also be necessary to align with new services, features or adjustments to cookie usage practices on the Platform. Users are encouraged to review the policy regularly to stay informed about any updates or modifications.
Contact information
For any inquiries, concerns, or complaints regarding this Cookie Policy, Rampnow encourages open communication to address and resolve issues effectively. Users may reach out through the following contact channels:
Email: [email protected]
Address: ul. Uniwersytecka 13, 40-007 Katowice
Email: [email protected]
Address: ul. Uniwersytecka 13, 40-007 Katowice