Information used to provide the service
- Account identity such as an email address or verified mobile number.
- The product option, quantity, order reference, payment state and support history needed to fulfil an order.
- The checkout values required by the selected product. The store rejects password, secret, API-key and token fields in the current schema.
- Technical security signals used to protect sessions, rate limits and abuse controls.
Storage and access
Sensitive checkout and delivery values are encrypted outside ordinary public order notes. Access is limited to the operations needed for fulfilment and is audited. Customer messages contain status and the random support reference, not delivery secrets or provider credentials.
The browser receives an opaque session in an HttpOnly cookie. Session tokens are not exposed to page JavaScript or included in public catalog responses.
Retention
Input and delivery records use bounded retention settings in the private commerce system. A scheduled cleanup removes ciphertext after its configured period while retaining a value-free audit record. The final legal retention period and operator contact must be approved before launch.
Your choices
You can request help with account access, order information or a privacy question through the published support channels. We may need to verify account ownership before changing or revealing private information. Do not send a password or payment secret in a support message.
Contact support
No active support channel is published for this language.
View my orders