India-region by default
All borrower data, recordings, and decisioning workloads run in an India region. No borrower data leaves the country for routine operations. Decisioning workloads stay in-region too.
Trust & Compliance
Every compliance rule below is enforced in the platform — not in a slide, not in a policy PDF, not in agent training. The audit trail is built as work happens, not reconstructed at quarter-end.
All borrower data, recordings, and decisioning workloads run in an India region. No borrower data leaves the country for routine operations. Decisioning workloads stay in-region too.
Outbound calls are restricted to the 8 AM–7 PM IST window at the dialer layer. Agents cannot override. The audit trail records every attempted dial — including the ones blocked by the lock.
DNC and NDNC registry lookups gate every outbound channel — voice, SMS, and WhatsApp. Frequency caps are encoded; consent state per channel is persisted and re-checked at send time.
Immutable, partition-aware audit log captures every request and response, with PII redaction policy enforced in code. Click tracking for payment links anonymizes identifiers after the retention window.
Tenant scoping is enforced at the data layer — not just by application code. Defense in depth: if application code forgets to filter, the data layer still does.
100% call recording with retention-aware policy. Per-tenant configuration. Recordings, transcripts, and evidence artifacts are all addressable through the audit trail.
Compliance summary
Book a 30-minute walkthrough
We'll show calling, Smart Collect attribution and decisioning, payment-link orchestration, and field visit evidence — using common DPD bands and industry-standard workflows.
Or write to hello@credmux.com