Security

Built for connected accounts, approvals, and resale data.

resell manages inventory, marketplace context, buyer messages, order events, market values, and agent approvals. The security model is built around explicit user control before anything leaves the platform.

Approval-gated agents

Agents can draft listing edits, buyer replies, price updates, portfolio posts, and sync actions. External writes require explicit user approval before execution.

Encrypted provider tokens

OAuth and provider tokens are stored encrypted at rest and scoped to the provider capabilities the user connects.

Webhook validation

Webhook endpoints support shared secrets, provider signatures where available, and non-broadcast tenant routing so provider events are handled for the intended account.

Audit history

Inventory changes, orders, approvals, notifications, sync jobs, and automation dispatches are recorded so a seller can review what happened later.

Export and deletion

Users can export account data, revoke connected provider access, and delete account data from account settings. Supported marketplace deletion notices are processed when matched.

No botting boundary

resell does not procure inventory, automate checkout, bypass anti-bot controls, bypass CAPTCHA, bypass MFA, spam buyers, or coordinate pricing between sellers.

Production requirements

Secrets and provider credentials are deployment blockers.

A production deployment must configure strong app secrets, encryption keys, webhook secrets, cron secrets, OAuth credentials, APNs credentials, App Store signing, and provider-specific scopes before live customers connect accounts.

See launch support
Incident response

What happens when something looks wrong.

  1. 1Triage the report and preserve relevant logs.
  2. 2Disable affected provider credentials, sessions, jobs, or webhooks where needed.
  3. 3Notify affected users when required by law, platform rules, or material risk.
  4. 4Ship a remediation and document follow-up controls.