Education · Schools & minors

Children’s data — clear for parents, consistent across every system

Most learners are minors; guardians sit at the centre of consent while the school stays accountable. Kavach is the shared notice and consent layer across ERP/SIS, LMS, transport, fees, and comms — APIs and webhooks, plus optional browser assist on legacy staff screens.

  • Guardian-first
  • Campus + edtech
  • Not owned by one ERP

Touchpoints

Where children’s data shows up — in six bands

Grouped for K–12; universities and coaching centres can drop or merge rows. Kavach runs workflows and evidence — your counsel sets lawful grounds.

Band Typical data Notice & guardian themes
Admissions & identity Forms, prior records, ID photos, directory lists. Relationship proof; retention; separate optional uses (merch, referrals).
Learning & assessment LMS, marks, portfolios, board registration. Educational purpose; staff access; per-vendor edtech notices.
Campus life & safety Attendance, gates, transport GPS, trips, health office. Safeguarding; location minimisation; trip photos vs marketing.
Money & comms Fees, canteen wallets, SMS/app/email. Processing only; channel prefs; promos actually stop on unsubscribe.
Events & media Annual day, web galleries, press, yearbook vendors. Explicit face/voice choices; withdrawal hits web + photographer + bus.
Support, discipline, alumni Counselling notes, incidents, CCTV commons, graduate outreach. Restricted roles; legal/safety trails apart from marketing; fresh basis after school.

At a glance

School-year rhythm and where Kavach sits

One lane for the academic arc; one map for systems inside the school versus vendors outside — same integration model as our platform page.

1 · From enrolment through alumni (simplified)

Each arrow ≈ a natural notice checkpoint

Kavach keeps a continuous timeline per child and guardian — not a one-off admission checkbox.

2 · Inside the school vs outside vendors

APIs / webhooks · optional browser assist on legacy ERP

A guardian withdraws photo or marketing consent → webhooks reach CRM, site, and photographer — not only the ERP row.

Guardians, edtech, checks

Product shape that matches how schools actually work

Guardian accounts and child profiles under one family; audit shows who consented and which notice version applied. New class apps get a purpose pack and roster/SSO only after policy allows — same APIs as our platform. Mature learners can get scoped roles when your policy says so.

  • Optional uses (photos, marketing, research) refusable without hurting core schooling.
  • One guardian update → bus, website, and photographer get the same signal.
  • Per-child timeline exportable for boards or grievances — minutes, not days.

Guardian portal

History, purposes, and requests in plain language

Aligned with what admins see internally — fewer “but the ERP said…” disputes.

Portal view of consent history and preferences suitable for a parent account
Transparency Branding and policy packs map to your school.

Next steps

Map your ERP, bus stack, and edtech with us

We start from the parent journey and your minor-data map.