Privacy notice
Your information deserves a clear explanation. VALUNARA is a TEST storefront: checkout creates demonstration records, not real purchases. This draft describes the intended demo data flows and needs a verified technical inventory and legal review before any live launch.
Who is responsible for your information?
VALUNARA is a demonstration brand name, not an identified legal entity. Company name / legal entity: Not yet provided — required before launch. Business address: Not yet provided — required before launch. VAT number / applicable registration details: Not yet provided — required before launch. Real privacy and support contact: Not yet provided — required before launch. These details must be completed and verified before launch.
Information used in the demo
The demo may store the name, email address, delivery details, selected products and test order status that you submit during checkout, as well as contact-form submissions. Only enter fictional, non-sensitive test information; do not enter real payment-card details. The server and hosting infrastructure may process technically necessary connection information for operation and security; the actual logs, providers and retention periods must be audited before launch.
Guest orders and your browser secret
Guest order access uses a secret token kept in your browser rather than a customer account. Treat this token as a credential: someone who obtains it may be able to access the associated demo orders. Do not share it or use sensitive test information on a shared device. Clearing browser storage, changing devices or using a private browsing session may remove access to your order history. Removing the browser token does not by itself delete records stored on the server.
Cart, wishlist and necessary storage
Your cart and wishlist are saved locally in your browser to keep your selections between visits. Necessary browser storage can also support guest order access and remember privacy choices where implemented. Local storage is not the same as a cookie, but both can retain information on your device. You can clear site data through your browser; this may reset selections and guest order access.
Stripe test checkout
Payment testing uses Stripe in test mode where configured. Stripe may process test checkout information to simulate a payment and return a test status. This is not a real charge, a live payment service or a promise of shipment. Use only Stripe's documented test payment details. Before live payments are enabled, the operator must verify the integration and explain Stripe's role, applicable notices, data transfers and any other actual service providers.
Contact requests and optional marketing
The contact form submits your name, email, topic and message to the demo server for storage. No live support inbox or response service is configured. Do not include passwords, card numbers or sensitive personal information. Marketing signup is optional and separate from browsing or checkout; it must use an affirmative opt-in where required. A demo opt-in is not evidence of a functioning mailing service, and no marketing delivery is promised.
Analytics and non-essential tracking
This draft does not claim that analytics or advertising tools are installed. Analytics must be described only if actually configured, with the real provider, purposes, data and retention disclosed. Where consent is required, non-essential tracking must remain disabled until valid consent is given, and withdrawal must be possible. The live implementation must be checked against this notice before launch.
Purposes, retention and your rights
The intended purposes are operating the test shopping flow, showing demo orders, storing demonstration contact requests and maintaining the service. The operator must document the applicable legal bases, recipients, international transfers and retention schedule before launch; none is represented as finalized here. Depending on applicable law, you may have rights to access, correction, erasure, restriction, portability, objection or withdrawal of consent, and to complain to a supervisory authority. An operational contact and rights-request process must be provided before live use. Clearing local storage does not guarantee server-side erasure.