TRANSFERBCN / LEGAL INFORMATION
Cookie Policy
Information about browser storage, optional tracking and your choices.
This page requires client and legal review. Bracketed instructions identify information that must be completed or confirmed. Effective date: 1st August 2026.
1. What cookies and similar technologies are
Cookies are small pieces of information stored by a browser. Similar technologies can include local storage, pixels and scripts that access information on a device. They can support site functions, remember choices or measure activity.
This policy must describe the technologies actually used on transferbcn.es. [COMPLETE: legal entity responsible for the site and policy effective date.] Contact: info@transferbcn.es.
2. Necessary technologies
Some storage or access can be strictly necessary to transmit a communication or provide a service you expressly request. Examples can include maintaining a requested session or remembering a consent choice, depending on the implementation.
[AUDIT REQUIRED: identify the actual necessary technologies and explain why each is necessary.] A technology is not exempt from consent merely because it is useful to the business or installed by a plugin.
3. Preferences, analytics and advertising
Preference tools can remember optional settings. Analytics can measure use of the website. Advertising technologies can measure campaigns, build audiences or personalise advertising.
These are category descriptions, not a declaration that all are installed. [CONFIRM: which categories and tools are active, their purposes and the consent required.] Non-essential technologies must not activate before valid consent where consent is required.
4. Your choices
Where optional technologies are used, the consent interface should let visitors accept, reject or choose categories through clear controls. Rejecting optional cookies should be as easy as accepting them.
[IMPLEMENT AND VERIFY: consent interface, equal prominence of accept/reject choices, category controls, prior blocking and a persistent way to reopen preferences.] Continuing to browse is not itself consent. This page does not activate a consent manager.
5. Cookie and storage inventory
[REPLACE WITH THE VERIFIED AUDIT INVENTORY BEFORE PUBLICATION.] For every actual cookie or similar technology, list its name or identifier, provider and domain, purpose, category, first- or third-party status, duration and whether consent is required.
Audit an initial visit, acceptance, rejection, booking, embedded content and any logged-in functions separately. No named cookie is asserted in this draft because the live browser storage and scripts have not been inspected.
6. Third-party services and embedded content
External maps, videos, payment tools, chat or other embedded services can involve device storage or third-party requests, depending on how they are implemented.
[COMPLETE: actual third-party services, their technologies, durations and privacy information.] Consent-dependent embeds must be controlled accordingly. A normal external link and an embedded tracker should not be treated as the same thing.
7. Withdrawing consent and browser settings
You should be able to reopen preferences and withdraw optional consent as easily as it was given. Withdrawal does not affect the lawfulness of earlier consent-based processing.
[CONNECT: the actual persistent cookie-preferences control and document its location.] Browser settings can also restrict or delete cookies. Removing necessary cookies may affect requested site functions. Browser deletion alone does not necessarily withdraw a consent record held elsewhere.
8. Duration, recipients and transfers
Cookie lifetimes, renewal rules and consent-record retention must reflect the implemented tools. Some browser storage persists until removed rather than expiring like a cookie.
[COMPLETE: each duration, consent-review approach, recipients, international transfers and applicable safeguards.] Related personal-data handling is described in the Privacy Policy.
9. Policy updates and contact
Update this inventory when technologies, providers or purposes change, and obtain fresh consent where the change requires it. State the effective date of the published policy.
For questions, contact info@transferbcn.es. This draft follows the structure of a site-specific notice; it must be matched to the live consent configuration before use.