Legal information

Privacy policy

Information about the data processed, its purposes and the rights of FinLeak users.

Last updated: 11 October 2026
Website: https://finleak.eu

This Privacy Policy explains the processing of personal data arising from visits to FinLeak, use of the contact form, emails, website analytics and cookie preferences. The applicable framework includes Regulation (EU) 2016/679 (GDPR), Spain’s Organic Law 3/2018 (LOPDGDD) and relevant rules on electronic communications.

Proposed controller: Xavier Rius Garcia, provided he actually determines and assumes responsibility for the purposes and essential means of processing. Project: FinLeak. Contact: finleak.contact@gmail.com. Controller’s contact address: Castellar del Vallès, carrer tarragona 14, 3 2. Website: https://finleak.eu.

FinLeak is an editorial name, not a separate legal person. If another person actually determines the processing purposes or means, this identification must be corrected before publication.

Browsing and security: technical systems may receive IP addresses, HTTP headers, browser details, date and time, requested resources and other information required to deliver pages or protect the website. Technical log retention follows the criteria in Section 11.

Contact: the form accepts an optional name, an email address, an optional subject and a message. The text may contain additional information voluntarily provided by the sender, and email delivery involves associated metadata. A WordPress security check and an anti-spam honeypot are used.

Consented first-party analytics: random visitor and session identifiers in the browser; server-side events with pseudonymised visitor and session hashes or identifiers, a page path without query parameters, referring domain, device category and timestamp. These are used to measure visits and sessions. See Section 11.

Consented Google Analytics 4: visited pages, enabled interaction events, approximate referral and location information, browser/device characteristics and online identifiers. Google Signals is disabled, but enhanced measurement of pages, scrolls, outbound clicks and form interactions is enabled.

Consent preferences: whether analytics were accepted or refused and the technical data used to remember that preference. This information is used to remember the preference and demonstrate it where required and technically possible.

Purpose Primary lawful basis
Deliver pages, respond to technical requests and maintain service Legitimate interests in operating and protecting the site (GDPR Art. 6(1)(f)), following the appropriate balancing assessment
Prevent abuse, detect failures and secure infrastructure Legitimate interests (Art. 6(1)(f)); legal obligation (6(1)(c)) where a specific legal duty exists
Respond to contact messages Legitimate interests in responding (Art. 6(1)(f)); pre-contractual steps (6(1)(b)) where relevant
Run non-essential GA4 and FinLeak First-party Analytics Consent (GDPR Art. 6(1)(a) and LSSI-CE Art. 22(2))
Record and manage cookie choices Compliance with legal duties when applicable (6(1)(c)), and legitimate interests in technical management (6(1)(f))
Respond to privacy requests and lawful authority demands Legal obligation (Art. 6(1)(c))

A general checkbox acknowledging this policy is not treated as blanket consent for every purpose. Where consent is required, it must be requested separately and may be withdrawn.

To submit an enquiry, visitors must provide an email address and message; the name and subject are optional. Data travel to WordPress over HTTPS, and the configured delivery path uses WP Mail SMTP, a TLS connection to Gmail and the mailbox finleak.contact@gmail.com. The inspected public site has no visitor accounts, comment service or newsletter sign-up. Retention criteria for communications and any related technical records are set out in Section 11.

Please avoid including unnecessary sensitive personal data. Sending an enquiry does not automatically subscribe the sender to marketing messages.

FinLeak uses two analytics systems when the Analytics category is accepted: Google Analytics 4 (measurement ID G-2NX26H4VZ0) and FinLeak First-party Analytics, which records metrics in the WordPress database. Their purpose is to understand visits, page use and overall performance and improve the site.

GA4 currently has 2 months’ event-data retention and 14 months’ user-data retention configured. These settings are not the same as cookie lifetimes or necessarily the retention of aggregated reports. Retention of the first-party analytics database is addressed in Section 11.

The existing configuration initially sets analytics_storage, ad_storage, ad_user_data and ad_personalization to denied. Analytics systems load following the relevant consent choice. Preferences can be changed using the mechanism described in Section 7.

Necessary and language-preference cookies are distinguished from analytics cookies requiring consent. The Cookie Policy identifies observed cookies, providers and lifetimes. Under the current system, visitors can accept, reject or configure analytics and later change their choice through “Configurar cookies” in the footer (translated where available).

The system was tested in fresh, isolated browser contexts on 11 October 2026, across CA/ES/EN/FR: no analytics requests were observed before acceptance or after rejection, and both analytics systems became active after acceptance. On withdrawal, the site saves the rejection, disables GA4, removes analytics cookies and reloads the same page if GA4 was already loaded, to prevent pending transmissions. No new analytics requests after withdrawal were observed in the tested scenarios. These results are not a guarantee for every browser or future configuration change.

Withdrawal does not automatically erase data lawfully collected earlier; applicable data-subject rights may be exercised. The future advertising CMP will require fresh verification.

