A small, essential cookie posture for a trust-based product.

Essential cookies keep a signed-in user authenticated, preserve secure session state and protect routes that require account access. Without them the dashboard, export and approval flows would not work — you would be signed out between pages. These cannot be switched off while you are using an account, because they are the account.

One further item is stored in your browser under the key caprice_consent_analytics. It holds a single value, granted or denied, and exists solely to remember the choice you made on the consent bar so you are not asked again on every page. It is set by this site, read by this site, and sent nowhere.

This site uses Google Analytics 4 to see which pages are useful, and the analytics tag does not load until you choose Accept. Until then the site sends nothing to Google for analytics: no request, no cookie. If you never make a choice, that is where it stays. When you do accept, the consent signal (Google Consent Mode v2) is set to granted before the tag sends anything, so the whole visit, first page view included, is counted with your consent.

Choosing Accept loads the tag and sets analytics_storage to granted, for your browser only. Choosing Decline keeps the tag from loading at all, so nothing is sent to Google, and records the decline so you are not asked again. The advertising signals — ad_storage, ad_user_data, ad_personalization — remain denied in both cases. There is no branch of this site where they are enabled, because there is no advertising on it.

If you accept, two cookies appear and they are the only two: _ga, which holds the anonymous browser identifier, and _ga_C372PEK7KT, which holds the session state for this property. Both are first-party, both expire on their own, and neither carries anything you typed. Nothing else is written. The Google Ads conversion linker, which would otherwise add a third cookie called _gcl_au the moment analytics were allowed, is switched off in the tag configuration — it has nothing to link, because this site runs no advertising.

The previous arrangement is worth naming because it was wrong: analytics set a cookie on first paint, before any interaction, on a property serving Italy and the EU, with no consent surface anywhere in the page. That has been fixed. If you visited before that change and want the cookie gone, clearing site data for this domain removes it.

No advertising cookies, no retargeting pixels, no third-party marketing tags, no cross-site identifiers, no data brokers. The analytics property is not linked to an ad account and we do not sell, license or share what it records.

The measurement data at the centre of this product — your body measurements, your fit history, your garment records — is not cookie data and is not covered by anything on this page. It lives in your account under the permission model described in the privacy policy, and it is never used for advertising by anyone, including us.

Cookie settings, at the bottom of every page and in the menu once you are signed in, reopens the consent bar. Choose Decline and analytics stops: the two analytics cookies are deleted and the page reloads without the tag. Your choice is stored in this browser, so the bar does not ask again unless you open it.

Clearing cookies and site data for this domain also removes the session cookie and the stored choice. You will be signed out and the bar will appear again on your next visit.

Your browser can also block cookies for this domain. Analytics cookies are then never set, but the bar cannot remember your choice: it asks on every visit, and Accept still loads the tag for that page. Signed-in features will not work, because they depend on the session cookie, and that is a limitation of how sessions work rather than a decision on our part.

If you see a cookie or a network request from this site that this page does not describe, we would rather hear about it than not. Use the contact route with the page you were on and what you saw, and we will either explain it or fix it.

The legal detail on how personal data is processed, on what basis and for how long, is in the privacy policy. The cookie posture described here is a subset of that: what your browser stores, as distinct from what the service holds.