Cookie Policy
This document describes which files we store on your device when you visit databridgar.com, what they are for and how you can change your choice at any time. We apply Google Consent Mode v2, so no analytics or advertising cookie activates before you authorise it.
1. What a cookie is
A cookie is a small file that a site saves in your browser to remember information between visits. We also use equivalent technologies, such as local storage (localStorage), which serve the same function and are subject to the same rules described here.
2. Categories we use
We group cookies into three categories. Only the first one activates without your authorisation.
- Necessary — they support the operation of the site: they remember your chosen language, keep your cookie decision and protect the forms against automated submissions. They map to the security_storage and functionality_storage signals of Consent Mode.
- Analytics — they let us understand in aggregate which sections are consulted most and where the wording should improve. They map to analytics_storage. Switched off by default.
- Advertising — they allow us to measure the effectiveness of our outreach campaigns and cap how often you see the same notice. They map to ad_storage, ad_user_data and ad_personalization. Switched off by default.
3. Detail of the main files
- dbdg_consent_v1 (first party, localStorage, 13 months) — stores your category choice and the date you recorded it.
- dbdg_lang (first party, localStorage, 12 months) — remembers whether you prefer the site in Spanish or English.
- _gcl_au (Google, cookie, 90 days) — campaign attribution. Created only if you enable “Advertising”.
- _ga and _ga_* (Google, cookie, 13 months) — aggregated audience measurement. Created only if you enable “Analytics”.
- _gac_* (Google, cookie, 90 days) — links a visit to an outreach campaign. Created only if you enable “Advertising”.
4. Google Consent Mode v2
Before any Google tag loads, the site declares a default consent state in which ad_storage, ad_user_data, ad_personalization, analytics_storage and personalization_storage are set to “denied”, while functionality_storage and security_storage are set to “granted”. A wait_for_update margin of 500 milliseconds is also applied so your choice is registered before any measurement.
In addition we enable ads_data_redaction, which suppresses advertising identifiers while consent is denied, and url_passthrough, which carries campaign information through the URL without writing cookies.
When you accept or save preferences, we run a state update through the consent update command and publish the cookie_consent_update event to the data layer. From that moment, and only for the enabled categories, the Google Ads and GA4 tags may operate in full mode. If you reject, the tags remain in restricted mode and limit themselves to sending aggregated signals without identifiers.
Your choice is stored in your own browser. If you clear the site's local storage or cookies, the state returns to the default denied value and the consent panel appears again on your next visit.
5. How to change your choice
You can change your preferences at any time from the “Cookie preferences” link available in the footer of every page of the site. The change applies immediately, with no need to reload.
You can also block or delete cookies from your browser settings. Bear in mind that blocking necessary cookies may affect how the language switcher and the request form work.
6. Third parties involved
The only third party that may receive data through cookies is Google Ireland Limited (Gordon House, Barrow Street, Dublin 4, Ireland), as the provider of the Google Ads and Google Analytics 4 tags. The information is processed under the terms published by that provider and always within the scope of the consent you have given.
7. Questions
If you need clarification about this document or want the technical detail of a specific cookie, write to us at privacidad@databridgar.com.