Cookie Policy - publica.la

This page explains the cookies and similar technologies used on publica.la (the "Site"), why we use them and how you can control them. For full details on how we process personal data, see our Privacy Policy.

What are cookies?

Cookies are small text files that a site places on your device when you visit. They are widely used to make sites work, to make them work more efficiently, and to provide information to the site owner. We also use similar technologies such as local storage and pixels.

Your choices

Nothing that is not strictly necessary is loaded, sent or stored until you choose: no analytics tag, no request to Google or Microsoft, and no note about your visit in your browser. If you never answer the cookie banner, that is a no. You can change your mind at any time using the button, also available in the footer of every page. Withdrawing deletes what was stored under that choice from this browser.

Categories we use

1. Strictly necessary

Required to operate the Site or a service you asked for. These do not require consent.

publicala_session — Laravel session identifier, on the pages that carry a form.
XSRF-TOKEN — protection against forged form submissions.
publicala-consent — stores your cookie preferences (180 days).
rondine_device — set only when you run one of the free tools: a random identifier that limits each free tool to one run per device (2 years).
pla.intent.* (local storage) — remembers for a week that you closed an announcement, so it does not open again.

2. Analytics (consent required)

Help us understand how visitors use the Site so we can improve it. Disabled by default.

Google Analytics 4 (_ga, _ga_*) — aggregate traffic, sessions, page views. The Google tag is not loaded until you accept. IP is truncated; advertising signals are disabled.
Microsoft Clarity (_clck, _clsk, CLID, MUID) — anonymised session replay (mouse, scroll, clicks). Sensitive form fields are masked.
Ahrefs Web Analytics — page view counts. It sets no cookies, and its script is still loaded only after you accept.
publica.la: your visit (session storage, pla.track.*) — where you came from, the page you landed on, the pages you read and the campaign tags in the link. It stays in your browser and is deleted when you close the tab; we receive it only if you send us a form. Without consent, a form tells us only the page it was sent from and the campaign tags in that page's address.

3. Remembering you (consent required)

rondine_lead — if you fill in a form, an encrypted identifier of the email address you entered, so that we do not ask for your details again next time (1 year).

Embedded content

Booking calendars and registration forms are served from crm.publica.la, our own system, and follow this policy. The Site embeds no third-party video or content.

We use Google Consent Mode v2 with every signal set to denied by default, and the Google tag itself waits for your consent: before you accept analytics, no request reaches Google, including the "cookieless pings" Consent Mode can otherwise send. Advertising signals stay denied even after you accept.

Retention

Your consent decision is stored for 180 days. After that period — or if you clear your browser data — the banner is shown again. Analytics cookies have their own retention defined by Google (up to 2 years for _ga) and Microsoft (up to 1 year for Clarity). The record of your visit is deleted when you close the tab, rondine_lead after 1 year and rondine_device after 2 years.

Your rights

Under the GDPR (EU/UK), LGPD (Brazil), CCPA (California) and other applicable laws, you have the right to access, rectify, erase, restrict or object to the processing of your personal data, and to data portability. To exercise any of these rights write to [email protected].

Updates

This Cookie Policy may be updated to reflect changes in our practices or regulatory requirements. Last updated: November 2026.