1. Introduction
This Cookie Policy explains how we use cookies on draivn.com and Draivn Services. By accessing and utilizing our website and Services, you agree to the use of cookies as described in this policy. This Cookie Policy is an extension of our Privacy Policy, which provides further details on how we collect and use your information.
2. What are cookies?
When you access Draivn website and Services, the browser sends small pieces of text – cookies – to your laptop, smartphone, or other internet-enabled devices. Cookies help us remember information about your visit, recognize your device, and enhance your user experience as you access our website and Services in the future.
3. How we use cookies
We may use cookies to identify that you’ve logged in to the Services and learn how and when you interact with them. We may also use cookies to monitor aggregate usage and web traffic routing on our Services and to customize and improve them. We use the following types of cookies:
- Session cookies, namely “tabUid,” to remember information during your visit, e.g., for keeping you logged in. These temporary cookies will be deleted when you close your browser.
- Persistent cookies to store your preferences and settings. When you return to the site, it will remember you and ensure you continue working in the familiar setting.
You can be sure that we will only use cookies as described in this Cookie Policy. Below is a detailed list of the cookies set for draivn.com and our Services:
| Cookie name | Purpose |
|---|---|
| zab_g_{exp_key} (stores a random alphanumeric string of length 7 or 32) |
Used to track successful custom/pageview goal conversions obtained in the same domain. |
| zabUserID | Used for identifying individual visitors along with the status of new and returning visitors. |
| zabVisitID | Used for identifying every visit made by the user on the web page. |
| zabSplit | Used for sending the experiment and visitor information to the server upon redirection. |
| zabBucket | Used to consistently serve visitors the same variation of the test they've seen before. |
| zabHMBucket | 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) |
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) |
Used for tracking actual user conversions. |
| zsr {expkey} (stores a random alphanumeric string of length 7 or 32) |
Used for mapping all the user actions performed within a session. |
| zabme | 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) |
Used for identifying the start time, last interacted time, and number of pages visited for a session. |
| ps_payloadSeqId | Used to keep track of duplicate payloads (session data). |
| zabPZBucket | Used to consistently serve visitors the same experience they have seen before. |
| zPersonalization | Used for sending the experiment and visitor information to the server upon redirection. |
| zia_ {projectkey} | Used to avoid sending the same visitor data multiple times to the server. |
| zpc{projectkey} | Used to ensure that the banner does not reappear to the same visitor on your website. |
| zps_permission_status | 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) |
Used to track user impressions and whether they respond to a popup. |
| zps-tgr-dts | Used for identifying the polls experiment to be served on the web page. |
| "zpspb" + {exp_id} | Used for tracking user actions like impressions and answered/unanswered popups. |
| zpsPopupBucket | Used for identifying the popup experiment to be served on the web page. |
| "zpssr" + {current time in milliseconds} | Used to identify the top level domain in your session recording experiment. |
4. Third-party cookies
We may use third-party services like Google Analytics to help us understand how visitors interact with our website. These third-party services may set cookies on your device to collect information about your activities on our site and other websites. We do not control these cookies and recommend you review the privacy policies of these third-party services.
We also use cookies that identify recurring visitors on a web browser across different domains and store cookie data under the domain called "cdn.pagesense.io".
| Cookie name | Purpose |
|---|---|
| zab_g_{exp_key} (stores a random alphanumeric string of length 7 or 32) |
Used to track successful custom/pageview goal conversions obtained across different domains. |
| {variation_url} | Used for identifying the exact split experiment and its corresponding variation URL for returning visitor. |
| zab_ {expkey} | Used for tracking actual form conversions. |
| {zps_push} | Used for deciding whether to show or hide the notification box and maintain its position on a website. |
| zPersonalization | Used for identifying and redirecting users to consistently show the same experience. |
5. Other tracking technologies
We also use “Web Beacons” also known as clear gifs. These are tiny graphics with unique identifiers that may be included on our Services for several purposes, including to deliver or communicate with cookies, to track and measure the performance of our Services, to monitor how many visitors view our Services, and to monitor the effectiveness of our advertising. Unlike cookies, which are stored on the user’s hard drive, Web Beacons are typically embedded invisibly on web pages or in an email.
6. Your choices regarding cookies and opt-out options
You can manage or disable cookies by adjusting your browser settings. Most browsers allow you to refuse or delete cookies, but please note that disabling cookies may affect your ability to use certain features of our website and Services.
Browser manufacturers provide help pages relating to cookie management in their products. Please read the documentation that your browser manufacturer provides.
7. Changes to this Cookie Policy
We may revise this Cookie Policy periodically to reflect changes in our practices or to comply with operational, legal, or regulatory requirements. Consequently, we will amend the 'Last updated' date at the top and bottom of this policy and notify you as necessary.
We encourage you to review this page regularly to stay informed about any changes. Additionally, please note that our use of cookies comply with EU cookie laws and the General Data Protection Regulation (GDPR).
8. Applicable law
This Cookie Policy shall be governed in all respects by the substantive laws of USA. Any controversy, claim, or dispute arising out of or relating to the Cookie Policy shall be subject to the jurisdiction of the Superior Court New Castle County in accordance with its Rules of Arbitration as in force and effect on the date of the Cookie Policy.
Disputes shall be settled by a single arbitrator. Arbitration proceedings shall be held in Delaware, USA. The place of arbitration shall be Delaware, USA. The language of arbitration shall be English. Relevant documents in other languages shall be translated into English if the arbitrators are so direct.
All expenses and costs of the arbitrators and the arbitration in connection therewith will be shared equally, except that we and your entity will each bear the costs of its own prosecution and defense, including without limitation attorney’s fees and the production of witnesses and other evidence. Any award rendered in such arbitration shall be final and may be enforced by either party.
9. Contact us
If you have any questions or concerns about this Cookie Policy, please contact us at support@draivn.com.
10. Date of last update
This policy was last updated on August 13, 2024.