Frequently asked questions

How often is my store backed up?

Products, collections, orders and customers are captured as they change, through Shopify webhooks. Pages and articles follow within about fifteen minutes on a catch-up pass; blogs themselves are picked up by the weekly comparison. Themes are checked daily, and inventory levels up to four times a day on paid plans. Navigation and URL redirects are covered by the weekly comparison, which also re-checks the whole store against the backup, so a missed notification does not turn into a missing version.

Nothing needs to be scheduled or switched on. The first backup starts by itself when you install the app.

A version records a change we saw. If a record is edited twice between two passes, the backup keeps the state at the second pass, not the moment in between - webhooks make that gap small for products, collections, orders and customers, and it is the catch-up interval for everything else.

How far back does the history go?

As far as your plan's window: 7 days on Free, 30 on Starter, 90 on Growth, 365 on Pro. That window applies to everything we version, themes included. What it limits is how far back you can roll a record that changed - not whether the record is in the backup.

At least one copy of every record is kept however old it is, so a product nobody has touched in two years is still restorable on the free plan. Deleted records keep their last copy too, with the deletion itself as the newest row. Moving to a smaller plan does not trim anything for 30 days, and the app shows the exact date.

What can be restored, and what cannot?

Restored back into the store: products with their variants, options and metafields, collections with the products of each hand-picked collection, pages, and inventory levels on paid plans. For a page, title, handle, body, visibility and metafields come back, and anything a theme or another app keeps alongside the page stays as it is now. Cost per item comes back on every plan from product versions stored since 18 September 2026; an older version does not hold it, so restoring one leaves cost per item as it is. Every restore shows the exact list of what will change before anything is written. After a write we read the record back from your store and compare it with the backup: anything not fully verified is reported as partial or unverified rather than as success, and a record we could not read or compare before writing is left untouched and named in the result. A restore that overwrote records can be undone - we keep what it overwrote; a restore that only recreated missing records has nothing to undo, because undoing never deletes records from your store. An undo also puts back the theme files a restore rewrote; stock levels are not part of it, and a file a restore added to a theme stays. Restores applied before 17 September 2026 did not save theme files before writing, so their undo leaves theme files as they are.

Backed up and exportable, but not written back into the store: blogs, articles, navigation and URL redirects. Product images and other media are captured with their metadata and not re-attached by a restore, and the collection image is not written back either. A collection sorted by hand gets its products back in their saved order. A product or collection that was deleted comes back under a new ID. The web address (handle) comes back with it when no other record has taken it; when one has, the record still comes back, at a new address with a suffix, and the result names it. It goes back on the Online Store only if the backup shows it was there and you have allowed publishing: products from versions stored since 18 September 2026, collections from versions stored after your store allowed publishing. Otherwise it comes back unpublished in every sales channel. Other sales channels are not restored. Collection versions stored before 17 September 2026 do not hold Shopify’s newer collection features (more than one source in a collection, excluded products, conditions mixed with hand-picked products): restoring one of those versions brings back the collection’s title, description and products, not those parts. Orders and customers are archived, compared and exportable, and never restored in place - Shopify creates a new order rather than bringing the original back, so calling that a restore would not be true. Theme files are written back into the theme they came from once you allow it; a theme you deleted comes back as a .zip you upload yourself, because we never create a theme. The full map is on what backup apps can and cannot restore.

What happens if I uninstall the app?

Your backup is kept for about four weeks and then erased completely: Shopify confirms an uninstall 48 hours after it happens, and the 25-day countdown starts from that confirmation. The window exists because apps get uninstalled by accident: reinstall inside it and your history is still there. If you want it gone sooner, the Settings screen has an erase button, and everything becomes unreadable the moment you confirm it by email.

Where is my data kept, and who can read it?

In Cloudflare R2, as ciphertext. Backups are encrypted in transit and at rest with a key unique to your store, and the storage provider never holds that key: what sits on their disks is unreadable without it. The index that points at those objects lives in our own database on a rented server, and it holds pointers and titles, not the contents of your records.

How long depends on your plan: the free plan keeps 7 days of version history, paid plans keep 30 to 365 days. The most recent version of every record is kept whatever the plan, and uninstalling starts a four-week countdown before everything is erased.

Every read of protected data is written to an access log you can see in the app, and nobody here browses your data: there is no console that shows it. More detail is on the security page and in the privacy policy.

Do you charge by orders?

No. A plan sets two things: how many products are covered and how far back the version history goes. The number of orders is not part of the calculation on any plan, so a store doing 50,000 orders a month pays the same as one doing 50 if their catalogues are the same size. Orders are archived without a cap on how many of them there are.

Two limits worth naming, because neither is a limit on order count and both are easy to mistake for one. The history window on your plan is how far back you can roll a record that changed, not how long a record is kept: at least one copy of every order stays in the backup however old it is. And within a single order we capture up to 250 fulfilments and 250 refunds - a ceiling inside one order, not on how many orders you have.

One limit is Shopify's rather than ours: apps see only the last 60 days of orders unless the merchant's store has approved access to the full history. We hold that approval, so the whole archive is captured - what that limit is.

Will it slow down my storefront?

No. The app runs entirely inside your Shopify admin: it adds no code to your theme and makes no requests from your storefront. It reads your theme files to back them up, and it writes them only when you ask for a theme restore and approve the plan - never on its own, and shoppers never touch it.

Who answers support?

The people who build the app. Write to support@storevault.app and you reach the same person who works on the code, not a queue. If you are an agency looking after several stores, the agency page is the shorter route.