Like other websites, the Website www.alisedainmobiliaria.com (the “Website”) uses a technology called “cookies” to collect information about how the Website is used You can view the information about the company that manages the Website by clicking here.
For more information about cookies, you can view the following explanatory technical document: http://www.allaboutcookies.org/
Our Websites use first and third-party cookies, which are described below:
|DOMAIN||NAME||PURPOSE||OWNERSHIP (FIRST OR THIRD-PARTY)|
|https://www.google.es||Google Analytics Cookies (__utma, __utmb, __utmc, __utmz)||These four cookies are set by Google Analytics to collect a variety of information about the user's browsing of our website. For example, the location of the visitor, details of the visit (time, pages viewed etc.). As well as using the browser to block these cookies, the user can use this add-on provided by Google to disable the Google Analytics service during his/her visit.||Google (third-party)|
|https://www.alisedainmobiliaria.com||Strictly necessary cookies for the web platform (PHPSESSID, viewed_cookie_policy)||These cookies are used by the website and are designed to enable you to visit it.||Aliseda (First-party)|
|www.addthis.com||AddThis Cookies (__atuvc, uid)||They allow the user to share content via social networks and by email. When we include links to third-party services on our website it is possible that they will temporarily store a cookie on your device to make their service simpler.||AddThis (third-party)|
|https://twitter.com||Twitter Cookie (guest_id)||The Twitter cookie appears on the pages that use the Tweet button and it is used to identify the user with a unique number associated with Twitter.||Twitter (third-party)|
|https://www.google.es||Google Cookie (NID)||This is a unique identifier used by Google applications to store information about the user’s preferences.||Google (third-party)|
By continuing to browse our Website you give your consent to the use of the aforementioned cookies, for the prescribed periods and under the conditions stipulated in this policy.
We inform you that you can block or disable cookies by activating the setting on your browser that allows you to reject the installation of all or some cookies. Most browsers allow you to be notified of the presence of cookies or reject them automatically. If you reject them you can continue to use our Website, although the use of some of its services may be restricted and, therefore, your experience on our Website may be less satisfactory.
In any event, below you will find the instructions for the most popular desktop and mobile browsers.
If at any time you wish to withdraw your consent regarding the Cookies Policy, you should delete the cookies that are stored on your computer by using the configurations and settings on your internet browser.
If you have any queries, comments or suggestions regarding the Cookies Policy, please write to: Paseo de la Castellana 280, 2ª Planta, 28046 Madrid.
No state is maintained on the web or application servers. Instead, after the user authenticates, the application generates a "cookie" for that user for only that session, with the following information:
- A version number that identifies the format of the cookie
- A long random string that acts as the session ID
- A routing hint
- A checksum
The routing hint is used to optimize the traffic within our network by telling us something about the shortest path to the user's data--in this case, the OrgID. This value is not used in anyway to identify the user (this is done by the random value) or establish privileges (this is done by settings inside the application). We generally don't treat the OrgID as a secret because it really is just an opaque internal identifier.
The checksum is included as an optimization - if the cookie has been garbled or modified in transit, this allows us to skip a database round trip just to discover that the cookie is no good.
The user ID is written to a state table in the database.
The cookie is base62-encoded.
For each request a user submits to the application, the browser sends the cookie to the application server. The application server compares the cookie to the state table in the database to verify that the session is valid.
Session cookies have these limits:
- Unique for each user and each session (non-persistent)
- Invalidated when the user logs out or closes (quits) his browser
- Invalidated when the session duration limit is exceeded