READ BEFORE USING THIS DRAFT
This page is a clearly marked owner-review draft. It is not a substitute for legal advice, does not establish a finalized privacy policy, and should not be published until the owner confirms the bracketed details and approves the final wording.
01 / SCOPE
What this draft covers
MySellerHQ is a software-as-a-service workspace for Amazon seller operations. This draft describes categories of information the service may handle, depending on how a customer uses the workspace and what access the customer authorizes. It does not add collection claims for analytics, advertising, location, or other purposes that are not evidenced by the current product surface.
02 / INFORMATION
Information MySellerHQ may handle
Depending on authorization and use of the service, the workspace may handle the following categories:
- Account and workspace identity details. These may identify a signed-in customer, the customer's workspace, and the people permitted to use it.
- Contact and support information. This may include information a customer submits when requesting access, asking a question, or seeking support.
- Connected seller-account details. These may include a provider or seller-account identifier, display name, connection status, and connection timestamps.
- Read-only Amazon operating data. Depending on the authorized scope and available source data, the workspace may represent sales, orders, units, inventory, listings, fees, advertising, reviews, account-health signals, alerts, and derived recommendations.
03 / PURPOSES
Why the service may use this information
The current product surface supports these high-level purposes:
- Provide the customer's operating picture and assistant experience.
- Surface alerts, source context, and derived recommendations for review.
- Maintain and display the customer's connected seller-account status.
- Support the service and respond to customer-submitted questions.
- Administer plans, hosted checkout, and subscription status.
- Protect the service and keep authorized workspace access working.
04 / AMAZON BOUNDARY
Read-only access and customer control
MySellerHQ does not ask for an Amazon password. The current workspace is read-only, and any authorized Amazon access is limited to the applicable read-only scope. MySellerHQ does not currently post changes to Seller Central. Customers remain responsible for their Amazon account, authorization decisions, source data, and review of any recommendation before acting on it.
05 / BILLING
Billing records and payment-card handling
MySellerHQ may retain billing and subscription records needed to administer the current pricing and hosted checkout flow, such as a selected plan, checkout or subscription identifiers, subscription status, and period information.
The current Growth path is configured as a payment-card-required seven-day trial and, when selected, a recurring monthly subscription. Payment-card details are handled through the configured billing provider's hosted checkout. This draft does not claim that MySellerHQ stores full payment-card details.
[OWNER-FILL: confirm the billing provider name and the final payment-card handling description before publication]
06 / CONNECTION TOKENS
Connection metadata and provider credentials
The current ConnectedSellerAccount application model stores connection metadata, including the provider, provider account identifier when available, display name, connection status, and created and updated timestamps. Provider credentials and token exchange stay outside that application model.
That model boundary is verifiable from the current application code, but it does not complete the owner's security documentation. The following details must be supplied and approved before publication:
- [OWNER-FILL: actual provider token system and token lifecycle]
- [OWNER-FILL: how connection tokens are encrypted at rest]
- [OWNER-FILL: key management, rotation, and access controls]
- [OWNER-FILL: transport and other security details]
07 / DISCONNECT & RETENTION
Disconnecting a seller account and what follows
At the time of this draft, the inspected seller-account API exposes GET and POST operations and does not expose a customer-facing disconnect or delete operation. This page therefore does not claim that a finished in-product disconnect flow exists.
OWNER-FILL POST-DISCONNECT POLICY
- [OWNER-FILL: exact customer action for disconnecting an account]
- [OWNER-FILL: provider-token revocation and deletion behavior]
- [OWNER-FILL: whether operating snapshots and derived recommendations are deleted or anonymized]
- [OWNER-FILL: data-retention period]
- [OWNER-FILL: what remains available after disconnect and for how long]
08 / CUSTOMER CHOICES
Questions and privacy requests
The owner should confirm which requests the service supports and the process for submitting them. The intended request categories to review are:
- Ask what information the service may hold and request a copy where applicable.
- Request correction of inaccurate account or workspace information.
- Request deletion or anonymization where the owner's policy permits it.
- Ask about disconnecting a connected seller account and related token handling.
- PRIVACY CONTACT
- [OWNER-FILL: legal/privacy contact email]
- LEGAL ENTITY
- [OWNER-FILL: legal entity name]
- MAILING ADDRESS
- [OWNER-FILL: mailing address]
- JURISDICTION
- [OWNER-FILL: governing law/jurisdiction]
09 / INDEPENDENCE
MySellerHQ is independent
MySellerHQ is not affiliated with, endorsed by, or sponsored by Amazon. Nothing in this draft should be read as an Amazon partnership, certification, audit, or other endorsement claim.
[OWNER-FILL: effective or last-updated date]