Cookies policy questionnaire

The purpose of providing a website /application cookie notice is to notify users that cookies are being used by your site/Mapting application (the “App”), and to be transparent about that cookie activity. It can be cross-referenced in the Privacy Policy or added in the document (but I would not recommend this in an app) and should be easily accessible to the users.

In order for me to create a compliant privacy policy, I will need some information from your IT/ development team, as the cookies policy will contain the following key parts:

 
For your information to ease of reference, the various categories of cookies that you may have on the app are:

Strictly necessary cookies

trictly necessary cookies are required for the operation of a website/app and are essential to enable you to navigate the website and use its features; for example, they allow the users to access secure areas of the site. These cookies are primarily session cookies or connection cookies. Strictly necessary cookies are not persistently stored on the computer or device and are deleted when they close the browser.

 

Functionality cookies

Functionality cookies allow the website to recall information users have entered or choices they have made (such as language or investor status) and are designed to enable enhanced and more personalised features. These cookies also allow the user to optimise its use of the site after logging in. Functionality cookies are not deleted when the users close their browser; hence they are persistently stored on the computer or device and allow use and recognition over multiple devices.

Analytical / performance cookies

These are mainly visitor cookies which identify the origin of the visit, website performance cookies and statistical or analytical cookies.

These cookies allow the data controller to record and count the number of visitors and traffic sources, so that we can measure and improve the performance of a website. They help the owner to see if there are problems with particular pages, whether error messages are appearing, which pages are most and least popular and how visitors move around the website. The owner can use this information to adapt and improve the app or its website, make it more user-friendly, allow more intuitive navigation and generally provide users with a more positive online experience.

Analytical/performance cookies are not deleted when the users close the browser; hence they are persistently (but not eternally) stored on the computer or device.

Tracking (advertising) cookies

These cookies allow the owner of a site/app to keep track of user’s visits and activities on its website/app, the pages visited and the links clicked. These cookies allow the owner to link each visit to the information provided voluntarily by the visitor. We use this information to make the website/app and its content more relevant to the person’s interests. Tracking (advertising) cookies are not deleted when users close their browser; hence they are persistently stored on your computer or device.

Technical cookies for tracking user consent

These cookies are used to keep track of the visitors’ consent to the use of tracking (advertising) cookies. Technical cookies are not deleted when the user closes the browser; hence they are persistently stored on the computer or device.

Session cookies versus persistent cookies

Session cookies are temporary and deleted when the browser is closed, whereas persistent cookies are more permanent in that they are saved on the device. They are not deleted when the users close their browser. They are used, for example, to remember user’s preferences for the next time they visit the app or website.

First-party cookies versus third-party cookies

First-party cookies are set by the website when the person is visiting. Only the owner of the app or website can read them.

Third-party cookies are installed by someone other than the owner of the website you are visiting, in order to collect certain information so as to analyse user behaviour or demographic or other characteristics.

The small chart below is an easy way for you to list the cookies you are using on Mapting.

I have inserted some examples to guide you but they do not reflect at all what may be in place in your App, it is only for illustration purposes.

You may indicate if cookies fit in a specific category as listed above or detail what the cook does as I have indicated in a couple of examples below.

 

 

Name

Type

Expiration

Purpose

_Auth

 

Essential

Session

Account login

__utmt

Performance

Ten minutes

Google analytics

Demdex

 

Performance:

Counts the number of visits made by a website user

 

180 days

Adobe Analytics

 

da_sid

 

Analytical/performance:

Connects a visitor to a recorded web session

Browser session

Decibel Insight

 

__utmc

 

End of the session

Google analytics

PHPSESSID

 

End of the session

To maintain information about each visit to the website and enable core site functionality