Version 1.0 · Last updated: August 2026
1. Controller
This Cookie Policy applies to the website yolisto.app, operated by CIIGMA TECHNOLOGIES S.L., Tax ID (NIF) B26584524, with registered office at Paseo de Recoletos 5, 28004, Madrid (Spain), registered with the Commercial Registry of Madrid, sheet M-876098. Contact: legal@yolisto.app.
2. What cookies are
Cookies are small text files that websites store in the user's browser or device when they visit. Among other things, they allow the site to work properly, remember preferences, or collect statistical information about how the site is used. In this policy, the term "cookies" also covers similar technologies, such as browser local storage or equivalent identifiers.
3. Which cookies Yolisto uses
Yolisto only uses the following categories of cookies:
3.1 Technical or essential cookies
These are necessary for the Platform to work: for example, they keep users logged in to the Agency dashboard, remember the selected language, or help secure the service. These cookies are exempt from consent under Article 22.2 of the Spanish LSSI-CE, as they are strictly necessary to provide the service requested by the user.
3.2 Analytics cookies and technologies
These are used to measure, in aggregate, how the Platform is used (pages visited, traffic sources, performance) in order to improve it. [Confirm after technical audit which tools are active: Vercel Analytics and/or Google Analytics 4.]
- [If Vercel Analytics is active: this tool does not use cookies or persistent browser identifiers; it collects aggregated, anonymized metrics.]
- [If Google Analytics 4 is active: this tool uses cookies set by Google and will only load if the user has given prior consent through the cookie banner.]
3.3 Cookies we do NOT use
Yolisto does not use advertising cookies, behavioral advertising cookies or commercial profiling cookies, and does not sell browsing data to third parties.
4. Cookie table
[Table to be completed after the technical audit of the site. Keep it updated whenever tools change.]
| Cookie | Provider | Type | Purpose | Duration |
|---|---|---|---|---|
| [session/authentication cookie name] | Yolisto (first party) | Technical | [Keep registered users logged in] | [Session / duration] |
| [language preference cookie, if any] | Yolisto (first party) | Technical | [Remember the ES/EN language choice] | [duration] |
| [consent banner cookie, if any] | Yolisto (first party) | Technical | [Remember the user's cookie choice] | [duration] |
| [_ga, _ga_XXXX, only if GA4 is active] | Google (third party) | Analytics | [Aggregate usage statistics] | [duration per audit] |
5. Legal basis and consent
Technical cookies are used on the basis of Article 22.2 of the Spanish LSSI-CE and do not require consent.
Non-essential cookies (such as cookie-based analytics) are only set if the user has given prior consent through the cookie banner shown on the first visit. Until the user accepts, those cookies are not loaded. Rejecting them does not prevent normal use of the Platform.
6. How to manage or withdraw consent
At any time, users can:
- Change their choice through the Platform's cookie settings panel, available at [footer link "Cookie settings", pending implementation].
- Delete or block cookies from their browser. Instructions are available in each browser's help pages (Chrome, Safari, Firefox, Edge). Please note that blocking technical cookies may affect how the site works.
Withdrawing consent does not affect the lawfulness of processing carried out before such withdrawal.
7. International transfers
[Only if GA4 or another third-party tool is active:] Some analytics providers may process data on servers located outside the European Economic Area, in particular in the United States. In that case, the transfer relies on the adequacy decision under the EU-US Data Privacy Framework for certified providers and, failing that, on standard contractual clauses. More information is available in the Privacy Policy.
8. Updates to this policy
We may update this Cookie Policy when the tools used or the applicable regulations change. The version in force will always be the one published on the Platform, together with its update date.