Skip to content
Skip to content
FOR CLINICS AND HOSPITALS

DPDP-compliant document collection. Built for how a hospital front desk works.

Your patients’ ID proofs, insurance cards, reports and discharge summaries are personal data under the DPDP Act. Confidential Dispatch lets you collect them the way the Act requires, so every admission’s documents arrive compliant and sit in one place, admission by admission.

Start free, no card required LIVE AT APP.CONFIDENTIALDISPATCH.COM · INDIA
02 · YOUR INTAKE TODAY

Multiple places. No single answer.

Sunrise Hospital Admission, 12 Aug 2026 Admission and insurance pre-authorisation, 12 Aug 2026
Insurance card Document Lab reports, July Document Discharge summary, 2025 Document Pre-authorisation form DocumentYour documents are kept for 5 years, then deleted. This link stays open for 14 days.
‹ SP Suresh Pillaionline
Please send the reports and the insurance card10:02✓✓
PDFReports.pdf8 pages · PDF
18:40
PDFDischarge summary.pdf3 pages · PDF
18:40
↪ Forwarded
JPGInsurance card.jpg1 page · JPG
18:43 COPY 2
Rest on email.18:44
Message
Search mail
Compose Inbox12 Starred Sent Drafts
Suresh Pillai19:02Re: Re: Admission documents – attaching insurance…
Billing desk19:20Fwd: Fwd: Re: Admission documents – for billing
S. Iyer19:31Fwd: Re: Admission documents – saved to drive
Suresh PillaiMarthe January check-up
Re: Re: Admission documents
RSuresh Pillaito me
Attaching insurance card. Reports sent on WhatsApp to Dr Mehta.
JPGInsurance card.jpg
JPGAadhaar.jpg
ReplyForward
+ New My Drive › Clients › 2025 › Suresh Pillai Shared with 4
Files
PDFHealth check-up Jan 2026.pdf
PDFPre-authorisation form.pdf
PDFReports_final_v2.pdf
COPY 2
PAN card copy.jpg
COPY 3
✕ 6 DPDP CHECKS FAILED
03 · BUILT IN

DPDP-compliant collection.

Everything the Act asks for at collection. None of it by hand.

Insurance cardJPG
Insurance cardDocument
Lab reports, JulyPDF
Lab reports, JulyDocument
Discharge summary, 2025PDF
Discharge summary, 2025Document
Pre-authorisation formPDF
Pre-authorisation formDocument
HOW IT GOES TODAY

It starts with a message.

A pre-admission starts with a message from the attendant: “sending the reports and the insurance card”. Photos of reports arrive in a WhatsApp chat with the doctor, the insurance card comes to the billing desk by email, the TPA form is forwarded twice, and the front desk saves what it can to the desktop. Nobody told the patient why each document was needed, how long it would be kept, or that they could ask for it back. Nothing records that they agreed.

UNDER THE ACT

Every step is a gap.

Under the Act, each of those is a gap: no notice, no consent that can be demonstrated, no retention date, no record. And these are health records, the most sensitive documents a person hands anyone. When a patient asks what you hold on them, there is no single answer.

AND THE PRESSURE TO KEEP

So you keep everything, everywhere.

The pressure is not only the Act. The medical council already requires you to keep patient records for a fixed period, and insurers ask for the same documents again at claim time. So you keep everything, on every phone, indefinitely. That is exactly what the Act no longer allows.

04 · ONE REQUEST, END TO END

One request, from your desk to their phone and back.

Every request goes out with what the Act asks for at collection: the notice, the consent, the declared purpose, the retention date, the proof record and the path for your client to exercise their rights. You do none of it by hand.

How it works, in full
05Afterwards, kept for 5 years

Or any period you choose. Then the documents delete on their own, on the date the notice promised, unless you say otherwise. Every step, from the notice to the deletion, stays on a record that cannot be quietly changed. And your client can ask for a copy, a correction or deletion from the link on their receipt, at any time.

05 · BUILT FOR HOW A HOSPITAL FRONT DESK WORKS

