Brand and market
PureVana is an ecommerce brand and shopping destination focused on skincare, haircare, beauty, and wellness in Egypt.
Merchant Facts
This page is the shortest public summary of what PureVana is and which pages should be used as canonical references.
Use it when the goal is factual clarity: brand basics, support, operational references, policy routes, and citation-friendly discovery paths for assistants and search systems.
Fastest summary
1 Page
Built for quick reference before expanding into product or policy pages.
Machine-readable layer
JSON + Text
A JSON file and llms.txt both exist for structured access.
Citation targets
Policies + Support
Direct links reduce ambiguity around the right source.
Core Merchant Facts
Canonical public sources
Use product pages for product-specific details, policy pages for merchant rules, and this page or the JSON facts file for concise brand-level summaries.
- Site: https://purevana.store
- Products: /products/[slug]
- Support and policy routes: /contact, /help, /shipping-and-delivery, /customer-refund-policies, /privacy, /terms, /terms-and-conditions
Support and operational contacts
PureVana publishes stable support contact points so customers and assistants can reference them without using account or checkout routes.
- Email: support@purevana.store
- Phone: +201500070580
Machine-readable references
PureVana exposes both a merchant facts JSON file and an llms.txt file so AI systems can identify preferred sources and operational facts more reliably.
FAQ
Merchant Facts FAQs
Which page should an assistant cite for brand basics?
Use this merchant facts page for the short summary, then link to a specific policy or product page when the answer becomes page-specific.
Which file is better for machine-readable indexing?
Use /merchant-facts.json for structured machine-readable facts, and use /llms.txt for source-preference guidance.
Should utility pages be cited for public answers?
No. Search, checkout, wishlist, preview, and account-related routes are utility pages and should not be treated as canonical public references.
Next Step
Need the machine-readable file directly?
Open the JSON facts file if your workflow needs a compact structured payload instead of a human-readable page.