SellerWeave
Public beta information
SECURITY

Security at SellerWeave

The controls used to isolate customers and protect Amazon Information. SellerWeave uses defense in depth for customer and Amazon information.

Last updated:

Operator

SellerWeave is developed and operated by CUVER, a business registered in Türkiye. SellerWeave is independent and is not endorsed by Amazon.

Identity and access

Accounts use Argon2id password hashing, revocable server-side sessions (Redis), origin protection, rate limiting and least-privilege role-based permissions for modules and production actions. TOTP multi-factor authentication is mandatory for owners, administrators and operators. Amazon production access is granted separately for each seller connection.

Tenant isolation

Every catalog and workflow record is scoped by organization, Amazon connection and marketplace. PostgreSQL tenant scoping with forced Row-Level Security provides a second deny-by-default boundary. Background jobs carry the same scope and cannot select credentials from another connection.

Encryption and secrets

Traffic is protected with TLS (HTTPS) and HSTS, and a Content Security Policy is applied. Amazon refresh tokens use authenticated AES-256-GCM encryption at rest. Application secrets and master keys are supplied as Docker secrets and are redacted from logs and structured audit events.

Operations

Encrypted off-site backups with scheduled restore verification, security audit retention and incident response procedures are maintained for the public deployment. Security-relevant account and connection changes are visible to organization administrators.

Report a concern

Report a suspected vulnerability or incident privately to amazon@sellerweave.com or use the support channel and mark the request as a security issue. Do not include passwords, refresh tokens or other secrets. Do not access other customers’ data, perform denial-of-service tests, or publish sensitive details before coordinated resolution.