Privacy operations for India's DPDP Act

Ask for consent. Know where the data goes. Prove it.

Scrutora is the system a privacy programme runs on. Collect consent from parents, patients and customers. See where their personal data really travels. Keep your processing register, track every withdrawal until it is finished, and hand an auditor the evidence.

Need the whole programme, not only the software? Our partners run it with you.

An erasure request in Scrutora: eight systems that hold one person's data, each marked done, in progress, blocked or not started.A consent form on a phone, addressed to a parent about their child, listing each purpose with its own checkbox.
The product, on demo data. Behind: one person's erasure request, tracked system by system. In front: the consent form a parent receives on their phone.
Hosted in India
Consent records and customer data are stored in Mumbai.
Tamper-evident records
Consent records are hash-chained and can be checked independently.
Your code is not kept
A scan reads the repository, reports what it found, then discards the copy.
3,000 repositories studied
Our published index of healthcare code found confirmed violations in 43.6% of them. Read the study

1Ask

Consent from people who will never see a cookie banner.

Parents of a class, patients at reception, drivers joining a fleet. Send a short form by WhatsApp, SMS or email, or print a QR code for the front desk. Each purpose has its own tick box, the person keeps a receipt, and you keep a record of who agreed to what, and when.

  • A parent or guardian signs for a child, and the relationship is recorded
  • Paper forms entered by staff land in the same record
  • The same person can withdraw from their receipt, at any time
  • A consent banner for your website, on the same record
The receipt a signer keeps: what they agreed to, purpose by purpose, with a link to download it.A consent campaign: five people invited by WhatsApp, with who has opened, answered or still needs a reminder.
Left: the receipt the signer keeps. Right: the desk view of one campaign, showing who has answered and who needs a reminder.

2Know

Your privacy policy is a promise. Your code is the proof.

Scrutora reads your repositories and cloud accounts and draws the map: each personal-data field, where it is stored, and every vendor that receives it. There is no questionnaire to fill in. It then compares what your software collects with what people actually agreed to.

  • A data-flow map read from source code, in 12 languages
  • Cloud accounts checked against the same rules
  • Vulnerable libraries ranked by whether they touch personal data
A data-flow map: personal data entering an application, the services that process it, and the logs and stores where it lands.
The data-flow map of a public banking application, read from its source code.

3Record

The register the law expects, without the spreadsheet.

List what you do with personal data: the purpose, the lawful basis, the systems and the vendors. Start from what the code scan found, import what you already have, and send short questionnaires to the teams who know the rest.

  • Gaps listed with what to do about each one
  • Vendors, contracts and review dates kept alongside
  • Exports as a record of processing when someone asks for it
A processing register for a clinic: six activities, each with its status, lawful basis, source and next review date.
A clinic's processing register: six activities, with lawful basis and review date.

4Honour

When someone says stop, finish the job everywhere.

A withdrawal or an erasure request opens a tracker that lists every system and vendor holding that person's data, taken from your register. Each line has an owner and moves from not started to in progress to done. The request closes only when every line has.

  • Opens by itself when someone withdraws on a form
  • Backups and outside vendors appear as their own lines
  • A dated log of who did what, for the day you are asked
The Consent Withdrawal tracker: an erasure request with two of eight systems done, one in progress and one blocked.
One erasure request. Two of eight systems are done, one is in progress, and one is blocked with the reason noted.

5Prove

Hand over evidence, not assurances.

Export the consent records, the register, the data map and the findings as they stood on one date. Because consent records are chained together, anyone can check that none was changed after it was captured, without taking our word for it.

  • One evidence pack for an auditor, a customer or the Board
  • Findings mapped to clauses across 26 frameworks
  • A public checker for any pack you are handed
The evidence screen for a consent site: verify the record chain and download the evidence pack.
Verifying a site's consent records and downloading the evidence pack.

Need the whole DPDP programme, not only the software?

Software does not write your notices or train your staff. Our partners are privacy and security practices who do that work, and they do it on Scrutora, so what they set up is what you operate afterwards.

  1. AssessWhere you stand today, from your code, your cloud and the paperwork you already have.Partner, using the scan and the register
  2. Put in placeNotices, consent forms, the register, vendor agreements and staff training.Partner and your team
  3. OperateRequests, withdrawals, reviews and evidence, month after month.Your team, on Scrutora

For engineering teams

Start with one repository.

Point Scrutora at a public GitHub repository and read its data-flow map and findings a few minutes later. It is free and needs no call. When you are ready it runs in your pipeline and your editor.

See it on your own forms, register or code.

Tell us what you collect and from whom. We will show you the five steps on your case, not on ours.