Cart to Nowhere

Shopping simulator. No real items or charges in pretend checkout.

Explore the collection ↗
THE CART TO NOWHERE JOURNAL

Your browser, your collection.

Cart to Nowhere stores your bag, wishlist and simulated orders in your browser. Shopping requires no account or payment information. Clearing this site’s browser data removes that local collection; it does not delete an optional account or server-side drop signup.

The personal edit builder saves a separate selection of product IDs in this browser only when you choose to save. Shared edit links include those product IDs, never your identity, order history or account data. Anyone with a link can view its selection. Opening a shared edit does not replace your saved edit automatically. These selections are not synchronized by signing in and are not included in Analytics events.

Item suggestions are optional and require no email or account. When enabled, the form sends the item name, brand, optional product link and note to our private AWS catalog inbox for review. Please include no personal details. Suggestions are scheduled for deletion after 90 days; automated deletion may take a few additional days. A hash of your network address and hourly time window is kept briefly to limit spam, scheduled for deletion after 24 hours. AWS processes network information to serve the request. Suggestion contents are never sent to Analytics, and we do not fetch submitted product links automatically.

Weekly drops use shared, simulated quantities. When enabled, AWS stores drop item identifiers, a random checkout identifier and a timestamp to confirm availability and prevent duplicate claims. No checkout names, addresses, payment details or prices are sent. Checkout receipts are scheduled for deletion after 90 days. A hash of your network address and drop identifier limits repeat claims until one day after that drop ends. Regular collection shopping continues locally without this service.

The optional drop list stores your email, consent wording version, signup time and a secret withdrawal credential in our private AWS inbox. No email service is connected to this list yet, and no announcements are sent. Unconfirmed entries are scheduled for deletion after 90 days; actual removal may take a few additional days. We will require email confirmation before enabling announcements. A network/time-window hash limits signup spam and expires after 24 hours. Your browser saves only an opaque credential for the “Withdraw my signup” action, not your email. Withdrawing removes the signup. Your email and credentials never enter Analytics. If browser data is cleared, unconfirmed entries still expire.

Optional account sign-in uses Amazon Cognito. If you choose to create an account, Cognito processes your email address and authentication details to provide sign-in, verification, and password recovery. When Google sign-in is available and you choose it, Google shares your basic account identity and email with Cognito. Signing in does not upload or sync your local collection. Sign-in tokens are kept in this tab’s session storage. If you select weekly drop updates on the account page, we keep that choice in this tab for up to one hour and submit your verified account email to the private drop list after successful sign-in. This is optional and does not start email delivery. The drop-list retention and withdrawal choices above also apply.

Optional paid digital experiences

After Hours purchases use Stripe-hosted Checkout. Stripe processes the contact, payment and billing information you enter, along with device and network information needed to process payments and prevent fraud. We never receive your full card number. Our private AWS billing service stores your Cognito account identifier, experience identifier, checkout/payment references, payment or revocation status, and timestamps to provide and restore access and handle refunds or disputes. These records are separate from simulated orders and local browser backups. No card details, account identifiers or paid story choices are sent to our Analytics integration.

Protected stories load after the server verifies access. Story choices remain in memory during your visit; keepsake images are created on your device. Payment records have no automatic deletion schedule at present and may be retained for accounting, dispute and legal requirements. See purchase terms and support for access, refund and account requests. Stripe explains its processing in its privacy policy.

Account verification and password recovery emails use Zoho ZeptoMail in India. Zoho processes the recipient email address and message content to deliver these account emails. Open and click tracking are disabled.

Optional measurement uses Google Analytics through the Firebase web SDK. It loads only if you choose “Allow analytics.” Google processes cookie identifiers, device/browser information, approximate location derived from network information, and visits and shopping actions. We send no names, emails, checkout fields, personal coupon codes, order identifiers, search text, or simulated purchase amounts. Advertising personalization, Google signals, automatic form tracking, and session replay are disabled. This measurement does not upload your collection or create an account.

A small set of public campaign links can attach fixed campaign labels to consented visits, so we can understand which invitation brought someone here. Arbitrary query text and your selected pieces are not sent. After consent, a recognized campaign label may stay in this tab for up to 30 minutes; withdrawing consent removes it. A separate browser preference can exclude testing visits from measurement without changing your shopping data. Result cards are made on your device and contain only your selected catalog pieces and their reference prices. We do not receive or automatically publish those images.

Change or withdraw consent using “Privacy choices” on the site. Withdrawing stops future collection and clears this site’s Google Analytics cookies; it does not erase data Google already received. Your shopping data stays in your browser. Our consent preference is stored separately from shopping backups. A browser Global Privacy Control signal keeps analytics off. See how Google uses information from partner sites. Hosting providers may process ordinary request logs.