Protected credentials and sessions
Passwords use Argon2id hashing. Short-lived access tokens and rotated refresh sessions are handled through HttpOnly cookies in the web application.
Security posture
Trust starts with precise claims.
OmniSeller is being built around tenant isolation, least-necessary access and explicit data boundaries. We publish the controls implemented today and the production controls still open.
Accurate beta statement: OmniSeller has a security-conscious software foundation. It is not represented as security-certified, Amazon-approved, SOC 2 compliant or “enterprise-grade.”
Implemented foundation
Controls present in the product code.
These controls have local implementation and test evidence. External deployment configuration must preserve them.
Tenant-scoped data access
The verified session supplies the organization identity. Services scope seller records by that tenant rather than accepting a tenant identifier from browser input.
Authorization instead of passwords
OmniSeller uses Amazon's authorization model and does not ask users to disclose their Seller Central password.
Encrypted refresh credentials
Amazon refresh credentials are encrypted before database storage. Environment secrets are not shipped in the public website.
Validated external data
Structured request and external-response validation rejects malformed values instead of trusting unchecked payloads.
Baseline web protections
Security headers, CORS restrictions, request-rate controls, role checks and structured audit events cover core paths.
Open production gates
Work still required before broad release.
Private beta access is constrained while these controls and operational practices mature. Open work is not hidden behind broad marketing language.
Public HTTPS deployment
RequiredThe app needs a stable production origin, registered OAuth login URI and HTTPS callback before a real public SP-API flow can be completed.
Multi-factor authentication
In developmentTOTP primitives exist, but complete enrollment, recovery and login enforcement are not yet active.
Managed secret storage
Open gateProduction must move sensitive configuration from local environment files into a managed secret system.
Observability and alerting
Open gateStructured logs and health probes exist; distributed traces, operational dashboards and service-level alerts remain open.
Durable background jobs
Open gateListing synchronization is not yet backed by a durable queue with shared locks, automatic retry and restart recovery.
Independent assurance
Not claimedNo external certification, penetration-test attestation or formal compliance audit is currently claimed.
Data boundaries
Access only for the service requested.
Seller-authorized information is used to provide the OmniSeller workspace, protect accounts, troubleshoot incidents and meet legal or platform obligations—not for resale.
Necessary data
The beta focuses on account identity, marketplace connection metadata and the seller's own catalog information needed for the described workflows.
Disconnect and request deletion
A seller can request disconnection, account closure, export or deletion through direct support while self-service controls are completed.
Security contact
Suspected security issues should be sent directly to info@nexastore.com with “OmniSeller Security” in the subject.
Responsible disclosure
Found a possible security issue?
Do not include seller data, credentials or active secrets in the first message. Describe the affected page, expected behavior and observed behavior.