Octopus Seller is built around Amazon's Acceptable Use and Data Protection policies. This page describes the controls that are in place today. Questions or a vulnerability report: [email protected].
Access to Amazon data
- Sellers connect through Amazon's own website authorization in Seller Central. We never ask for Amazon passwords or keys.
- Least privilege: only the roles the features need. No restricted roles, so buyer names, addresses, e-mails and phone numbers are never requested; any such field in an API response is removed before storage.
- Sellers can revoke access at any time in Seller Central (Manage Your Apps).
- Only official Amazon Selling Partner APIs are used. No scraping and no automated browsing of Seller Central.
Encryption
- HTTPS/TLS for all traffic, with HSTS.
- Amazon refresh tokens and multi-factor secrets are encrypted at rest with AES-256-GCM.
- Passwords are stored as bcrypt hashes; integration API keys and one-time e-mail links only as SHA-256 hashes.
- Nightly database backups are encrypted with AES-256 before they leave the server, stored on a separate server that can only receive new files (write-only), and kept for 30 days.
Isolation and access control
- Every record belongs to one seller account and every query is scoped to it; a seller can only reach their own data.
- The internal API and the database are not reachable from the internet. Server administration uses key-only SSH (password login disabled) and an encrypted private network.
- Optional TOTP multi-factor authentication for every user (required for platform administrators), login throttling, 12-hour sessions in HttpOnly Secure cookies, and all other sessions end when a password is reset.
- Staff accounts see orders and stock but never money, billing or settings.
No change without approval
Prices, listings and inventory on Amazon change only after the seller explicitly approves each change in the dashboard. Price changes are logged with who made them and Amazon's response. Review requests use Amazon's Solicitations API, once per order, only when the seller turns them on.
Servers and monitoring
- Firewall, intrusion detection (Suricata), anti-malware scanning (ClamAV), brute-force protection (fail2ban) and automatic security updates on the application server.
Third parties
- Paymob processes subscription payments on its own hosted page; card and wallet details never reach our servers, and payment callbacks are accepted only with a valid HMAC signature.
- Anthropic (Claude) receives a product's listing text and the seller's specifications only when the seller uses the content writer. No buyer information and no credentials are sent.
- Cloudflare proxies the web application (data in transit only).
Retention and deletion
Sellers can delete their account themselves in Settings, which immediately removes their Amazon Information, users, keys and tokens (payment records are kept for accounting). Encrypted backups age out within 30 days.
Incident response
We maintain a written incident response plan. If a security incident affects Amazon Information, we notify Amazon ([email protected]) and the affected sellers within 24 hours of detection, contain it, rotate the affected credentials and document what happened.