Cookies and Similar Tracking Technologies Policy | Midot

Cookies and Similar Tracking Technologies Policy

Cookies and Similar Tracking Technologies Policy

This cookies and similar technologies policy provides you with general information about cookies and similar technologies (collectively, “Tracking Technologies”) and on how and for what purposes Midot – Ethics Computerized Diagnostic Systems LTD (“Midot” “we”, “our” or “us”) use such Tracking Technologies on scientifically validated, field-proven assessment solutions, delivered through an advanced, secure technology platform (the “Service”).

Please take the time to read this policy, which complements our general privacy policy. If you have questions or comments, you are welcome to contact us through: https://midot.com/contact-us/.

Index

What Are ‘Cookies’?

Cookies are small files with pieces of information, normally consisting of just letters and numbers, which websites and other online services use when users visit them.

Software on the users’ devices (for example, a web browser) can store cookies and send them back to the online service the next time they visit, to make a specific function of the online service’s work and to provide information about the user’s activities on the online service.

For What Purposes are Cookies Being Used?

Cookies are used in numerous ways. For example, when analyzing traffic to an online service or tracking users’ browsing behavior.

Cookies are widely used as they allow an online service to recognize a user’s device. Tracking Technologies help online services to remember the visitors and their activities, for example, the user’s language preferences.

What are ‘Session’ and ‘Persistent’ Cookies?

“Session Cookies” are removed from user’s device once they close their browser session.

“Persistent Cookies” last for longer periods on your device – after users close their browser session.

Users can delete previously set persistent cookies manually or configure the browser settings to delete cookies, as further described below.

What are ‘First-party’ and ‘Third-party’ Cookies?

First-party cookies are set directly by the online service that the users are using.

Third-party cookies are set by a domain other than the one the users are visiting. For the purpose of this policy, these are cookies that are set by our service providers, such as Google Analytics.

What are ‘Similar Technologies’?

Functions usually performed by a cookie can be achieved by other means. This could include, for example, using certain characteristics to identify devices so that visits to an online service can be analyzed.

Any technology that stores or accesses information on your device is relevant for this purpose, and therefore it includes, for example, HTML5 local storage, Local Shared Objects and fingerprinting techniques.

Additionally, technologies like use of log files, scripts, tracking pixels and plugins, wherever these are used – are also considered as similar technologies.

How do we Use Tracking Technologies and for What Purposes?

We use both Session Cookies and Persistent Cookies as part of your experience on the Site so that we can facilitate the use of the Site’s features and tools, keep track of your preferences, improve your experience with our Site, for web analytics and for marketing purposes.

Some cookies are strictly essential for the operation of the Site while other cookies help to improve our services and marketing activities. The same rule goes for all Tracking Technologies that we use.

When a Tracking Technology contains personal data, then our general privacy policy applies as well.

Does Midot Need to Obtain my Consent for Using Tracking Technologies?

Yes, under certain data protection laws, such as EU laws that govern the use of cookies, and if such laws are applicable to your use of the Service, and only with respect to the Tracking Technologies that are not strictly essential for the operation of the Site.

If you do not agree to accept our cookies or other Tracking Technologies that are not strictly essential for the operation of the Site, you can manage your tracking technologies preferences as described below.

Can I Manage my Tracking Technologies Preferences?

Yes, through the Service’s cookie management settings. In addition, every browser allows you to manage your Tracking Technologies preferences, usually found in the “Help” or “Settings” sections of the web browser. Here are some links to Tracking Technologies preferences management for commonly used web browsers: (a) Google Chrome; (b) Microsoft Edge; (c) Mozilla Firefox; (d) Microsoft Internet Explorer; (e) Opera; (f) Apple Safari.

You can turn off certain third party targeting or advertising cookies by visiting the following link: Network Advertising Initiative.

To find out more about cookies, including how to see what cookies have been set, you can visit the following websites: www.aboutcookies.org and www.allaboutcookies.org.

Will Midot Vision Change this Policy?

We will update this policy, where needed. Every time we will change this policy we will post a notice on the Site, and obtain your consent once again, where required under applicable laws.

Last updated: November 1, 2022


Appendix A – Tracking Technologies Table

Essential Cookies

These cookies are strictly essential for enabling your movement around the Service and providing access to features such as your profile, and other secure areas Midot uses and the identity of the provider.

This category of cookies cannot be disabled.

 

Name Purpose & Expiration Date First/Third Party Cookie
__cf_bm This cookie is used to distinguish between humans and bots. This is beneficial for the Service, in order to make valid reports on the use of the Service.

Expiration – 1 day

