SETU Demo applications
The model ↗
Demonstration only. Chandrapur Ward 7 · 32,400 residents · 7,100 households. A fictional unit. No real ward has agreed to anything. Nothing here is stored anywhere but your own browser.
Pillar 06 · Decide, learn, care

Sahyog

The most sensitive screen, so the design argument is subtraction. A name, a time, and whether the call was answered — and nothing else.

Sandhya Setu — check-ins due

Opt-in · revocable in one step

Volunteers come from the same few streets, so they generally know the person already. Hiding the name would be theatre. What matters is that the system does not become a record of what the volunteer knows — so the roster carries a name, a time and whether the call was answered, and nothing else.

Violence, abuse or coercion

Never enters this system
  • ✕ No mediation. No elders. No committee.
  • ✕ Nobody asks the survivor to explain themselves.
  • ✕ Nobody suggests reconciliation.
  • ✕ Direct referral to survivor-centred professional and legal services.
  • ✕ The community record closes at the point of referral.

There is no field on this screen where such a case could be recorded, because a rule that depends on people remembering it is not a rule.

What this screen holds

The Data Register
Consent record Proves they asked to be checked on While active
Preferred time So the call comes when they want it While active
Contact number To make the call While active
Answered / not answered To know whether to knock Deleted after 7 days

Four fields. Published as an ordinary page anyone can check, including people who do not trust the unit.

What it does not hold

  • — Why the person opted in
  • — Any medical or health information
  • — Household finances or debts
  • — Family circumstances
  • — Notes a volunteer wrote about them
  • — A history of previous check-ins

A volunteer who needs to know more asks the centre admin. That request is a deliberate act by a named person, and it is logged.