Data Processor Opt-Outs
Control which third-party processors handle your data by configuring your own channel alternatives. Opt-outs require a Bring Your Own Channel (BYOC) setup first.
Enterprise feature. 1 of 5 processors support opt-out. Data continues flowing through the current processor until your alternative is active and verified. Reversion is available at any time.
MSG91 Pvt Ltd
Using vendorOTP delivery via SMS and WhatsApp
Region: IndiaData processed: Phone number, OTP message content
Razorpay Software Pvt Ltd
Using vendorRequired processorPayment processing and subscription billing
Region: IndiaData processed: Payment tokens, Bank account info, Transaction metadata
Amazon Web Services Inc
Using vendorRequired processorCloud infrastructure, storage, and AI inference
Region: India (ap-south-1)Data processed: All data at rest and in transit
MongoDB Inc
Using vendorRequired processorManaged database for CRM and business data
Region: India (ap-south-1)Data processed: CRM records, Lead and contact data, Integration configurations
Google LLC (Firebase)
Using vendorRequired processorCustomer authentication via OTP
Region: Global (EU data region available)Data processed: Phone number, Auth token
Changes to this list are communicated 30 days in advance per our Data Processing Agreement. View full public list.
Scaffold data shown — wire compliance.subProcessorOptOuts.list tRPC when API running.