Third Party – Cloudinary
__cfruid This cookie is a part of the services provided by Cloudflare – Including load-balancing, deliverance of online content and serving DNS connection for the online service’s operators.

Expiration – Session

Third Party – Cloudinary
incap_ses_* Incapsula DDoS Protection and Web Application Firewall: The cookie on which HTTP requests are related to a certain session (AKA visit). Re-opening the browser and accessing same site is supposed to be considered different visits.

Expiration – Session

First Party
visid_incap_* Incapsula DDoS Protection and Web Application Firewall: The cookie on which sessions are related to a specific visitor (visitor representing a specific computer) In order to identify clients which have already visited Incapsula.

Expiration – 1 year

First Party
nlbi_*

Incapsula DDoS Protection and Web Application Firewall: Load balancing cookie. To ensure requests by a client are sent to the same origin server.

Expiration – Session

First Party
__zlcmid Is a token set by Zopim (the live chat software provided by Zendesk) to help identify a user’s chat

Expiration – Session

First Party
org.jboss.seam.core.Locale

Remembers user’s Locale settings

Expiration – 1 year

First party
AWSELB AWS Classic Load Balancer Cookie: Load Balancing Cookie: Used to map the session to the instance.Expiration – Session Third party
JSESSIONID A session cookie is required to follow your progress through the Service. It is essential to ensure that any information you enter or routes you take are remembered by the Service. Without this cookie, every page you visited would treat you as a completely new visitor. This cookie does not identify you personally and is not linked to any other information we store about you.

Expiration – Session

First Party
key Remembers examinee to prevent parallel test proceeding and allow examinee to revert the same exam in case that the page was refreshed.

Expiration – Session

First party
tabName Remembers type of login (examinee type or recruiter type) on the login page

Expiration – Never

First party
usr Remembers user’s encrypted email to know what a user last logged in and show login page in appropriate language.

Expiration – Never

First party
usrsvc Second verification encrypted key.

Expiration – 7 days

First Party

Analytics Cookies

Analytics cookies collect information about how visitors use the Service. Our service providers can transfer relevant information to third parties where required by law or where such third parties process such information on their behalf.

Name Purpose & Expiration date First/Third Party Cookie
_ce.s Collects data on the user’s navigation and behavior on the Service. This is used to compile statistical reports and heatmaps for the Service’s operators.

Expiration – 1 year

Third Party – Cloudinary
_ga Registers a unique ID that is used to generate statistical data on how the visitor uses the Service.

Expiration – 2 years

Third Party – Cloudinary, Google
_ga_* Used by Google Analytics to collect data on the number of times a user has visited the Service as well as dates for the first and most recent visit.

Expiration – 2 years

Third Party – Cloudinary
_gid Registers a unique ID that is used to generate statistical data on how the visitor uses the Service.

Expiration – 1 day

Third Party – Cloudinary,

www.googleoptimize.com

 

FPID Registers statistical data on users’ behaviour on the Service. Used for internal analytics by the Service’s operator.

Expiration – 2 years

Third Party – Cloudinary
FPLC Registers a unique ID that is used to generate statistical data on how the visitor uses the Service.

Expiration – 1 day

Third Party – Cloudinary
hjSessionUser{site_id}

Hotjar cookie that is set when a user first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.

Expiration – 1 year

First Party
_gid Registers a unique ID that is used to generate statistical data on how the visitor uses the Service.

Expiration – 1 day

First Party
_ga Used by Google Analytics to collect data on the number of times a user has visited the Service as well as dates for the first and most recent visit.

Expiration – 2 years

First Party
_gat_gtag_UA_* This cookie is installed by Google Analytics to store the Service’s unique user ID.Expiration – 1 minute First Party

Marketing Cookies

Marketing cookies collect personal information such as your name, which pages you visit on our Service, your history arriving at our Service and so on. Collected information is used to evaluate and improve the effectiveness of our marketing campaigns.

Name

Purpose & Expiration Date First/Third Party Cookie
_gcl_au Used by Google AdSense for experimenting with advertisement efficiency across websites using their services.

Expiration – 3 months

Third Party – Cloudinary
_mkto_trk Contains data on visitor behaviour and interaction with the Service. This is used in context with the email marketing service Marketo.com, which allows the Service to target visitors via email.

Expiration – 2 years

Third Party – Cloudinary
DSID These cookies are used by DoubleClick.net for targeting and advertising

Expiration – 14 days

Third Party – DoubleClick
IDE These cookies are used by DoubleClick.net for targeting and advertising

Expiration – 2 years

Third Party – DoubleClick

Additional Similar Technologies

Name Purpose & Expiration Date
Third Party Unclassified Cookie used by Cloudinary

Expiration – session

Skip to content