The Acceptable Use Policy ("AUP") clarifies the appropriate use of the Amazon Services API (including the Marketplace Web Service API). In addition to the Amazon Services API Developer Agreement, Developers must comply with the following policies. Failure to comply may result in suspension or termination of Amazon Services API access.
1. Perform acceptable Amazon activities
The Amazon Services API is for Developers who wish to help Authorized Users build, manage, and grow successful businesses in Amazon's store and/or participate in any Amazon Services.
1.1 Use the Amazon Services API only to perform acceptable Amazon activities, and only for Authorized Users who have authorized you to perform these activities on their behalf.
1.2 Do not facilitate or promote violation of any agreement between Authorized Users and Amazon (such as the Amazon Services Business Solutions Agreement), directly or indirectly.
1.3 If you suspect that, an Authorized User is using your service to violate their agreement with Amazon, notify Amazon (firstname.lastname@example.org) and block the Authorized User's access to your Application.
1.4 Comply with Amazon policies that pertain to specific APIs or functionality that your Application provides.
2. Provide quality applications and services
2.1 Do not falsely advertise your Application or service.
2.2 Be clear and honest with Authorized Users about what data you are accessing and for what purpose.
2.3 Do not attempt to deceive Authorized Users through the deliberate modification of Information.
2.4 Be explicit about any calculations and the use of models such as artificial intelligence in the service you provide, their accuracy, and data freshness.
2.5 Comply with all applicable laws including data privacy and data protection laws (e.g., GDPR, Cybersecurity Law of the People's Republic of China).
2.6 Do not offer Applications or services that infringe on the copyrights, patents, or trademarks of others.
Quality and performance
2.7 Provide Application availability, performance, and support required to perform the business task.
2.8 Identify and mitigate any negative Authorized User impact before launching new features, especially for business-critical tasks.
2.9 Design your Application to respect per-Authorized User throttling quotas.
2.10 Implement data integrity and validation checks within your Application for any analytical processing (e.g., AI models for insights, automated decision-making) that has material impact on an Authorized User's business.
3. Keep data secure
3.1 Never share access keys or passwords.
3.2 Never request or accept an Authorized User’s or another Developer’s access keys for any purpose.
3.3 Do not request or share Amazon Portal usernames or passwords from Authorized Users.
3.4 Only act on behalf of Authorized Users that have granted you permission through third-party authorization.
3.5 Do not apply for access keys that you will not use. Amazon will baseline access keys every 90 days. Access keys that do not make a successful call in 90 days will be deleted and the Developer will need to re-apply for access keys.
3.6 Do not ask Authorized Users to share information retrieved from Amazon Portals manually or programmatically to circumvent Amazon policies.
3.7 If Amazon Portal access is required to provide features or services that benefit Authorized Users, ask the Authorized User to grant access through secondary user permissions.
3.8 Do not request access to or retrieve Information that is not necessary for your Application's functionality.
3.9 Only grant access to data on a "need-to-know" basis within your organization, to any individual employed or contracted by your organization, and among your Application users.
3.10 Do not attempt to circumvent throttling quotas through the creation of multiple Developer accounts within the same region.
3.11 Inform Amazon (email@example.com) within 30 days of any organizational changes or events that change your organization’s need for or use of Information. 3.12 Disclose to Amazon about affiliated entities involved in your Application or service.
3.13 Comply with the Data Protection Policy ("DPP"), which provides specific requirements on the receipt, storage, usage, transfer, and disposition of Information.
4. Use data for acceptable purposes
4.1 Do not use Personally Identifiable Information about Customers for any purposes other than merchant fulfilled shipping or to meet legal requirements, including tax and regulatory requirements.
4.2 Do not target Amazon Customers for product marketing or review fabrication and modification using data retrieved through the Amazon Services API or any external (non-Amazon) data services.
4.3 Do not use, offer, or promote external (non-Amazon) data services that vend Information or data retrieved from Amazon's public-facing websites.
4.4 Do not aggregate data across Authorized Users’ businesses or Customers obtained through the Amazon Services API to provide or sell to any parties including competing Authorized Users.
4.5 Do not promote, publish, or share insights about Amazon's business. Do not use insights about Amazon's business for your own business purposes.
4.6 Do not disclose Information, individually labeled or aggregated, to other Application users, affiliated entities, or any outside parties, unless required to perform acceptable Authorized User activities for Authorized Users that authorized your Application.
4.7 Ensure the parties you share data with to comply with standards at least as strict as the Data Protection Policy (“DPP”) and the Acceptable Use Policy (“AUP”).
4.8 Be transparent with Authorized Users about what data you share, with whom, and for what purposes.
5. API-specific policies
5.1 If you support Buyer-Seller Messaging using the Buyer-Seller Messaging Service, you must comply with the Communication Guidelines.
5.2 If you are using the Buyer-Seller Messaging Service, you must also support Amazon-approved templates through integration with the Messaging and Solicitations API.
5.3 If you are using the Merchant Fulfillment API, you must comply with the Merchant Fulfillment API Service Terms.
“Amazon Services” means services provided or operated by Amazon.
“Amazon Services API” means any application programming interface (API) offered by Amazon for the purpose of helping Amazon Authorized Users to programmatically exchange data. "Amazon Services API" means any application programming interface (API) offered by Amazon for the purpose of helping Amazon Authorized Users to programmatically exchange data.
“Amazon Portal” means any Amazon website used by Authorized Users or others in a business relationship with Amazon to manage their participation in Amazon Selling Partner Services or other services provided by Amazon. This includes Seller Central and Vendor Central.
“API Materials” means Materials we make available in connection with the Amazon Services API, including APIs, documentation, specifications, software libraries, software development kits, and other supporting materials, regardless of format.
“Application” means a software application or website that interfaces with the Amazon Services API or the API Materials.
“Authorized User” means a user of Amazon’s systems or services who has been specifically authorized by Amazon to use the applicable systems or services.
“Customer” means any person or entity who has purchased items or services from Amazon's public-facing websites.
“Developer” means any person or entity (including you, if applicable) that uses the Amazon Services API or the API Materials for a Permitted Use on behalf of an Authorized User.
“Information” means any information that is exposed through the Amazon Services API, Amazon Portals, or Amazon's public-facing websites. This data can be public or non-public, including Personally Identifiable Information about Amazon customers.
“Personally Identifiable Information” (“PII”) means information that can be used on its own or with other information to identify, contact, or locate an individual (e.g., Customer or Authorized User), or to identify an individual in context. This includes, but is not limited to, a Customer or Authorized User’s name, address, e-mail address, phone number, gift message content, survey responses, payment details, purchases, cookies, digital fingerprint (e.g., browser, user device), IP Address, geo-location, or Internet-connected device product identifier.
Copyright © 2009-2021 Amazon.com, Inc. or its affiliates. Amazon and Amazon.com are registered trademarks of Amazon.com, Inc. or its affiliates. All other trademarks are the property of their respective owners.
Data Protection Policy
The Data Protection Policy ("DPP") governs the receipt, storage, usage, transfer, and disposal of the data vended and retrieved through the Amazon Services API (including the Marketplace Web Service API). This policy is applicable to all systems that store, process, or otherwise handle data vended and retrieved from the Amazon Services API. This Policy supplements the Amazon Services API Developer Agreement and the Acceptable Use Policy. Failure to comply may result in suspension or termination of Amazon Services API access.
1. General Security Requirements
Consistent with industry-leading security, Developers will maintain physical, administrative, and technical safeguards, and other security measures (i) to maintain the security and confidentiality of Information accessed, collected, used, stored, or transmitted by a Developer, and (ii) to protect that his Information from known or reasonably anticipated threats or hazards to its security and integrity, accidental loss, alteration, disclosure, and all other unlawful forms of processing. Without limitation, the Developer will comply with the following requirements:
1.1 Network Protection. Developers must implement network protection controls including network firewalls and network access control lists to deny access to unauthorized IP addresses. Developers must implement anti-virus and anti-malware software on end-user devices. Developers must restrict public access only to approved users.
1.2 Access Management. Developers must assign a unique ID to each person with computer access to Information. Developers must not create or use generic, shared, or default login credentials or user accounts. Developers must implement baselining mechanisms to ensure that at all times only the required user accounts access Information. Developers must review the list of people and services with access to Information at least quarterly, and remove accounts that no longer require access. Developers must restrict employees and contractors from storing Information on personal devices. Developers will maintain and enforce "account lockout" by detecting anomalous usage patterns and log-in attempts, and disabling accounts with access to Information as needed.
1.3 Least Privilege Principle. Developers must implement fine-grained access control mechanisms to allow granting rights to any party using the Application and the Application's operators following the principle of least privilege. Access to Information must be granted on a "need-to-know" basis.
1.4 Password Management. Developers must establish minimum password requirements for personnel and systems with access to Information. Password requirements must be a minimum of eight (8) characters, contain upper and lower case letters, contain numbers, contain special characters, and rotated at least quarterly.
1.5 Encryption in Transit. Developers must encrypt all Information in transit with secure protocols such as TLS 1.2+, SFTP, and SSH-2. Developers must enforce this security control on all applicable internal and external endpoints. Developers must use data message-level encryption where channel encryption (e.g., using TLS) terminates in untrusted multi-tenant hardware (e.g., untrusted proxies).
1.6 Incident Response Plan. Developers must create and maintain a plan and/or runbook to detect and handle Security Incidents. Such plans must identify the incident response roles and responsibilities, define incident types that may affect Amazon, define incident response procedures for defined incident types, and define an escalation path and procedures to escalate Security Incidents to Amazon. Developers must review and verify the plan every six (6) months and after any major infrastructure or system change, including changes to the system, controls, operational environments, risk levels, and supply chain. Developers must notify Amazon (via email to firstname.lastname@example.org) within 24 hours of detecting Security Incident or suspecting that a Security Incident has occurred. Developers must investigate each Security Incident, and document the incident description, remediation actions, and associated corrective process/system controls implemented to prevent future recurrence. Developers must maintain the chain of custody for all evidences or records collected, and such documentation must be made available to Amazon upon request (if applicable). If a Security Incident occurred, Developers cannot represent or speak on behalf of Amazon to any regulatory authority or customers unless Amazon specifically requests in writing that the Developer do so.
1.7 Request for Deletion or Return. Developers must permanently and securely delete or return Information upon and in accordance with Amazon's notice requiring deletion or return within 72 hours of Amazon’s requests unless the data is necessary to meet legal requirements, including tax or regulatory requirements. Secure deletion must occur in accordance with industry-standard sanitization processes such as NIST 800-88. Developers must also permanently and securely delete all live (online or network accessible) instances of Information 90 days after Amazon's notice. If requested by Amazon, the Developer will certify in writing that all Information has been securely destroyed.
2. Additional Security Requirements Specific to Personally Identifiable Information
The following additional Security Requirements must be met for Personally Identifiable Information ("PII"). PII is granted to Developers for select tax and merchant fulfilled shipping purposes, on a must-have basis. If an Amazon Services API contains PII, or PII is combined with non-PII, then the entire data store must comply with the following requirements:
2.1 Data Retention. Developers will retain PII for no longer than 30 days after order delivery and only for the purpose of, and as long as is necessary to (i) fulfill orders, (ii) calculate and remit taxes, (iii) produce tax invoices, or (iv) meet legal requirements, including tax or regulatory requirements. If a Developer is required by law to retain archival copies of PII for tax or other regulatory purposes, PII must be stored as a "cold" or offline encrypted backup (e.g., not available for immediate or interactive use).
2.3 Asset Management. Developers must keep inventory of software and physical assets (e.g. computers, mobile devices) with access to PII, and update quarterly. Physical assets that store, process, or otherwise handle PII must abide by all of the requirements set forth in this policy. Developers must not store PII in removable media, personal devices, or unsecured public cloud applications (e.g., public links made available through Google Drive) unless it is encrypted using at least AES-128 or RSA-2048 bit keys or higher. Developers must securely dispose of any printed documents containing PII.
2.4 Encryption at Rest. Developers must encrypt all PII at rest using at least AES-128 or RSA with 2048-bit key size or higher. The cryptographic materials (e.g., encryption/decryption keys) and cryptographic capabilities (e.g. daemons implementing virtual Trusted Platform Modules and providing encryption/decryption APIs) used for encryption of PII at rest must be only accessible to the Developer's processes and services.
2.5 Secure Coding Practices. Developers must not hardcode sensitive credentials in their code, including encryption keys, secret access keys, or passwords. Sensitive credentials must not be exposed in public code repositories. Developers must maintain separate test and production environments.
2.6 Logging and Monitoring. Developers must gather logs to detect security-related events to their Applications and systems including success or failure of the event, date and time, access attempts, data changes, and system errors. Developers must implement this logging mechanism on all channels (e.g., service APIs, storage-layer APIs, administrative dashboards) providing access to Information. All logs must have access controls to prevent any unauthorized access and tampering throughout their lifecycle. Logs must not contain PII unless the PII is necessary to meet legal requirements, including tax or regulatory requirements. Logs must be retained for at least 90 days for reference in the case of a Security Incident. Developers must build mechanisms to monitor the logs and all system activities to trigger investigative alarms on suspicious actions (e.g., multiple unauthorized calls, unexpected request rate and data retrieval volume, and access to canary data records). Developers must implement monitoring alarms to detect if Information is extracted from its protected boundaries. Developers should perform investigation when monitoring alarms are triggered, and this should be documented in the Developer's Incident Response Plan.
2.7 Vulnerability Management. Developers must create and maintain a plan and/or runbook to detect and remediate vulnerabilities. Developers must protect physical hardware containing PII from technical vulnerabilities by performing vulnerability scans and remediating appropriately. Developers must conduct vulnerability scanning or penetration tests at least every 180 days and scan code for vulnerabilities prior to each release. Furthermore, Developers must control changes to the storage hardware by testing, verifying changes, approving changes, and restricting access to who may perform those actions.
3. Audit and Assessment
Developers must maintain all appropriate books and records reasonably required to verify compliance with the Acceptable Use Policy, Data Protection Policy, and Amazon Services API Developer Agreement during the period of this agreement and for 12 months thereafter. Upon Amazon's written request, Developers must certify in writing to Amazon that they are in compliance with these policies.
Upon request, Amazon may, or may have an independent certified public accounting firm selected by Amazon, audit, assess and inspect the books, records, facilities, operations, and security of all systems that are involved with a Developer's Application in the retrieval, storage, or processing of Information. Amazon will keep confidential any nonpublic information disclosed by a Developer as part of this audit that is designated as confidential or that, given the nature of the information or the circumstances surrounding its disclosure, reasonably should be considered confidential. Developers must cooperate with Amazon or Amazon's auditor in connection with the audit or assessment, which may occur at the Developer's facilities and/or subcontractor facilities. If the audit or assessment reveals deficiencies, breaches, and/or failures to comply with our terms, conditions, or policies, the Developer must, at its sole cost and expense, and take all actions necessary to remediate those deficiencies within an agreed-upon timeframe. Upon request, Developer must provide remediation evidence in the form requested by Amazon (which may include policy, documents, screenshots, or screen sharing of application or infrastructure changes) and obtain written approval on submitted evidence from Amazon before audit closure.
"Amazon Services API" means any application programming interface (API) offered by Amazon for the purpose of helping Amazon Authorized Users to programmatically exchange data.
"API Materials" means Materials we make available in connection with the Amazon Services API, including APIs, documentation, specifications, software libraries, software development kits, and other supporting materials, regardless of format.
"Application" means a software application or website that interfaces with the Amazon Services API or the API Materials.
"Authorized User means a user of Amazon’s systems or services who has been specifically authorized by Amazon to use the applicable systems or services.
"Customer" means any person or entity who has purchased items or services from Amazon's public-facing websites.
"Developer" means any person or entity (including you, if applicable) that uses the Amazon Services API or the API Materials for a Permitted Use on behalf of an Authorized User.
"Information" means any information that is exposed through the Amazon Services API, Amazon Portals, or Amazon's public-facing websites. This data can be public or non-public, including Personally Identifiable Information about Amazon Customers.
"Personally Identifiable Information" ("PII") means information that can be used on its own or with other information to identify, contact, identify in context, or locate an Amazon Customer or Authorized User. This includes, but is not limited to, a Customer or Authorized User's name, address, e-mail address, phone number, gift message content, survey responses, payment details, purchases, cookies, digital fingerprint (e.g., browser, user device), IP Address, geo-location, nine-digit postal code, or Internet-connected device product identifier.
"Security Incident" means any actual or suspected unauthorized access, collection, acquisition, use, transmission, disclosure, corruption, or loss of Information, or breach of any environment containing Information.
Copyright © 2009-2021 Amazon.com, Inc. or its affiliates. Amazon and Amazon.com are registered trademarks of Amazon.com, Inc. or its affiliates. All other trademarks are the property of their respective owners.