Cookie Policy

1.    The commitments of DOVIRIS

DOVIRIS respects the privacy of its users and commits that all information to identify the user, remain confidential.

In accordance with the law of 6 January 1978, relating to data processing, data files and personal rights, readers and users of DOVIRIS website have the right to access, to rectify and to oppose their personal data. This right can be exercised by letter to:

43 avenue Georges Clémenceau

85120 La Chataigneraie


2.    How does DOVIRIS use Cookie Policy?

A cookie is a text file placed on your computer during the visit of a website or the clicking on and watching of an advertisement. Its target is to collect relevant information concerning your browsing and to send you personalised services on your terminal (computer, mobile phone and/or tablet).

The website of DOVIRIS is conceived to be attentive towards the needs and expectations of our users. This is amongst others the reason why we use cookies, for example to identify you when you make a comment on one of our articles.

-          We use the cookies to log you in and authenticate you. When you log into your account on the website with your login details, we store your login details and the time you signed in, in an encrypted cookie on your hard disk. This cookie allows you the browse the pages of the website without establishing a new connection on every single page.

-          We also use the cookies to facilitate the connecting process. For example, your e-mail address can be stored within a cookie which remains on your computer after the disconnection. The cookie gives information about your e-mail- address and you will only have to enter your password during the following connection. If you use a public computer or if you prefer that the information is not stored, you shall click on the appropriate option button on

-          We collect and analyse statistics. We can use the cookies to count the number of visits, of users and the visited pages. They enable us also to create other global statistics considering the activities on our websites and our services.


These analysis allow us to better manage our websites and services and to ameliorate their performance.

3.    Set your Internet Browser

You can chose to deactivate the cookies. Your browser may also be set to inform you about cookies that are stored on your computer and to ask you to accept them or not. You can accept or refuse the cookies from case to case or you can refuse them systematically.

We remind you that the settings may alter the conditions of your access to our contents and services which require the use of cookies. If you browser is configured to refuse all cookies, you will not be able to benefit from our services.

For more information on how you can modify the cookies settings in your browser please go on the website for the acceptation of cookies and for the management of the cookies settings in general.

4.    Data stored in a visitor/client's cookie




The date and time the cookie was created (in YYYY-MM-DD HH:MM:SS format).


The ID of the selected language.


The ID of the selected currency.


The ID of the last visited category of product listings.


Whether the cart block is "expanded" or "collapsed".


The IDs of recently viewed products as a comma-separated list.


The ID of the current wishlist displayed in the wishlist block.


Whether the "Terms of service" checkbox has been ticked (1 if it has and 0 if it hasn't)


The guest ID of the visitor when not logged in.


The connection ID of the visitor's current session.


The customer ID of the visitor when logged in.


The last name of the customer.


The first name of the customer.


Whether the customer is logged in.


The MD5 hash of the _COOKIE_KEY_ in config/ and the password the customer used to log in.


The email address that the customer used to log in.


The ID of the current cart displayed in the cart block.


The Blowfish checksum used to determine whether the cookie has been modified by a third party.
The customer will be logged out and the cookie deleted if the checksum doesn't match.