Every claim below maps to a configuration we operate in production — not a roadmap item.
Data residency
Customer data resides in the Kingdom of Saudi Arabia on a SanadAIs-owned origin host. Our edge in Paris terminates TLS for app.sanadwa.com and api.sanadwa.com and forwards each request over an authenticated tunnel to the KSA origin — it does not persist customer data on its disk. Edge access logs are scrubbed of paths, request bodies, and response bodies.
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. The hop from the edge in Paris to the KSA origin runs over an authenticated SSH tunnel — never plain TCP.
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
Every workspace has three roles — owner, admin, and operator — with progressively narrower permissions. The API enforces role checks on every protected endpoint.
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.
Tenant isolation
Every API endpoint filters database queries by the session tenant ID. One workspace cannot read or write another workspace data.