AMAZON DATA PROTECTION AND PRIVACY POLICY

Last updated May 28, 2023
1. NETWORK PROTECTION
  • MarketplaceHub developers have active, in force, AES-256 encryption and a network firewall to deny access to unauthorized IP addresses. All public access is denied.
  • MarketplaceHub developers are assigned a unique ID/Keys/Authentication to control and monitor computer access to Amazon Information and developers cannot create or use generic, shared, default login credentials or user accounts. All access/authorization is controlled by MarketplaceHub CEO.
  • MarketplaceHub developers have active, in force, baseline mechanisms to ensure that at all times only the required user accounts can access Amazon Information.
  • MarketplaceHub CEO, solely reviews the authorized list of people and services with access to Amazon Information on a monthly basis, and removes accounts that no longer require access.
  • MarketplaceHub developer employees are restricted from storing Amazon data on personal devices.
  • MarketplaceHub developers maintain and enforce "account lockout" by detecting anomalous usage patterns, log-in attempts and disables accounts with access to Amazon Information as needed.
  • MarketplaceHub developers have, in force, HTTPS encryption for all Amazon Information in transit within, but not limited to our network or between hosts.
  • MarketplaceHub developers enforce this security control on all applicable external endpoints used in internal communication channels including, but not limited to data propagation channels among storage layer nodes, connections to external dependencies and operational tooling.
  • MarketplaceHub developers disable communication channels which do not provide encryption in transit even if unused, including, but not limited to removing the related dead code, configuring dependencies only with encrypted channels, and restricting access credentials to the use of encrypted channels.
2. DATA RETENTION AND RECOVERY
  • MarketplaceHub developers retain PII only for the purpose of, and as long as is necessary to fulfill orders, but no longer than 30 days after order shipment or to calculate/remit taxes. If a MarketplaceHub developer is required by law to retain archival copies of PII for tax or similar regulatory purposes, this archived Amazon Information is stored as a "cold" or offline and is not available for immediate or interactive use. All backup is stored in a physically secure facility, and all archived data on backup media is encrypted. In the event that PII is lost, MarketplaceHub will be able to recover all PII lost.
3. DATA GOVERNANCE
  • MarketplaceHub developers create, document, and abide by the MarketplaceHub privacy and data handling policy for their Applications or services which govern the appropriate conduct and technical controls to be applied in managing and protecting information assets.
  • MarketplaceHub developers keep inventory of software and physical assets such as, but not limited to computers and mobile device with access to PII, and update regularly. A record of data processing activities such as specific data fields and how they are collected, processed, stored, used, shared, and disposed for all PII Information is maintained to establish accountability and compliance with regulations.
  • MarketplaceHub developers have established and abide by the MarketplaceHub privacy policy for customer consent and data rights to access, rectify, erase, or stop sharing/processing their information where applicable or required by data privacy regulation.
4. ENCRYPTION AND STORAGE
  • MarketplaceHub developers encrypt all PII at rest including, but not limited to, when the data is persisted, using industry best practice standards by using AES-256. All cryptographic materials including, but not limited to encryption/decryption keys and cryptographic capabilities, daemons implementing virtual Trusted Platform Modules and providing encryption/decryption APIs used for encryption of PII at rest are only accessible to the MarketplaceHub developer's processes and services.
  • MarketplaceHub developers do not store PII in removable media including, but not limited to USB, unsecured public cloud applications and/or public links made available through Google Drive.
  • MarketplaceHub developers securely dispose of any printed documents containing PII.
5. LEAST PRIVILEGE PRINCIPLE
  • MarketplaceHub developers implement fine-grained access control mechanisms to allow granting rights to any party using the Application including, but not limited to access to a specific set of data at its custody and the Application's operators with access to specific configuration and maintenance APIs such as kill switches following the principle of least privilege. Application sections or features that vend PII are protected under a unique access role, and access is only granted on a "need-to-know" basis.
6. LOGGING AND MONITORING
  • MarketplaceHub developers gather logs to detect security-related events including, but not limited to access and authorization, intrusion attempts or configuration changes to their Applications and systems.
  • MarketplaceHub developers have, in force, this logging mechanism on all channels including, but not limited to service APIs, storage-layer APIs or administrative dashboards providing access to Amazon Information. All logs have, in force, access controls to prevent any unauthorized access and tampering throughout their lifecycle. Logs themselves do not contain PII and are retained for at least 90 days for reference in the event of a Security Incident.
  • MarketplaceHub developers have, in force, mechanisms to monitor the logs and all system activities to trigger investigative alarms on suspicious actions, including, but not limited to, multiple unauthorized calls, unexpected request rate and data retrieval volume, or access to canary data records.
  • MarketplaceHub developers perform an investigation when monitoring alarms are triggered. This event is documented in the Developer's Incident Response Plan.
7. AUDIT
  • MarketplaceHub developers maintain all appropriate books and records reasonably required to verify compliance with the Acceptable Use Policy, Data Protection Policy, and Amazon Marketplace Developer Agreement during the period of agreement and for 12 months thereafter.
  • Upon Amazon's written request, MarketplaceHub developers will certify in writing to Amazon that they are in compliance with these policies.
  • MarketplaceHub developers will cooperate with Amazon or Amazon's auditor in connection with the audit, which may occur at the MarketplaceHub developer's facilities and/or subcontractor facilities. If the audit reveals deficiencies, breaches, and/or failures to comply with Amazon or Amazon’s auditor’s terms, conditions, or policies, MarketplaceHub, at its sole cost and expense, take all actions necessary to remediate those deficiencies within an agreed-upon timeframe.

2024 © All Rights Reserved