Privacy and data handling
Zubaz LLC · Updated September 23, 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 SellerCloud, the selected shipping carrier, Veeqo when used to obtain rates or buy labels, our hosting provider Railway 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 14 days after the carrier-confirmed delivery date for every purchased package, with an earlier backstop of 30 days after each package's recorded fulfillment completion (printer submission plus successful SellerCloud shipment update) or first confirmed carrier movement, whichever occurs first. The backstop does not require a delivery scan and is not extended by an open claim, reprint or later delivery confirmation. Every active package must meet a deadline. Active purchases, live printing and station locks can delay cleanup and generate administrator alerts. Missing shipment evidence requires review; label purchase or printing alone never starts the backstop or proves delivery. Printer submission is not proof of physical dispatch or delivery.
Saved shipping payloads, customer details, labels, invoices, integration settings and supported local backups use application-level AES-256-GCM encryption. Deployment secrets hold the encryption key outside the application volume. Data is decrypted in memory for authorized use.
Confirmed voided labels are eligible for cleanup after 14 days. Confirmed canceled orders are eligible after 14 days, with a fresh order-status check before deletion. Active postage, recent voids, shared active label purchases, held print jobs and unresolved operations require review and can delay cleanup. Voiding one label does not erase a replacement label or prevent the order from being shipped again.
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.
Encrypted recovery copies are stored in a separate geographically separated service. Copies expire after two days. Customer-data cleanup also removes managed remote recovery copies before completing and retries if remote deletion cannot be confirmed. Deletion resumes when the archive returns after an outage.
Security events exclude buyer payloads and credentials. A separate encrypted archive retains these events for 366 days with restricted access and application-enforced retention.
This cleanup covers supported records and local backups on the application volume. It does not delete records in SellerCloud, carrier systems, cloud snapshots, Veeqo records, 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.