How we handle your store, code and data
A plain account of what Weaverse stores, where it runs, who can access it and how changes reach your storefront.
How we work
Six areas teams ask about before they connect a store.
Data handling
Weaverse stores the pages, sections, settings and project data you create in Studio. Store data such as products and orders is read from Shopify through its APIs, within the permissions you approve when installing the app.
Hosting and deployment
The Weaverse app runs on Fly.io with its database on PlanetScale, and uses Cloudflare for caching and asset storage. Your storefront is deployed to your own hosting, such as Shopify Oxygen.
Access control
You sign in to Weaverse through Shopify, and each session is scoped to the stores it was authorized for. On service projects we ask only for the store and repository access the work needs.
Change management
On service projects, code changes are made in pull requests on your GitHub repository, with the review process agreed for your project.
Previews, versions and backups
Studio keeps page version history so a published page can be restored to an earlier version, and project backups can be downloaded from the dashboard. Service projects use the preview and launch process agreed in the statement of work.
Reporting a security issue
Email support@weaverse.io with “Security” in the subject, the affected store and what you observed.
Service providers
Weaverse uses these providers to run its features.
- ShopifyApp installation, sign-in and billing
- Fly.ioApplication hosting
- PlanetScaleDatabase
- CloudflareCaching, images and asset storage
- GitHubSource repositories and theme sync
AI model providersAI features
- PostHogProduct analytics
- CrispSupport chat
See also: Privacy Policy · Terms of Service
Questions about
security?
Tell us what your security review needs and we will answer it directly.
