- Home
- Cookies
Cookies
How basket, sign-in, saved items and payment security use browser storage.
Last updated
We use cookies and local storage to provide shop features you request and to remember your cookie choices. Some identifiers stay in browser storage; others are sent to our commerce service or payment provider when those features are used. Browser storage is not a promise that its contents are never sent to a server.
Basket and sign-in
- provenience_cart_id — basket cookie. Identifies your basket for up to 30 days. The name is retained from our previous store name so existing baskets keep working. It can link to basket contents and contact or delivery details you enter; it is not anonymous merely because it contains an identifier. It uses SameSite=Lax and Secure on HTTPS.
- connect.sid — sign-in session. Our commerce service uses a session cookie to authenticate account requests. It is sent to the commerce service when needed; account and order records are held on the server. Signing out ends the authenticated session. Its lifetime is controlled by the server session configuration.
- Order confirmation and session updates. Browser storage may cache order receipts and record sign-in changes so tabs stay in step. A cached receipt may contain order and delivery details. Clear site storage or use a private session on a shared device.
Saved items, support and cookie choices
- Guest wishlists are stored locally; signing in can copy those items into your account. Signed-in wishlists are stored by our commerce service, with a local fallback if that service is unavailable.
- pv.support.session and pv.support.conversation remember a support session and conversation when you use support. Those identifiers are sent to our support service to retrieve messages and replies. Messages are stored on the server.
- pv.consent stores your cookie choices and the time you made them. You can reopen Cookie settings from the footer.
- Local-storage entries remain until removed by the shop, you or your browser; they do not all have the basket cookie's 30-day expiry.
Stripe payment security
Stripe provides the secure payment fields at checkout. Stripe.js and the selected payment method may use cookies and similar technologies for payment operation, authentication and fraud prevention. These can include __stripe_mid and __stripe_sid. Stripe receives payment and technical information when its payment fields are used; full card details are handled by Stripe rather than stored by our shop.
Stripe describes its storage purposes and durations in its cookie policy and privacy policy. The actual storage depends on the payment method and browser. Optional wallet or payment-provider features may have their own notices and choices.
Optional tracking and your choices
We have not installed shop analytics or advertising tags. Our cookie panel gives Accept all and Reject all equal prominence, remembers a refusal and lets you change your choice through Cookie settings. Accepting optional categories does not turn on services that are not installed. Any future non-essential technology must be disclosed and obtain consent where required before it runs.
Managing browser storage
Your browser lets you inspect, delete and block cookies and local storage. Blocking storage needed for a requested feature can prevent baskets, sign-in, saved items, support or payment from working. Clearing this site's storage does not delete the server's order or accounting records. To ask about personal information, see our privacy policy.