Cookie policy

This Cookie Policy explains the use of cookies and similar technologies on www.innovaurbis.com, a website owned by INNOVA URBIS, S.L.

1. What are cookies?

Cookies are small files downloaded to or stored on a user's device when they visit a website. Among other functions, they make it possible to ensure the technical operation of the website, remember preferences, measure website use, integrate third-party content and personalise advertising.

This policy also covers similar technologies, such as identifiers, pixels, tags, local storage and scripts that may access or store information on the device.

2. Who uses cookies?

The website may use first-party cookies, managed directly by Innova Urbis or its technology provider, and third-party cookies, managed by external companies whose services are integrated into the website.

3. Types of cookies used

• Technical or necessary cookies: enable browsing, security, form operation, consent management and access to requested functions. They do not require consent where they are strictly necessary.
• Preference or personalisation cookies: remember choices such as language, region, display settings or the configuration selected by the user.
• Analytics or measurement cookies: provide aggregated information about how the website is used, including visits, pages viewed, performance and errors, and help improve content and services.
• Advertising and marketing cookies: measure campaigns, attribute conversions, limit advertisements, create audiences or display personalised advertising on this website or on other platforms.
• Functional and external-content cookies: enable maps, videos, messaging buttons, anti-spam protection and other third-party services. Some of these services may perform measurement or tracking.

4. Consent and settings

When first accessing the website, users may accept all non-essential cookies, reject them or configure them by category. Analytics, advertising, non-essential personalisation cookies and cookies associated with certain third-party content must not be installed until the user has given consent.

The options to accept and reject cookies must be presented clearly and accessibly. Users may modify or withdraw consent at any time through the permanent “Cookie settings” link available on the website. Withdrawal does not affect the lawfulness of processing carried out before the preference was changed.

The user's choice will be retained for a reasonable period not exceeding 24 months, unless significant changes make it necessary to request consent again.

5. Services and cookies that may be used

The specific cookies installed depend on the user's preferences, the pages visited and the services currently active. The following list identifies cookies and technologies commonly used by providers integrated into the website. Providers may change their names, purposes or durations, and Innova Urbis will therefore review this inventory and the settings panel periodically.

• Innova Urbis / consent management platform — consent cookie.
  Category: necessary.
  Purpose: to retain the user's choice and the categories accepted or rejected.
  Duration: up to 24 months.
• Innova Urbis / web server — session and security cookie.
  Category: necessary.
  Purpose: to maintain the technical session, protect forms and prevent fraudulent requests.
  Duration: session.
• Cloudflare or equivalent security service — __cf_bm.
  Category: necessary.
  Purpose: to distinguish legitimate traffic from automated traffic and protect the website.
  Duration: approximately 30 minutes.
• Cloudflare or equivalent security service — cf_clearance.
  Category: necessary.
  Purpose: to remember that the device has passed a security check.
  Duration: according to configuration.
• Google Analytics 4 — _ga.
  Category: analytics.
  Purpose: to distinguish users and produce usage statistics.
  Duration: up to 2 years.
• Google Analytics 4 — _ga_<ID>.
  Category: analytics.
  Purpose: to maintain session status and measure interactions.
  Duration: up to 2 years.
• Google Analytics — _gid.
  Category: analytics.
  Purpose: to distinguish users for a short period.
  Duration: 24 hours.
• Google Analytics — _gat / _gat_<ID>.
  Category: analytics.
  Purpose: to limit the request rate.
  Duration: approximately 1 minute.
• Google Ads / Conversion Linker — _gcl_au.
  Category: marketing.
  Purpose: to measure conversions and advertising campaign performance.
  Duration: approximately 3 months.
• Google Tag Manager.
  Category: tag management.
  Purpose: to manage the activation of analytics, marketing and other scripts in accordance with consent.
  Duration: it does not normally set cookies by itself.
• Meta Pixel — _fbp.
  Category: marketing.
  Purpose: to identify browsers, measure conversions and create advertising audiences.
  Duration: approximately 3 months.
• Meta Pixel — _fbc.
  Category: marketing.
  Purpose: to retain information about clicks originating from Meta advertisements.
  Duration: approximately 3 months.
• Meta / Facebook — fr.
  Category: marketing.
  Purpose: to deliver, measure and personalise advertising.
  Duration: approximately 3 months.
