Last updated: 11 October 2026
Website: https://finleak.eu
1. What are cookies?
Cookies are small files or identifiers stored by a browser to remember preferences, enable functions or measure visits. Some identifiers can distinguish visitors and qualify as personal data. FinLeak distinguishes necessary and preference cookies from non-essential analytics technologies requiring consent under Article 22(2) of Spain’s LSSI-CE and, where applicable, the GDPR.
2. Categories
- Technical and consent-management cookies: support essential functions and remember privacy choices.
- Preference cookies: remember the selected language through Polylang, where the legal conditions for an exemption from consent apply.
- First-party analytics: measure visits and sessions using FinLeak First-party Analytics after consent.
- Google Analytics: assess website usage through Google Analytics 4 after consent.
- Advertising: Google AdSense is planned but advertising is not yet active under the current configuration.
3. Cookies identified on the public site
| Name | Service | Purpose | Lifetime | Category |
|---|---|---|---|---|
finleak_consent |
FinLeak | Remember analytics acceptance/refusal | 180 days | Consent management |
pll_language |
FinLeak / Polylang | Remember the selected language | 1 year | Preferences |
finleak_analytics_id |
FinLeak First-party Analytics | Random persistent visitor identifier | 90 days from issuance; not renewed by activity | Analytics |
finleak_analytics_session |
FinLeak First-party Analytics | Analytics session identifier | 30 minutes, renewed on consented activity | Analytics |
_ga |
Google Analytics 4 | Distinguish visitors or browsers | 2 years by default, subject to browser limits | Analytics |
_ga_2NX26H4VZ0 |
Google Analytics 4 | Maintain analytics session state | 2 years by default, subject to browser limits | Analytics |
An effective lifetime of 400 days was observed for both Google cookies in Chrome. Other browsers and later configurations may enforce different limits. Cookie expiration should not be confused with server-side data retention.
4. Analytics data
With analytics consent, FinLeak First-party Analytics uses random browser and session identifiers, the page path without query parameters, referring domain, device category and time. Individual server-side events with pseudonymised (hashed) identifiers are kept for no more than 90 days and are purged through hourly maintenance; hashing does not, on its own, make them anonymous. Monthly protected summaries without individual visit details may be retained long term only after assessing re-identification risk.
Google Analytics 4 may process viewed pages, enabled events and browser/device information. The property is configured for 2 months of event-data retention and 14 months of user-data retention, separate from cookie lifetimes. See the Privacy Policy.
5. How is consent requested?
The current interface offers Accept, Reject and Configure, with Necessary and Analytics categories. All four Google Consent Mode v2 states initially default to denied; GA4 and first-party analytics are not loaded until express acceptance. Silence and continued browsing do not constitute consent. Accepting and rejecting should be equally accessible.
Network tests in fresh isolated browsers on 11 October 2026, across CA/ES/EN/FR, observed no analytics requests before acceptance or after rejection in the tested scenarios. Introducing AdSense will require a newly verified advertising CMP.
6. Changing or withdrawing preferences
The footer’s “Configurar cookies” link (translated where available) lets users withdraw or renew analytics consent. On withdrawal, the choice is saved as rejected, GA4 is disabled, analytics cookies are removed and, if GA4 has already loaded, the same page reloads automatically to discard pending events. The isolated-browser checks in CA/ES/EN/FR observed no further analytics requests after withdrawal in the tested scenarios; re-acceptance reactivates both analytics systems.
Visitors can also remove cookies through their browsers. Withdrawal does not automatically delete data lawfully collected earlier; data-subject rights may be exercised separately. These findings apply to the current setup and will need revalidation when the CMP changes.
7. Providers and further details
The identified services are FinLeak’s own analytics and Google Analytics 4. Google’s information: https://policies.google.com/privacy and https://policies.google.com/technologies/partner-sites. See the Privacy Policy for purposes, legal bases and international transfers.
8. Administration and subdomains
WordPress may set authentication and preference cookies for administrators, which should not be attributed to anonymous public visitors. PostHog and RudderStack were observed in the private environment at n8n.finleak.eu; some related cookies use .finleak.eu and may therefore be visible on the main domain even if generated within n8n. It has not been established that public pages set these trackers in fresh visitors’ browsers.
9. Future advertising and CMP
The current public-site configuration does not yet load AdSense advertisements. Before ads are activated, this inventory will be updated and an appropriate Google-compatible consent management platform and transparency framework will be implemented, without contradictory duplicate banners. Users will be informed of vendors, purposes and withdrawal options.
10. Contact and rights
For questions or requests regarding personal data: finleak.contact@gmail.com. Controller identification and further rights information are set out in the Privacy Policy.
11. Updates and languages
This policy will be updated as technologies, suppliers or purposes change. Its Catalan, Spanish, English and French versions will describe equivalent practices, cookies and rights.