Skip to main content
Legal information

Cookie policy

Ajuridic uses Cloudflare Web Analytics to measure page performance. This measurement does not install analytics or advertising cookies.

Last updated: 8 October 2026.

Summary

ajuridic.com uses Cloudflare Web Analytics to measure technical page performance using browser metrics. Cloudflare states that this service does not use cookies or collect personal data from website visitors. We do not use advertising or social media cookies, advertising pixels or browser fingerprinting techniques.

1. What a cookie is

A cookie is a small file that a website saves in the browser of whoever visits it. It serves to recognise that browser on later visits: remembering a logged-in session, a chosen language or, in the case of advertising cookies, following a person's trail across different sites in order to show them adverts.

Their use is governed by article 22.2 of Ley 34/2002, on information society services and electronic commerce, which requires information to be given and consent obtained before installing any cookie that is not strictly necessary.

2. Cookie-free performance measurement

The website uses Cloudflare Web Analytics, a performance measurement service that collects page-load and page-experience metrics through browser performance APIs. According to Cloudflare's documentation, it does not use cookies or collect visitors' personal data. The service sends metrics to Cloudflare's measurement endpoint. See the data collection documentation.

Accordingly, this website does not use:

  • analytics cookies: Cloudflare performance measurement runs without cookies;
  • advertising, remarketing or targeting cookies;
  • social media cookies or share buttons that install them;
  • advertising pixels or cross-site tracking beacons;
  • techniques of fingerprinting or browser fingerprinting;
  • videos, maps or embedded third-party content acting as trackers.

The performance measurement described above does not install cookies. This notice describes the service's technical operation and is not a substitute for advice about the legal obligations that apply to each technology.

3. Technical storage

The site does not use cookies, but it does store a few things in the browser's own storage (localStorage and sessionStorage). These are not cookies: they are not sent to the server with every request, they cannot follow anyone from one website to another, and they are not used for advertising or audience measurement. These are the only ones:

  • The conversation with GorIA, the chat assistant, so that it is not lost when you move between pages, and a note that its greeting has been seen. Both are deleted when you close the tab.
  • The boxes ticked in the document checklists in the tools, so that they stay ticked when you come back. They remain in the browser until they are cleared from the list itself.
  • What you answered in the case guide, so that you reach the form without having to repeat it. It is deleted when you close the tab and, in any event, after half an hour.

The data stored in the local browser storage described above does not leave the browser unless the visitor submits a form. Separately, Cloudflare receives the performance metrics described in the previous section.

Two technical elements may be involved, and they are worth explaining, because they do not depend on an editorial decision by the firm:

  • Server logs. Like any web server, the one hosting this site records the requests it receives (IP address, date, page requested, type of browser). These are technical logs needed in order to provide the service and detect security incidents, not cookies, and they are not used to build profiles or cross-referenced with any other data.
  • Network and security provider. If the site is served through a content delivery network with protection against attacks, that infrastructure may install a strictly necessary cookie to tell legitimate traffic from automated traffic. This type of cookie is exempt from the consent requirement under article 22.2 of the LSSI-CE, does not identify the person and is not used for advertising or analytics purposes.

4. Typefaces and other external resources

The site's typefaces are loaded from Google's fonts service. That service installs no cookies, but in order to deliver the file it needs to know the IP address of the browser requesting it, as happens with any resource served from another domain.

Anyone who prefers to avoid that connection altogether can block external font domains in their browser: the site will still be perfectly legible, it will simply be shown with the system typefaces.

5. Outbound links

Clicking a link that leads away from ajuridic.com, to an official gazette, to the Bar Association, to WhatsApp or to noemiampurdanes.com, takes you to a site with its own rules. Those pages may indeed use cookies, and how they handle them is outside the firm's control. It is worth consulting their own policy.

6. How to check it

This statement can be verified without taking anyone's word for it: just open the browser's developer tools (usually with the F12 key), go to the storage or application tab and look through the list of cookies for the domain.

And if you ever want to delete the cookies from any site, every browser allows this from its privacy settings, as well as offering private browsing modes that discard them when the window is closed.

7. If this were to change

If in future the firm were to bring in a tool requiring cookies, this page would be updated before it was activated and the corresponding notice would be shown to obtain prior consent, with the ability to refuse it just as easily as to accept it.

How the data that is collected (from the form, the email and the telephone) is handled is explained in the privacy policy. The identifying details of the site's owner are set out in the legal notice.

First consultation

Speaking to the firm leaves no trace

A call or an email is enough to find out what scope there is in a matter and what time limits are running.

Call WhatsApp Appointment