Cookie and Similar Technologies Notice

This candidate document is provided for legal and operational review. It is not effective, does not replace any existing agreement, and must not be used to collect consent until TCW records final approval and a publication date.

Cookies are small values stored by a browser. Local storage, session storage, pixels and similar tools can remember a session or create events. This notice applies regardless of the technical label. TCW will not classify an advertising or analytics technology as essential merely because it is useful to the business.

TCW may use session and browser storage needed for authentication, security, fraud prevention, load balancing, checkout handoff, consent choices, accessibility and delivery of a feature you request. These tools cannot be disabled through an optional-cookie panel because the related service would not function, although browser settings may block them and cause sign-in or checkout to fail.

• Authentication session and token storage managed by the configured identity provider.
• Security, rate-limit, anti-forgery and payment-return state.
• Consent and privacy preference records so TCW does not repeatedly ask or ignore a choice.
• Short-lived cart, draft or interface state necessary for the current action.

The candidate application currently uses the following first-party names. Final publication still requires a production scan because an authentication key contains the configured project reference and provider-hosted pages can change independently.

• The Supabase authentication key, commonly named with an sb- project prefix and auth-token suffix, keeps the requested signed-in session and refresh information until sign-out, expiry or browser clearing.
• sidebar_state is a functional interface-preference cookie retained for seven days.
• tcw.search.queries.v1 and tcw.search.hits.v1 keep up to six recent searches or selected results on that device until overwritten or browser clearing.
• tcw.ui.v1 keeps signed-in device preferences such as theme and interface state until changed or cleared.
• tcw.state.v3 keeps only the signed-out device theme and a guest cart or checkout draft until sign-in, migration, replacement or browser clearing. It does not store server records, money, activity, operator authority or paid entitlement.
• Retired tcw.state.v1 and tcw.state.v2 snapshots are not read and are deleted automatically when the current application hydrates.

Preference storage that is not strictly required, audience measurement, third-party analytics and advertising technologies must be documented with provider, purpose, duration and access before use. Where consent is required, they remain off until the user opts in and can be withdrawn as easily as given. Rejecting optional technologies must not block ordinary account use.

TCW does not currently authorize cross-site behavioral advertising cookies. A future change requires a revised notice, a functioning choice mechanism, regional opt-out support and testing before release.

Stripe, Printify, a print provider or another disclosed service may operate its own hosted page and set technology under its own notice. TCW is responsible for the integrations it chooses and will provide a direct link or disclosure at the handoff where practical. An embedded tool is not exempt from TCW's consent duties merely because another company supplies it. The candidate site uses local system font stacks and does not contact a remote font provider.

When optional tools are enabled, TCW must provide a persistent privacy or cookie control that permits category-by-category choices, saves a consent record and allows withdrawal. Browser controls can delete or block storage but may also sign you out. Privacy rights and recognized opt-out signals are described in the Privacy Notice and Regional Privacy Addendum.

Before publication, TCW must complete a production scan, document every first- and third-party cookie or storage key, provider, purpose and retention period, test the consent state before and after a choice, and repeat the scan after material integrations. This draft does not state that a scan has already proven the final production set.