Cookie Policy
Summary
The adlessio.com website uses no tracking, analytics or advertising cookies. That is why there is no consent banner: under the LGPD and the GDPR, consent is required only for non-essential storage, and we have none.
This policy explains what is actually stored in your browser, why, and how to remove it.
Cookies, localStorage and sessionStorage
The law treats all three the same way — what matters is storing information on the user's device, not the technical mechanism. So we describe all of them here.
- Cookie — a small file sent with every request to the server.
- localStorage — persistent local storage, not sent to the server automatically.
- sessionStorage — the same, but cleared when the tab closes.
What the marketing site stores
Nothing. The adlessio.com pages are static HTML and CSS, with no third-party JavaScript, no tracking pixel, no external fonts and no analytics tool.
What the panels store
The panels at /painel/ and /clients/ require sign-in and store the minimum needed to keep you logged in:
| Item | Where | Purpose | Duration | Category |
|---|---|---|---|---|
| adlessio.user.access | localStorage | Access token authenticating your requests | 30 minutes | Strictly necessary |
| adlessio.user.refresh | localStorage | Token that renews access without asking for your password again | 14 days | Strictly necessary |
| adlessio.staff.access | localStorage | Same purpose, staff panel | 30 minutes | Strictly necessary |
| adlessio.staff.refresh | localStorage | Same purpose, staff panel | 14 days | Strictly necessary |
| adlessio_sessionid | Cookie | Django Admin session (technical administrators only) | Session | Strictly necessary |
| csrftoken | Cookie | Cross-site request forgery protection in Django Admin | 1 year | Strictly necessary |
All are strictly necessary: without them there is no way to keep an authenticated session. None is used for profiling, advertising or audience measurement.
What the extension stores
The extension keeps, in the browser's own storage:
- Device identifier — a random code generated locally, with no personal data, used to enforce the licence device limit.
- Licence state — plan and expiry, cached so it works offline.
- Your preferences — allowlisted sites, active lists and the adjustments you made.
- Blocklists — downloaded periodically and applied locally.
None of this is sent to third parties, and the lists never carry the history of what you visited.
Third-party cookies
There are none. The site loads no scripts, fonts, maps, embedded videos or social media widgets from other domains.
If we ever add a third-party resource that stores non-essential information, this policy will be updated and we will ask for prior consent, with a clear way to refuse.
How to clear
- Chrome / Edge / Brave — Settings → Privacy and security → Clear browsing data.
- Firefox — Settings → Privacy & Security → Cookies and Site Data → Clear Data.
- Safari — Settings → Privacy → Manage Website Data.
Clearing storage signs you out of the panels — you will just sign in again. If you clear the extension's data, the device identifier is recreated; remove the old device in the panel to free the slot.
Questions
Write to [email protected].