This cookie policy (the “Cookie Policy”) describes how WeDontHaveTime AB, reg. no. 559126-1994 (“WeDontHaveTime”, “we”, “us” or “our”), at the address C/O Kivra: 559126-1994, 106 31, Sweden, uses cookies and similar identification technologies on our social network, including our website and mobile application.
We may from time to time need to amend this Cookie Policy. The most recent version of the Cookie Policy is always available on our social network.
If you have any questions that have not been addressed in this Cookie Policy, please contact us at the address provided or at info@wedonthavetime.org.
Our social network use so called cookies. Cookies are small text files that are stored on your browser or device (e.g. computer, mobile phone and tablet) and generally used to save functional settings or to monitor what you do on our social network.
By using our social network, you consent to the use of cookies as set forth in this Cookie Policy. If you do not accept our use of cookies, you can set your browser or device not to accept cookies. You can also set your browser or device to notify you whenever our social network tries to place a cookie on your browser or device. Through the browser and device setting, you can also delete previously stored cookies. Please refer to your browser’s and device’s help section for more information. Furthermore, you can delete cookies manually from your hard drive or device at any time. Please note that if you choose not to accept cookies, some of the functionalities of our social network may be limited.
There are two types of cookies: 1) persistent cookies remain on your browser or device for a fixed time; 2) session cookies are stored temporarily in the device’s memory while you have our social network ongoing. Session cookies disappear when you leave our social network.
We use ”pixel tags”, ”web beacons”, ”JavaScript” or similar technologies that enable, among other things, the tracking of your activities when you use our social network (jointly referred to as “Pixel Tags”). Pixel Tags may be used in connection with our social network or our online advertising, either by us, our service providers or other third parties. By using our social network, you consent to our use of Pixel Tags in accordance with this Cookie Policy.
Pixel Tags are used to collect typically anonymous data to help identify certain information, e.g. to compile reports on tracking information regarding demographics and patterns on our social network, and other information to make our social network more user friendly.
Pixel Tags may also be used to identify why you visit our social network, e.g. if any online advertisement or email has brought you to the network. Third party cookies or Pixel Tags may also collect information about user activities on our social network over time and across different websites. Furthermore, certain Pixel Tags may be used by other companies to track visits to their websites, to identify whether such internet traffic came from our social network or to confirm your eligibility to receive services or benefits.
We use the following cookies:
Name and type of cookie
Purpose and additional information
Deletion
Google Analytics, __utma, persistent cookie.
Thiscookie is typically written to the browseror deviceupon the first visit to a site from that web browser or mobile application. Ifthe cookie has been deleted by the browseror deviceoperator, and the browser or device subsequently visits a site, a new __utma cookieis written with a different unique ID. This cookie is used to determine uniquevisitors to a site or mobile application and it is updated with each page view.Additionally, this cookie is provided with a unique ID that Google Analyticsuses to ensure both the validity and accessibility of the cookie as an extrasecurity measure.
2years.
Google Analytics, __utmb, persistent cookie.
This cookie is used to establish and continue a user session with a site or mobile application. When a user views a page on the site or mobile application, the Google Analytics code attempts to update this cookie. If it does not find the cookie, a new one is written and a new session is established. Each time a user visits a different page on the site or mobile application, this cookie is updated and expire in 30 minutes. You can modify the default length of a user session with this method: _setSessionCookieTimeout().
30 minutes.
Google Analytics, __utmc, session cookie.
Historically, this cookie operated in conjunction with the __utmb cookie to determine whetheror not to establish a new session for the user. For backwards compatibilitypurposes with sites and mobile application still using the urchin.js trackingcode, this cookie will continue to be written.
When the session ends.
Google Analytics, __utmz, persistent cookie.
This cookie stores the type of referral used by the visitor to reach a site ormobile application, whether via a direct method, a referring link, a websitesearch (via a website and mobile application), or a campaign such as an ad oran email link. It is used to calculate search engine traffic, ad campaigns andpage navigation within our social network. The cookie is updated with each pageview.
6 months.
Google Analytics, __utmv, persistent cookie.
This cookie passes the information provided via the _setVar() method, which you use to create a custom usersegment. This string is then passed to the Google Analytics servers via theutmcc parameter.
2 years.
Google Analytics, __utmx, persistent cookie.
When the optimizer script executes, this cookie stores the variation the visitor isassigned to for each experiment, so the visitor has a consistent experience on oursocial network. See the Website OptimizerHelp Center for more information.
18 months.
.ASPXAUTH, session cookie/persistent cookie.
This is used by the ASP.NET framework to define whether a user is logged in or not.If you choose not to tick “Rembember me” when logging in, the cookie is asession cookie.
2 days (if ”Rembember me” is ticked).
Sessions-ID, ASP.NET_SessionsId, session cookie.
This is set by the ASP.NET framework and it identifies uniquely the user session onthe server; it’s used by the framework to pass information between serverrequests.
When the session ends.
Load balancing, AWSALB, persistent cookie.
This is used by the load balancer to make the session “sticky”, so that user isalways sent to the same server.
7 days.
_hjClosedSurveyInvites
Hotjar cookie. This cookie is set once a visitor interacts with a Survey invitation modal popup. It is used to ensure that the same invite does not re-appear if it has already been shown.
365 days.
_hjDonePolls
Hotjar cookie. This cookie is set once a visitor completes a poll using the Feedback Poll widget. It is used to ensure that the same poll does not re-appear if it has already been filled in.
365 days.
_hjMinimizedPolls
Hotjar cookie. This cookie is set once a visitor minimizes a Feedback Poll widget. It is used to ensure that the widget stays minimizes when the visitor navigates through your site.
365 days.
_hjDoneTestersWidgets
Hotjar cookie. This cookie is set once a visitor submits their information in the Recruit User Testers widget. It is used to ensure that the same form does not re-appear if it has already been filled in.
365 days.
_hjMinimizedTestersWidgets
Hotjar cookie. This cookie is set once a visitor minimizes a Recruit User Testers widget. It is used to ensure that the widget stays minimizes when the visitor navigates through your site.
365 days.
_hjIncludedInSample
Hotjar cookie. This session cookie is set to let Hotjar know whether that visitor is included in the sample which is used to generate funnels.
365 days.
_hjShownFeedbackMessage
This cookie is set when a visitor minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if they navigate to another page where it is set to show.
365 days.
We use Google Tag Manager services that may place cookies cookies in the browser, see Google's Privacy policy for details.