Like other websites, the website www.alisedaorigomare.com (the "Website") uses a technology called "cookies" to gather information about the use of the Website. You can consult by clicking here the information related to the company that manages the Website.
To learn more about cookies, you can consult the following explanatory technical document: http://www.allaboutcookies.org/es/
Type of Cookies used by the Websites
Our Websites use its own and third-party cookies, which are described below:
|Domain||Name||Purpose||Ownership (own or third parties)|
|https://www.google.es||Google Analytics Cookies (__utma, __utmb, __utmc, __utmz)||These four cookies are served by Google Analytics to collect various information about the user's browsing through our site. For example, the location of the visitor, details of the visit made (time, page views, etc.). In addition to blocking these cookies through the browser, the user can use this add-on provided by Google itself to disable the Google Analytics service during their visit.||Google (third parties)|
|https://www.alisedainmobiliaria.com||Technical cookies of the web platform (PHPSESSID, viewed_cookie_policy)||These cookies are used by the page and are intended to allow the visit to the page.||Aliseda (Own)|
|www.addthis.com||AddThis Cookies (__atuvc, uid)||They allow the user to share content through social networks and email. When we include links to third-party services on our pages, they may temporarily store a cookie on your device to make your service easier.||AddThis (third-party)|
|https://twitter.com||Twitter Cookie (guest_id)||The Twitter cookie appears on the pages that use the Tweet button and serves to identify the user with a unique number associated with Twitter.||Twitter (third-party)|
|https://www.google.es||Google Cookie (NID)||It is a unique identifier used by Google applications to store information about user preferences.||Google (third-party)|
In the event that you continue browsing the Website, you consent to the use of the aforementioned cookies, for the periods indicated and in the conditions contained in this policy.
Disable and block cookies
We inform you that you can block or disable cookies by activating the configuration of your browser that allows you to refuse the installation of all cookies or some of them. The majority of browsers allow to warn of the presence of cookies or to reject them automatically. If you reject them you may continue to use our Website, although the use of some of your services may be limited and therefore your experience on our Website less satisfactory.
In any case, from here you can access the instructions of the most popular desktop and mobile browsers.
Google Chrome, Mozilla Firefox, Internet Explorer, Safari.
IOS, Android, Blackberry, Windows Phone.
Withdraw my consent
If you wish to withdraw your consent related to the Cookies Policy at any time, you must delete the cookies stored on your computer through the settings and settings of your Internet browser.
Changes in the Cookies Policy
If you have any questions, comments or suggestions about the Cookies Policy, please write to: Paseo de la Castellana 280, 2nd Floor, 28046 Madrid.
No state is stored in web servers and applications. In contrast, once the user is identified, the application generates a cookie for that user and only for that session with the following information:
- A version number that identifies the format of the cookie
- A random long string that acts as session ID
- A routing track
- A checksum
The routing track is used to optimize traffic within our network by indicating the shortest route of access to user data; in this case, the OrgID. This value is not used in any way to identify the user (this is done by the random value) or to establish privileges (this is done by the application configuration). Generally, we do not treat the OrgID secretly because in reality it is simply an opaque internal identifier.
The checksum is included as an optimization - if the cookie has been distorted or modified in transit, it will allow us to omit a round-trip database only to discover that the cookie is not good.
The user ID is written in a status box in the database.
The cookie is coded on base62.
Processing of cookies
For each request that a user sends to the application, the browser sends the cookie to the application server. The application server compares the cookie in the database status box to verify that the session is valid.
Session cookies have the following limitations:
- Unique for each user and each session (non-persistent)
- Canceled when the user closes the session or closes (abandons) the browser
- Canceled when the duration of a session is exceeded