OpenBoxesLift
    • FeaturesWhat OpenBoxes Lift includes
    • For 3PL warehousesPick, pack, ship and client billing
    • IntegrationsAlerts, the API and webhooks
    • SecurityHow we protect your data
  • Pricing
  • Demo
    • DocsGuides and API reference
    • BlogArticles on running inventory
    • VideosShort guided walkthroughs
    • What's newMonthly product updates
    • AboutWho we are
    • ContactTalk to the team
    • NonprofitsOur nonprofit discount
Sign InStart Free Trial

WooCommerce and Amazon Connections: Privacy Notice

Last updated: November 8, 2026

Table of Contents

  • 1. About This Notice
  • 2. Who Does What
  • 3. WooCommerce Stores
  • 4. Amazon Seller Accounts
  • 5. Why We Use It
  • 6. Where and How It Is Stored
  • 7. How Long We Keep It
  • 8. Disconnecting a Store
  • 9. Privacy Requests
  • 10. Contact Us

1. About This Notice

This notice explains what OpenBoxes Solutions LLC ("we," "our," or "us") reads from a WooCommerce store or an Amazon seller account that is connected to OpenBoxes Lift, what we store, what we send back, and how long we keep it. It adds to our Privacy Policy and, for warehouses that use OpenBoxes Lift, our Data Processing Agreement. The OpenBoxes Lift app for Shopify has its own Shopify app privacy notice.

A warehouse (a third-party logistics provider, or "3PL") that runs OpenBoxes Lift can ask a merchant to connect the merchant's online store. Orders from that store are then picked, packed and shipped by the warehouse, and tracking details and, if the warehouse chooses, stock levels are sent back to the store. Apart from a check that the store's address belongs to a WooCommerce store, nothing described here happens unless the merchant approves the connection.

The WooCommerce connection is available now. The Amazon connection is not available yet. This notice describes how they work, and it applies once a merchant connects a WooCommerce store or an Amazon seller account.

2. Who Does What

  • The merchant owns the WooCommerce store or the Amazon seller account, decides which warehouse fulfils its orders, and is responsible for its buyers' personal information.
  • The warehouse (3PL) is the merchant's service provider. It fulfils the orders under its own agreement with the merchant.
  • We provide the OpenBoxes Lift software the warehouse uses. We process order data on the warehouse's behalf, as its processor.

3. WooCommerce Stores

How the connection works

The warehouse gives us the store's web address, and our staff approve that address before we send it any request. The merchant then approves the connection in WooCommerce (or creates a key by hand and gives it to us), which creates a WooCommerce REST API key with read and write access named "OpenBoxes Lift for" followed by the warehouse's name. We read the store through WooCommerce's REST API only; no WordPress plugin is installed.

The key acts as the WordPress user who approved it, and WooCommerce lets a key with read and write access reach more of the store than we use. Our software calls only a fixed list of WooCommerce requests, for orders, order notes, shipment tracking, products and stock, and asks only for the fields listed below. We ask the merchant to approve as a Shop manager user, which gives the key less access than an administrator.

About the store, we store:

  • the store's web address;
  • the REST API key and its secret, stored encrypted;
  • the store's product and variation identifiers, SKUs, product names and variation attributes, and each product's type, status, whether it is virtual or downloadable, and its stock and backorder settings, so orders and stock can be matched;
  • the names of the store's shipping methods.

For each order that is ready to ship, we read and store:

  • the order number, its status and dates, and WooCommerce's identifiers for its lines;
  • the ship-to name, company, address (street, city, state or province, postal code and country) and phone number;
  • the products and quantities to ship, and any quantities refunded;
  • the shipping method the buyer chose, by name.

If the ship-to phone number is empty and the shipment needs one (for example, a shipment to another country), we read the billing phone number of that order only. If the store's answers ever include any other billing detail, we stop reading the billing phone number for that store, and the warehouse asks the merchant for a phone number instead.

We also read orders that are on hold in WooCommerce, so stock levels stay correct. For those we store only the products and quantities. We store an order's ship-to details only once it is ready to ship.

We never request or store:

  • the buyer's email address;
  • the billing address;
  • the buyer's customer account or customer history;
  • the buyer's IP address or browser details;
  • the note the buyer adds at checkout;
  • custom fields that plugins add to orders or order lines;
  • payment details, prices or order totals.

