Review Saleringo security controls
Transparent trust review
Product implementation baseline · not a certification statementThese controls describe the current Saleringo product architecture. They are not a certification or an audit report, and they do not promise an uptime figure. If you need something that is not on this page, ask us.
- Review owner
- Saleringo product security review
- Product baseline reviewed
- 18 August 2026
- Confirmed on this page
- Current product architecture and implementation controls
- Not covered on this page
- Audit reports, certifications, and availability commitments
Identity and least privilege
Protected operations resolve identity, active membership, workspace, tenant, region, and an exact permission rule before access.
- High-risk actions require step-up authentication and, where configured, human approval.
- Administrative support access is separately requested, approved, scoped, and audited.
- Secrets and payment credentials are not accepted through public forms or URLs.
Tenant and regional data boundaries
Control-plane records and regional tenant data use explicit boundaries with tenant-scoped access policies.
- Regional application tables enforce tenant-aware row-level security.
- Placement projections are versioned and reconciled rather than joined across databases.
- Where your information is stored and processed is listed in the Privacy Policy.
Operational integrity
Commands are designed around atomic state changes, audit evidence, safe retries, and bounded provider calls.
- Idempotency records protect supported commands from duplicate effects.
- Transactional outbox and durable event handling separate state changes from delivery.
- Provider timeouts and late-result rejection are applied at sensitive boundaries.
Ask a security or privacy question
Tell us the countries, channels, and kinds of customer information you plan to use. You do not need to design anything before contacting us.