Privacy Policy

Last updated 18 October 2026

This policy covers Meirun WMS, the warehouse management and order management service operated by AOOS SIGN INC, a California corporation ("we"), at meirunwms.com, meirun.com and their subdomains, including wms.meirun.com and oms.meirun.com.

Who the data belongs to

Almost all personal data we hold arrives from a business customer, not from the person it describes. A seller connects their sales channel or files an order, and the order carries the name, address and telephone number of the buyer who placed it. For that data the seller is the controller and we are their processor: we hold it to receive, store, pack and ship the goods they instruct us to ship, and for no other purpose.

We are the controller for the account data of the people who sign in to the service: their name, email address, and the record of what they did in it.

What we collect

• Recipient details — name, delivery address, telephone number and, where the sales channel gives it, email address. Used to pick, pack, label and dispatch a shipment, and to answer a delivery enquiry about it.
• Clearance lot enquiries — the name, email address and, if given, telephone number, shop name and message of a person asking to buy a clearance lot on the public lots page. Passed to the seller of that lot so they can answer, and stored encrypted.
• Clearance lot purchases — the buyer's name, email address and telephone number, and for a tax-exempt purchase the seller's permit number and resale certificate. Card details are entered on Stripe's page and never reach us; we keep only Stripe's payment reference. The buyer's name and telephone go to the warehouse that hands the lot over; the certificate is kept as the record of an exempt sale that sales-tax law requires.
• Order and inventory records — what was ordered, what was in each box, its dimensions and weight, and what happened to it.
• Account details — the name and email address of each person given a login. We never store a password; only a salted one-way hash of it.
• Activity and security records — the changes made through the service, kept so a seller can see what was done on their account and by whom; and a security log of every request to the service's interfaces: which account made it, when, from which network address and browser, and whether it was allowed. The security log holds no buyer details, no search terms and no request contents.
• Platform credentials — the keys and tokens a seller supplies, or authorises us to obtain, so we can collect their orders.

We do not collect buyer payment details. Payment is taken by the sales channel, and card and bank numbers do not reach this service.

Data from Amazon

When a seller authorises the service to their Amazon store, we receive that seller's orders through Amazon's Selling Partner API. We use them only to fulfil those orders and to report their fulfilment. The buyer's name, address and telephone number are used to label the parcel and are passed only to the carrier delivering it. We never use them to contact the buyer, we never combine one seller's Amazon data with another's, and we erase them 30 days after the order ships.

Where it goes

Recipient details are disclosed to the parties that have to have them for a parcel to arrive: the carrier or freight forwarder handling the shipment, and the customs authorities of the destination country where a declaration is required. Nothing is sold, rented, or shared for advertising. We do not use recipient data to build profiles and we do not market to buyers.

Where a seller's sales channel requires it, order status and tracking numbers are sent back to that channel. Where a seller switches it on, the buyers of orders from that seller's own online store (never Amazon orders) are sent delivery updates by email or text message; text messages are sent through Twilio Inc.

Payments for clearance lots are processed by Stripe, Inc., under its own privacy policy. Where automatic translation is switched on, messages written between a seller and a warehouse are translated by Alibaba Cloud's machine translation service.

Where it is held

Data is held in Silicon Valley, California, United States, on servers we rent in Alibaba Cloud's US region. Each warehouse's records live in a separate database file, so a query made for one warehouse cannot reach another's records. Buyers' names, addresses, telephone numbers and email addresses, the keys and tokens for sellers' sales channels, and two-step sign-in secrets, are encrypted at rest with AES-256-GCM, under a key held only in the server's own environment and replaced at least once a year. Traffic to the service is encrypted in transit with TLS. Backups are taken every six hours and kept for fourteen days; encrypted fields stay encrypted in them.

How long we keep it

A buyer's name, address, telephone number and email address are erased from a shipment 60 days after it ships or is cancelled, and 30 days after for an order that came from Amazon. What remains of the shipment — what was sent, by which carrier, its tracking number, weight, charges and dates — is kept for as long as the customer's account is open and for seven years afterwards, which is the period customs and tax authorities may ask us to produce it for. Security log records are kept for 400 days. Personal data that is not part of a shipment record is deleted within 90 days of an account closing. Platform credentials are deleted as soon as a connection is removed.

Your rights

You may ask for a copy of the personal data we hold about you, ask us to correct it, or ask us to delete it. If the data reached us from one of our business customers, we will pass the request to that customer and act on their instruction, because the data is theirs and not ours to give away. Write to AOOS SIGN INC, 725 S Brea Canyon Rd Ste 3, Walnut, CA 91789, United States, or email privacy@meirunwms.com. We answer within 30 days.

Security

Each person signs in with their own account. Passwords are stored only as a salted one-way hash, computed with scrypt; a password must be at least ten characters, none of a person's last ten passwords can be used again, and an account is locked after repeated failed attempts. Two-step sign-in with an authenticator app is available on every console, and a warehouse can require it of all its staff. Session tokens are stored only as a hash, so a copy of our database is not a set of usable sessions. A session lasts at most 30 days and ends after 7 days without use (14 days on the sellers' console). Changing a password ends every session belonging to that account.

A warehouse gives each member of staff a role, and a role reaches only the screens and interfaces it is granted. Credentials and access tokens belonging to a seller's sales channels are never returned to a browser: a screen is told whether one is stored and the last four characters of the identifier, and nothing more.

Access to a seller's account by warehouse staff, where a seller has asked for help, is recorded against the person who performed each action and the operator acting on their behalf, and that record is visible to the seller. Every request to the service's interfaces is written to the security log, which is reviewed at least every two weeks.

Children

The service is sold to businesses and is not directed at children.

Changes

If this policy changes materially we will tell account holders by email before the change takes effect. The date at the top is the date of the current version.

Contact

AOOS SIGN INC, 725 S Brea Canyon Rd Ste 3, Walnut, CA 91789, United States. Email privacy@meirunwms.com.