We ask WooCommerce for the fields listed above only. If a store sends more than we asked for, we discard the extra fields as we read the answer and never store them.

What we send back to the store:

  • the tracking number of each shipment: through the WooCommerce Shipment Tracking extension if the store has it, or otherwise as an order note addressed to the buyer, which WooCommerce emails to the buyer;
  • the order's status, set to Completed when it ships, unless the warehouse turns that setting off;
  • private order notes for the merchant, for example that the warehouse received the order, or that only part of it could be shipped. Private notes are not shown to the buyer;
  • stock levels for the products matched to the warehouse's products, only if the warehouse turns stock updates on, and, if the warehouse chooses, the setting that lets WooCommerce manage stock for those products.

We do not email the store's buyers ourselves. WooCommerce sends its usual emails, including the tracking details we add to the order.

4. Amazon Seller Accounts

How the connection works

The merchant authorizes OpenBoxes Lift in Amazon Seller Central from a link the warehouse sends. The connection covers orders on the United States Amazon marketplace that the merchant ships itself (merchant-fulfilled orders). Orders fulfilled by Amazon are not included. Of the restricted permissions Amazon offers, we ask only for the one that allows a seller's own shipping provider to see where an order goes (Direct-to-Consumer Shipping).

About the seller account, we store:

  • Amazon's identifier for the seller account, the marketplace and the store name;
  • the authorization Amazon issues to us (a refresh token), stored encrypted. The short-lived access tokens made from it are kept in memory only and never stored;
  • the seller SKUs, Amazon product identifiers (ASINs) and listing titles of the products matched to the warehouse's products.

For each merchant-fulfilled order of matched products, we read and store:

  • Amazon's order number and item identifiers, the order's status, its latest ship and delivery dates, whether it is a Prime order, and whether the buyer asked to cancel it;
  • the seller SKUs and quantities to ship;
  • the recipient's name, address (street, city, state, postal code and country) and, when Amazon provides it, phone number. We request these once, when the order is created at the warehouse, and not again.

We never request or store:

  • the buyer's email address, or any of the buyer information Amazon offers separately from the shipping recipient;
  • payment details, prices or order totals;
  • orders fulfilled by Amazon.

What we send back to Amazon:

  • a shipment confirmation for each order: the carrier, the tracking number, the ship date and the items shipped;
  • the quantity available for each matched product, so the listing matches what the warehouse holds.

We do not email Amazon buyers. Amazon tells the buyer when the order ships.

Amazon's authorization lasts 12 months. Before then, the warehouse asks the merchant to authorize again. Without that, we stop reading the account and sending updates to it.

5. Why We Use It

We use this information only so the warehouse can fulfil the merchant's orders: to receive orders, buy shipping labels and ship to the address given, send tracking details and stock levels back to the store, and handle cancellations and changes. The ship-to details go to the shipping-label service the warehouse uses (for example, its own ShipStation account) and to the carrier, so the parcel can be labelled and delivered. That service may send the buyer its own shipping emails, depending on the warehouse's settings there. We do not sell this information, use it for advertising or marketing, or use it to contact the merchant's buyers ourselves. This is Customer Tenant Data under our Privacy Policy, and we do not use Customer Tenant Data to train machine-learning models.

6. Where and How It Is Stored

  • Data is stored and processed in the United States, on Google Cloud Platform. Our other service providers are listed on our sub-processors page.
  • Each warehouse's order data is kept in its own database. A shared directory of ours records which warehouse each store or seller account is connected to, so that it is connected to only one at a time.
  • The ship-to details of each order are encrypted with a key that belongs to the warehouse's account, which is itself protected by Google Cloud Key Management Service. The WooCommerce API key and the Amazon authorization are encrypted with that key too. For Amazon orders, the ship-to details are also sealed under keys kept for that seller account, which we destroy when the details must be gone.
  • All traffic between the store, us and the warehouse uses TLS.
  • Warehouse staff see a full address only when they need it, and each time they open one it is recorded. Our own staff open one only to finish a privacy request the warehouse has not finished, and that is recorded too.

7. How Long We Keep It

