India
Made for Indian teams, down to the invoice.
Rupee pricing, sending from Mumbai and a consent ledger designed around the DPDP Act, with a GST tax invoice carrying your GSTIN once billing opens. WhatsApp journeys are next.
- region
- ap-south-1
- sending
- Mumbai, India
- stored
- contacts and properties
- message content
- events and logs
Stored in IndiaComing
Priced in rupees. Invoiced for GST.
Once billing opens, your finance team gets a tax invoice it can file every month, for both kinds of email.
Rupee prices, before GST
Every rupee price we show excludes GST and says so. 18% GST is added on the invoice.
Your GSTIN on every invoiceComing
One tax invoice a month covers transactional and marketing email, with your GSTIN, so you can claim input tax credit.
CGST and SGST, or IGST
Same state as ours: CGST 9% plus SGST 9%. Another state: IGST 18%. The place of supply decides; the total is the same.
UPI Autopay, e-NACH or cardComing
Set up a recurring mandate once, and each month’s invoice will be paid from it.
Tax invoice
SAMPLE| Transactional1,00,000 emails / month | ₹2,699.00 |
| Marketing10,000 subscribed contacts | ₹2,999.00 |
| Subtotal | ₹5,698.00 |
| CGST @ 9% | ₹512.82 |
| SGST @ 9% | ₹512.82 |
| Total | ₹6,723.64 |
Intra-state supply shown (CGST + SGST). Inter-state supply is billed as IGST @ 18%. Your GSTIN on the invoice lets you claim input tax credit.
Your data, in India.
Mail goes out from Mumbai. Here is each kind of data we hold, and where it is kept, stated no more strongly than we can back.
| Data | Where it is kept |
|---|---|
| Outgoing mailEvery message you send | Sent from Mumbai (ap-south-1) |
| ContactsAddresses, properties, topics and consent records | Stored in IndiaComing |
| Message contentSubjects, bodies and templates | Stored in IndiaComing |
| Events and logsDelivery events, opens, clicks and API logs | Stored in India, with your contactsComing |
| Attachments and received mailFiles you send, and inbound email | Not confirmed yet |
| BackupsCopies of all of the above | Not confirmed yet |
A consent ledger built for the DPDP Act.
Every contact carries a record of what they agreed to, how, and when they changed their mind.
What each row records
- Who and when
- The contact, and the time in IST.
- For what
- The purpose: the topic they agreed to, such as offers or product updates.
- Under which notice
- The version of your consent notice they were shown.
- From where
- A signup form, your API, an import or the preference page.
- Withdrawals
- A withdrawal is its own row, with the same detail as the consent it ends.
- Double opt-in
- Signup forms can ask people to confirm before they are subscribed.
Who does what
You: the Data Fiduciary
You decide why your contacts’ data is collected, show them your notice and ask for their consent.
Refiremail: your Data Processor
We process that data on your behalf and on your instructions, under a data processing agreement.
Read the draft DPA- [email protected]granted
- [email protected]granted
- [email protected]withdrawn
- [email protected]granted
The timeline
- Aug 2023Parliament enacts the Digital Personal Data Protection Act.
- Nov 2025The DPDP Rules are notified, with an eighteen-month period for phased compliance.
- 18 months onThe phased period ends. Consent records made now will already be in the ledger.
Coming
WhatsApp journeys.
A WhatsApp step inside the same journey, on the same contact, with the same consent record.
Not available yet, and there is no date to share. This page will change when it ships.
A person reads every email.
Questions about GST, residency or consent go to the same inbox as support.