Legal
Security & Data Protection
Last updated: 2026-10-08
SellerKey processes Amazon Selling Partner data on behalf of Amazon sellers. This page describes the technical and organizational security controls we maintain. The controls are designed to meet the requirements of Amazon's Selling Partner API Data Protection Policy (DPP), Amazon's Acceptable Use Policy (AUP), and the GDPR.
This document is a public summary of our internal Information Security Policy and is reviewed at least annually, after any material change to our infrastructure, and after any reportable incident. The Information Security Officer can be reached at security@sellerkey.co.
1. Acceptable Use Policy compliance
We acknowledge and comply with Amazon's Acceptable Use Policy as published at sellercentral.amazon.com. We:
- Use Amazon Information solely to provide the analytics services that the Selling Partner has explicitly authorized.
- Do not sell, lease, trade, redistribute or repurpose Amazon Information; do not combine it with data from other sources except to render the authorized service for the same Selling Partner.
- Do not use Amazon Information to train any machine-learning or artificial-intelligence model.
- Do not contact Amazon buyers using Amazon Information for any unsolicited purpose.
- Honor data deletion requests from Selling Partners and from Amazon, and remove Amazon Information from all systems within 30 days of the triggering event.
2. Authorization and scope minimization
- Sellers authorize our applications through Login with Amazon (LWA) using Amazon's OAuth flow. No client secret leaves our backend.
- We request only the minimum SP-API roles necessary for the analytics features the seller signed up for. Amazon's consent page shows the requested access before the seller approves it.
- Sellers can revoke our access at any time from within our application or from Seller Central → Apps and Services → Manage Your Apps (see §6 for what happens to the token in each case).
3. Credential Management
Aligned with Amazon's Credential Management guidance.
- Application secrets. The Login with Amazon client secret, the database service key and third-party API keys are stored as encrypted environment variables in our hosting provider, never in source control.
- Refresh tokens. Amazon refresh tokens are stored in our managed database, which the provider encrypts at rest. They sit in tables and columns that the roles used by browsers cannot read; only our server, using a service credential, can read them. They are never sent to the browser.
- Access tokens. Short-lived SP-API access tokens (valid for about one hour) are cached in the same restricted storage as refresh tokens until they expire, so that our background jobs can reuse them. They are never sent to the browser.
- Rotation. Application secrets are rotated immediately upon any suspected leak and when a team member with access leaves the organization. The Login with Amazon client secret is rotated within the period Amazon requires.
- Least privilege. Database roles grant only the permissions required by the workload they serve: signed-in users reach data through row-level security, and the service credential is used only by server code.
- Multi-factor authentication. Operator access to production consoles (cloud providers, repositories) requires multi-factor authentication.
- Access logging. Operator access to production credentials and databases is logged and reviewed.
4. Network Protection Controls
Aligned with Amazon's Network Protection guidance.
- Encryption in transit. All public endpoints enforce TLS 1.2 or higher with modern cipher suites. HSTS is enabled. Plain-HTTP requests are redirected to HTTPS.
- Encryption at rest. Application data, backups and object storage are encrypted at rest by the underlying providers.
- Database access. Browsers never hold privileged database credentials. They reach data only through the database provider's API with the signed-in user's session, constrained by row-level security. Direct database connections require credentials that only our servers and operators hold.
- Edge protection. Public endpoints sit behind our hosting provider's edge network, with managed DDoS mitigation and automated TLS.
- Rate limiting. Sign-in and account emails are rate-limited by our authentication provider. Costly actions, such as questions to the AI assistant and manual data refreshes, are limited per account.
- Outbound calls. SP-API requests are made server-side from our backend; credentials are never exposed to browsers or other untrusted clients.
- Tenant isolation. Multi-tenant data is isolated through Postgres row-level security policies that constrain every query to the authenticated tenant.
5. PII Data Retention
Aligned with Amazon's PII Data Retention guidance. The default position of SellerKey is to not collect Amazon buyer-level Personally Identifiable Information at all.
- Minimization at ingest. We do not store Amazon buyer names, email addresses, phone numbers or street addresses. Order reports are reduced to non-identifying fields (such as country and postal zone) before storage.
- Multi-Channel Fulfillment. For Multi-Channel Fulfillment orders, which the seller creates for sales on their own channels, we store the recipient name the seller supplied so the seller can identify each shipment.
- Encryption. All data held at rest, including any personal data, is encrypted at rest by our database provider.
- No sharing. PII is never shared with third parties beyond the subprocessors listed in the Privacy Policy, all of which are contractually bound to equivalent safeguards.
- Deletion. When a seller disconnects an Amazon account in SellerKey, its tokens are deleted immediately. Data derived from it, including any personal data, is deleted from primary systems within 30 days of a deletion request or of account deletion, and from backups within the next backup rotation cycle (90 days or less).
6. Token and data lifecycle on disconnection
- When a seller removes an Amazon connection inside SellerKey, our backend deletes the corresponding refresh token immediately and stops making SP-API calls for it.
- When a seller revokes access from Seller Central instead, Amazon invalidates the token and our SP-API calls for it fail with an authorization error. The stored token can no longer be used and is deleted when the seller removes the connection in SellerKey or asks us to at privacy@sellerkey.co.
- Selling Partner records derived from a disconnected authorization are deleted within 30 days of a deletion request to privacy@sellerkey.co or of account deletion.
- Backups containing pre-deletion data are retained for at most 90 days, after which they are rotated out and irrecoverable.
7. Incident Management
Aligned with Amazon's Incident Management guidance. We maintain a written Incident Response Plan, owned by the Information Security Officer, reviewed at least annually and tested through tabletop exercises.
A reportable incident includes any of: unauthorized access to production systems, unauthorized disclosure or exfiltration of Amazon Information or personal data, malware or ransomware on systems that process Amazon Information, lost or stolen credentials with access to Amazon Information, and any event materially compromising the confidentiality, integrity or availability of the Service.
- Detect & triage. Alerts from infrastructure, application logs and third-party monitoring are routed to an on-call rotation. The on-call engineer acknowledges within 30 minutes and triages within 2 hours.
- Contain. Compromised credentials are revoked, affected systems are isolated, and emergency rotations are performed.
- Notify.
- Amazon is notified at security@amazon.com within 24 hours of detection where Amazon Information is, or may be, implicated.
- The Estonian Data Protection Inspectorate is notified within 72 hours where required by Article 33 GDPR.
- Affected users are notified by email without undue delay where the incident is likely to result in a high risk to their rights and freedoms.
- Investigate. Logs are preserved, root cause is identified, and the scope of impact is determined.
- Remediate. Fixes are deployed, controls are reviewed, and lessons learned are documented in a written post-incident report.
- Post-incident review. A written summary is shared internally and, where appropriate, with affected users and Amazon.
8. Organizational change notification (Data Access 3.11)
We maintain a written policy requiring SellerKey to notify Amazon at security@amazon.com within 30 days of any organizational change that affects, or could affect, our need for or use of Amazon Information. The policy explicitly covers:
- Changes in legal entity, beneficial ownership, or controlling shareholder.
- Mergers, acquisitions, divestitures or restructurings.
- Changes to the Service that materially expand or change the categories of Amazon Information processed or the SP-API roles requested.
- Changes in the location of data processing, hosting providers, or any subprocessor with access to Amazon Information.
- Changes in the personnel role responsible for Amazon Information governance.
- Discontinuation of the Service or of an integration that uses Amazon Information.
The Information Security Officer is accountable for triggering the notification within the 30-day window and for keeping a record of every notification sent.
9. Personnel security
- New team members complete a written security onboarding before being granted production access. Onboarding covers credential handling, the Incident Response Plan, the Acceptable Use Policy, and the obligations of this page.
- Production access is least-privilege and is reviewed at least quarterly. Access is revoked within 24 hours of a team member leaving the organization or changing role.
- All personnel with access to Amazon Information are bound by written confidentiality obligations.
10. Software development lifecycle
- All production code lives in version control. Every production build runs type checking and linting, and a build that fails either is not deployed.
- Production deployments are immutable and reproducible from version control; emergency rollback to the previous deployment is available at all times.
11. Backups and business continuity
- The production database is backed up automatically by our managed Postgres provider.
- Backups are encrypted at rest in the same region as the primary database.
- Backup retention is capped at 90 days, after which backups are rotated out.
- Restore procedures are tested at least annually.
12. Reporting a vulnerability
We welcome coordinated disclosure of security vulnerabilities. Please email security@sellerkey.co with reproduction steps. We commit to:
- Acknowledging receipt within 48 hours.
- Providing an initial assessment within 5 business days.
- Fixing confirmed high-severity issues without undue delay.
- Crediting the reporter in our post-fix communication, on request.
Please do not test against accounts that are not your own, do not exfiltrate data beyond the minimum required to demonstrate the issue, and do not publish details before we have had a reasonable opportunity to remediate.
13. Contact
Information Security Officer: security@sellerkey.co.
Full legal entity, registered address and identifiers are listed on the legal information page.