This Cookie Policy was last updated on May 31, 2023 and applies to citizens and legal permanent residents of the European Economic Area and Switzerland.
1. Introduction
Our website, https://www.greenstayn.nl (hereinafter: “the website”) uses cookies and other related technologies (for convenience all technologies are referred to as “cookies”). Cookies are also placed by third parties we have engaged. In the document below we inform you about the use of cookies on our website.
2. What are cookies?
A cookie is a small simple file that is sent along with pages of this website and stored by your browser on the hard drive of your computer or another device. The information stored therein may be returned to our servers or to the servers of the relevant third parties during a subsequent visit.
3. What are scripts?
A script is a piece of program code that is used to make our website function properly and interactively. This code is executed on our server or on your device.
4. What is a web beacon?
A web beacon (or a pixel tag) is a small, invisible piece of text or image on a website that is used to monitor traffic on a website. In order to do this, various data about you is stored using web beacons.
5. Cookies
5.1 Technical or functional cookies
Some cookies ensure that certain parts of the website work properly and that your user preferences remain known. By placing functional cookies, we make it easier for you to visit our website. This way, you do not need to repeatedly enter the same information when visiting our website and, for example, the items remain in your shopping cart until you have paid. We may place these cookies without your consent.
5.2 Statistics cookies
We use statistics cookies to optimize the website experience for our users. With these statistics cookies we get insights in the usage of our website. We ask your permission to place statistics cookies.
5.3 Marketing/Tracking cookies
Marketing/Tracking cookies are cookies or any other form of local storage, used to create user profiles to display advertising or to track the user on this website or across several websites for similar marketing purposes.
5.4 Social media
On our website, we have included content from LinkedIn to promote web pages (e.g. “like”, “pin”) or share (e.g. “tweet”) on social networks like LinkedIn. This content is embedded with code derived from LinkedIn and places cookies. This content might store and process certain information for personalized advertising.
Please read the privacy statement of these social networks (which can change regularly) to read what they do with your (personal) data which they process using these cookies. The data that is retrieved is anonymized as much as possible. LinkedIn is located in the United States.
6. Placed cookies
7. Consent
When you visit our website for the first time, we will show you a pop-up with an explanation about cookies. As soon as you click on “Save preferences”, you consent to us using the categories of cookies and plug-ins you selected in the pop-up, as described in this Cookie Policy. You can disable the use of cookies via your browser, but please note that our website may no longer work properly.
7.1 Manage your consent settings
8. Enabling/disabling and deleting cookies
You can use your internet browser to automatically or manually delete cookies. You can also specify that certain cookies may not be placed. Another option is to change the settings of your internet browser so that you receive a message each time a cookie is placed. For more information about these options, please refer to the instructions in the Help section of your browser.
Please note that our website may not work properly if all cookies are disabled. If you do delete the cookies in your browser, they will be placed again after your consent when you visit our website again.
9. Your rights with respect to personal data
You have the following rights with respect to your personal data:
- You have the right to know why your personal data is needed, what will happen to it, and how long it will be retained for.
- Right of access: You have the right to access your personal data that is known to us.
- Right to rectification: you have the right to supplement, correct, have deleted or blocked your personal data whenever you wish.
- If you give us your consent to process your data, you have the right to revoke that consent and to have your personal data deleted.
- Right to transfer your data: you have the right to request all your personal data from the controller and transfer it in its entirety to another controller.
- Right to object: you may object to the processing of your data. We comply with this, unless there are justified grounds for processing.
To exercise these rights, please contact us. Please refer to the contact details at the bottom of this Cookie Policy. If you have a complaint about how we handle your data, we would like to hear from you, but you also have the right to submit a complaint to the supervisory authority (the Data Protection Authority).
10. Contact details
For questions and/or comments about our Cookie Policy and this statement, please contact us by using the following contact details:
GreenStayn
Louis Pregerkade 204, 3071 AZ Rotterdam
Netherlands
Website: https://www.greenstayn.nl
Email: ln.nyatsneerg@tcatnoc
This Cookie Policy was synchronized with cookiedatabase.org on May 31, 2023.
This website only uses Zoho PageSense to analyse the visitors’ behaviour.
About our cookie policy
At Zoho PageSense, we use cookies to identify and analyze your visitors’ data when they land on your website. This cookie policy is a declaration (or consent) to users on what cookies we add to your website, what visitor metrics we track, for what purpose, and how your users may opt out of the cookies. This cookie policy is part of our privacy policy, which also includes additional details about our information collection and usage.
Why does Zoho PageSense use cookies?
PageSense uses cookies to identify individual visitors and their behavior on your website. These cookies determine whether the visitor is part of an experiment, track visitor views over a variation and let serve the same variation to the visitor consistently over multiple visits, and, finally, track completed goals. They are also used to accelerate your future activities on your website. We use different types of cookies, local storage objects, and similar technologies, each storing a different set of data. These cookies do not interfere with the loading or functioning of the web page at all. Also, they collect information that does not personally identify anyone.
GDPR with PageSense
PageSense’s activities, like tracking visitor behavior on websites and targeting specific visitors for A/B tests, generate data that’s considered private under GDPR. All of this tracked data is stored with anonymized IP addresses, so you can safely capture, process, and use it without infringing on visitors’ data privacy.
Current list of cookies
The following cookies are placed in the visitor’s browser to track and test website visitor activity.
First-party Cookies
These identify and store cookie data on a web browser within the same domain, on which the PageSense tracking code is installed and fired.
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. | 1 year | 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. |
{ 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. |
{ 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. |
{ sessionId } (stores a random alphanumeric string of length 7 or 32) | This cookie stores the session’s metadata for your session recording experiments. | Sets once after the user starts 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. |
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. |
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. |
Third-party Cookies
These identify recurring visitors on a web browser across different domains and store cookie data under the domain called “cdn.pagesense.io”.
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. |
{ exp_key } | 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 revenue goal into it. | 1 year | Used to keep track of successful revenue 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. |
{ 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 number of visitors who dropped off while traversing through the funnel. |
{ 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. | |
{ exp_id } +”polls” | 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 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. |
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. |
localStorage
These store visitor data locally within the visitor’s browser.
Cookie Name | Information Stored | Generation State | Expiry Period | Purpose |
---|---|---|---|---|
payloadQueue | This cookie stores the session’s data on a local storage system for your session recording experiments. | Sets when the user starts interacting on a web page. | No expiry | Used to resend canceled or failed requests and prevent data loss during session recording. |
{ 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. |
sessionStorage
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. |