Platform
Five jobs, one record.
A privacy programme asks for consent, knows where personal data goes, keeps a register of its processing, vendors and rules, honours every request and breach, and proves all of it. Scrutora does each job, and because they share one record, the answer to one is the evidence for the next.
| Step | What it does | How it connects | Modules |
|---|---|---|---|
| 1. AskCollect consent you can show later. | Consent forms sent by WhatsApp, SMS or email or signed at a desk, a banner for your website, and a receipt for every person. | Each consent names its purposes, which are the same purposes your register lists. | |
| 2. KnowSee where personal data really goes. | A map of where personal data travels, read from your source code and cloud accounts: each field, where it is stored and which vendors receive it. | The systems and vendors it finds become rows you can add to the register. | |
| 3. RecordKeep the register, your vendors and your rules. | Your record of processing, your vendors with their contracts and certificates, and your policies with who has read them and the training behind them. | A withdrawal looks up which systems and vendors hold a person's data here; the policies say which duties are covered. | |
| 4. HonourAnswer every request and every breach on time. | One queue for every rights request and withdrawal, with a risk band and escalation to the DPO, and an incident record that keeps the CERT-In and Board clocks and tells the people affected. | A withdrawal opens by itself from a consent form; an incident finds whose data a system held from the data map. | |
| 5. ProveHand an auditor and your board the evidence. | A consent ledger, a proof pack per person, a monthly board summary, and evidence exports of the register and the data map that anyone can check. | Every report comes from the same record the other four steps keep. |
Who sees what
- Access per moduleGive each person no access, view, edit or manage in each module. Ready-made roles for a DPO, legal, IT and unit staff, or save your own.
- Per school or unitLimit a person to the schools, branches or products they look after. Everything they open stays inside them.
- Several consent units in oneA school with a junior and a senior wing can keep each wing's website consent, forms and requests apart, under one school.
Start with four questions.
Guided setup asks your sector, whether you handle children's data, how you collect personal data and whether it leaves India, then suggests what to switch on, which policies and courses to start from, and keeps a checklist that ticks itself.
Start with one step.
Most organisations begin with consent forms or the register and add the rest when they need it. Engineering teams often start with a free scan of one repository.
See it on your own case.
Tell us what you collect and from whom. We will show you the product on your forms, register or code.