Every claim below maps to a configuration we operate in production — not a roadmap item.
Data residency
Since November 2026 our production servers and database run in a cloud region in Riyadh, Saudi Arabia, operated for us by a third-party cloud provider, and database backups are kept in the same region. Some data still leaves the Kingdom: messages are delivered through Meta’s WhatsApp Business Platform, a few supporting services (payments, error monitoring, product analytics) are run by third parties that may process data outside Saudi Arabia, and we are still retiring what remains at our previous host outside Saudi Arabia. SanadAIs Company is a Saudi company and is subject to the Saudi Personal Data Protection Law (PDPL). Last verified: 2026-11-16.
Encryption in transit
All public traffic is terminated at our Caddy reverse proxy with TLS 1.2+ and modern cipher suites. HTTP requests are redirected to HTTPS.
Password hashing
User passwords are hashed with bcrypt. We never store, log, or transmit plaintext passwords. Password reset is handled via a one-time link.
Role-based access control
Account admins have full access and decide what everyone else can do. They can invite each teammate with a ready-made role, build custom roles, or give any individual permission to any member, and limit a teammate to specific WhatsApp numbers. A member can only pass on permissions they hold themselves, and only an admin can make someone an admin.
Audit logging
Operator actions and system events emit structured JSON logs to disk with stable schemas. Sensitive fields (tokens, message bodies) are redacted at the logger.
Workspace isolation
Every API request is scoped to the signed-in workspace. One workspace cannot read or write another workspace’s data.