Privacy Policy

We process account email addresses, consent records, uploaded try-on photos, generated image assets, shared look metadata, reactions, and checkout details.

We also process technical signals such as cookies, IP-derived hashes, and device fingerprints for quota, abuse prevention, and session handling.

If you allow optional analytics and deliberately choose Shop or Try from a public Chic Vote or shared look, we use signed first-party cookies and pseudonymous source identifiers to preserve that social journey. Declining or withdrawing analytics consent does not affect shopping. The click record does not contain the share code, buyer identity, IP address, user agent, or referrer.

We use data to deliver sign-in, virtual try-on, saved looks, public sharing, reactions, gift checkout, moderation, and reward flows.

We use social-attribution records to measure whether a shared decision influenced a try-on, checkout, or order and to prevent self-referral or source-mismatch errors. Measurement does not mean that a campaign owner is enrolled as a creator or entitled to payment.

Optional marketing and approved shared-look reuse are handled only when you explicitly grant those consents.

Source try-on photos are retained for up to 30 days by default.

Generated try-on and story assets are retained for up to 90 days by default.

For guest try-on continuity, a random capability is stored in an HttpOnly cookie and shared local browser storage. The shared browser record is provisional for up to five minutes before cookie acknowledgement and is then retained for no more than 30 days; it is cleared when invalid or expired, after successful account linking, or after confirmed account deletion.

When an account sign-in session expires, its stored bearer token, IP address, and user-agent data become eligible for periodic deletion. When a temporary sign-in or verification value expires, its email-derived identifier and hashed one-time-code state also become eligible for periodic deletion. Active and future-expiring values are not part of those cleanups.

Decision votes keep their choice and integrity-review status for aggregate results. When a decision closes, is disabled, or reaches its deadline, its browser-session fingerprint is replaced with a unique per-vote archive value and its IP- and user-agent-derived hashes are cleared.

Public reactions keep their reaction type and integrity-review status for aggregate counts. A server-issued reaction session cookie can remain in the browser for up to 365 days, but each stored reaction's session fingerprint and IP- and user-agent-derived hashes are retained for no more than 30 days. Those stored identifiers are also archived or cleared after the shared look is disabled or its owner's account is deleted.

When analytics is allowed, a social-attribution context cookie expires after seven days and its anonymous browser-session cookie expires after 30 days. A closed or deadline-expired decision can issue new measured shopping attribution for up to seven days; later winner links remain functional without new attribution. Withdrawing consent makes an existing context ineligible for new try-ons or checkouts. Expired, unlinked touch records are periodically deleted; snapshots linked to checkout or order records follow the corresponding fraud, bookkeeping, and legal retention period.

Operational logs, order records, and moderation records may be retained longer when required for fraud prevention, bookkeeping, or legal obligations.

We share data with infrastructure and service providers used for hosting, storage, transactional email, analytics, error monitoring, payments, and try-on generation.

Public shared looks are visible to anyone who receives the shared URL until the look is disabled, expires, or is removed.

You can review or update optional marketing preferences and approved marketing reuse preferences in account settings.

You can request account deletion from within the app. That flow clears app-owned generated assets, disables sharing, and signs you out on the current device.

For privacy questions, deletion follow-up, or moderation concerns, use the support contact published in the live product or transactional email footer.