Subprocessors
SachDesk Technology Services Private Limited (“SachDesk”, “we”, “us”) provides Samvaads and related services as a multi-tenant SaaS platform. To operate the Service we engage third-party subprocessors that process personal data on our behalf.
This page lists the subprocessors we currently use for the Samvaads product and related platform operations. Website-only tools (for example analytics on sachdesk.com) are described in our Cookie Policy and Privacy Policy.
How we use subprocessors
Each subprocessor is authorized to process personal data only as needed to provide their service to us, under a data processing agreement or equivalent contractual terms where required. We remain responsible for the Service under our agreements with customers.
Channel platforms that a customer connects with their own credentials (for example a customer’s Meta / WhatsApp Business account, or customer-provided email infrastructure) are not SachDesk subprocessors; those relationships are between the customer and that provider.
Current subprocessors
| Subprocessor | Purpose | Typical data categories | Primary location |
|---|---|---|---|
| Amazon Web Services, Inc. (AWS) | Cloud hosting, compute, networking, object storage (per-tenant S3 buckets), managed cache/queues (for example ElastiCache / messaging), secrets, security scanning (for example GuardDuty), and optional AI inference via Amazon Bedrock | Tenant application data, files and attachments, logs, and operational metadata | AWS Mumbai region (ap-south-1), unless otherwise agreed |
| MongoDB, Inc. (MongoDB Atlas) | Managed databases for platform and per-tenant data stores | Account, contact, ticket, conversation, configuration, and related tenant data | Atlas cluster region(s) configured for our deployment |
| ActiveCampaign, LLC (Postmark) | Transactional and product email delivery, domain/DNS assistance for tenant sending domains, and related delivery webhooks | Email addresses, message content and metadata, delivery events | As described in Postmark’s documentation |
| Microsoft Corporation (Azure OpenAI) | Optional large language model and speech features (including Whisper transcription) when configured for our AI stack | Prompts, transcripts, audio submitted for transcription, and related model outputs as configured by the tenant | Azure region(s) of the configured deployment |
| OpenAI, L.L.C. (and affiliates) | Optional LLM / transcription provider when our stack is configured to use OpenAI APIs instead of or alongside Azure | Prompts, transcripts, audio, and model outputs as configured | As described in OpenAI’s documentation |
| Meta Platforms, Inc. | WhatsApp, Instagram, and Facebook Messenger channel APIs used when tenants connect Meta-backed channels through Samvaads | Message content, media, channel identifiers, and webhook events exchanged via Meta APIs | As described in Meta’s documentation |
| Razorpay Software Private Limited | Payment processing for plan upgrades, subscriptions, and usage add-ons where enabled | Billing contact details, payment identifiers, and transaction metadata (card data is handled by Razorpay) | India / as described by Razorpay |
| Google LLC (reCAPTCHA) | Bot protection on public forms on sachdesk.com (contact, demo, signup, privacy requests) | IP address, device/browser signals, form interaction signals | As described in Google’s documentation |
Updates to this list
We may add or replace subprocessors as our infrastructure evolves. We will update this page when material changes occur. Where a customer agreement or data processing addendum requires advance notice, we will provide notice as stated in that agreement (typically by email to the account owner or admin contacts on file).
If you have questions about subprocessors, contact contact@sachdesk.com or use our contact form.