A plain-language view of the storefront data flow.
This page is a reviewable implementation draft based on the fields and services currently used by the storefront. It is not the final privacy notice until the business contact, retention, rights, and jurisdiction inputs are confirmed.
Store operator
This store is operated by Akechi Inc. Customer service is available at contact@akechi.net. The privacy-specific policy decisions below remain under review.
Information entered during shopping
The current checkout flow can receive a customer name, email address, optional phone number, shipping address fields, order notes, and the cart lines needed to validate an order.
- The browser stores cart lines locally so the shopping bag can persist between page views.
- Checkout validates product handles, requested quantities, current prices, and available quantities on the server.
- Do not place payment card numbers, passwords, or verification codes in an order note.
Payment and order processing
The storefront creates a hosted Stripe Checkout session after the cart and checkout profile pass validation. Payment details are entered in Stripe Checkout rather than the storefront page; the storefront receives the checkout and payment result needed for order intake.
- Stripe is the payment service named by the current implementation.
- A paid order is staged for internal review before fulfillment promotion.
- Order lookup uses the public order ID and the order status exposed by the storefront.
Analytics and technical events
The storefront can send page-view, product-view, add-to-cart, begin-checkout, and purchase-confirmed events. The current event payload includes an anonymous browser session identifier, path, and limited product, quantity, or value details when available.
- The anonymous session identifier is stored in browser local storage.
- Analytics must not interrupt shopping when the event endpoint is unavailable.
- This draft does not claim a specific cookie banner, advertising profile, or cross-site tracking program.
Open policy decisions
The implementation does not establish the final retention period, customer rights process, responsible privacy contact, governing jurisdiction, or final notice wording. Those are business and legal review inputs, not facts to infer from the code.
- Confirm the public privacy contact before publication.
- Confirm retention and deletion handling for order, payment, and analytics records.
- Have the final notice reviewed for the actual operating entity and applicable law.
Frequently asked questions
Does Akechi Inc. receive my full card number?
The current candidate uses hosted Stripe Checkout for payment entry. The storefront implementation is not the card-entry surface. Final public wording remains subject to business and legal confirmation.
What should I put in an order note?
Only include information needed to review the order. Never include a card number, password, one-time code, or other payment credential.
How long is information kept?
A retention period is not approved in this candidate. The business must confirm the retention and deletion approach before this becomes the final notice.