Data protection and security
This page explains how AdSuite Pro collects, processes, stores, uses, shares and disposes of the Amazon data a seller authorizes, and the security controls that protect it.
Last updated: 20 October 2026Separate by seller
Every seller has an isolated workspace. Data is never stored together.
No passwords
You sign in on Amazon’s own pages. We never see or store your Amazon password.
Encrypted in transit
All traffic uses HTTPS. Access keys are stored encrypted.
Full activity log
Changes, sign-ins and denied access are recorded.
From Amazon to deletion, in six stages
1. What Amazon data we access, and why
We request only the permissions the application needs. A seller sees this list on Amazon's consent screen before authorizing.
| Area (Amazon permission) | What we read | Why |
|---|---|---|
| Product listing | The seller's own listings, attributes and listing issues; changes the seller saves in our editor | Listing health, catalog clean-up, editor |
| Pricing | The seller's own prices and Amazon's live price for them | Price tracking and profit calculation |
| Inventory and order tracking | Inventory levels, order dates and order item data (no buyer name, address, email or phone) | Sales, stock-aware advertising, profit |
| Finance and accounting | Settlement and transaction data: sales, fees, refunds | Profit per product |
| Selling Partner Insights | Account and marketplace information | Show which marketplace is connected |
| Brand analytics | Search-term data for the seller's brand | Keyword gaps and brand defense |
| Buyer solicitation | Whether an order is eligible for Amazon's review request | Review requests |
| Amazon fulfillment | FBA inventory, inbound shipment plans and box labels, FBA return and reimbursement reports | Returns analysis, FBA stock awareness, inbound planning |
| Direct-to-consumer shipping (restricted) | Return records for the seller's own Seller Flex orders: return ID, SKU, units, return reason, status, dates and marketplace channel. Amazon's return records do not contain a buyer name, address, email or phone. | Returns analysis for Seller Flex sellers |
| Amazon Ads (separate authorization) | Campaigns, ad groups, keywords, targets, budgets, and performance and spend data; changes the seller approves or automates | Reporting and advertising automation |
Buyer personal information. AdSuite Pro requests one restricted Amazon permission (direct-to-consumer shipping) to read Seller Flex return records. Those records contain no buyer name, address, email address or phone number, and AdSuite Pro does not collect or store them.
2. Life of the data
| Stage | What happens |
|---|---|
| Collected | Only after the seller authorizes the application through Amazon's own consent screens. Collected by scheduled and on-demand report requests from Amazon. |
| Processed | On the seller's own isolated AdSuite Pro environment, to build dashboards, rules and insights. |
| Stored | In the seller's own isolated database. Data of different sellers is never stored together. |
| Used | Only to provide AdSuite Pro to that seller. Never used for another seller, never for advertising to the seller, and never for benchmarking against other sellers. |
| Shared | Not sold or shared with other sellers. Limited service providers act on our behalf (see Privacy policy, section 5). AI features send only the summary figures and text needed for the question. |
| Disposed | When a seller disconnects, cancels, or asks us to delete, the Amazon connection key is removed immediately and the stored data is deleted within 30 days, including backups within 35 days. |
3. How Amazon access is protected
- Sellers authorize through Amazon's standard sign-in and consent (OAuth). We never see or store Amazon passwords.
- Amazon access keys (refresh tokens) are stored encrypted on the seller's own environment.
- Our application secret is held only on our central connection service and is never placed in code that is public or shared with sellers.
- Sellers can disconnect anytime, from AdSuite Pro or from Amazon Seller Central.
4. Security controls
- Isolation: every seller has a separate environment; staff and teammates see only the data of the account they belong to.
- Access control: role-based permissions, with the owner deciding what each teammate can see or do; devices are approved by the owner.
- Sign-in security: two-step sign-in for all users; strong password rules.
- Encryption in transit: all traffic uses HTTPS (TLS).
- Encryption at rest: database encryption
- Activity log: changes, sign-ins, failed sign-ins and denied access are recorded and retained for 12 months.
- Backups: Everyday at cloudflare R2 storage and instant restore if required
- Testing: vulnerability scans every 30 days and an internal security test before major releases. Last scan: on 17/10/2026.
- Change control: changes are tested before release; critical findings are fixed within 7 days and high findings within 30 days.
5. Security incidents
We keep an incident response plan. If we detect unauthorized access to Amazon information, we will tell Amazon at security@amazon.com within 24 hours of detection, and we will tell affected sellers without undue delay. Incident contact: Chintan K C, admin@selluxproxltools.com.
6. Reporting a security concern
If you believe you have found a vulnerability, please email admin@selluxproxltools.com with details. We will acknowledge within 2 business days.
Questions about your data or your account?
Write to admin@selluxproxltools.com or message us on WhatsApp. We reply to every request.
AdSuite Pro is an independent product of Sellux Pro Private Limited and is not affiliated with, endorsed by, or sponsored by Amazon. Amazon and related marks are trademarks of Amazon.com, Inc. or its affiliates.