Cookie Policy
Cookie Policy
Last updated: 25 agosto 2026
Courtesy translation. This is an English translation of a document originally written in Italian, provided to make it readable. The Italian version is the binding one: in case of any discrepancy between the two texts, the Italian text prevails.
This page describes the use of cookies and similar technologies on the Social Web Automation website, in line with the Italian Data Protection Authority’s cookie guidelines of 10 June 2021 and the ePrivacy Directive.
1. What cookies are
Cookies are small text files that websites save on the user’s device. They divide into technical cookies (necessary for operation, no consent required) and profiling or marketing cookies (requiring explicit prior consent).
2. Cookies used by this site
| Cookie | Type | Purpose | Duration | Consent |
|---|---|---|---|---|
| next-auth.session-token | Technical | User authentication (dashboard login) | Session / 30 days | Not required |
| next-auth.csrf-token | Technical | Anti-CSRF protection | Session | Not required |
| active_cliente_id | Technical | Active client / workspace (multi-tenant) | Session | Not required |
| cookie_consent | Technical | Stores your cookie choice | 6 months | Not required |
Technical cookies are always active because they are necessary. Marketing cookies are loaded only after explicit consent through the banner, and serve Meta Pixel and the Conversions API.
No marketing cookie is active on this site. We do not load the Meta pixel or any other advertising script, so the _fbp and _fbc cookies are never set. The consent we ask for in the banner is not about cookies: it is about campaign measurement, described under point 3.
3. Third parties and campaign measurement
The site loads no third-party script: no analytics tool, no advertising pixel, no embedded content. That is a choice, not an omission: an external script sees everything you do on the page, and measuring a campaign does not require it.
When an advertising campaign is running, and only if you have given marketing consent, our server sends Meta two events: a consultation request and the start of a purchase. The communication leaves from the server, not from your browser. The email address and phone number are transmitted hashed with SHA-256 — Meta never receives the values in clear text — together with the IP address, the browser type and the amount of the transaction.
Without your consent nothing is sent: the control is in the code, not only in the intention. If you withdraw consent, the sending stops. The detail of the processing is in the Privacy Policy.
4. Managing consent
You can change or withdraw your preferences at any time through the cookie banner (which reappears on withdrawal) or by deleting cookies from your browser settings. Disabling technical cookies may break the dashboard — for example, you may not be able to stay signed in.
5. How to manage cookies from your browser
6. Controller and contact
For any request about cookies: swsdautomation@gmail.com. See also the Privacy Policy.