Integration signing secrets
The implementation encrypts supported integration signing secrets with AES-256-GCM. These secrets are not the ordinary lead or contact fields.
SECURITY · REVIEWED 10/09/2026
Security information with its limits visible.
Use this page to identify the controls you need to assess. It separates measured deployment facts, implemented controls and unfinished work; it is not a certification or a promise of complete legal compliance.
How workspace separation is enforced
Saudaflow uses a shared PostgreSQL database with organisation identifiers and row-level security: database rules that separate workspace records. It does not provide a separate database for each customer.
The deployment review on 09/09/2026 found 170 public tables with an organisation identifier. All 170 enabled row-level security; 152 also forced it for the table owner. The remaining 18 need review. This is a measured coverage gap, not evidence that customer records were exposed.
Application access also uses permissions, record scope and field visibility. A person’s ability to open a record does not automatically grant permission to export it or see every sensitive field.
Exactly what is encrypted
Call-recording subsystem
The recording subsystem implements encrypted audio and wrapped recording keys. Account configuration, keys and a verified recording workflow are required before it can be treated as operational.
CRM records and uploaded files
Leads, contacts, deals, bookings, payment records and uploaded documents are not separately encrypted by the application. They rely on access controls rather than field or file encryption.
Backups and hosting
The reviewed backup arrangement keeps database dumps on the same machine and does not wrap them in a separate encryption key. This does not provide an independently encrypted, off-site backup. Recovery testing and retention need their own dated evidence.
The prior deployment review supports Mumbai hosting. A hosting location does not prove that every connected service processes data only in India. The information sent to each enabled messaging, email or payment provider must be assessed separately.
The website and app use HTTPS for data in transit. Encryption during a connection does not change the storage limitations described above.
Staff access and audit visibility
The internal console includes permission gates, reason codes, time-limited assist records and audit controls. These controls should be assessed against the specific access path being used.
The reviewed customer-assistance workflow is incomplete: entry into the tenant app, a tenant-visible assistance screen and a working customer stop control are not all built. We do not promise that every possible staff access is visible to the customer in one finished screen.
Sensitive product actions carry audit records where implemented. An audit entry can explain a recorded action; it does not establish that every possible infrastructure access has been captured.
Accounts and customer contact
Password authentication uses Argon2id, a one-way password protection method. Session handling includes rotating refresh tokens. Use a separate account for each person and review role access when responsibilities change.
Single sign-on and a customer-workspace second authentication factor were not verified as available. The internal staff console has different authentication controls; those must not be presented as customer account features.
SMS and WhatsApp sign-in delivery are currently blocked. Review the available email route and the contact details in your workspace before inviting brokers or buyers.
Call and WhatsApp consent can be allowed, refused or not recorded. Missing CRM consent is informative for manual actions; it is not proof of permission. Recorded opt-outs and messaging-provider requirements still apply.
Providers, privacy and assurance
Source-supported external service paths include hosting, Resend email, MSG91 sign-in messaging, Meta WhatsApp, Exotel calling, Expo notifications and Cashfree subscription payments. Their presence in source does not establish that every account is configured or that delivery succeeds.
Buyer Connect can pass a payment-link request to the builder’s team; it does not provide an inline buyer payment gateway. Cashfree billing integration concerns the customer’s subscription to Saudaflow.
No security certification, independent penetration-test result or blanket DPDP compliance claim is made here. Request the specific evidence needed for your assessment. Legal policy pages remain under review and should not be used to override the limitations on this page.
Name the requirement you need to rely on.
Ask for the control, its scope and dated evidence before treating it as part of an agreed commitment.