Skip to content
SALERINGOSITE v1.27.0
한국어Get my proposal

Review published service providers

Check the approved provider record, processing purpose, location information, and update path without inferring an unlisted provider or service dependency.

Review current controlsStart my security and procurement review
Review each provider at the data boundary.Provider-review model, not a list of active or approved connections.
  1. 01
    Customer workspace
    Select
    An agreed service purpose
    Limit
    The fields to be shared
  2. 02
    Provider review
    Record
    Provider, purpose, location
    Check
    Data and transfer safeguards
  3. 03
    Applicable register
    Approve
    The deployment-specific list
    Maintain
    Change-notice procedure
A provider logo would not prove approval.

Request the current applicable register and confirm how changes are reviewed and communicated.

Transparent trust review

Subprocessors

Approved register process · deployment-specific entries supplied before purchase

Saleringo does not infer providers or processing locations before the production deployment is approved. Procurement receives the register applicable to the selected channels, AI services, hosting, communications, and support scope.

Review owner
Deployment procurement and privacy review
Product baseline reviewed
18 August 2026
Confirmed on this page
Required register fields and provider-change boundary
Still requires approval
The vendors, purposes, locations, and notice terms selected for the customer order

Register fields

Each approved entry identifies the service used for the customer deployment.

  • Legal entity and service name
  • Processing purpose and relevant data category
  • Processing location or transfer context and notice process

No silent provider substitution

Provider changes follow the applicable contract and notification process rather than an unreviewed website assumption.

  • Provider-neutral product adapters do not remove the need for disclosure.
  • Only deployment-approved services should receive customer data.
  • Request the current applicable register from the product team.

Start a security or procurement review

Tell us the countries, channels, data categories, and deployment scope. You do not need to design the architecture before contacting us.

Contact the product teamEmail a review request

Complete your security review.

Use the published controls as a review starting point. The signed order and applicable agreement remain the final authority for your deployment.

Review the security controls