• Google Maps — NID.
  Category: functional / marketing.
  Purpose: to remember preferences and personalise Google services when maps are displayed.
  Duration: approximately 6 months.
• Google Maps / Google — SOCS.
  Category: functional.
  Purpose: to retain Google consent choices.
  Duration: approximately 13 months.
• Google Maps / Google — CONSENT.
  Category: functional.
  Purpose: to retain Google consent status and preferences.
  Duration: up to 2 years.
• Google Maps / Google — AEC.
  Category: security.
  Purpose: to prevent fraud and ensure that requests are made by the user.
  Duration: approximately 6 months.
• YouTube — YSC.
  Category: functional / analytics.
  Purpose: to record interactions with embedded videos.
  Duration: session.
• YouTube — VISITOR_INFO1_LIVE.
  Category: functional / analytics.
  Purpose: to estimate bandwidth and personalise playback.
  Duration: approximately 180 days.
• YouTube — VISITOR_PRIVACY_METADATA.
  Category: functional.
  Purpose: to retain the user's privacy settings.
  Duration: approximately 180 days.
• YouTube — PREF.
  Category: preferences.
  Purpose: to remember playback and display preferences.
  Duration: approximately 8 months.
• Vimeo — vuid.
  Category: analytics.
  Purpose: to assign an identifier to visitors viewing embedded videos.
  Duration: up to 2 years.
• Vimeo — player.
  Category: preferences.
  Purpose: to retain video-player preferences.
  Duration: up to 1 year.
• Vimeo / Cloudflare — __cf_bm.
  Category: necessary.
  Purpose: to protect the service against automated traffic.
  Duration: approximately 30 minutes.
• Vimeo — continuous_play_v3.
  Category: preferences.
  Purpose: to remember continuous-playback preferences.
  Duration: up to 1 year.
• Google reCAPTCHA — _GRECAPTCHA.
  Category: necessary / security.
  Purpose: to protect forms and detect automated or abusive activity.
  Duration: approximately 6 months.
• Google reCAPTCHA — rc::a.
  Category: necessary / security.
  Purpose: to analyse behaviour in order to distinguish people from automated systems.
  Duration: persistent.
• Google reCAPTCHA — rc::b / rc::c.
  Category: necessary / security.
  Purpose: to detect bots and protect forms during the session.
  Duration: session.
• WhatsApp — WhatsApp link or widget.
  Category: functional.
  Purpose: to allow the user to start a conversation. Where a simple link is used, Innova Urbis does not set WhatsApp cookies before the click; Meta's policies apply once the user accesses the service.
  Duration: according to the service.
• CRM and forms — technical CRM identifiers.
  Category: necessary / functional / analytics.
  Purpose: to manage forms, enquiries, commercial follow-up and attribution, depending on the provider's configuration.
  Duration: according to the provider.
• Google Fonts or other external fonts.
  Category: functional.
  Purpose: to load typefaces and graphic resources. The user's IP address may be communicated to the provider where resources are not hosted locally.
  Duration: these services do not normally set cookies.

6. Third-party content

Maps, videos, messaging buttons, social networks, form-protection systems and other external content may allow the third party to collect information about browsing activity, particularly where the user is logged into that service. Where the content is not strictly necessary, it will be blocked until the user accepts the relevant category or expressly requests that the content be loaded.

7. International transfers

Some providers may process information outside the European Economic Area. In such cases, the safeguards described in the Privacy Policy will apply, including adequacy decisions, valid participation in the EU-US Data Privacy Framework, Standard Contractual Clauses or other mechanisms provided for by the GDPR.

8. Deleting or blocking cookies through the browser

In addition to the website settings panel, users can allow, block or delete cookies through their browser settings. Blocking strictly necessary cookies may prevent some pages, forms or security measures from operating correctly.

• Google Chrome: Settings > Privacy and security > Cookies and other site data.
• Microsoft Edge: Settings > Cookies and site permissions > Manage and delete cookies.
• Mozilla Firefox: Settings > Privacy & Security > Cookies and Site Data.
• Safari: Settings or Preferences > Privacy > Manage Website Data.

The menu paths may change when browsers are updated. Users are advised to consult the relevant official help centre.

9. Policy updates

This Cookie Policy may be amended when the cookies used, providers, website functionalities, guidance from supervisory authorities or applicable legislation change. Users are advised to review it periodically.

10. Contact

For questions about the use of cookies, please contact Innova Urbis at info@innovaurbis.com.