WooCommerce

  • An order's ship-to details (except the country and state or province), its WooCommerce order number, its line identifiers and the tracking details we sent are erased 12 months after the order is shipped or cancelled, or sooner when a privacy request asks for it (section 9). The same applies, 12 months after we last handled it, to the order number of an order the warehouse never took on (for example, one with nothing to ship).
  • After that, the order record keeps what the warehouse needs to bill for its work and count its stock: the products, quantities, dates, and the country and state or province. We also keep, for as long as the order record, a coded value made from the order number that cannot be turned back into the number without our key, so an erased order is never taken in again.
  • An order that is never shipped or cancelled keeps its details until the warehouse closes it. We prompt the warehouse to close it once it has been idle for 12 months.

Amazon

  • An order's ship-to details (except the country and state) are erased 30 days after the order ships, or 72 hours after it is cancelled at the warehouse. An order still open 30 days after its latest delivery date is cancelled at the warehouse and its details erased.
  • Copies in our backups become unreadable at the same time, because we destroy the keys the details were sealed under.
  • Amazon's order number and item identifiers are kept after that, so a shipment can still be confirmed and an order is never taken in twice, and are deleted 18 months after the order is shipped or cancelled at the latest.

8. Disconnecting a Store

WooCommerce

When the warehouse disconnects a store, we erase the API key and send the store no further requests. If the warehouse chooses to set the matched products to out of stock as it disconnects, we do that first, within an hour; otherwise stock levels in WooCommerce stay as we last sent them. Orders not yet shipped are held at the warehouse. Thirty days later we delete the store's details, its product matches, its shipping-method names and our records of what we sent it. Orders keep the retention in section 7.

We cannot remove the key from WooCommerce ourselves. The merchant should delete the "OpenBoxes Lift for" key in WooCommerce (Settings, then Advanced, then REST API). Deleting the key there also stops our access at once. The store's details stay with the warehouse until it disconnects the store, so the merchant should also ask the warehouse to disconnect.

Amazon

The merchant can remove OpenBoxes Lift in Amazon Seller Central at any time, and the warehouse can disconnect the account. Either way, we delete the authorization and stop reading the account. When the warehouse disconnects, we first set the quantity of each matched product to zero on Amazon and cancel, at the warehouse, the orders it has not started. When the merchant removes OpenBoxes Lift, we can no longer update Amazon, so its quantities stay as we last sent them, and orders not yet started are held at the warehouse. Within 30 days, we delete everything we hold from that seller account: ship-to details, Amazon's order numbers and item identifiers, and product matches. Any order still open then is cancelled at the warehouse first, and the keys its details were sealed under are destroyed.

9. Privacy Requests

A buyer who wants to see, correct or erase their personal information should contact the store they bought from. The merchant can pass the request to its warehouse, which can view or erase the details of that buyer's orders in OpenBoxes Lift. Merchants and warehouses can also contact us (section 10).

WooCommerce does not send privacy requests to connected services. If the merchant uses WooCommerce's own tool to remove a buyer's personal data from an order, we see this the next time we read the order and erase our copy of its ship-to details once the order has shipped or been cancelled, so the warehouse can still deliver it. We track each such request so that it is finished within 30 days.

10. Contact Us

Email: privacy@openboxes.cloud
Help with a connection: support@openboxes.cloud
Mailing address: OpenBoxes Solutions LLC, Boston, Massachusetts, United States

A buyer with a question about an order should contact the store they bought from first. The store can contact its warehouse or us.

OpenBoxesLift

Warehouse and inventory management made simple.

Product

  • Features
  • For 3PL warehouses
  • Integrations
  • Pricing
  • Lift vs Self-Hosted
  • Status
  • Security

Resources

  • Documentation
  • Getting Started
  • 3PL Guide
  • API Reference
  • Blog
  • Ways to Host OpenBoxes
  • Lift vs mSupply
  • OpenBoxes vs OpenLMIS
  • Community

Company

  • About Us
  • Contact
  • Careers
  • Nonprofits

Legal

  • Terms of Service
  • Privacy Policy
  • Cookie Policy
  • Data Processing Agreement
  • Sub-Processors

© 2026 OpenBoxes Solutions LLC. All rights reserved.