India's Digital Personal Data Protection Act, 2023 doesn't mention number masking, but its core duties (use personal data only for a stated purpose, protect it, erase it when the purpose ends) fit what masking does: people talk without seeing each other's numbers. Masking supports a privacy program; it doesn't replace one. This is not legal advice.
Share fewer phone numbers: Open the Edesy masking portal. Set up masked sessions or extension codes for customer-partner calls.
Why phone numbers are a privacy problem
Marketplaces, delivery apps, home services, classifieds and dating apps all connect two people who need to talk but don't need each other's number. Without masking, the app hands a customer's number to a rider, technician or seller, and it stays in their phone long after the job. Once shared, you can't take it back, limit its use or delete it.
Masking puts a virtual number in between. Each side calls the virtual number, and the platform connects them. Neither side sees the other's real number, and the link can be ended when the job is done.
DPDP principles and where masking helps
The table maps general principles in the Act to what masking can contribute. It's a planning aid, not an interpretation of the law.
| Principle (general) | What it asks of a business | How masking can help | What masking doesn't do |
|---|---|---|---|
| Purpose limitation | Use personal data only for the stated purpose | Numbers are used only to connect the call for that order or booking | Write your notice or purpose statement |
| Sharing only what's necessary | Don't collect or disclose more than you need | Partners never receive the customer's number | Decide which other data you collect |
| Retention and erasure | Erase data once the purpose is served | Sessions expire; extension codes can be deactivated or deleted | Delete data in your own systems |
| Security safeguards | Protect personal data with reasonable measures | Encrypted recording storage, signed links, signed webhooks | Secure your own app and staff access |
| Accountability for processors | Make sure vendors handling data on your behalf act on your instructions | Configurable expiry, recording, routing and logs | Replace your contract with the vendor |
| Rights of individuals | Respond to requests for access, correction and erasure | Per-session history and CSV export help you find records | Run your request process |
How Edesy masking works
| Feature | What it does |
|---|---|
| Sessions | Pair A and B on a virtual number; route by who is calling; set expiry and max calls; pause, extend or end |
| Webhook routing | Your server decides where each call goes (masking.route) |
| Extension codes | One masked number plus a short code; for tags, labels, listings, intercom |
| Two-leg click-to-call | Ring A, then bridge to B, with a masked caller ID |
| Recordings | Per-number toggle; encrypted cloud storage with signed links |
| Events | Signed webhooks for session and call events |
| Logs | Per-session history, analytics, CSV export |
A privacy-minded masking setup
- Define the purpose. "Let the rider reach the customer about this delivery." Write it down; it drives every other choice.
- Pick the mode. Sessions when both people are known; extension codes when the caller isn't (a parcel label or a vehicle tag). See extension code number masking.
- Set an end. Give sessions an expiry and a max-call limit that match the purpose. Deactivate extension codes when the shipment, listing or booking closes.
- Decide on recording. Leave it off unless you have a reason. If you record, tell people and limit who can listen.
- Limit access. Use workspace roles so only the people who need call logs and recordings can see them.
- Verify webhooks. Check the HMAC signature on every event before acting on it.
- Clean up your side. Masking keeps numbers out of partners' phones, but your own database still holds them. Apply your retention rules there too.
- Write it into your notice. Tell customers that calls with partners go through a masked number, and whether they're recorded.
Common gaps masking doesn't close
- Numbers shown in the partner app. If your app displays the customer's number next to the call button, masking the call doesn't help. Show only the masked number.
- Numbers in exports. CSVs shared with partners or agencies can leak what masking protected.
- SMS and WhatsApp. Edesy masking is for voice calls. If partners message customers directly, those numbers are still shared.
- Long-lived sessions. A session that never expires is a permanent shared line.
Questions to ask any masking vendor
- Can I set an expiry and a call limit per session?
- Can I turn recording off per number?
- How are recordings stored and accessed?
- Are webhooks signed, and is there a delivery log?
- Can I export call logs for my own records and requests?
- What does the vendor do with my data, and what does our contract say?
On the last point, ask for answers in writing and have them reviewed. Edesy doesn't claim any DPDP certification; you decide whether its features meet your needs.
Cost
Masked calls are Rs 1.50/min on a 60-second pulse with a 1-minute minimum, plus number rental (Rs 499/month for mobile or 92-series). Prices exclude 18% GST. See number masking pricing.
Further reading
- What is number masking?
- DPDP Act and voice AI
- Number masking for marketplaces and gig platforms
- The number masking hub and number masking docs
This article is for general information. It isn't legal advice, and the law and the rules made under it can change. Speak to a qualified adviser about your obligations.