Documentation of supported COOKIES files in the widget
Cookie name | Script setting/reading the cookie | Expiration time | Cookie domain | Website | Website owner/administrator | Description | Purpose of the cookie | Data collected by the cookie | Does it collect location data? | Do other companies have access to the data? If so, what kind? | Will cookie data be used for behavioral or tracking advertising? | Can the website be used without cookies? |
| JS | 180 days | client's (main e.g. | (where the client installs the widget) | webankieta.pl client | Information about the user's session on the website made available to the widget. | Based on this cookie, conditions defined in the display rules are checked, e.g., user's time on the page, number of page views. | Session expiration time ( User's time spent on the page (counted in seconds). Number of subpages visited by the user. | No, regarding geolocation data. | If the widget is placed on the client's site, then the client's server provider. If the widget is in the Webankieta panel, then the server provider (Asseco, Hostersi.pl ...) | No, but potentially the client can configure the widget this way | Yes, but the widget will not work |
There can be many of these cookies: | JS | 180 days | client's (main e.g. | (where the client installs the widget) | webankieta.pl client | Based on this cookie, the widget's display rules are checked. | closed: boolean determining whether the widget is closed. | No, regarding geolocation data. | If the widget is placed on the client's site, then the client's server provider. If the widget is in the Webankieta panel, then the server provider (Asseco, Hostersi.pl ...) | No, but potentially the client can configure the widget this way | Yes, but the widget will not work |
Please note the presence of localStorage.
FAQ
1. For what purpose are the cookies set?
Cookies and localStorage are used to collect information:
about the user's session on the website
about actions related to each widget separately
Data from localStorage cannot be directly shared between subdomains of the same domain. This is due to the "same-origin policy" enforced by web browsers. Therefore, our solution is cookies as a mirror copy of localStorage. They are set so that the user can manage display rules between their products across different subdomains. The startquestion-session cookie updates user session data on the main domain.
2. Is it necessary to save them for 6 months?
We chose this period based on the average needs of our users.
3. Why are cookies set on the main domain example.com instead of the service domain www.example.com?
The reason is sharing them between subdomains as mentioned in point 1.
4. What is the reason for reading/writing cookies/LocalStorage every 5 seconds?
By setting this interval, we chose a compromise between CPU usage and the update frequency of the user's presence time on the page. We concluded that setting such a time will cause an unnoticeable load on current processes and provide a reasonable reaction time for display rules, e.g., Time on the entire site.
5. What browser versions do you support?
All that support es2016plus (Array.from, Array.map, Array.includes, Array.filter, Set, Map, …). We do not support IE11, which has not received technical support from Microsoft since June 15, 2022. Browser list: "es6" | Can I use... Support tables for HTML5, CSS3, etc
6. Would it be possible for you not to use the cookie mechanism, or are they absolutely necessary for proper operation?
It is not absolutely necessary, but it expands configuration possibilities using display rules.