Cookies and technologies on the public website
Last updated: 20 July 2026. The inventory describes technologies identified on the public website and separates necessary from optional tools; it will be updated when the services actually in use change.
1. Public information for the early-access website
This page is published for the Accord.ia early-access website. The website does not currently enable checkout, subscriptions, or paid contracts.
Formal company details, including legal name, registered office, VAT number, REA registration, and certified email (PEC), will be added as soon as they are available and confirmed. For website information, contact support@accordia.tech; this is a support channel and is not presented as a PEC address or formal service address.
2. What we mean by cookies and similar technologies
Besides cookies, the website uses or may use local storage, session storage, SDKs, and technical identifiers. Some remember a requested choice; others measure website use and may only be enabled after consent. Server-side logs and emails sent through forms are described for transparency but are not necessarily stored on or read from the terminal.
3. Public website inventory
| Technology | Provider | Category | Purpose and data | Duration | Consent |
|---|---|---|---|---|---|
| NEXT_LOCALE (first-party cookie) | Accord.ia | Necessary / requested preference | remembers selected language; en or it value | 12 months | No, it remembers an explicit choice |
| accordia-analytics-consent-v2 (local storage) | Accord.ia | Necessary for privacy choice | remembers acceptance or rejection of analytics | until the choice changes or site data are cleared | No |
| accordia-country-suggestion-v1 (local storage) | Accord.ia | Functional | remembers that the country/language suggestion was handled | until site data are cleared | No, where used only to remember the choice |
| accordia-newsletter-popup-state-v2 (local storage) | Accord.ia | Functional | remembers dismissal or subscription of the popup | until site data are cleared | No, where used only to remember the choice |
| accordia-display-currency-v1 (local storage) | Accord.ia | Functional | remembers displayed currency; currency code | until changed or site data are cleared | No, where requested by the user |
| accordia-marketing-attribution-v1 and accordia-marketing-attribution-tracked-v1 (session storage) | Accord.ia | Analytics | UTM parameters, click IDs, referrer, and landing page for attribution | browsing session | Yes |
| Amplitude Browser SDK and Session Replay | Amplitude | Analytics / replay | events, pages, pseudonymous identifiers, interactions, and sampled masked replay where enabled | names and durations depend on SDK settings and must be confirmed in the CMP before launch | Yes, before activation |
| Cloudflare Turnstile | Cloudflare | Strictly necessary security | token and technical signals to prevent spam and automated form submissions when a user interacts with a form | short technical duration set by the provider; actual names must be verified in the production inventory | No, where limited to necessary security |
Server-side Sentry may receive runtime errors and technical data. Brevo receives information submitted through forms. These processing activities are described in the Privacy Notice and should not be presented as cookies unless they store or read information on the terminal.
4. Consent and free choice
Non-essential tools remain off on the first visit. Accept and reject controls must be equally visible and easy to use; closing the banner keeps necessary settings. If there is only one optional category, rejecting disables that category entirely.
Browsing and essential content do not depend on accepting analytics. Consent is not inferred from scrolling or continued browsing.
5. Changing or withdrawing a choice
The choice must be available to reopen at any time through a persistent website control. Until that control is complete, users can clear the domain's local storage and cookies in the browser. This technical workaround does not replace the persistent control required for launch.
Withdrawal does not affect processing carried out lawfully before withdrawal. The banner must not repeatedly prompt a user who rejected unless conditions materially change, the choice cannot technically be remembered, or the interval allowed by applicable guidance has elapsed.
6. Third parties and transfers
Amplitude and Cloudflare may process data under their own roles and terms. Settings, region, subprocessors, retention, transfer safeguards, and current notice links must be documented for providers actually in use; this policy will be updated with confirmed information.
7. Browser and device controls
Browsers and devices allow users to delete or block cookies and storage. Blocking necessary technologies may stop the site remembering language, preferences, or security checks. Rejecting analytics does not prevent use of public pages.
8. Updates, contacts, and references
We update the inventory and policy when code, providers, settings, or purposes change. A website and CMP scan must accompany every material change. Formal privacy contacts will be added as soon as the controller details are available and confirmed.
- Article 122 of the Italian Data Protection Code
- Directive 2002/58/EC on privacy and electronic communications
- Italian Data Protection Authority guidelines on cookies and tracking tools dated 10 June 2021
- Regulation (EU) 2016/679 for transparency and consent