Cookies Policy
The exact list of cookies and browser-storage entries we use, and how to control them.
What we store on your device
Tenerife Live keeps its on-device footprint deliberately small. We do not run advertising trackers, retargeting pixels, social-media widgets that read cookies, heatmaps, or session-replay tools. The list below is exhaustive — if a row is not on this page, we are not storing it on your device.
Strictly necessary
Cannot be disabled because they are required for the site to function. Today this category contains exactly one entry: the record of your cookie choice itself.
| Name | Provider | Storage | Duration | Consent | Purpose |
|---|---|---|---|---|---|
| tm.cookie-consent.v1 | Tenerife Live (first-party) | localStorage | 12 months from last write | No (essential) | Remembers your cookie choice so the banner does not reappear on every visit. Contains only the category decision and a timestamp — no personal data. |
Analytics (optional)
Loaded only after you click Accept optional. These help us understand which pages and events are popular so we can prioritise editorial work.
| Name | Provider | Storage | Duration | Consent | Purpose |
|---|---|---|---|---|---|
| _ga, _ga_<container-id> | Google Analytics 4 | Cookies | Up to 24 months | Yes | Distinguishes unique visitors and sessions. Loaded only after you opt in. IP anonymisation and ad-data redaction are forced on. |
| Vercel Analytics ping | Vercel Inc. | Network request only | No persistent client storage | Yes | Aggregated page-view counts for the operator. Loads only after you opt in. |
| Vercel Speed Insights ping | Vercel Inc. | Network request only | No persistent client storage | Yes | Real-user performance metrics (Core Web Vitals). Loads only after you opt in. |
Categories we do NOT use
- Advertising or marketing cookies
- Retargeting / personalisation pixels (Meta, TikTok, Google Ads, etc.)
- Social-media share widgets that set cookies
- Heatmaps or session-replay (Hotjar, Microsoft Clarity, FullStory, etc.)
- Cross-site fingerprinting identifiers
- A/B-testing or feature-flag SDKs that store identifiers
If this changes in the future we will update this page and re-prompt you for consent before the new category loads.
Outbound links and the redirect endpoint
Ticket and tour buttons go through /api/out/<provider>, a server-side redirect to allow-listed partners (Ticketmaster, GetYourGuide, Tiqets, Klook). The redirect logs click metadata (provider, content id, surface) on the server only — it does not write a cookie or browser-storage entry on your device and does not collect your IP or User-Agent. Once you reach the partner website, that website's own cookie policy applies.
Maps
On pages that show a map (venues map, venue detail) we render Mapbox GL JS to draw vector tiles. Mapbox may cache map tiles in your browser's sessionStorage / IndexedDB for performance. No personal identifier is set by us and Mapbox telemetry is treated as functional storage strictly necessary to render the map you asked to see. Pages without a map do not load Mapbox.
Changing or withdrawing your choice
You can change or withdraw your consent at any time:
- Use the Cookie settings link in the footer of every page.
- Or clear the tm.cookie-consent.v1 entry in your browser's site data.
- Or use your browser's built-in cookie / storage controls.
Questions about cookies?
If you have any questions about this policy, please contact us.
Last updated: 2026-05-16