Verama handling of cookies & other storage technologies
1. What are cookies?
Cookies are small pieces of text used to store information on web browsers. Cookies are used to store and receive identifiers and other information on computers, phones and other devices. Other technologies, including data we store on your web browser or device, identifiers associated with your device, and other software, are used for similar purposes. In this policy, we refer to all of these technologies as "cookies."
Depending on the Site or Service you are using, the answer varies. While we do our best to keep this table updated, please note that the number and names of cookies, pixels and other technologies may change from time to time.
2. Why do we use JWT?
JSON Web Token (JWT, sometimes pronounced) is a Internet standard for creating JSON-based access tokens that assert some number of claims. For example, a server could generate a token that has the claim "logged in as admin" and provide that to a client. The client could then use that token to prove that it is logged in as admin. The tokens are signed by one party's private key (usually the server's), so that both parties (the other already being, by some suitable and trustworthy means, in possession of the corresponding public key) are able to verify that the token is legitimate. The tokens are designed to be compact, URL-safe, and usable especially in a web-browser single-sign-on (SSO) context. JWT claims can be typically used to pass identity of authenticated users between an identity provider and a service provider, or any other type of claims as required by business processes JWT relies on other JSON-based standards: JSON Web Signature and JSON Web Encryption (https://en.wikipedia.org/wiki/JSON_Web_Token)
3. What Verama use Cookies for
Cookies help us provide, protect and improve Verama, such as by personalising content, and providing a safer experience. While the cookies that we use may change from time to time as we improve and update the Verama, we use them for the following purposes:
-
Authentication. We use cookies to verify your account and determine when you're logged in so we can make it easier for you to access the Verama and show you the appropriate experience and features.
-
Performance. We use cookies to provide you with the best experience possible. For example: Cookies help us route traffic between servers and understand how quickly Verama load for different people. Cookies also help us record the ratio and dimensions of your screen and windows and know whether you've enabled high-contrast mode, so that we can render our sites and apps correctly.
-
Analytics and research. We use cookies to better understand how people use the Verama so that we can improve them. For example: Cookies can help us understand how people use the Verama service, analyse which parts of the Verama people find most useful and engaging, and identify features that could be improved.
4. How to block or/and delete cookies
Most browsers have a default setting that accepts the use of cookies, but you can set the usage and extent of cookies in your computer settings. You can also set up your computer so that you will be notified each time a cookie is placed or you can turn off all cookies through your browser and delete existing cookies (in the Help feature of your browser, you can read more about how to changes or updates your cookies). We want to point out that this is a computer setting and that these settings only apply to the computer on which the settings are made. If you are using more than one computer, the settings must be made on each computer.
5. Which cookies are Verama using?
Cookies set in the http://verama.com domain
5.1. Authentication
| Cookie | Details | Validality |
|---|---|---|
| JWT | User ID | 1h |
| JWT | Token ID | 1h |
| JWT | Email address | 1h |
5.2. Third party websites and apps
Our business partners may also choose to share information with us from cookies set in their own websites' domains.
Google Analytics
| Cookie | Details | Validality |
|---|---|---|
| _ga | Used to distinguish users https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage |
2 years |
New Relic
| Cookie | Details | Validality |
|---|---|---|
| _initial_utms | Analytics / Performance Cookies https://newrelic.com/termsandconditions/cookie-policy |
1 day |
| JSESSIONID | Cookie which is used to monitor session counts https://docs.newrelic.com/docs/browser/new-relic-browser/page-load-timing-resources/new-relic-cookies-used-browser |
Session |
| NREUM | Cookie which is only created in browsers that do not support the Navigation Timing API | Session |
| NRAGENT | cookie, created only when a token is handed out to an end user by the New Relic server | Session |
Hotjar
| Cookie | Details | Validality |
|---|---|---|
| X-Access-Key | Keeps your website session alive. https://www.hotjar.com/legal/policies/cookie-information |
Session |
Kissmetrics
| Cookie | Details | Validality |
|---|---|---|
| km_abi | A unique string that is used to remember which KM A/B test variation was seen | 5 years |
| km_ai | A person’s Anonymous ID | 5 years |
| km_ni | A person’s Named ID | 5 years |
| km_lv | Time the last visit, to determine whether they are a returning visitor or not. Has a value of ‘x’ if they are already designated as a returning visitor. | 5 years |
| km_vs | Set to ‘1’ if the visitor is in an active browsing session. | 30 minutes |
| km_uq | A URL queue that preserves unsent tracking URL’s from page to page. | It empties out if our tracking servers are online. |
HubSpot
| Cookie | Details | Validality |
|---|---|---|
| __hs_opt_out | This cookie is used by the opt-in privacy policy to remember not to ask the visitor to accept cookies again. This cookie is set when you give visitors the choice to opt out of cookies. | 13 months |
| __hs_do_not_track | The cookie can be set to prevent the tracking code from sending any information to HubSpot. Setting this cookie is different from opting out of cookies, as is still allows anonymized information to be sent to HubSpot. | 13 months |
| hs_ab_test | This cookie is used to consistently serve visitors the same version of an A/B test page they’ve seen before. | end of session |
| <id>_key | When visiting a password-protected page, this cookie is set so future visits to the page from the same browser do not require login again. The cookie name is unique for each password-protected page. | n/a |
| __hsmem | This cookie is set when visitors log in to Hubspot-hosted site | 1 year |
| __hstc | The main cookie for tracking visitors. It contains the domain, utk, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). | 13 months |
| hubspotutk | This cookie is used to keep track of a visitor’s identity. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. | 13 months |
| __hssc | This cookie keeps track of sessions. This is used to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. It contains the domain, viewCount (increments each pageView in a session), and session start timestamp. | 30 minutes |
| __hssrc | Whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted their browser. If this cookie does not exist when HubSpot manages cookies, it is considered a new session. | end of session |
Freshdesk
| Cookie | Details | Validality |
|---|---|---|
| fw_fr fw_flu fw_vi fw_sq first_session |
Freshworks | Website analytics cookie for visitor information and source |
| tvc_helpdeskName io SERVERID |
Google Tag Manager | Website analytics cookie for visitor information and source |
| __distillery | Wistia | These cookies enhance performance on the website |
| zarget_user_id Zarget_funnel_id zaget_visitor_info zarget_goal_info zg_freshchat_session_id_upd_time zg_freshchat_session_id _zg Fm_sr_log_events pageViewCookie |
Zarget | These cookies collect information that is used either in aggregate form to help understand how Websites are being used or how effective marketing campaigns are, or to help customise Websites |
| _utma _utmb _utmc _utmt _utmz _dc_gtm_UA-# _uv_id |
Google Analytics | These cookies collect information that is used either in aggregate form to help understand how Websites are being used or how effective marketing campaigns are, or to help customise Websites |
| _uet_sid _uetsid |
Bing Conversion | These cookies collect information that is used either in aggregate form to help understand how Websites are being used or how effective marketing campaigns are, or to help customise Websites |
| mp__mixpanel | Mixpanel | These cookies collect information that is used either in aggregate form to help understand how Websites are being used or how effective marketing campaigns are, or to help customise Websites |
| muxdata wistia-http2-push-disabled |
Wistia | These cookies collect information that is used either in aggregate form to help understand how Websites are being used or how effective marketing campaigns are, or to help customise Websites |
| __smToken __smSmartbarShown |
Sumo | These cookies collect information that is used either in aggregate form to help understand how Websites are being used or how effective marketing campaigns are, or to help customise Websites |
| __ar_v4 | Double click Conversion | These cookies collect information that is used either in aggregate form to help understand how Websites are being used or how effective marketing campaigns are, or to help customise Websites |
| _hjIncludedInSample | Hot Jar | These cookies collect information that is used either in aggregate form to help understand how Websites are being used or how effective marketing campaigns are, or to help customise Websites |
| pubsub_cookie hop- |
Freshchat widget | These cookies collect information that is used either in aggregate form to help understand how Websites are being used or how effective marketing campaigns are, or to help customise Websites |
| _hp2_id_ | Heap Analytics | These cookies collect information that is used either in aggregate form to help understand how Websites are being used or how effective marketing campaigns are, or to help customise Websites |
| BCookie | Slideshare | These cookies collect information that is used either in aggregate form to help understand how Websites are being used or how effective marketing campaigns are, or to help customise Websites |
Leadfeeder
| Cookie | Details | Validality |
|---|---|---|
| _lfa | This cookie is used for identifying the IP address of devices visiting the website. The cookie collects information such as IP addresses, time spent on website and page requests for the visits and then set a unique identifier to separate different visitors. This collected information is used later on in marketing and sales activities. | 2 years |