Skip to content

Security and trust

Built for the questions your security team will ask.

How we keep each client's data separate, who can reach it, where it is stored, how long we keep it and how we respond when something goes wrong.

  • Each client's data is used only for that client.
  • We collect only what the service needs.
  • We do not sell personal data or use your customers' messages to advertise or to train general-purpose AI models.
  • We use the official WhatsApp Business Platform only.

Your data, separated

Every table that holds client data has row-level security switched on and enforced in the database. Each one has an automated test that tries to read another client's data and must fail. Background services use their own limited database roles.

Who can sign in, and how

  • Two-step verification with an authenticator app. An organisation can require it for all members; it is always required for clients onboarded by Astitva and for Astitva staff.
  • Owner, admin and member roles, with per-member permissions.
  • Astitva staff use a separate admin console with two-step verification, a 30-minute idle timeout and a 12-hour session limit. High-risk staff actions ask for a fresh code.
  • Staff access to client data is limited and audited.

Encryption

  • WhatsApp business tokens and journey secrets are encrypted with AWS Key Management Service (envelope encryption). They are never shown in the browser, logs or error reports.
  • Data is encrypted in transit (TLS 1.2 or higher) and at rest.
  • Files are kept in a private store and opened only through short-lived signed links.

Where your data lives

All Senderr data stores are in India: the database in Supabase's Mumbai region, and services, queues, keys and files in AWS Mumbai (ap-south-1). Messages pass through Meta's WhatsApp infrastructure as part of delivering them, under Meta's terms.

Error reporting (Sentry) runs outside India. It is optional, can be switched off, and message text, tokens and phone numbers are removed before a report leaves Senderr.

How long we keep data

DataKept for
Messages, conversations, internal notes and activity24 months (your contract can set another period)
Media files12 months (your contract can set another period)
Raw webhook events from Meta30 days
Campaign recipient records and link clicks12 months
Contacts you deleterecoverable for 30 days, then erased
Audit events7 years

A daily job applies these periods. When you disconnect a number, its business token is deleted at once and its conversations, messages and media 30 days later. When you leave Senderr, your data is deleted 30 days after offboarding. A legal hold pauses deletion only when there is a dispute or a request from an authority.

Digital Personal Data Protection Act, 2023

For your customers' data, you are the data fiduciary and Astitva processes it on your behalf. Senderr helps you meet your duties:

  • A consent ledger with the source, time and proof of every opt-in and opt-out
  • Opt-out by reply, in English, Hindi and Hinglish, honoured automatically
  • Export or delete everything held about one customer from their profile, each request logged with a due date
  • Automatic retention and deletion
  • Anonymised opt-out proof kept after deletion, so an opt-out keeps being honoured

This is not legal advice. Your counsel decides how the Act applies to you.

A record of sensitive actions

Approvals, number connections, setting changes, exports, staff actions and other sensitive events are written to an append-only audit trail and kept for 7 years. Astitva can export your organisation's audit trail for a review. A self-serve audit log inside Senderr is coming soon.

Safe sending

  • Consent, suppression and WhatsApp's 24-hour window checked before every message
  • Each message sent once, even if a worker restarts mid-send (tested with 50,000 messages)
  • Campaigns pause on their own when a number's quality rating or messaging limit drops
  • Every file customers send is scanned for viruses; infected files are quarantined
  • Journey web requests cannot reach private or internal networks
  • Astitva can pause sending for an organisation during an incident

Sub-processors

Sub-processorWhat they do
Meta PlatformsWhatsApp Business Platform (Cloud API): delivers and receives messages, manages templates and accounts
Amazon Web Services, Mumbai (ap-south-1)services, queues, encryption keys and file storage
Supabase, Mumbaidatabase, authentication and file storage
Sentry (Functional Software, Inc.), outside Indiaoptional error reports with sensitive data removed
Email delivery providersign-in, invitation and alert emails only; no customer message content
Googleonly if a user chooses Sign in with Google; receives no client or customer data

We tell clients before we add a sub-processor.

If something goes wrong

We follow a written security incident runbook: contain, assess, notify and review. Affected clients are told what happened, what data was involved and what we are doing about it. Report a security concern to the security contact named in your agreement, or through Request access.

Coming soon

  • Coming soonSingle sign-on (SAML) and SCIM user provisioning
  • Coming soonAudit log and export inside Senderr
  • Coming soonPhone number masking by role
  • Coming soonIP allow-lists and session policies per organisation
  • Coming soonIndependent penetration test report and security certifications

Need our security questionnaire answers?

Request access and mention your review. We will share what we have.