StockLume Privacy

Effective date: 2026-09-20

StockLume stores your Shopify shop and session identifiers so the app can authenticate and work with your store. Shopify authentication may also provide optional merchant staff session fields, such as a staff name or email; these are used for session administration, not shopper profiling.

StockLume imports product and variant IDs, product titles, variant titles, SKUs, tracked inventory, active-location quantities, and aggregate net order-line quantities from the last 30 days to calculate demand. Inventory and demand are retained in the latest two complete snapshots. Product and variant details are also retained with procurement settings until the shop is deleted.

Merchants may enter supplier names, supplier email addresses, supplier contact names, phone numbers, addresses, contact notes, payment terms, supplier SKUs, lead times, minimum order quantities, case quantities, safety stock, purchasing rules, supplier currencies, exact supplier costs, and supplier cost history. StockLume also stores merchant-owned purchase orders with immutable supplier and line snapshots, receipts, accepted/damaged/rejected and short-shipment discrepancies, reversals, actor identifiers, inventory reconciliations, landed-cost revisions, and audit events. This information is used for procurement planning, reporting, reconciliation, and exports.

When a merchant emails a purchase order to a supplier, StockLume sends the PO PDF to the supplier email address stored with that supplier or PO, through the SMTP mail server configured by the app operator, with the shop's contact email as the reply address. The email contains a signed confirmation link that expires after 14 days and can be answered once. StockLume stores the link's recipient address, send and expiry times, and the supplier's answer (ship date, proposed quantities, an optional note, and the answer time) together with the merchant's approval or rejection, as part of that PO's history. The supplier page sets no cookies and is not indexed by search engines.

Reorder alert emails go only to the merchant: to the address the merchant enters, or the shop's contact email. They list product and variant titles, SKUs, suppliers and reorder dates. StockLume stores the alert settings and which variants were already notified. If the merchant turns on Shopify Flow, StockLume sends Flow the same product, supplier and purchase order details for the merchant's own workflows; no shopper data is included.

On plans with change history, StockLume receives Shopify's product, inventory item and inventory level update webhooks, limited to product and variant ids, titles, SKUs, prices, unit costs, available quantities and update times. It stores the price, cost and quantity changes with the Shopify staff ID of the person who made a change in StockLume. History is kept for 90 days (365 on Plus), 30 days after a downgrade, and is deleted with the shop's other data on uninstall.

Imported order data is limited to aggregate line quantities and current quantity/net-demand information needed for planning; StockLume does not import separate return records or shopper fields. Freeform merchant-entered notes may contain personal data, so merchants should avoid entering information that is not needed for procurement. Shopify handles billing. Uninstall and shop-redaction webhooks delete active shop data; customer privacy webhooks are authenticated and acknowledged without importing shopper data.

To measure installs and conversions, StockLume keeps a record of install, uninstall and plan-change dates for the store domain, with the plan and its list price. After a shop-redaction request the store domain is replaced with a random identifier, so only an anonymous record of install, uninstall and plan-change dates remains.

The app keeps the latest two complete inventory snapshots. Procurement history is retained until authenticated uninstall or shop-redaction deletion of the active database record. Deleted records may remain in managed backups until those backups expire. Merchant-controlled exports are retained wherever the merchant saves them. Managed DigitalOcean backups have a seven-day recovery window. Temporary logical backups and restore-test databases are retained during release verification and recovery, then deleted when that work concludes; they are separate from the managed seven-day backup cycle. Data controller/operator: Alhussain Alajmi, Sabah Al-Salem, Co-op Society No. 1, Kuwait. See Support for contact details.