Basket Wise

Privacy policy

This policy describes the Basket Wise Cloudflare guest service developed by Yiping Deng. It does not describe OpenAI’s separate handling of your ChatGPT conversations.

Last updated: 10 October 2026

Information the service processes

Basket Wise receives the structured shopping information sent to its tools: trips, profile-wide shopping-list entries, store and item names, quantities, prices, currencies, personal spending thresholds, notes, and checkout status. It also uses guest and trip identifiers, revisions, timestamps, and request identifiers for authorization, duplicate prevention, and retention.

No Basket Wise email, password, or named account is required. Guest access uses OAuth credentials and a recovery key. The service stores credential hashes and authorization records; keep the actual credentials private.

The service does not receive or store photographs or your complete ChatGPT conversation. Only the structured shopping details sent to its tools are processed. Basket Wise does not make separate model API calls.

How information is used and hosted

Information is used to provide the baskets you request, calculate totals, keep widget and chat changes consistent, authorize access, support recovery, and limit abuse.

The service runs on Cloudflare Workers. Guest records are stored in Cloudflare Durable Objects. OpenAI sends tool requests and receives tool results as part of ChatGPT. These providers also process network and security information under their own policies.

Authorization uses a secure, first-party cookie and short-lived server-side flow state to bind the browser and prevent forged requests. It is not an advertising cookie. The application adds no analytics, advertising trackers, or custom request-body logs; Worker observability is disabled in its deployment configuration. Provider infrastructure processing is separate from those application settings.

Retention and deletion

Basket data expires after 24 hours without a successful new foreground basket action. The account-wise shopping list, anonymous profile, recovery-key hash, and OAuth grants expire after 90 days without a new foreground list or basket action. List activity renews only the profile, never basket retention.New intentional reads and changes count as activity. Token refresh, recovery, merely displaying a saved widget, failed requests, and retries do not extend either deadline. An explicit new open request counts as foreground activity for its list or basket.

Expired baskets are inaccessible even if cleanup is delayed; the same authorized connection can start fresh. At 90 inactive days, profile credentials are rejected even if cleanup is delayed. Access checks, alarms and scheduled cleanup purge expired trips, current-trip pointers and shopping snapshots. Minimal hashed replay records (request ID, fingerprint and expiry, not item contents) and clear-operation receipts remain for up to 90 days to prevent delayed retries recreating data. The list and its content-free idempotency receipts remain until profile expiry. Explicit guest deletion removes the guest’s list, trips and credentials from active storage without waiting for inactivity expiry.

Authorization flow state expires separately, normally after ten minutes. OAuth application-client registrations hold configuration and credential hashes rather than shopping records; they remain valid for the ChatGPT connection and are not deleted when baskets or profiles expire. Registration capacity is bounded. They do not keep an expired guest accessible.

Your ChatGPT history is not erased by deleting a Basket Wise guest. Manage it through OpenAI’s controls. Messages you choose to send to support are also separate from guest-vault storage and do not follow its automatic 24-hour deadline.

Your choices and requests

Provide only what your basket needs. Correct or remove items through the connected tools, clear baskets while retaining your list and profile, or explicitly delete the whole guest identity. Disconnecting ChatGPT alone is not a request to erase the guest’s records.

Use the contact below for privacy questions or requests about access, correction, or deletion. Do not send credentials. Because the service has no named accounts, an email address alone cannot identify a guest space or prove ownership. Support cannot bypass guest authorization or reconstruct lost credentials.

OpenAI’s and Cloudflare’s own privacy policies apply to their separate services and infrastructure: OpenAI privacy policy and Cloudflare privacy policy.