Cookies Policy

What IS A cookie?

The Web of APARTAMENTOS PÉREZ JIMÉNEZ S.L. (https://www.metropolitano-hotel.com/) uses Cookies. Cookies are files sent to a browser through a web server to record the User's activities on a specific website. The first purpose of Cookies is to provide the user with a faster access to the selected services. In addition, Cookies personalize the services offered by the Website, facilitating and offering each user information that is of interest to them or that may be of interest to them, based on their use of the Services.

The Website uses Cookies to personalize and improve the user's navigation as much as possible. Cookies are only associated with an anonymous user and their computer and do not provide references that allow to deduce the user's personal data. The user may configure their browser to notify and reject the installation of Cookies sent by the Web, without this affecting the user's ability to access the contents of this site. However, we would like you to note that, in that case, the functioning quality of the web site could diminish.

The Registered Users, who register or who have logged in, will be able to benefit from more personalized and profile-oriented services, thanks to the combination of the data stored in the cookies with the personal data used at the time of registration. These users explicitly authorise the use of this information for the specified purpose, without prejudice to their right to reject or disable the use of cookies.

Likewise, the Web will be able to know all the services requested by the users, so that they will be able to provide or offer the adequate information to the tastes and preferences of each user.

What types of cookies are there?

Cookies, depending on their Permanence, can be divided into:

Session cookies: Expire when the user closes the browser.
Persistent cookies: Expire once the cookies’ objective is achieved (for example, so that the user remains identified in the Services) or when the user deletes them annually.

Depending on their Owner, they can be divided into:

Own Cookies: These are those that are sent to the user's terminal equipment from a computer or domain managed by the publisher and from which the service requested by the user is provided.
Third-party Cookies: Those that are sent to the user's terminal equipment from a computer or domain that is not managed by the publisher, but by another party that processes the data collected through the cookies.

Additionally, depending on their Purpose, Cookies can be classified as follows:

Performance Cookies: This type of Cookie remembers your preferences for the tools found in the services, so you don't have to reconfigure the service each time you visit our site. As an example, in this typology are included:

Volume settings of video or audio players.
The video transfer speeds that are supported with your browser.

Geoocation cookies: These Cookies are used to find out what country you are in when you request a service. This Cookie is completely anonymous and is only used to help orient content to your location.
Log cookies: These Cookies are generated once the user has registered or opened his session thereafter, and are used to identify him in the services for the following purposes:

To keep the user identified so, if you close the service, browser or computer and at some other time or another day re-enter the service,the user will remain identified, improving his navigation without having to re-identify. This feature can be deleted if the user clicks in "end session", so that this Cookie is deleted and the next time you enter the service the user will have to log in to be identified.
Check whether the user is authorized to access certain services, for example, to participate in a contest.

Analytical cookies:analytic Cookie on the user's computer. This Cookie that is generated only in the visit, will serve in next visits to the Services of the Web to identify anonymously the user. The main objectives pursued are:

Allow the anonymous identification of the navigator users through the "Cookie" (identifies browsers and devices, not people) and therefore the approximate posting of the number of visitors and their trend over time.
Anonymously identify the most visited content and therefore more attractive to users.
Know if the user you are accessing is new or repeat visit.
Important: Unless the user decides to register for a Web service, the "Cookie" will never be associated with any personal data that can identify you. These Cookies will only be used for statistical purposes that help to optimize the experience of users on the site.

Targeting Cookies: This type of "Cookies" allows to extend the information of the ads shown to each anonymous user in the Web Services. Among others, the duration or frequency of display of advertising positions, the interaction with them, or the browsing patterns and/or user compartments is stored as they help to form an advertising interest profile. In this way, they allow us to offer publicity related to the interests of the user.
Third party advertising cookies: In addition to the web-managed advertising in its Services, the Website offers its advertisers the option to serve ads through third parties ("Ad Servers"). In this way, these third parties can store Cookies sent from the Web Services from the Users' browsers, as well as access the data stored in them.

What cookies do we use?

The cookies we use on our website are:

Own: Are those that are sent to the user’s terminal equipment from a computer or domain managed by the editor itself and from which the service requested by the user is provided.

• sb_cookie_policy_[guide_id]_[hotel_id]. Purpose: Cookie conset banner options. Type: Strictly Necessary.   Category: Own. Expires: 1 year (Bookassist)
• rotateWarning. Purpose: Device orientation. Type: Preferences    Category: Own. Expires: 1 day. (Bookassist)
• ba_popup_closed. Purpose: Used to store popup activity. Type: Preferences    Category: Own. Expires: 7 days (Bookassist)
•wd_calendar_date_in. Purpose: Stores data of the booking calendar. Type: Preferences    Category: Own. Expires: Persistent (Bookassist)
•wd_calendar_date_out. Purpose: Stores data of the booking calendar. Type: Preferences    Category: Own. Expires: Persistent (Bookassist)
• sb_calendar_room. Purpose: Stores data of the booking calendar. Type: Preferences    Category: Own. Expires: Persistent (Bookassist)
• sb_calendar_now. Purpose: Stores data of the booking calendar. Type: Preferences    Category: Own. Expires: Persistent (Bookassist)
•sb_calendar_destination. Purpose: Stores data of the booking calendar. Type: Preferences    Category: Own. Expires: Persistent (Bookassist)
•sb_calendar_promo_code. Purpose: Stores data of the booking calendar. Type: Preferences    Category: Own. Expires: Persistent (Bookassist)
•event_range_date_to. Purpose: Used to store events dates. Type: Preferences    Category: Own. Expires: Persistent (Bookassist)
•event_range_date_from. Purpose: Used to store events dates. Type: Preferences    Category: Own. Expires: Persistent (Bookassist)
•exp_last_activity. Purpose: Expression Engine cookies to track activity in the site if logged in. Type: Functional. Category: Own. Expires: 1 year (Bookassist)
•exp_last_visit. Purpose: Expression Engine cookies to track activity in the site if logged in. Type: Functional. Category: Own. Expires: 1 day (Bookassist)
•exp_tracker. Purpose: Expression Engine cookies to track activity in the site if logged in. Type: Functional. Category: Own. Expires: Session (Bookassist)

Third party: Are those that are sent to the user’s terminal equipment from a computer or domain that is not managed by the publisher, but by another entity that treats the data obtained through cookies.

•_ga. Purpose: This cookie is used to distinguish unique users by assigning a randomly generated number as a client identifier. Type: marketing/personal. Category: third party Expires: 2 years (Google)
•_gid. Purpose: This cookie is used to distinguish unique users by assigning a randomly generated number as a client identifier. Type: Analytics. Category: third party. Expires: 1 day (Google)
•_gat. Purpose: This cookie is used to distinguish unique users by assigning a randomly generated number as a client identifier. Type: Analytics. Category: third party. Expires: 1 day (Google)
•VISITOR_INFO1_LIVE. Purpose: Stores the user's video player preferences using embedded YouTube video. Type: marketing/personal Category: third party. Expires: 179 days. (Youtube)
•YSC. Purpose: Stores the user's video player preferences using embedded YouTube video. Type: marketing/personal Category: third party. Expires: session (Youtube)
•PREF. Purpose: Stores the user's video player preferences using embedded YouTube video. Type: marketing/personal Category: third party. Expires: 8 months (Youtube)
•GPS. Purpose: Stores the user's video player preferences using embedded YouTube video. Type: marketing/personal Category: third party. Expires: 1 day (Youtube)
•yt-remote-device-id. Purpose: Stores the user's video player preferences using embedded YouTube video. Type: functional.    Category: third party. Expires: Persistent (Youtube)
•yt-player-headers-readable. Purpose: Stores the user's video player preferences using embedded YouTube video. Type: functional.    Category: third party. Expires: Persistent (Youtube)
•yt-remote-connected-devices. Purpose: Stores the user's video player preferences using embedded YouTube video. Type: functional.    Category: third party. Expires: Persistent (Youtube)
•yt-player-bandwith.   Purpose: Stores the user's video player preferences using embedded YouTube video. Type: functional.    Category: third party. Expires: Persistent (Youtube)
•yt-remote-session-app. Purpose: Stores the user's video player preferences using embedded YouTube video. Type: functional. Category: third party. Expires: Session (Youtube)
• yt-remote-cast-installed. Purpose: Stores the user's video player preferences using embedded YouTube video. Type: functional. Category: third party. Expires: Session (Youtube)
• yt-remote-session-name. Purpose: Stores the user's video player preferences using embedded YouTube video. Type: functional. Category: third party. Expires: Session (Youtube)
• yt-remote-cast-available. Purpose: Stores the user's video player preferences using embedded YouTube video. Type: functional. Category: third party. Expires: Session (Youtube)
• yt-remote-fast-check-period. Purpose: Stores the user's video player preferences using embedded YouTube video. Type: functional. Category: third party. Expires: Session (Youtube)
•aka_debug. Purpose: Stores the user's video player preferences using embedded Vimeo video Type: Marketing/ Personal Category: third party. Expires: Session (Vimeo)
•vuid.   Purpose: Stores the user's video player preferences using embedded Vimeo video Type: Marketing/ Personal Category: third party. Expires: 2 years (Vimeo)
• test_cookie. Purpose: Cookie to collect information about users activity or preferences Type: Preferences. Category: third party. Expires: 1 day (Doubleclick.net)
• IDE. Purpose: Cookie to collect information about users activity or preferences. Type: Marketing/ Personal. Category: third party. Expires: 1 year (Doubleclick.net)
• DV. Purpose: Cookie to collect information about users activity or preferences. Type: Marketing / Personal. Category: third party. Expires: 1 day (Google)
• NID. Purpose: Cookie to collect information about users activity or preferences. Type: Marketing / Personal. Category: third party. Expires: 6 months (Google)
•CONSENT.   Purpose: Cookie to collect information about users activity or preferences. Type: Marketing / Personal. Category: third party. Expires: 20 years (Google)
•ANID.   Purpose: Cookie to collect information about users activity or preferences. Type: Marketing / Personal. Category: third party. Expires: 2 years (Google)
• 1P_JAR. Purpose: Cookie to collect information about users activity or preferences. Type: Marketing / Personal. Category: third party. Expires: 1 year (Google)
•r/collect. This cookie is used to distinguish between humans and bots Type: Marketing / Personal.   Category: third party. Expires: Session (Doubleclick.net)
•collect. Purpose: This cookie is used to distinguish between humans and bots. Type: Marketing / Personal. Category: third party.    Expires: Session (Google)
• rc::d-15#. Purpose: This cookie is used to distinguish between humans and bots. Type: Marketing / Personal. Category: third party.    Expires: Session
• rc::a. Purpose: This cookie is used to distinguish between humans and bots. Type: Marketing / Personal. Category: third party.    Expires: Session (Google)
• rc::c. Purpose: This cookie is used to distinguish between humans and bots. Type: Marketing / Personal. Category: third party.    Expires: Session (Google)
• rc::b. Purpose: This cookie is used to distinguish between humans and bots. Type: Marketing / Personal. Category: third party.    Expires: Session (Google)

How to disable Cookies?

Usually it is possible to stop accepting cookies from the browser, or to stop accepting cookies from a particular service.

All modern browsers allow you to change cookie settings. These settings are usually found at “Options” or “Preferences” in your browser’s menu. You can also set up your browser or email manager and install free add-ons to prevent Web Bugs from downloading when you open an email.

The website provides user-orientation on the steps to access the cookie Setup menu and, where appropriate, private browsing on each of the main browsers:

Internet Explorer: Tools -> Internet Options -> Privacy -> Settings. For more information, you can consult Microsoft Support or Browser Help.
Microsoft Edge: Settings and more -> Settings -> Clear browsing data.
Firefox: Tools -> Options -> Privacy & Security -> History -> Custom Settings.
Chrome: Settings -> Advanced -> Privacy and security -> Clear browsing data.
Safari: Settings -> Security. For more information, see Apple Support or Browser Help.

Can THE COOKIE POLICY BE MODIFIED?

The Web can modify this Policy of Cookies according to the legislative and regulatory requirements, or with the purpose of adapting this policy to the instructions dictated by the Spanish Agency of Data Protection, for that reason it is advised to the users to visit it periodically.

When significant changes occur in this Cookies Policy, registered users will be notified either via website or e-mail.