Cookies and tracking

This site sets no cookies of its own and does not remember who you are between visits. Two things we have always measured without touching your browser: how many visits arrive, and how quickly the page opens for you — the two sections below explain how. A third we measure only if you accept it: whether our ads lead to orders, with the Meta pixel, and that one does store two cookies. It is the only reason this site asks you anything, and it is explained in the "The Meta pixel" section. Sending a customization ticket or a review does not install cookies. What you build in the configurator lives in the page's memory: reload and you start again.

The typefaces are hosted on this site too, rather than on Google's servers, so your browser never has to contact a third party — or hand it your IP address — just to draw the text.

Knowing how many people come through helps us judge whether it is worth carrying on telling people about the workshop. The tool belongs to the hosting provider and reads the logs the server already keeps on its own: the counting never goes through your browser — no script, no cookies, no identifier following you from one visit to the next. An ad blocker will not catch it, because there is nothing in your browser to block.

What comes out of it are aggregate figures: how many pages were viewed and which ones, from which countries, how many distinct visitors, and which non-existent addresses were requested. The visitor count is based on the IP address within a single day, which the provider processes on its own side without passing it to us: what reaches us is a total, not a list. Nothing here leads back to a person.

Alongside those totals the site counts the main steps of a visit on its own — ready-to-ship pieces seen, configurator reached, a piece put in the cart, payment opened — to understand where it gets stuck. Each step carries language, country, model and where the visit came from: the site that sent you here, or the parameters an ad adds to the address. The steps of the same open page share a random number that lives only in the tab's memory: it is not saved in your browser, does not survive a reload and is not tied to you, so it says that two steps belong to the same visit but not who made it.

These figures stay in the hosting panel and are not shared with advertising platforms. If you arrive from an ad, whoever placed it knows it showed the ad to you, but receives nothing from us about your visit.

This one, unlike the counting, is the only thing that really runs in your browser. At the bottom of the page the hosting provider inserts a tiny script that times the loading: how long the main content took to appear, whether anything shifted under your fingers while you were reading, how long the page took to react to your first tap. These are the standard measurements used to judge a site's speed.

What leaves your browser is those timings, in milliseconds, along with the page they refer to. It sets no cookies, neither stores nor reads back anything in your browser, does not look at what you type in the configurator and builds no profile: it measures and sends. The script comes from an address belonging to the same provider that already hosts this site, so no new party enters the picture beyond those listed in the privacy statement.

It matters because a site's speed cannot be judged from the computer of the person who built it — there it is always fast — but from the phone of someone actually opening it, on whatever connection they have at the time. Those timings are the only way to know.

The workshop gets known through ads on Facebook and Instagram, and those ads cost money. The Meta pixel is what tells us whether that money brought orders or only curious visits: without it we can see how many people arrive, but not whether any of them bought, and the platform cannot learn to show the ad to people who resemble those who actually order. It is the only reason this site asks you for consent.

If you choose "Accept", the page loads a Meta script and from then on the following is shared with Meta: the pages you open on this site, your IP address and your browser, and what you do in the configurator — when you add a piece to the cart, when you start the payment, when a purchase completes, with its amount. The script stores two cookies in your browser, lasting at most three months, which let it recognize that the visit came from an ad. When a purchase completes the confirmation is also sent from our own server, and in that case we include your email address and shipping country reduced to an irreversible code: it lets Meta recognize someone it already knows, not learn your address, which never leaves this site in readable form.

If you choose "Decline", none of this happens: the script is not loaded, the two cookies are never created and the purchase confirmation is not sent to Meta. The same goes if you close the page without choosing. The site works identically either way — configurator, cart and payment do not change at all.

For ad measurement Meta acts as an independent controller: what it receives is matched to the profile it already holds and used under its own rules, available on its site. All we see in our panel are aggregate counts — how many times something was added to the cart, how many orders came from an ad — never a list of people.

When you add a piece to the cart, the page loads the PayPal payment module. At that point PayPal sets its own technical and security cookies: they keep the payment session open and help prevent fraud.

These are cookies necessary to provide the service you asked for — paying — and so they do not require prior consent. Until you add something to the cart, that script is not even loaded.

The full rules are PayPal's own, available on its site in the privacy and cookies section.

The links to the Instagram profile are ordinary links: they take you away from here and embed nothing in the page. No Instagram content is loaded inside the site, so until you click, no request goes to Meta. Once you land on Instagram, that platform's rules apply.

The banner at the bottom of the page is there for one thing only: the Meta pixel, which stores two cookies in your browser for an advertising purpose. It is the storing and the reading back that trigger the consent obligation, not the measuring — which is why the visit count and the speed timer, neither of which writes anything to your device, do not appear in the banner and are not a choice we put to you. PayPal's technical cookies stay out of it too: European rules and the Italian supervisory authority's guidelines exempt them because they are strictly necessary to deliver the service you asked for, namely paying.

"Accept" and "Decline" are two identical buttons, in the same place and with the same prominence: declining costs exactly one click, just as accepting does, as the Italian supervisory authority's guidelines require. Until you choose, nothing starts, and closing the page without choosing counts as a decline. No part of the site unlocks by accepting: configurator, cart and payment work identically either way.

You can change your mind at any time through the "Withdraw consent" control at the bottom of every page: withdrawing deletes the two Meta cookies immediately and stops all sharing, and requires neither writing to us nor filling anything in. Withdrawing must be as easy as consenting — Article 7(3) GDPR says so — and here it is the same single click.

Your choice is saved in your browser, because that is the only way not to ask you again on every page. It is the only thing this site writes to your device, it does not identify you and it never leaves the browser. If the purposes were ever to change, the choice would be asked afresh rather than assumed to still hold.

Every browser lets you view and delete stored cookies, or block them outright: the setting is usually under "Privacy and security". Block PayPal's cookies, though, and payment on the site stops working.