Authentication and authorization
Portal requires signed-in users and Team membership before a user can create or use an Amazon Seller connection. Gateway runtime credential access is authenticated and scoped to the selected Team and connection ids.
Amazon Selling Partner API
Security and Data Handling Policy
This page describes how OpenTeam handles Amazon SP-API credentials and Amazon seller information for Team-owned Portal connections.
Last updated: May 16, 2026
Data Use
- OpenTeam uses Amazon information only to perform Team-authorized seller workflows requested in Portal.
- Portal stores Amazon Seller ID, selected marketplace, derived marketplace ID, derived SP-API region, LWA client credentials, refresh token, and refreshed access token for the connected Team.
- Browser responses and normal UI surfaces expose only non-secret metadata. Secrets are returned only through authenticated runtime credential endpoints for the selected Gateway, Team, and connection.
- OpenTeam does not sell Amazon information, use it for advertising, or share it with unrelated third parties.
- When a Team disconnects an Amazon Seller connection, Portal removes that connection from normal runtime credential access.
Security Controls
Credential protection
Amazon connector credentials are encrypted with AES-256-GCM before storage. LWA access tokens are refreshed from the saved refresh token only when needed and are not printed in browser responses.
Logging and monitoring
OpenTeam records authentication, connector setup, runtime credential access, API errors, Gateway activity, and production service events for security review and incident investigation. Amazon-related security logs are access-controlled, protected from tampering, retained for at least 12 months, and reviewed through alerts or at least bi-weekly.
Incident response
Security incidents involving Amazon information are coordinated by OpenTeam operations as the incident management point of contact. Response includes containment, credential disablement or rotation, evidence preservation, investigation, remediation, documentation, and communication to affected parties or Amazon when required.
Password and secret management
Portal user access is passwordless email-code sign-in. Infrastructure credentials and administrator secrets must be unique, access-controlled, rotated when risk or role changes require it, and never embedded in source code or user-visible logs.
Least privilege
Amazon Seller runtime work uses the selected connection, marketplace, marketplace ID, and regional SP-API endpoint. Agents are instructed not to invent marketplace ids or disclose credential endpoint responses.
Amazon Review Summaries
These summaries align with common Amazon SP-API security questionnaire prompts.
Security logging and monitoring
OpenTeam logs auth, connector setup, runtime credential access, API errors, Gateway activity, and production service events. Amazon-related security logs are access-controlled, protected from tampering, retained for at least 12 months, reviewed through alerts or at least bi-weekly, and used for investigations.
Incident response plan
OpenTeam triages suspected database hacks, unauthorized access, or data leaks by containing affected systems, disabling exposed credentials, preserving logs, investigating scope and root cause, remediating defects, rotating secrets, documenting actions, and notifying impacted parties or Amazon when required.
Password management
Portal uses passwordless email-code sign-in for users. Admin and infrastructure secrets must be unique, access-controlled, stored in approved secret stores or service environment files, rotated after exposure or role change, and kept out of source code, chat output, and user-visible logs.
References
OpenTeam maintains this policy for Portal's Amazon Seller connector and keeps implementation details aligned with Amazon SP-API Data Protection Policy, Acceptable Use Policy, logging, monitoring, and incident response guidance.