Built for how a hospital front desk works.

See every feature
01

Name documents by the admission

Every document in a request has a name you can edit. “Discharge summary” becomes “Discharge summary, admission 12 Aug 2026” as you type it, so what the attendant uploads is already labelled for the file.

02

One folder per patient, admissions stacked

Every request you send a patient sits in that patient’s folder, newest on top. This admission sits above the last one without you moving anything.

03

The patient or attendant uploads in a minute, no login

They open the link on their phone, read the notice, agree, and upload, or fetch from DigiLocker where the document is available there. No account, no app, no password to reset. If they sent the wrong report they replace it while the link is open.

04

All patient documents in one place

Not across a doctor’s WhatsApp, the billing desk’s email, a front-desk PC and a shared drive. One copy, in the patient’s folder, with who viewed or downloaded it and when.

05

Keep sending the way you do

Copy the link into the WhatsApp chat the desk already has with the attendant, or open it pre-written in WhatsApp with one tap, or let the system email it. The chat stays the chat; the reports stop travelling through it.

06

Your hospital’s name and your logo, every time

Your hospital’s name is on every message the patient gets, and your name and logo are on the page they upload to, so they know the request is from the hospital and not a phishing attempt.

07

Accounts for the desk, billing and the TPA team, admin for the administrator

Invite your staff; the work belongs to the hospital, not to whoever did it. Admins control invites, settings and deletion; staff do the work. Every action carries the name of the person who took it.

08

Reminders that chase before the pre-authorisation

Reminders run on their own until every document is in: by email to the patient when we sent the link, a nudge to you when you sent it yourself. Claims week without the follow-up calls.

09

No backups to run

Documents, database, keys and backups are held in India (Mumbai), encrypted, and backed up for you. Nothing to copy to an external drive on a Friday.

10

Your patient list, yours to take

Every patient your hospital holds consent for, in one file, any time you want it. And when a patient asks, everything held on them exports as one file, and can be erased with the proof of erasure kept.

11

A record for when someone asks

Every notice shown, consent given, document received, viewed, downloaded, kept or deleted, on a record that cannot be quietly changed. When a patient, an insurer or the Board asks, you show the record for that request.

12

Kept for as long as the law says, then gone

Set the retention when you build the request: for the length of the treatment, then a second stage for the years the medical council or a law makes you keep the record, with that rule named. The documents stay through both stages, delete on their own when the second ends, and a patient’s withdrawal is recorded even while the statutory hold runs.

06 · YOUR TEMPLATE, READY ON DAY ONE

Your template, ready on day one.

Your account starts with a request already built for a hospital front desk: Patient registration, with an ID proof, the insurance card if there is one, and an emergency contact, the purpose and notice written, and the documents kept for as long as the person is your patient. Edit what differs and send.

And when a department needs something different, a new template takes about a minute: name it, list the documents, set the retention. Save it once, use it for every patient, every admission. A cashless claim, a second-opinion referral, a health check-up package: each one is a template you make once.

READY ON DAY ONEPatient registration
MADE BY YOUR FIRMCashless claim
MADE BY YOUR FIRMHealth check-up package
Document requests

New request

All requests
Start from a template One secure link per client
Press 1–3 to switch
Collect documents People upload what you ask for. Consent, notice and the files live here. Record consent only You hold the documents yourself. This records the notice and the consent.
Start from 1Blank 2Patient registration 3Cashless claim 4Health check-up package
01

Who it goes to

Name plus email or phone
Full nameSuresh Pillai Email[email protected] Phone52301 48762
Saved as +91 52301 48762
Add a person Each person gets their own link. ↵ on a complete row adds the next.
02 Patient registrationfor Patient registration and billing Change⏎ 03 4 items2 uploads · 2 written answers · 1 if applicable Change⏎ 04 Kept as long as they're a clientlink open 14 days · then deleted Change⏎

What the client sees

