Reordy — Privacy Policy

Who we are

For any question about this policy, or about data we hold, use Help & Support inside the app — it reaches us directly and tells us which store is asking.

What the app reads from a store

Only what the forecasts are made of. When a merchant installs Reordy, Shopify asks them to approve the access below, and the app reads nothing outside it:

• Products and variants — titles, SKUs, prices, and cost per item. Cost per item is also written back, when the merchant fills it in from our dashboard.
• Inventory — stock levels per location, incoming shipments and transfers, and the locations themselves.
• Stock history — daily stock on hand and stock adjustments per location, read through Shopify's reporting API. This is how the app measures how fast a product sells.
• Open fulfillment orders — the quantities still to ship, the location they are assigned to, and the date the order was placed. Units that are ordered but not yet shipped are not counted as sold.
• Shop settings — the store's name, currency and time zone, so figures are dated and priced the way the merchant sees them.

What the app never reads

Reordy never asks Shopify for the names, email addresses, phone numbers or postal addresses of a store's customers, and stores none of them. The app does hold permission to those four fields: Shopify opens its reporting API, which the stock history above comes from, only to apps approved for them, so we had to request them. No query the app makes selects any of them. It does not read customer accounts, carts, checkouts, or payment details, and it has no access to payment methods or card data. Of a store's orders it reads two things: how many units of which variant are still to ship, and the day the order was placed.

Personal data we do process

Three pieces, all of them belonging to the merchant or their staff rather than to a shopper:

• The store owner's email address, from Shopify, used once to confirm that the first sync has finished.
• Digest recipients — the addresses a merchant enters themselves to receive the daily summary. They are used for that and nothing else, and are removed when the merchant removes them.
• Support messages — if a merchant writes to us from the app's support page, we keep what they wrote and the email address or phone number they asked us to reply to.

Where it is stored

In a PostgreSQL database and application servers run by Render in the United States (Oregon). Render encrypts the database, its replicas and all of its backups at rest with AES-256, and connections to it are encrypted in transit. What we store is the figures the app works out — stock, sales rates, reorder points, ABC classes, transfer suggestions — keyed by the store's domain and by Shopify's own product and location identifiers.

Who else sees it

• Shopify — the source of the data and the host of the admin the app runs inside.
• Render (United States) — hosting and the database.
• Resend — delivery of the emails the app sends: the daily digest and the first-sync confirmation.
• Telegram — a support message written from the app is also delivered to us over Telegram so that it is seen quickly. It carries what the merchant wrote and the contact they gave.

Nothing is sold, rented, or shared with anyone else, and nothing is used to train models or to advertise.

How long we keep it

A store's data lives as long as the app is installed. When the app is uninstalled, everything it worked out for that store is deleted automatically — stock metrics, settings, suggestions, the lot. The one thing kept past uninstall is a support message, because it may still be owed a reply; when Shopify sends the shop/redact request that follows an uninstall, that goes too, and nothing of the store remains.

Reordy answers all three of Shopify's mandatory privacy webhooks. A request to see or erase a customer's data is answered truthfully: we hold none.

Security

• Everything travels over HTTPS; the database is encrypted at rest.
• Access to production is limited to the people who operate the app, over accounts protected by two-factor authentication.
• Test and production data are kept apart.
• We process the minimum needed for the app to work, which is why the list above is as short as it is.

Requests and complaints

A merchant can ask what we hold about their store, ask for it to be corrected, or ask for it to be deleted, through Help & Support in the app. Uninstalling the app has the same effect as a deletion request and needs no correspondence.

Changes

If this policy changes in a way that affects what we read or keep, the merchants who have the app installed are told by email before it takes effect.