EnigmaSuite

Privacy · AMZ-15

Amazon Selling Partner API Data Protection Statement

Document
AMZ-15
Version
1.0
Effective
November 18, 2026
Next review
November 2027
Owner
Data Protection Officer
Approved by
Executive Management

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

3. What we use and why

Selling Partner API areaWhat we receiveWhy the seller needs it
Listings, product types and catalogThe seller's listings, attributes, offers and listing issuesPublish and maintain the seller's catalog from one place
PricingThe seller's prices and offersKeep prices aligned across the seller's sales channels
Inventory, fulfillment and reportsInventory levels, fulfillment channel and Fulfillment by Amazon shipment and tracking reportsAvoid overselling and show the seller where each order is
OrdersOrder identifiers, items, amounts, status, fulfillment channel, and the city, state and postal code of the destinationImport orders into the seller's order management, route them to the right warehouse and track them
NotificationsChanges to orders and listingsKeep 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 sitePrint 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)

  1. EnigmaSuite imports the new order (without buyer personal information) and confirms that it is merchant-fulfilled.
  2. 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.
  3. The address is saved in the seller's order, encrypted at rest, visible only to the seller's users whose role includes order fulfillment.
  4. 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.
  5. The package is handed to the carrier, and EnigmaSuite sends the carrier and tracking number back to Amazon to confirm the shipment.
  6. 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)

  1. 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.
  2. The seller's warehouse confirms the shipment and packs it; when the packages are ready, EnigmaSuite requests the shipping label from Amazon.
  3. 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.
  4. The printed label is attached to the package and handed to Amazon's carrier; EnigmaSuite records the status and tracking.
  5. Printed documents with buyer information that are not attached to a package are shredded.
  6. 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

6. Retention and deletion

Details are in the Data Retention and Deletion Policy.

7. How Amazon Information is protected

ControlHowPolicy
Network protectionWeb application firewall and edge protection on every internet-facing endpoint, default-deny firewalls, internal services bound to localhost, managed database isolated from the application hostNSP-02
AccessLeast 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 hoursACP-05, SBS-04
EncryptionTLS 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 yearlyDCE-06
Tenant isolationRow-level security on every table, plus organization filters in every query; each seller sees only its own dataACP-05
Logging and monitoringLogs 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 recordsLMS-13
Vulnerability managementScans at least every 30 days, code scanning before every release, annual penetration test; Critical fixes in 7 days and High in 30 daysVTM-08
Secure developmentPeer review, separate environments, no credentials in code, automatic secret scanningSDL-14
Backups and recoveryEncrypted daily backups with a geographically separate copy, defined recovery objectives, quarterly restore testsBCP-12
EndpointsAnti-malware, full-disk encryption, screen lock, device management, no Amazon Information on devicesEPS-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.