VP Jardín de Recoletos

Cookies policy

What are cookies?

The website of APARTAMENTOS PÉREZ JIMÉNEZ S.L. (https://www.recoletos-hotel.com) uses cookies. Cookies are files sent to a browser by a web server to record the user’s activity on a particular website. The purpose of cookies is to provide the user with faster access to selected services. Cookies also personalise the services the website offers, facilitating and offering each user information of interest to him, or of potential interest to him, based on his use of the Services offered.

The Website uses Cookies to personalise and facilitate the user’s navigation as much as possible. Cookies are only associated with an anonymous user and their computer, and do not contain any references to the user’s personal data. The user can configure their browser to notify them of the installation of cookies sent by the site and to refuse them, without this affecting the user’s ability to access the contents of the website. However, it should be noted that the functioning of the website may be impaired in this case.

Users who have registered or logged in may benefit from more customised services, tailored to their profiles through, drawing upon the personal data stored in the cookies. Such users expressly authorise the use of this information for these purposes, without prejudice to their right to reject or disable cookies.

Similarly, the website may be aware of all the services requested by users so that it can provide or offer information appropriate to the interests and preferences of each user.

What types of cookies are there?

Cookies can be classified according to how long they are stored:

  • Session cookies: These expire when the user closes the browser.
  • Persistent cookies: These expire when the purpose for which they were used is fulfilled (for example, to keep the user identified across the services) or when they are manually deleted.

Depending on who owns the cookies, they can be classified as follows:

  • First-party cookies: These are sent to the user’s terminal from a device or domain managed by the website owner and from which the service requested by the user is provided.
  • Third-party cookies: These are sent to the user’s terminal from a device or domain that is not managed by the website owner, but by another entity that processes the data obtained through the cookies.

In addition, cookies can be classified according to their purpose:

  • Performance cookies: This type of cookie stores the user’s preferences for the tools found on the site, so that they do not have to reconfigure the service each time they visit. For example, this type includes volume settings for video or audio players.
    Video streaming speeds compatible with your browser.
  • Geo-location cookies: These cookies are used to find out which country you are in when a service is requested. This Cookie is completely anonymous, and is only used to help tailor content to your location.
  • Registration cookies: Registration cookies are generated once users have registered, or subsequently logged in, and are used to identify them in the services for the following purposes:
    • To keep the user identified so that, if he closes a service or website, browser, or computer and later tries to access the service or website again, he will still be identified, thus facilitating his browsing, without him having to identify himself again.
    • This feature is nullified if the user selects the “Log out” function, thereby deleting this cookie. The next time the user enters the service he will have to log in to be identified.
    • To verify whether the user is authorised to access certain services; for example, to participate in a contest.
  • Analytical cookies: Each time a User visits a service, a tool from an external provider generates an analytic cookie on the user’s computer. This cookie is only generated upon the visit, functioning, in future visits, to help Web Services to anonymously identify the visitor. The main objectives to be achieved are:
    • To allow for the anonymous identification of users through “Cookies” (identifying browsers and devices, not people) and, hence, the approximate calculation of the number of visitors, and these trends over time.
    • To anonymously identify the most visited content and, therefore, that most attractive to users.
    • To determine whether the user accessing is a new or returning visitor.
    • Important: Unless the user decides to sign for a service of the website, the “Cookie” will never be associated with any personal data that can identify him. These Cookies will only be used for statistical purposes to help optimise users’ experience on the site.
  • Behaviour-based advertising cookies: These types of “Cookies” make it possible to expand the information of the ads displayed to each anonymous user in the Web Services. Among other things, the duration or frequency of the displaying of advertisements, interaction with them, and browsing patterns and/or user behaviour are stored, among others, as they help to form a profile for advertising purposes. In this way, they make it possible to offer advertising that is tailored to the user’s interests.
  • Third-party advertising cookies: In addition to the advertising managed by the Website through its Services, the Website offers its advertisers the option to place advertisements through third parties (“AdServers”). In this way, these third parties can store cookies sent by the web services from the users’ browsers and access the data stored in them.

What cookies do we use?

The cookies we use on our website are:

First-party:

  • sb_cookie_policy_[guide_id]_[hotel_id] Purpose: Cookie consent options banner. Type: Strictly necessary. Category: First-party. Expiry: 1 year
  • rotate warning Purpose: Device orientation. Type: Preference Category: First-party Expiry: 1 day
  • ba_popup_closed. Purpose: Used to store popup activity. Type: Preference Category: First-party Expiry: 7 days
  • wd_calendar_date_in. Purpose: Stores booking calendar data. Type: Preference Category: First-party Expiration: Persistent
  • wd_calendar_date_out. Purpose: Stores booking calendar data. Type: Preference Category: First-party Expiry: Persistent
  • sb_calendar_room. Purpose: Stores booking calendar data. Type: Preference Category: First-party Expiry: Persistent
  • sb_calendar_now. Purpose: Stores booking calendar data. Type: Preference Category: First-party Expiry: Persistent
  • sb_calendar_destination. Purpose: Stores booking calendar data. Type: Preference Category: First-party Expiration: Persistent
  • sb_calendar_promo_code. Purpose: Stores booking calendar data. Type: Preference Category: First-party Expiry: Persistent
  • event_range_date_to. Purpose: Used to store the dates of events. Type: Preference Category: First-party Expiry: Persistent
  • event_range_date_from. Purpose: Used to store the dates of events. Type: Preference Category: First-party Expiry: Persistent
  • exp_last_activity. Purpose: Motor Expression cookies to track activity on the site when the user is logged in. Type: Functional Category: First-party Expiry: 1 year
  • exp_last_visit. Purpose: Motor Expression cookies to track activity on the site when the user is logged in. Type: Functional Category: First-party Expiry: 1 year
  • exp_tracker. Purpose: Motor Expression cookies to track activity on the site when the user is logged in. Type: Functional Category: First-party Expiry: 1 year

Third-party:

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

How to disable cookies?

It is usually possible to stop accepting browser cookies, or to stop accepting cookies from a particular service.

All modern browsers allow one to change Cookie settings. These settings are usually found in the “Options” or “Preferences” menu of the browser. You can also configure your browser or e-mail manager, in addition to installing free add-ons to prevent Web Bugs from being downloaded when you open an e-mail.

The website provides the user with instructions on how to access the settings menu for cookies and, where applicable, private browsing in each of the main browsers:

  • Internet Explorer: Tools – > Internet Options – > Privacy – > Settings. For more information, consult Microsoft support or browser help.
  • Microsoft Edge: Settings and more – > Settings – > Clear browsing data.
  • Firefox: Tools – > Options – > Privacy – > History – > Custom settings.
  • Chrome: Settings –> Advanced settings – > Privacy and security – > Clear browsing data.
  • Safari: Preferences – > Security. For more information, consult Apple support or browser help.

Can changes be made to the cookie policy?

The website may modify this cookie policy in accordance with legal or regulatory requirements, or to adapt it to instructions issued by the Spanish Data Protection Agency, and users are therefore advised to consult it periodically.

If there are significant changes to this cookie policy, users will be notified either via the website or by email to registered users.