scope: catalog data only — no customer, order, or payment access
Privacy policy
AnyMap syncs catalog data one-way, from your ERP into Shopify. This page explains exactly what we receive, what we store, why, and how to get rid of it.
last_updated: 17 July 2026
The short version
- → We never see your customers, orders, or payment data. The access we ask Shopify for doesn't include them.
- → We handle catalog data: products, variants, SKUs, barcodes, prices, stock levels, images, and custom fields.
- → Data moves one way — ERP → Shopify. We never write back to your ERP.
- → We don't sell your data, and we don't use it to train machine-learning models.
- → Ask us to delete everything and we will, within 30 days.
What we access in your Shopify store
When you install AnyMap, Shopify asks you to grant a specific, listed set of permissions. These are the only ones we request, and they are the complete set of what we can reach:
- read_inventory
- read_locations
- read_markets
- read_products
- read_publications
- write_inventory
- write_markets
- write_products
- write_publications
Notice what isn't there: no read_customers,
no read_orders, no payment access.
Shopify enforces this at the API level, so it isn't a promise we're asking you to take on trust —
a request for that data from us would simply be refused.
What we store, and why
your store connection
Your store's .myshopify.com domain and the access token Shopify issues at install. Without these we can't talk to your store at all. The token is what Shopify's own OAuth flow hands us; it expires and is renewed automatically.
the catalog data you send us
Whatever your ERP posts to your private ingest URL — typically product titles, SKUs, barcodes, prices, stock levels, image URLs, and custom fields. This is business data about your products. If you choose to put personal data in a product field, it reaches us too, so please don't.
your field mappings
The mapping template describing how your ERP's fields correspond to Shopify's. This is configuration, and it's what lets a sync repeat without you rebuilding it each time.
the audit log — including before-and-after snapshots
For every sync we record what changed and what the value was beforehand. This is what makes one-click rollback possible: without the prior value, an undo has nothing to restore. It's the core of the product, and it's the main reason we retain data at all.
your ingest API key
Stored only as a SHA-256 hash. The plaintext key is shown to you once, at creation, and never again — we cannot recover it, only issue you a new one.
your subscription status
Which plan you're on and whether it's active. Billing itself is handled entirely by Shopify — we never see your card details.
Who else touches your data
As few parties as we can manage. We don't sell, rent, or share your data with advertisers or data brokers — there is no such arrangement, and there won't be.
- · Shopify — the destination for every sync, and our billing processor.
- · Our hosting provider — runs the servers and database where the above is stored.
We disclose data otherwise only where the law requires it.
How long we keep it, and how to get rid of it
We keep your mappings and audit history for as long as AnyMap is installed, because that history is what a rollback restores from. Delete it and old syncs stop being reversible — which is a real trade-off, and yours to make, not ours.
When you uninstall, we stop syncing immediately: the access token stops working the moment Shopify revokes it, so no further reads or writes are possible. Email privacy@anymapsync.com to have your remaining data erased and we'll do it within 30 days.
If you're in the EU/UK, the GDPR gives you rights to access, correct, export, restrict, or erase your data, and to complain to your local supervisory authority. Ask and we'll act — we won't make you cite a statute to get a reply.
Security
Traffic runs over HTTPS. Your ingest endpoint is authenticated with a key we store only as a hash, and it's rate-limited and size-capped to blunt abuse. Each store's data is scoped to that store. No system is perfectly secure and we won't pretend otherwise — but if a breach affects you, we'll tell you and the relevant authority as the law requires, rather than hoping you don't notice.
Changes, and how to reach us
If we change this policy in a way that materially affects you, we'll say so in the app rather than quietly editing this page and moving the date.