MarketGuard resource

Privacy

Last updated 14 September 2026

What MarketGuard reads

MarketGuard requests only the Shopify permissions used by monitoring and the optional, merchant-confirmed Currency Guard setup:

• read_markets discovers active Markets and their regional configuration.
• read_products reads product, variant, price and shipping eligibility evidence.
• read_publications verifies whether selected products are available in each Market.
• read_validations inspects MarketGuard’s existing checkout validation before updating it.
• write_app_proxy configures the authenticated storefront route used by Currency Guard.
• write_inventory marks only the confirmed protected product’s inventory items non-shippable.
• write_products can set a fixed price for the selected product in the chosen Market price list after confirmation.
• write_validations installs or updates MarketGuard’s exclusive-currency checkout rule.

Monitoring does not write store data. Currency Guard performs those listed writes only after explicit confirmation. MarketGuard never writes catalogues, publications, translations, orders, customers or merchant theme code.

MarketGuard does not access customer or order records for monitoring. Shopify may include customer identifiers in mandatory privacy requests; MarketGuard acknowledges these requests without retaining their customer payload.

What MarketGuard stores

MarketGuard stores what it needs to tell you when something changed: which products and Markets you monitor, the policies you configure, the last verified state of each product and Market pair, findings and their history, scan records, webhook de-duplication records, and notification settings and delivery metadata.

Currency Guard records its storefront event name, the shop installation, the numeric product ID and a short failure reason. It does not record customer, address, cart-content or payment data for these events.

It does not keep a full catalogue mirror. It retains the product and variant identifiers, current and previous prices, currencies and verification evidence needed for monitoring. Finding and change records may include product titles and the values involved in the change.

Monitoring state is stored in Shopify app-owned metaobjects inside your own shop. Operational records such as job queues and sessions are stored in MarketGuard’s database.

Notification providers

If you connect an email, SMS or WhatsApp provider, MarketGuard stores the credential you supply, encrypted at rest, and the delivery metadata needed to report whether an alert was sent. Alerts are sent to the recipients you configure. Notifications are intended for you and your store team.

Deletion

When MarketGuard receives Shopify’s uninstall webhook, it deletes your sessions and operational database records, including provider connections and notification records. Shopify also sends a shop/redactrequest after uninstall; MarketGuard repeats its operational cleanup on receipt. Delivery or processing failures can delay cleanup. Contact support if you need assistance with deletion.

App-owned metaobjects and metafields are stored by Shopify and follow Shopify’s app-data lifecycle. A reinstall uses a new installation identity so retained monitoring records are not treated as current verification.

Shopify’s customers/redact and customers/data_request webhooks are acknowledged, and MarketGuard reports that it holds no customer data — because it does not.

Finding and change history is retained for the window included in your plan and is removed by scheduled retention processing after that window passes.

Sub-processors

MarketGuard runs on Google Cloud and stores operational data in Neon. It reads from and writes app-owned data to Shopify. If you connect a notification provider, messages you have configured are sent through that provider.

Contact

Questions about this page or about data MarketGuard holds can be sent through the support page.