Under the current configuration described by this policy, Google AdSense is not yet displaying advertisements on the website. Before enabling AdSense, affiliate arrangements or sponsored services, FinLeak will update the information about relevant providers, purposes, lawful bases and required consents. Selling visitors’ personal data is not identified as a FinLeak activity.

OVHcloud supplies server infrastructure and backups; the verified VPS is hosted in Strasbourg, France. Google processes information in connection with GA4 and Gmail, which is used for communications. WordPress is self-hosted website software; using it does not, by itself, mean visitor information is transferred to WordPress.com or Automattic. Providers’ legal roles depend on the particular processing activity.

The current public-site configuration does not use Meta or Pinterest tracking pixels. Technologies specific to administration environments are distinguished in the Cookie Policy. Information may be disclosed to competent authorities where required by law.

Although the verified main hosting environment is in France, Google’s services may involve access to or transfer of personal data outside the European Economic Area. Applicable safeguards depend on the service and may include adequacy decisions, the EU–US Data Privacy Framework where applicable to a particular recipient, standard contractual clauses or other mechanisms permitted by GDPR Articles 44 onward.

Processing is not necessarily restricted to EU territory. Enquiries about available safeguards may be sent to finleak.contact@gmail.com.

First-party analytics (FinLeak First-party Analytics). Individual events are stored with pseudonymised browser and session hashes or identifiers, the visited path, referring domain, device category and timestamp. Records are retained for no more than 90 days per event, with an hourly server maintenance task using an operational cut-off of 89 days. Pseudonymisation does not make these records anonymous.

Monthly statistical summaries. Before individual events are deleted, FinLeak may retain broad monthly counts of page views, sessions and browsers only after assessing re-identification risks. Small groups or revealing breakdowns are combined, rounded or suppressed. Accepted summaries may be retained long term, with an annual review of their necessity and risk; summaries that are not sufficiently detached from identifiable individuals will not be retained indefinitely. Browser counts should not be interpreted as counts of people.

Google Analytics 4. The property is configured for 2 months of event-data retention and 14 months of user-data retention. These settings are distinct from cookie lifetimes and from all aggregated reporting periods.

Contact form and email. Enquiries remain in Gmail for the period required to answer them and, where justified, to handle related issues or legal responsibilities. WordPress sends messages to Gmail; no permanent archive of contact-message bodies was identified in the two proprietary server components examined. No automated Gmail deletion period has been verified, and FinLeak does not claim that messages are deleted after a fixed number of days.

SMTP diagnostics and temporary entries. Email-plugin diagnostic events and errors are subject to a 14-day policy, enforced by server maintenance with a 13-day operational margin. This does not determine the retention of emails held in Gmail. Expired temporary counters related to analytics and contact-form rate limiting are periodically removed.

Server logs. Daily rotation rules have been configured for certain authentication, email and firewall logs. A universal 30-day limit cannot yet be guaranteed: actual retention of older records, Docker, system journal and other general logs has not been fully verified or bounded. Retention follows operational and security needs and is subject to further review and reduction where technically confirmed.

Backups. New manual backups created through FinLeak’s managed backup process automatically expire after 30 days, subject to narrowly justified exceptions. This does not cover the seven legacy backups awaiting classification, backups made outside the managed process, or automatic OVHcloud backups, whose effective deletion windows have not been verified. Backups may retain data for the applicable restoration window; the relevant purge rules must be applied again after restoration.

The finleak_consent cookie lasts 180 days. finleak_analytics_id expires 90 days after issuance, without indefinite renewal through subsequent visits, and the analytics session cookie lasts approximately 30 minutes. Older cookie formats migrate on the next consented visit. Cookie lifetimes are detailed in the Cookie Policy.

Individuals may request access, rectification, erasure, restriction, objection and portability where legally applicable, withdraw consent without retroactive effect and invoke rights concerning solely automated decisions where relevant. Requests should be sent to finleak.contact@gmail.com. Reasonable additional identity verification may be requested where there is genuine doubt. Responses will generally be provided within one month, subject to statutory extensions.

Complaints may be lodged with the Spanish Data Protection Agency (AEPD): https://www.aepd.es.

FinLeak offers public articles without visitor registration and is not specifically designed to collect children’s personal information. No proprietary feature making solely automated individual decisions with legal or similarly significant effects on visitors has been identified. Automated editorial publishing is not, by itself, such a decision. This information will be reviewed if the processing changes.

Proportionate safeguards will be applied, such as HTTPS, access controls and system maintenance. No online service can promise absolute security. Personal-data breaches will be documented and notified where required by GDPR Articles 33 and 34.

This policy will be updated when processing, providers or legal obligations change. Before activating AdSense, FinLeak will include the relevant advertising providers and consent-management arrangements. Dates will be shown and equivalent information will be maintained across Catalan, Spanish, English and French versions.