Privacy Policy — ByeLabel Order Sync

What the browser extension reads, what it sends, and what it keeps.

Applies to the ByeLabel Order Sync extension for Chrome. Effective 1 September 2026 · Version 1.0.0

What this covers

This policy covers the ByeLabel Order Sync browser extension only, and lives at extension.byelabel.com/privacy-policy. The ByeLabel web application and every other ByeLabel product have their own privacy policy.

Who is responsible for what

The extension exists to move a seller's own order data between two places the seller already controls: their marketplace shop and their ByeLabel account. It creates no new relationship with buyers and shows nothing to them.

Where that data describes a buyer, the seller is the data controller and ByeLabel acts as a processor on their instructions. The extension itself is a conduit that runs on the seller's own device, in their own browser, under their own marketplace login.

What the extension accesses

Only on user connected marketplace url, only while the seller has a tab open there, and only while they are signed in to their own seller account.

What is sent to ByeLabel

The marketplace returns a large order record. The extension reads only the delivery details from it and sends only these fields to the seller's own ByeLabel account:

• The marketplace order number
• Recipient name
• Delivery address — street lines, city, state or region, postcode, country
• Recipient email address and phone number, where the marketplace provides them

Separately, once the extension has marked an order as dispatched on the marketplace, it reports the outcome back: the ByeLabel order reference, whether the marketplace accepted it, and an error message if it did not.

That is the complete list. Nothing else from the order record — item details, prices, buyer profile, message history — is transmitted.

What is written back to the marketplace

For orders the seller has already bought a shipping label for in ByeLabel, the extension marks the order dispatched on the marketplace and attaches the carrier name, the tracking number, and the seller's own note if they set one. It performs no other action on the seller's marketplace account.

What is stored on the device

All of it lives in the browser's local extension storage. None of it is transmitted except as described above.

• for the one ByeLabel store the extension is linked to.
• — whether automatic sync is on, how often it runs.
• — the marketplace user and shop ID, the linked store name, how many orders were handled, and the last error.
• , capped at the 200 most recent entries. It holds order references and error messages, and is what the popup shows.

What the extension never does

How long data is kept

On the device: until the seller unpairs or removes the extension. Unpairing revokes the session on the server and clears the stored tokens, shop identifiers and activity log; only the seller's own preferences remain. Removing the extension erases everything.

In the seller's ByeLabel account: the delivery details this extension supplies are masked 30 days after the shipment is last updated. The recipient's name, email address, phone number, street, city and postcode are irreversibly replaced with ***. The order record itself stays, so the seller keeps their own history — but the personal data in it is gone and cannot be recovered.

Buyers' rights

Buyers who want to access, correct or delete their information should contact the seller they bought from — the seller controls that data and can act on it in both the marketplace and ByeLabel. Sellers who need ByeLabel to act on such a request can reach us at the address below, and we will act on the seller's instruction.

Changes to this policy

If the extension begins handling data differently, this page is updated before that version is released, and the effective date at the top changes. Material changes are communicated to sellers directly.

Contact

ByeLabel Order Sync · this policy applies to extension version 1.0.0 and later until superseded.