Company · Privacy
Privacy policy
This launch draft explains how ZeeBooth Seller handles platform information. It must be reviewed by qualified legal counsel and updated with final retention periods before production launch.
Information we collect
Account and business contact details; seller onboarding and U.S.-stock certifications; product, inventory-location, order, fulfillment, return, support, and finance records; uploaded business documents; and security and audit metadata. If a Seller enables the Amazon MCF API beta, we also process the Amazon account identifiers, authorization tokens, inventory, fulfillment orders, shipment events, tracking, fees, returns, and API logs needed for that feature. Customer shipping details are processed only to operate fulfillment and returns.
How information is used
We use information to authenticate users, review sellers and products, verify beta eligibility, assign and fulfill orders, coordinate returns, reconcile fees, maintain financial ledgers, provide support, prevent abuse, and meet legal and operational obligations. Amazon-connected data is used only for the enabled MCF workflow, security, troubleshooting, and required records.
Amazon authorization
Amazon or Hybrid Sellers may authorize a supported connection through Amazon's OAuth process. ZeeBooth does not request Seller Central passwords. Authorization tokens are used to request short-lived API access and may be revoked or disconnected. Disconnecting stops future access when effective but may not remove records needed for pending orders, returns, accounting, security, disputes, or law.
Sharing and service providers
Information is disclosed only as needed to authorized ZeeBooth personnel, the seller responsible for an order, the originating store, Amazon when an authorized MCF action is requested, and contracted infrastructure, email, storage, security, and payment providers. ZeeBooth does not sell personal information.
Security
Access is role-based and seller-scoped. Private files require server authorization, critical actions are audited, and production infrastructure is intended to use encrypted transport, managed secrets, restricted database access, backups, monitoring, and additional controls required for approved Amazon SP-API roles. Sellers must not send Amazon passwords, secret keys, or tokens through support messages or uploaded files.
Retention and deletion
Records are retained only for operational, financial, security, dispute, Amazon authorization, and legal requirements. Final retention periods and deletion procedures must be approved before launch and may vary by record type. OAuth tokens should be deleted or rendered unusable after disconnection unless temporary retention is required to complete revocation or investigate security events.
Your choices
Authorized users may correct account information, update a U.S.-stock certification, disconnect an available Amazon connection, ask about retained information, or request account closure subject to pending fulfillment, financial, fraud-prevention, audit, and legal retention requirements.
Privacy questions may be submitted through the Contact page. Existing sellers should use a tracked support ticket.