Cookie policy.

What we store, where

Three categories of browser storage:

1. Strictly necessary (no consent required)

• Capsule wardrobe state (localStorage, cw_wardrobe_v1): accepted/skipped/saved garments, palette preference. Required for the tool to remember your progress between sessions.
• Try-on counter (localStorage, cw_tryon_count): tracks how many free try-ons you've used. Required for the free-tier limit.
• Photo cache (sessionStorage, cw_user_photo): your uploaded photo, kept only while the tab is open. Cleared when you close the browser.
• Stripe checkout cookies(when you use the Pro tier checkout): Stripe sets necessary cookies for fraud prevention. We don't read them.

2. Analytics (consent-driven)

• Vercel Web Analytics — privacy-friendly, no third-party cookies, no fingerprinting. Tracks page views and basic engagement.
• Google Analytics 4 (when enabled) — sets _ga and _gid cookies for session tracking. Disabled by default until you accept the consent banner.

3. Marketing (we don't use these)

We don't set advertising cookies, retargeting pixels, or third-party tracking beacons. The site is deliberately not ad-supported.

How to control them

In our consent banner:the first time you visit, you'll see a banner asking about analytics. Decline → no analytics cookies are set. Accept → standard GA4 + Vercel Analytics behaviour.

In your browser: all major browsers let you block, clear, or inspect site storage. For Chrome/Edge: DevTools → Application → Storage. For Firefox: about:preferences#privacy. For Safari: Settings → Privacy → Manage Website Data.

To clear all our state at once: visit capsulewardrobe.aiand clear site data via your browser's settings. We don't maintain server-side session state for anonymous users — clearing your browser fully resets the relationship.

Third parties

When you use the AI try-on, your photo is sent to a third-party AI provider (currently Replicate, with Fashn.ai supported as alternative). The provider processes the image and returns a generated try-on, then deletes their short-lived input cache. Neither stores the photo long-term.

See our privacy policy for the full data flow and retention rules.