Strictly necessary
No application cookie is currently set by the site source. If the production host later requires a genuinely necessary technical cookie, it must be documented here with its purpose and retention.
Privacy and consent
Cookie policy
Information about cookies, local storage and similar technologies on ILS Tenerife.
- Spain-Licensed Attorney · ICATF nº 5961
- Spanish · English · Romanian
- Las Chafiras · Tenerife South
- Online service where appropriate
Current website state
No analytics or marketing cookies are active in the current build
The current ILS website does not set application cookies, localStorage or sessionStorage, and it does not load GA4, Google Tag Manager, advertising pixels, embedded maps or other non-essential third-party scripts. Google Maps and Bing Maps are ordinary outbound links and load only after the visitor chooses to follow them.
Because there are no optional cookie categories to accept in this build, no consent banner is displayed. Showing an accept/reject banner for technologies that are not present would not reflect the real processing architecture.
The final production host must still be checked before launch for any infrastructure-level cookie or similar storage that is not created by the repository itself.
Categories
Current consent matrix
Analytics
Inactive. GA4 and similar analytics are not implemented.
Marketing / profiling
Inactive. No advertising pixel or marketing tracker is implemented.
Cookie settings
There is currently nothing optional to enable, disable or revoke
The settings link remains permanently available so this page is the stable control point. If optional technologies are added later, this section must expose a real accessible preference panel that allows refusal and later withdrawal as easily as acceptance. Preferences must be stored without fingerprinting and only for the period justified by the consent architecture.
Future CMP contract
What must happen before any non-essential technology is introduced
- Block analytics, marketing and non-essential embeds before the applicable consent.
- Offer accept and reject at the same time, level and visibility, with granular purposes where needed.
- Keep a persistent way to change or withdraw the choice; do not rely on browser settings as the only withdrawal mechanism.
- Store only the consent state needed for proof and preferences—such as policy version, categories and timestamp—without fingerprinting.
- Re-request a choice when purposes or relevant third parties change. As an AEPD good-practice ceiling, consent should not be treated as valid indefinitely and should be renewed at least every 24 months.
Google Consent Mode is not implemented. If GA4 is expressly authorised in a future sprint, Consent Mode may be evaluated only after a separate legal and technical review; it does not replace the need for a valid consent architecture where consent is required.