1. Scope and Definitions
This Data Protection Policy describes how AMZBoost (operated by DMoose Enterprises Inc) protects data accessed through Amazon's Selling Partner API ("SP-API"), buyer information, seller business data, and any other sensitive information processed through the AMZBoost platform. It supplements our general Privacy Policy with the specific technical and operational safeguards required for our role as an Amazon Selling Partner API developer.
What this policy covers, in plain terms: when you authorize the AMZBoost platform on your Amazon Seller account, we access only the data you grant via OAuth, encrypt it in transit and at rest, restrict access to staff who need it for your work, delete it when you ask us to, and report any incident that touches it to Amazon within 24 hours.
2. Data We Access
AMZBoost accesses Amazon Selling Partner data only after a seller authorizes the connection through Amazon's OAuth consent flow. The exact data accessed depends on the SP-API roles the seller grants. Roles AMZBoost may request include:
- Product Listing (catalog content, ASINs, listing health)
- Pricing (list price, sale price, automate pricing rules)
- Amazon Fulfillment (FBA inventory, shipment plans, capacity)
- Buyer Communication (buyer seller messages on order related topics)
- Buyer Solicitation (Request a Review)
- Selling Partner Insights (account performance, settings)
- Finance and Accounting (settlement reports, fees, reserves)
- Inventory and Order Tracking (orders, shipments, returns)
- Brand Analytics (Search Query Performance, Repeat Purchase Behavior)
AMZBoost does not request the four restricted SP-API roles (Direct to Consumer Shipping, Tax Invoicing, Tax Remittance, Professional Services) at this time. We will publish an update to this policy if that changes.
AMZBoost does not request, store, or process buyer personally identifiable information (PII) such as buyer email addresses, phone numbers, or physical addresses. Where Amazon SP-API responses incidentally include order shipping addresses, AMZBoost stores them only for the duration of the seller's order display in our interface and does not export, reuse, or share them.
3. Purpose of Processing
AMZBoost processes Selling Partner data exclusively to deliver the services the seller has authorized. Specifically:
- Display the seller's catalog, inventory, ad performance, account health, and finance data in the AMZBoost interface
- Surface operator recommendations, alerts, and optimisations based on the seller's data
- Execute seller approved actions back to Amazon, such as catalog updates, advertising bid changes, inventory replenishment plans, and Request a Review
- Generate reports the seller has requested
We do not use Selling Partner data to train external machine learning models. We do not share Selling Partner data with third parties for advertising. We do not enrich third party data sets with Selling Partner data. We do not sell Selling Partner data.
4. Encryption Standards
All Amazon Selling Partner data is encrypted at every layer:
| Layer | Standard |
|---|---|
| In transit (client to platform) | TLS 1.2 or higher, HTTPS only, HSTS enforced |
| In transit (platform to Amazon SP-API) | TLS 1.2 or higher, certificate pinning where supported |
| At rest (primary database) | AES 256 encryption, managed by our cloud provider's key management service |
| At rest (backups) | AES 256 encryption, separate key, separate access controls |
| At rest (log and audit storage) | AES 256 encryption |
| Key management | Cloud provider managed KMS with documented rotation schedule, no plaintext key storage in code or repos |
| Secrets in application | Environment variables in encrypted secret manager, never committed to source control |
5. Access Controls
5.1 Authentication
All staff access to AMZBoost systems requires multi factor authentication (MFA) using time based one time passwords or hardware tokens. Passwords are at least 12 characters with complexity requirements, rotated annually, and managed through a centralised password manager. Shared accounts are prohibited.
5.2 Authorisation
AMZBoost uses role based access control (RBAC) with the principle of least privilege. Each staff role has a documented set of permissions, and access to Selling Partner data is restricted to roles that require it to deliver services. Admin level access is limited to a small number of named individuals.
5.3 Network segmentation
Production systems are network isolated from development and staging environments. Database access is restricted to application servers within the production virtual private cloud. Direct database access by individuals is logged, audited, and only permitted through bastion hosts with MFA.
5.4 Audit logging
Every access to Selling Partner data is logged with timestamp, user identity, action, and target. Logs are immutable, retained for at least 12 months, and reviewed monthly for anomalies.
6. Retention and Deletion
6.1 Active retention
Selling Partner data is retained for as long as the seller's authorization is active. Time series data (sales, ads, inventory) is retained at the daily granularity for 24 months, then aggregated to monthly summaries.
6.2 Deauthorization
When a seller revokes the AMZBoost authorization in Seller Central, AMZBoost stops accessing the seller's data immediately. The seller's stored data is retained for up to 90 days for reconciliation and audit purposes, then purged from active systems. Backup copies are purged within an additional 30 days, for a maximum total retention of 120 days post deauthorization.
6.3 Deletion on request
Sellers may request immediate deletion of their data at any time by emailing privacy@amzboost.com or security@amzboost.com. We confirm receipt within 2 business days, complete deletion within 30 days, and send a written confirmation when complete.
7. Subprocessors
AMZBoost uses a small set of vendors ("subprocessors") to operate the platform. All subprocessors are bound by data processing agreements that mirror the protections in this policy and are restricted to processing only what is required to deliver their specific service.
| Subprocessor | Purpose | Region |
|---|---|---|
| Amazon Web Services | Application and database hosting, file storage, key management | United States |
| Cloudflare | DNS, content delivery, TLS termination, web application firewall | United States and global edge |
| Hostinger | Website hosting for amzboost.com marketing pages | United States |
| Stripe | Payment processing for subscription billing | United States |
| Microsoft 365 | Internal email and document collaboration | United States |
| Slack | Internal team communication | United States |
| Sentry | Application error monitoring | United States |
We update this list when subprocessors change. Sellers can request notification of subprocessor changes by emailing privacy@amzboost.com.
8. Secure Development
AMZBoost follows a secure software development life cycle:
- All code changes go through peer review before merging to the main branch
- Dependencies are tracked, automatically scanned for known vulnerabilities, and patched within 14 days of a high severity disclosure
- Static analysis runs on every commit
- Production deployments require multi factor authentication and are logged
- Production credentials are never stored in source code, repositories, or client side applications
- Development and staging environments use synthetic data, never production seller data
- Penetration testing is performed at least annually by an independent third party once the platform is in general availability
9. Incident Response
AMZBoost maintains a documented incident response plan that is reviewed every six months. The plan defines:
- An on call rotation with named primary and secondary responders
- Severity classification (P1 through P4) with response time targets
- Internal notification within 24 hours of detection of any security incident
- Notification to Amazon's security team via security@amazon.com within 24 hours when the incident involves Amazon Information
- Notification to affected clients without undue delay, and where required by law within 72 hours
- Root cause analysis and corrective action published internally within 14 days
Sellers can report a suspected incident to security@amzboost.com. We confirm receipt within 24 hours.
10. Audit and Compliance
AMZBoost commits to the security controls required by Amazon's Acceptable Use Policy and the Data Protection Policy for Selling Partner API developers. Internal audit reviews are conducted quarterly against this policy. We will pursue third party attestation (SOC 2 Type I or equivalent) once the platform reaches general availability and a 12 month operating history is established.
11. Contact
Questions about this Data Protection Policy, requests for data deletion, or to report a suspected incident:
AMZBoost (operated by DMoose Enterprises Inc)
Privacy: privacy@amzboost.com
Security: security@amzboost.com
General: hello@amzboost.com
Website: amzboost.com
