Security & Deployment Practices
This page explains the security and deployment boundaries that matter when you build a Hydrogen storefront with Weaverse. For the company-level overview (data handling, hosting, access and service providers), see Trust & Security.What Weaverse Stores and What Stays Elsewhere
- Weaverse stores the pages, sections, settings, translations and project data you create in Studio.
- Shopify keeps your products, orders and customers. Weaverse reads store data through Shopify APIs within the permissions you approve when you install the app.
- Your storefront host (for example Oxygen or a Docker or Workers deployment) runs your production Hydrogen storefront on the hosting arrangement you choose, separately from the Weaverse visual editor. Where available, Weaverse-managed sandboxes provide development and preview environments.
How Changes Reach Production
- Code: your Hydrogen storefront lives in your own repository. Code changes ship through your normal Git and deployment workflow. See Deployment.
- Content: content edited in Studio is published from Studio. Published content is delivered to your storefront through the Weaverse SDK; previews and page version history let you review and restore earlier versions.
- Studio preview: Studio loads your storefront in a preview frame. Allow it through your Content Security Policy configuration.