The complete list. Each sub-processor is bound by its own data-protection terms, and we only send each one the minimum it needs to do its job. Last updated: October 2026.
| Provider | What they do | Data touched | Region |
|---|---|---|---|
| Render | Application hosting & managed Postgres database | All product data (at rest) | Singapore |
| Cloudflare | visaler.com website hosting, DNS & CDN | Website visits, demo form submissions (transit) | Global edge |
| S3-compatible object storage | File & media storage (visit photos, invoices, uploads) | Uploaded files only | Configured per deployment |
| SMS delivery provider | One-time-password delivery for salon order-portal logins | Mobile number + OTP (transit only) | India |
| Google Workspace | Transactional email for demo requests & support | Name, work email, message content | Global |
Object storage provider and SMS gateway are chosen at deployment; ask us for the exact provider configured for your account.
When we add or replace a sub-processor that touches a new category of data, we update this page first and notify organization admin contacts before the change takes effect — giving you the objection window GDPR Article 28 requires.
Every sub-processor is engaged under a contract requiring at least the level of protection in our Data Processing Agreement.
Need the exact sub-processor set for your region or deployment? sales@visaler.com.