Scope of this build
The site is currently a development and controlled sandbox environment. Production checkout is closed, there is no real payment connection, and the current contact page does not submit or send information.
Only authorized testers should enter test information. Real customer lists, real card details, and unnecessary personal information must not be used for sandbox testing.
Information the sandbox can use
When an authorized tester creates a sandbox order, the service can process the information required to exercise the order and delivery workflow:
- Email address, first and last name, and phone number.
- Shipping and, when different, billing address fields.
- Product identifiers, selected option text, quantities, shipping preference, and payment-method preference.
- Server-calculated prices, order number, status, test payment record, and test shipment record.
The order lookup feature uses an order number together with the matching email address. It returns limited order status, totals, items, shipping method, and tracking information; it does not display a full address.
Information this site does not collect
The current pages do not request or store a card number, CVV or security code, card expiry date, bank account, routing number, wallet password, or payment-provider login. No real payment provider is contacted and no real charge occurs.
The current build also does not send real customer email, run a newsletter subscription service, or provide a working contact submission form. Do not enter payment credentials into any free-text field.
Browser, session, and server storage
- Cart
- Product selections are stored in this browser under local storage so the cart can persist between pages.
- Public session
- An essential, HttpOnly session cookie supports CSRF protection, one-time order requests, and private same-session receipts.
- Order records
- Controlled sandbox orders are stored in the project database so the transaction, stock, dashboard, and lookup flows can be tested.
- Security data
- Limited request and network information may be used in private security logs or rate-limit state to protect sensitive endpoints.
A production retention schedule and deletion process have not been approved. They must be defined before public launch, including how long orders, security records, and support correspondence are kept.
Sharing and service providers
The current controlled build does not send order details to a real payment gateway, email service, carrier, analytics platform, or advertising network. Local product photography is served from this project rather than a remote image host.
Production hosting providers, payment processors, email services, carriers, analytics choices, cross-border transfers, and legally required disclosures must be identified and documented before launch. This draft does not claim that no provider will ever be used.
Access, correction, deletion, and contact
No verified privacy request channel is published in this pre-launch build. The legal operator, applicable rights, identity-verification process, response time, complaint route, and contact details must be finalized before public launch.
For now, authorized testers should avoid real personal data. Browser cart data can be removed by clearing the cart or local storage. A successful sandbox order clears the cart in that browser, but the associated test order remains in the test database until an authorized maintenance process removes it.
See Contact for the current support-channel status and Terms for the sandbox transaction boundary.