Workspace isolation
Merchant records are scoped to their workspace and store. Server-side membership and role checks protect tenant-owned operations.
- Tenant-scoped queries
- Role-based access
- Server-side authorization
Security at Leavecart
Responsible recovery starts with responsible infrastructure.
Leavecart is designed to protect merchant access, keep provider credentials private, and prevent outreach when required safeguards are not satisfied.
Security overview reviewed September 2026
Credentials and integrations
Provider credentials stay on the server, are encrypted before storage, and are never exposed to browser code.
- Encrypted credentials
- Signed webhooks
- Replay protection
Storefront chat
The widget accepts requests only from merchant-approved HTTPS origins and uses hashed session tokens, bounded input, and rate limits.
- Exact origin allowlist
- Hashed session tokens
- Bounded requests
Safer outreach
Every send is checked against consent, quiet hours, cooldowns, frequency limits, and store-level launch controls.
- Global STOP handling
- Human takeover
- Emergency pause
Operational assurance
Sensitive actions are recorded without storing secrets. Releases run automated linting, type checks, tests, and production builds.
- Administrative audit history
- Idempotent provider events
- Privacy-safe error logging
Clear boundaries.
Sandbox by default
The product tour uses test data and never contacts real shoppers. Live mode requires merchant-owned provider accounts and a completed launch review.
Verifiable assurance
Leavecart publishes only controls and certifications that can be verified. Formal audit reports and legal agreements are shared only when they are accurate and available.
Security question or report?