Home · Security & privacy

Security & privacy

Your child's data, kept private.

Kindred is designed for India's Digital Personal Data Protection Act (DPDPA, 2023) from the first line of code. We encrypt in transit, enforce strict per-row access, and never share school, parent or child data with third parties for advertising or analytics.

Where your data lives

All school, parent, child and message data is stored in a Supabase Postgres database in Mumbai, India (Supabase on AWS, region ap-south-1). Until 11 November 2026 it was in Seoul, South Korea; that old copy is being shut down. If that changes, we'll update this page and our privacy policy and tell you first.

Who can see what

We enforce row-level security at the database level, not just in the app. A parent's session can only read their own child's records. A teacher can read the records of children at their own school, and no school can read another's. Kindred's founder account can see records across schools, to run and support the service.

What we never do

Your DPDPA rights

You can request a full export of every record we hold about you and your child, correct anything that's wrong, or ask us to delete it. We honour requests within 30 days. Full details in our privacy policy.

Operational controls

Vendors we use

The list is short by design. Each is a data processor with a narrow purpose:

No advertising SDKs, no behavioural-analytics SDKs and no chat widgets that read your messages, anywhere in the app. Our public pages for schools use LinkedIn's Insight Tag to measure our own advertising; see the privacy policy.

For your school's data-protection officer

We're happy to share our security architecture document, processor list with data-processing agreements, and pen-test summaries on request. Email privacy@kindredschool.in.

Bring DPDPA-native to your school.

Most school software was built before DPDPA existed. Kindred wasn't.

Read the privacy policy →