Cookie policy
What we measure, and what doesn't run until you say yes
This page lists everything that's actually installed, including whatever records your browsing. A notice that forgets a tool isn't incomplete: it's false.
In brief
- Before you choose, no measurement tool writes a cookie. Google Analytics and Google Ads start in cookieless mode; Meta and LinkedIn aren't loaded at all.
- "Reject all" and "Accept all" carry the same weight in the banner: same size, same position, same colour. Rejecting must not cost more than accepting.
- You can change your choice at any time from the Cookie preferences link at the bottom of every page.
- We don't use an external consent platform: the banner is ours, it runs on this domain and sends data to no one.
What cookies are, and who sets them
A cookie is a tiny text file that a site saves in your browser and can read again on later visits. It's used to recognise the browser — not the person — and to remember something from one page to the next.
- First-party cookies
- Set by this site, on the segnalazionevincente.com domain. The cookie that stores your choice about cookies is of this kind.
- Third-party cookies
- Set by another domain — Google, Meta, LinkedIn, Microsoft — when you load their tool. These are the ones that follow the browser from one site to another, and they're the reason consent exists.
Alongside cookies we use technologies that work the same way and fall under the same rules: identifiers in the browser's local storage, tracking pixels and measurement scripts. When this page says "cookie" it means all of these technologies.
How consent works here
The mechanism is the kind you can verify, and it's worth explaining because how it's built says more than any statement of intent.
- As soon as the page opens, the site declares to the tag manager that all consents are denied — statistics, advertising, personalisation. That's the starting state, even before the banner appears.
- The tag manager (Google Tag Manager, container GTM-TWL4LFR7) loads, but doesn't write its own cookies and holds back every tool that requires a consent you haven't given.
- Tools that don't know how to obey that signal — Meta and LinkedIn — aren't even downloaded: before consent, not a single request goes out to their servers.
- When you choose, the choice is written into the sv_consent cookie on this domain and applied immediately. On your next visit it's read again before any tool runs.
What happens anyway, even without consent
This needs to be said, because it's the only thing that moves before your choice. Google Analytics 4 and Google Ads send Google cookieless signals (consent mode): nothing is saved in your browser, there's no identifier following you from one visit to the next, and the data lets Google statistically estimate overall traffic. Your IP address is still transmitted and processed in that exchange. If you'd rather avoid even this, browser ad-blockers and script-blocking extensions stop the tag manager from loading at all.
The three categories
- Necessary — always active
- Make the site work and store the choice you're making. They can't be switched off and they don't measure anything.
- Statistics — off until you consent
- Count how many people read which pages, and where they come from.
- Marketing — off until you consent
- Measure advertising campaigns and let us reach you again with relevant ads.
Necessary cookies
These don't require consent because without them the service you asked for doesn't work. There's only one, and it's the cookie that remembers your answer to this banner: without it, the banner would reappear on every page.
| Name | Who sets it | What it's for | Duration |
|---|---|---|---|
| sv_consent | This site (first party) |
Stores your choice on the categories, the date you made it and the version of the tool list it refers to. It's also the proof of consent we're required to be able to show | 180 days |
The tag manager (Google Tag Manager) loads on every page but doesn't set its own cookies: it's the system that decides which tools can run, not a measurement tool itself.
Statistics
| Name | Domain | What it's for | Duration |
|---|---|---|---|
| _ga | First party | Distinguishes one browser from another to count visitors | 2 years |
| _ga_ZX7W1SNQ53 | First party | Maintains the browsing session state | 2 years |
Purpose: understanding how many people read which pages, where they come from and which paths work. The tag is configured inside the GTM container and isn't repeated on the page.
Marketing
These are the tools that measure advertising campaigns and let us show you an ad again after you've visited the site. None of them runs without "Marketing" consent.
| Name | Domain | What it's for | Duration |
|---|---|---|---|
| _gcl_au | First party | Links the visit to the ad you arrived from, to attribute conversions | 90 days |
| IDE, test_cookie and others | doubleclick.net google.com (third party) |
Google's advertising cookies for remarketing and measurement. Set by Google's advertising services at the moment of consent | Up to 13 months, per the durations Google declares |
| Name | Domain | What it's for | Duration |
|---|---|---|---|
| _fbp | First party | Identifies the browser to measure campaigns on Facebook and Instagram and to show you relevant ads | 3 months |
| _fbc | First party | Stores the ID of the ad you clicked, when you arrive from a Meta ad | 3 months |
| Name | Domain | What it's for | Duration |
|---|---|---|---|
| bcookie | linkedin.com (third party) |
Browser identifier, used by LinkedIn for site functions and advertising | 1 year |
| bscookie | linkedin.com (third party) |
Security and verification of LinkedIn authentication | 1 year |
| li_sugr | linkedin.com (third party) |
Probabilistic matching of the browser to a profile | 90 days |
| UserMatchHistory | linkedin.com (third party) |
Synchronisation of LinkedIn advertising identifiers | 30 days |
| AnalyticsSyncHistory | linkedin.com (third party) |
Records when the last sync happened | 30 days |
| lidc | linkedin.com (third party) |
Technical routing to the LinkedIn data centre | 1 day |
| li_gc | linkedin.com (third party) |
Stores the consent given to LinkedIn on the use of non-essential cookies | 6 months |
Purpose: measuring LinkedIn campaigns and letting us reach professional audiences similar to whoever visits the site. Official list in LinkedIn's cookie table.
Where the data collected by cookies goes
Google, Meta and LinkedIn also process the data collected by these tools in the United States. Transfers take place in compliance with Arts. 44-49 GDPR, on the basis of the EU-US Data Privacy Framework adequacy decision (EU Decision 2023/1795) for providers that adhere to it, and the Standard Contractual Clauses approved by EU Decision 2021/914.
These providers partly determine their own purposes and should be considered independent controllers for what they do with data on their own networks. Their notices are public: Google, Meta, LinkedIn.
The complete picture — legal bases, processors, retention and rights — is in the site's privacy notice.
How to change your mind, at any time
Revoking must cost the same as consenting. The panel below is the same one that opens from the Cookie preferences link at the bottom of every page on the site.
What you switch off isn't filtered downstream: it simply isn't loaded at all. The revocation takes effect from the next page load — a script already present on the page can't be removed mid-visit, and that's one of the reasons we don't load any of them before consent.
Revoking doesn't delete cookies already written by providers on their own domains: for those, use your browser, as explained below, or the individual providers' opt-out tools.
How to delete them from your browser
Every browser lets you view, delete and block cookies, including ones already written. Careful: blocking all cookies can stop many sites from working properly, this one included.
- Google Chrome (in Italian)
- Mozilla Firefox (in Italian)
- Safari (in Italian)
- Microsoft Edge (in Italian)
For Google's personalised advertising, besides the browser, there's My Ad Center: it acts on the Google account, not on the individual device.
Who to contact
Data controller: Migastone International S.r.l., Via 28 Luglio 212, 47893 Borgo Maggiore, Republic of San Marino — Economic Operator Code SM28583.
- Privacy requests: privacy@migamatch.com
- Data Protection Officer: Ing. Antonio Mirizzi — rpd@invictusaziende.it
- EU Representative under Art. 27 GDPR: Walter Coslop — w.coslop@migastone.com