Cookie Policy
Eight cookies. Four of them are yours to switch off.
Draft for review. This document was prepared as part of the Wristcraft site build and has not been reviewed by counsel. Confirm the entity details, retention periods and jurisdiction clauses with your lawyer before launch.
Cookies are small files a site stores on your device. We use as few as the app can work with, and none for advertising unless you say yes. There is no consent wall you have to fight; refusing everything optional leaves the app fully usable.
1. What we set
| Name | Purpose | Provider | Type | Expires |
|---|---|---|---|---|
wc_fitting_session |
Holds an in-progress fitting session: the reference you entered, the measurements resolved so far, and where you are in the flow | Wristcraft (first party) | Strictly necessary | 30 days |
wc_wardrobe_draft |
Keeps an unsaved wardrobe and its tweaks so a reload does not lose your work | Wristcraft (first party) | Strictly necessary | 30 days |
wc_consent |
Records your cookie choices so we stop asking | Wristcraft (first party) | Strictly necessary | 12 months |
wc_session |
Keeps you signed in and protects forms and checkout against cross-site request forgery | Wristcraft (first party) | Strictly necessary | Session |
wc_region |
Remembers your delivery country and measurement units, so prices and millimetres are right | Wristcraft (first party) | Functional | 6 months |
wc_render_tier |
Remembers whether your device coped with the 3D preview, so we do not retry a renderer that failed | Wristcraft (first party) | Functional | 90 days |
wc_stats |
Aggregate page and step counts: which fitting steps get abandoned | Wristcraft (first party, self-hosted) | Analytics | 13 months |
wc_attr |
Records which campaign or publication referred you, so we know where to spend | Wristcraft (first party) | Marketing | 90 days |
2. Why the fitting session needs a cookie
A fitting session is a multi-step piece of state: a reference, a set of resolved measurements, wear-pattern answers and a draft wardrobe. Without wc_fitting_session and wc_wardrobe_draft there is nowhere to hold that between page loads, so every step would start over and a build could never be assembled. Those two are strictly necessary in the Article 5(3) ePrivacy sense — set to deliver a service you asked for — so they are set without consent, and they are first party, they hold no identity, and they expire in 30 days. Nothing in either cookie is used for analytics or marketing.
3. Analytics and marketing
Everything outside the strictly-necessary rows is off until you accept it in the banner. Analytics is self-hosted, aggregated, and stores no cross-site identifier; we use it to find the fitting step people give up on. Marketing is one first-party attribution cookie. There are no third-party advertising pixels on this site, no retargeting tags, and no data-broker integrations.
4. Changing your mind
Use the “Cookie settings” link in the footer, at any time, on any page. It reopens the banner with your current choices, and turning a category off deletes its cookies immediately. Withdrawing consent does not affect processing that already happened, and it will not lose an in-progress fitting session.
We honour Global Privacy Control. If your browser sends the signal, analytics and marketing stay off and we do not show you the banner at all.
5. Browser controls
You can block or delete cookies in your browser settings — every major browser has a per-site control, usually behind the padlock in the address bar. Blocking the strictly-necessary cookies will break the fitting session and checkout; the rest of the site, including the whole of the atelier and legal pages, keeps working.
Private or incognito windows discard everything on close, which means a fitting session started in one cannot be recovered.
6. Third parties
Two, both narrow. The payment processor sets its own cookies inside its hosted checkout frame for fraud prevention; those are strictly necessary and governed by its policy, which is linked at checkout. Fonts are self-hosted, so no font provider sees your address. There is no embedded video, no social sharing widget, no comment platform, no chat bubble.
7. What we do not do
- We do not fingerprint your device to work around your cookie choices.
- We do not use your fitting measurements for advertising, ever, and they are not exposed to any analytics tag.
- We do not sell or share cookie data with data brokers.
- We do not re-ask for consent for twelve months after you decline.
Questions about anything on this page: privacy@wristcraft.app.