Privacy Policy – Atlas Digital Marketplace Connector
This policy is specific to data accessed through Amazon Seller Central and aligns with Amazon Selling Partner API (SP-API) requirements.
Overview
Atlas Precision Consulting provides integration services connecting Amazon Seller Central, eBay, and Epicor Prophet 21 ERP.
This policy describes how data, including Amazon-sourced information, is accessed, used, processed, and protected.
Amazon Data Usage Summary
The Atlas Digital Marketplace Connector accesses and processes Amazon Seller Central data solely to support operational workflows such as order synchronization, inventory management, pricing synchronization, financial reconciliation, and transaction tracking.
- Only the minimum required operational data is accessed
- No buyer shipping addresses are retrieved
- No buyer contact information is retrieved
- No Amazon buyer PII is stored or retained
- All data access is controlled, logged, and secured
For full details on how data is handled, please review the sections below.
What is Personally Identifiable Information (PII)
Personally Identifiable Information (PII) is information that may be used to identify an individual, either directly or indirectly.
Examples may include:
- Names
- Shipping addresses
- Email addresses
- Phone numbers
The Atlas Digital Marketplace Connector is designed to operate without accessing or processing Amazon buyer PII.
Information Processed
Data is collected exclusively through authorized API access to Amazon Seller Central using permissions granted by the seller during application authorization.
The application processes only the information necessary to support integration workflows, including:
- Marketplace order identifiers
- Order status information
- Inventory information
- Pricing information
- Payment and transaction status information
- Fulfillment status information
Only the minimum data necessary to perform operational integration functions is accessed.
Amazon Buyer Data
The Atlas Digital Marketplace Connector does not access, process, store, or retain Amazon buyer personally identifiable information.
No buyer shipping addresses, names, phone numbers, email addresses, or other customer contact information are retrieved by the application.
For FBM orders, order records may be synchronized into Prophet 21 ERP using non-customer-specific placeholder address information solely to support:
- Inventory tracking
- Financial reconciliation
- Transaction management
- Historical sales recordkeeping
The application is not used for customer fulfillment activities and does not require access to Amazon restricted data.
Purpose of Data Use
Amazon data is used solely to support operational business processes, including:
- Creating sales orders in Prophet 21
- Synchronizing inventory information
- Synchronizing pricing information
- Reconciling transaction activity
- Supporting accounting and reporting workflows
The application does not use Amazon data for:
- Marketing
- Advertising
- Customer profiling
- Data resale
- Analytics unrelated to operational marketplace management
Data Processing and Flow
- Order information is retrieved from Amazon Seller Central through SP-API.
- Operational marketplace data is synchronized into Prophet 21 ERP.
- FBM orders are imported using non-customer-specific placeholder address information.
- Inventory, pricing, and transaction data are synchronized between systems.
- Operational events are logged for monitoring and troubleshooting.
These processing activities are performed solely to support inventory management, accounting, transaction tracking, and related operational workflows.
Data Retention
The application does not access or retain Amazon buyer PII.
Operational marketplace data required to support business workflows may be retained according to the seller’s business requirements and ERP data retention practices.
The application does not store:
- Amazon buyer names
- Amazon buyer addresses
- Amazon buyer phone numbers
- Amazon buyer email addresses
No Amazon buyer PII is persisted within the application.
Logging and Monitoring
System activity is logged for operational monitoring and troubleshooting.
Logging may include:
- Order synchronization events
- Inventory synchronization events
- Pricing synchronization events
- System health and error events
Logs include operational metadata such as timestamps and correlation identifiers.
Sensitive credentials are never written to logs.
Security Controls
Encryption
- Data in transit is encrypted using TLS 1.2 or higher
- Sensitive credentials are encrypted before storage
Access Control
- Role-Based Access Control (RBAC) restricts access
- Access is limited to authorized users
- Multi-factor authentication (MFA) may be enabled where available
Data Minimization
- Only required operational data is accessed
- No Amazon buyer PII is accessed
Environment Isolation
- Each seller operates within a dedicated single-tenant environment
- No cross-account data commingling occurs
Data Sharing
Operational marketplace data is used only within:
- The Atlas Digital Marketplace Connector
- The seller’s ERP environment (Epicor Prophet 21)
Amazon buyer PII is not accessed, processed, stored, sold, transferred, or shared by the application.
Marketplace data is not sold, licensed, or provided to third parties for commercial purposes.
Data may be processed by infrastructure providers solely for system operation under appropriate security controls.
Seller Authorization and Control
- Sellers explicitly authorize access via Amazon OAuth
- Access is limited to granted permissions
- No data is accessed beyond the authorized scope
Incident Response
Security incidents are managed according to the Atlas Incident Response Policy, including detection, investigation, containment, remediation, and notification where required.
Contact
Email: support@atlasprecon.com
Phone: (205) 690-2319