Live
Sunrise Hospital Patient registration New client onboarding
ID proof (Aadhaar or PAN) Document Insurance card Document Emergency contact name Answer Emergency contact mobile AnswerYour documents are kept for as long as they're a client, then deleted. This link stays open for 14 days.
Ready to send 1 person gets their own link; the notice is frozen the moment you create. Press ⌘ ↵ to create
SCREEN · BUILDER ON “PATIENT REGISTRATION” WITH THE CLIENT’S LIVE PREVIEW
07 · YOUR CLIENTS’ DOCUMENTS, KEPT SAFE

Compliance is what you are buying. Security is what makes it credible.

AWS · SOC 2 · ISO 2700119.08°N 72.88°EAP-SOUTH-1 · MUMBAIDOCUMENTS · DATABASE · KEYS · BACKUPS
THE RECORD · SHA-256
18:40CONSENT GIVEN · SURESH P.a91f
18:41DOCUMENT RECEIVED3c07
11:02VIEWED · YOUR STAFFe5d2
11:05DOWNLOADED · YOUR STAFF7b40
CHAIN INTACT
AES-256-GCMENCRYPTED AT REST · HTTPS IN TRANSIT
DOCUMENT KEY
FIRM KEY
HELD BY YOUR FIRM ONLY
PDFDOCUMENT.PDFSURESH PILLAI
HELD BYYOU
SHARED WITHNONE
THIRD PARTIES0
THE DOCUMENT

Never shared, never sold

Your clients’ documents are not shared with or sold to any third party, now or ever. The only outside services that touch anything are the ones that run the app for you: the hosting holds encrypted files it cannot open, and the mail provider carries the message, never the document.

KEY PER DOCUMENT · KEY PER FIRM

No access to anyone outside your firm

Including us: the files remain encrypted, and no panel shows them to anyone at Confidential Dispatch. Inside the firm: roles, two-factor sign-in, and every view and download recorded. When retention ends, the document’s key is destroyed, so it cannot be rebuilt from a backup.

AES-256-GCM · HTTPS

Securely sent and stored

HTTPS in transit, AES-256-GCM at rest, a key per firm and a key per document. The upload page is receive-only: once a document is sent, nobody can view or download it from there.

SHA-256 HASH CHAIN

A record that cannot be altered

Every action is on a SHA-256 hash chain, each entry tied to the one before, and the chain’s head is written daily to write-once storage. Change one entry and every later one stops matching.

MUMBAI · AP-SOUTH-1

Held in India, in Mumbai

Documents, database, keys and backups are all held in Mumbai. Nothing about your clients is stored outside India.

THE DOCUMENT

Never shared, never sold

Your clients’ documents are not shared with or sold to any third party, now or ever. The only outside services that touch anything are the ones that run the app for you: the hosting holds encrypted files it cannot open, and the mail provider carries the message, never the document.

KEY PER DOCUMENT · KEY PER FIRM

No access to anyone outside your firm

Including us: the files remain encrypted, and no panel shows them to anyone at Confidential Dispatch. Inside the firm: roles, two-factor sign-in, and every view and download recorded. When retention ends, the document’s key is destroyed, so it cannot be rebuilt from a backup.

AES-256-GCM · HTTPS

Securely sent and stored

HTTPS in transit, AES-256-GCM at rest, a key per firm and a key per document. The upload page is receive-only: once a document is sent, nobody can view or download it from there.

SHA-256 HASH CHAIN

A record that cannot be altered

Every action is on a SHA-256 hash chain, each entry tied to the one before, and the chain’s head is written daily to write-once storage. Change one entry and every later one stops matching.

MUMBAI · AP-SOUTH-1

Held in India, in Mumbai

Documents, database, keys and backups are all held in Mumbai. Nothing about your clients is stored outside India.

HOSTED ON AWS IN MUMBAI; AWS’S INFRASTRUCTURE IS SOC 2 AND ISO 27001 CERTIFIED.

Collect the DPDP-compliant way from your next admission.

Sign up and send your first request in a few minutes. Nothing to install, for you or your clients.Start free, no card required
Read our guide: DPDP for healthcare, explained