Privacy and data handling

Zubaz LLC · Updated September 17, 2026

Zubaz Shipper is our warehouse fulfillment application. For privacy requests or to report a security concern, contact adams@zubaz.com.

Information used for fulfillment

The application processes order identifiers, recipient names and delivery addresses, contact details needed for shipping, purchased items, package measurements, shipping charges, tracking information, labels and required invoices. Staff account and operational records support access control, troubleshooting and prevention of duplicate postage purchases or printing.

Information comes from connected order-management systems, authorized sales channels, shipping carriers and authorized staff. We use it to prepare, purchase and print shipping documents, update fulfillment information and resolve shipping problems. This application does not use customer information for advertising, profiling or unrelated marketing.

Who receives information

Fulfillment information is shared with our connected order-management provider, the selected shipping carrier, hosting providers and authorized warehouse systems as needed for these functions. Application access depends on assigned roles. Printed labels, invoices and printer queues can also contain personal information.

Storage and retention

Automatic cleanup checks completed app shipments every minute. It removes recipient details in saved shipping requests and carrier responses, address suggestions, saved labels and invoices, and matching copies in local application backups after all package labels and required invoices have finished submitting to the printers and the shipment update to SellerCloud has succeeded. Unfinished purchases, print jobs, invoices and shipment updates delay cleanup until reviewed or completed. Printer submission is not proof of physical dispatch or delivery.

Expired documents cannot be reprinted or fetched again through this app. Restricted order identifiers, tracking, carrier, postage and fulfillment status remain for reconciliation and duplicate-purchase prevention. These identifiers may still be personal information. Staff accounts, customer billing profiles and integration credentials have separate lifecycles.

This cleanup covers supported records and local backups on the application volume. It does not delete records in SellerCloud, carrier systems, cloud snapshots, exports, warehouse computers, printer queues or physical copies. Older orders without reliable completion records require review. These remaining copies and exceptions need separate retention procedures.

This notice does not certify compliance with any marketplace's retention or security requirements.

Requests and corrections

Contact adams@zubaz.com to request access, correction or deletion, or report suspected misuse. We may need to verify your identity and authority before acting. Applicable recordkeeping and fulfillment obligations may affect a request. Please do not include passwords, API tokens, complete shipping labels or unnecessary customer information in an initial message.

We will update this notice when our processing practices change.