Privacy · AMZ-15
Amazon Selling Partner API Data Protection Statement
1. Who we are and what this statement covers
Enigmatech Mexico SAPI de CV ("Enigmatech") develops and operates EnigmaSuite, a business management platform for sellers. Sellers who sell on Amazon connect their Amazon seller account to EnigmaSuite to manage their catalog, inventory and orders, and to fulfill from their own warehouses the orders they ship themselves. This statement explains, for those sellers and for Amazon, what information we receive through the Amazon Selling Partner API ("Amazon Information"), how we use it, and how we protect and delete it. It complements our Privacy Policy and our security policies.
We follow the Amazon Services API Developer Agreement, the Amazon Data Protection Policy and the Amazon Acceptable Use Policy for all Amazon Information.
2. How a seller connects and disconnects
- An administrator of the seller connects the account from the Integrations section of EnigmaSuite, which sends them to Amazon Seller Central to review and authorize our application. We never ask for the seller's password or access keys.
- The authorization produces a refresh token that is stored encrypted in our secrets vault and used only by our servers, only for that seller.
- The seller can disconnect at any time, in EnigmaSuite or in Seller Central. We then delete the token and, within 30 days, the Amazon Information we received for that seller (see section 6).
3. What we use and why
| Selling Partner API area | What we receive | Why the seller needs it |
|---|---|---|
| Listings, product types and catalog | The seller's listings, attributes, offers and listing issues | Publish and maintain the seller's catalog from one place |
| Pricing | The seller's prices and offers | Keep prices aligned across the seller's sales channels |
| Inventory, fulfillment and reports | Inventory levels, fulfillment channel and Fulfillment by Amazon shipment and tracking reports | Avoid overselling and show the seller where each order is |
| Orders | Order identifiers, items, amounts, status, fulfillment channel, and the city, state and postal code of the destination | Import orders into the seller's order management, route them to the right warehouse and track them |
| Notifications | Changes to orders and listings | Keep the seller's data current without polling |
| Direct-to-Consumer Shipping (restricted) | For orders the seller ships itself: the buyer's name, shipping address, phone number and the email Amazon provides; and, for Seller Flex sites the seller operates, the shipments, packages and shipping labels assigned to that site | Print the shipping label, pack and hand the package to the carrier, and confirm the shipment to Amazon |
We request only the roles listed above and only the data each feature needs. We do not receive buyer information for orders that Amazon ships from its own fulfillment centers.
4. The shipping process that uses buyer information
Buyer personal information is used only to ship orders the seller fulfills itself, and to meet the seller's legal and tax obligations. The process is:
4.1 Merchant-fulfilled orders (the seller ships from its warehouse)
- EnigmaSuite imports the new order (without buyer personal information) and confirms that it is merchant-fulfilled.
- When the order enters the seller's order management to be fulfilled, our server requests a Restricted Data Token for that single order and uses it to read the buyer's shipping address and contact details. The token is short-lived and is never stored.
- The address is saved in the seller's order, encrypted at rest, visible only to the seller's users whose role includes order fulfillment.
- The seller's warehouse picks and packs the order, and the label is purchased from the carrier the seller chooses (or through Amazon's shipping services) using that address.
- The package is handed to the carrier, and EnigmaSuite sends the carrier and tracking number back to Amazon to confirm the shipment.
- No later than 30 days after the order is delivered, an automated job deletes the buyer's personal information from the order and from every copy linked to it.
4.2 Seller Flex orders (the seller operates an Amazon-designated site)
- EnigmaSuite lists the shipments assigned to the seller's Seller Flex site through the External Fulfillment Shipments API and matches each one to its order.
- The seller's warehouse confirms the shipment and packs it; when the packages are ready, EnigmaSuite requests the shipping label from Amazon.
- The label file is downloaded by our server over TLS and delivered straight to the warehouse user who prints it. We do not keep a copy, and the link Amazon provides is never logged or shared.
- The printed label is attached to the package and handed to Amazon's carrier; EnigmaSuite records the status and tracking.
- Printed documents with buyer information that are not attached to a package are shredded.
- For the inventory of the site, EnigmaSuite sends Amazon the available quantity of each product, without any personal information.
4.3 Orders fulfilled by Amazon
Amazon ships these orders. EnigmaSuite reads their status and tracking from Amazon's fulfillment reports and keeps only the order identifier, carrier, tracking number and dates; buyer details that appear in those reports are discarded when the report is processed and are never stored.
5. What we never do
- We never use Amazon Information to market to Amazon customers, to contact them for any purpose other than delivering their order, or to request, write or change reviews.
- We never sell, rent or share it, and never disclose it to other users of EnigmaSuite, to affiliated companies or to any third party, except our subprocessors (who process it on our instructions under data protection terms at least as protective as ours) or when the law requires it.
- We never aggregate it across sellers, never use it to build insights about Amazon's business, and never offer data services based on it.
- We never use it to train artificial intelligence models, and our AI-assisted features do not receive buyer personal information obtained from Amazon.
- We never request access to information we do not need, and our personnel access it only to support the seller at its request or to handle a security incident.
6. Retention and deletion
- Buyer personal information is deleted no later than 30 days after the order is delivered. If the law requires the seller to keep a specific record for longer (for example, a tax invoice), only that record is kept, encrypted and with restricted access, and only for the period the law requires.
- Shipping labels are not stored.
- All other Amazon Information is deleted within 30 days of the earliest of: the seller disconnecting its account, Amazon asking us to delete it, our determining that we are no longer entitled to it, or the end of our participation in the program.
- Deletion means deletion, not anonymization, and reaches backups as they rotate (within 35 days). We certify deletion in writing when Amazon or the seller asks.
Details are in the Data Retention and Deletion Policy.
7. How Amazon Information is protected
| Control | How | Policy |
|---|---|---|
| Network protection | Web application firewall and edge protection on every internet-facing endpoint, default-deny firewalls, internal services bound to localhost, managed database isolated from the application host | NSP-02 |
| Access | Least privilege, denial by default, multi-factor authentication, 12-character passwords with complexity and expiration, lockout after 10 failed attempts, quarterly access reviews, removal within 24 hours | ACP-05, SBS-04 |
| Encryption | TLS 1.2 or higher in transit; AES-256 at rest for the database, backups and file storage; tokens and secrets in an encrypted vault; keys managed by the providers' key management systems and rotated at least yearly | DCE-06 |
| Tenant isolation | Row-level security on every table, plus organization filters in every query; each seller sees only its own data | ACP-05 |
| Logging and monitoring | Logs without personal information, kept at least 12 months, reviewed at least every two weeks, with alarms on unusual access and data volumes and on canary records | LMS-13 |
| Vulnerability management | Scans at least every 30 days, code scanning before every release, annual penetration test; Critical fixes in 7 days and High in 30 days | VTM-08 |
| Secure development | Peer review, separate environments, no credentials in code, automatic secret scanning | SDL-14 |
| Backups and recovery | Encrypted daily backups with a geographically separate copy, defined recovery objectives, quarterly restore tests | BCP-12 |
| Endpoints | Anti-malware, full-disk encryption, screen lock, device management, no Amazon Information on devices | EPS-03 |
8. Security incidents
If we detect an actual or suspected security incident that may involve Amazon Information, we notify Amazon at [email protected] within 24 hours of detecting it, and the affected sellers within 72 hours. Our Incident Management Point of Contact is the Security Lead, reachable at [email protected]. The full process is in the Incident Response Policy.
9. Sellers' choices and questions
Sellers can see what their users can access, disconnect Amazon at any time, export their data, and ask us to delete the Amazon Information we hold by writing to [email protected]. Amazon customers who have questions about their data should contact the seller they bought from; if they contact us, we forward the request to the seller within 5 business days.