KidsHealth360 Trust Centre

• Sensitive health and identity fields are encrypted at rest with AES-256-GCM; everything travels over TLS.
• Data is hosted on managed infrastructure located in India.
• Every account is role-scoped — a parent, teacher, principal, doctor and therapist each see a different slice of the platform, enforced at the database layer, not just in the interface.
• Staff and clinician accounts are subject to multi-factor enrolment checks and cannot elevate their own privileges.
• Every read, write, export and emergency disclosure is written to an append-only audit log that cannot be edited or deleted by anyone, including us.
• Backups are encrypted and restore procedures are tested.

Consent on KidsHealth360 is collected in two clearly separated parts:

• Part 1 — Emergency medical authorisation given to the school: first aid, ambulance, transport to hospital and sharing the emergency card with treating clinicians.
• Part 2 — DPDP Act, 2023 consent for the collection, storage and processing of the child's personal and health information, with each statutory right confirmed individually.

• The guardian's identity is verified by mobile OTP, and optionally Aadhaar or DigiLocker.
• The exact version of the consent text that was accepted is stored with the signature, timestamp, device and verification method, and can be downloaded as a PDF at any time.
• Consent is specific and purpose-bound. A new purpose requires fresh consent — we do not quietly widen an existing one.
• Consent can be withdrawn at any time from Account → Settings & privacy.

The full text lives in our Privacy Policy and DPDP compliance page.

• On grant means a doctor sees a child's record only after the guardian explicitly grants access, and only until the guardian revokes it.
• Emergency scan means the emergency card only — blood group, allergies and guardian contact — reachable by scanning the child's Health Passport, and every scan is logged.
• Aggregate only means counts and trends across a class or school, never a named child.
• Age-tiered means older children get a confidentiality tier over counselling notes, in line with clinical practice; safety concerns are always escalated to the guardian.
• KidsHealth360 staff do not browse child records. Support access is limited, purpose-logged and time-bound.

AI is used in a small number of clearly labelled places:

• Summarising a child's recent health signals into a plain-language "Today" view for the guardian.
• Drafting nutrition and vitamin guidance from logged meals and growth data.
• Suggesting smart reminders and follow-up nudges after screenings.
• Preparing a doctor-visit brief from records the guardian already holds.

And these are the hard limits:

• Child health data is never used to train any AI model — ours or a vendor's.
• AI output is guidance, never a diagnosis. Clinical decisions stay with a registered practitioner.
• Direct identifiers are minimised before a request leaves the platform; only the fields needed for the specific summary are sent.
• AI is never used to decide eligibility, to profile a child, or to target advertising — we run no advertising at all.
• Every AI call is recorded in an inference log for audit, including which feature invoked it.
• A guardian can ignore or dismiss any AI suggestion, and school staff never see a child's AI summaries.

• The child's school — screening entries the school itself recorded, plus the emergency card.
• A doctor — only for the duration of a guardian-issued access grant, revocable in one tap.
• A therapist or counsellor — only after a separate therapy consent.
• Emergency responders — the emergency card, via a Health Passport scan, logged every time.
• Government health programmes — RBSK and RPwD submissions where the school is statutorily required to report, through official channels.
• Processors that run the platform — hosting, SMS, email and payments — contractually bound, no independent use of the data.

• Account → Settings & privacy → Export my data produces a machine-readable file containing the child's profile, screenings, reports, appointments, consents, payments and audit history.
• Uploaded documents can be downloaded individually from the Health Vault; the consent forms and Health Passport print as PDFs.
• Exports are generated on demand and delivered to the signed-in guardian only.

• Withdraw consent — processing stops and the portal is locked. The record of the withdrawal itself is kept as legal proof.
• Delete the account — the guardian and children profiles, reports, screenings, appointments, messages and stored files are erased, along with the sign-in account.
• Where a record must be retained by law — such as a statutory screening submission or a payment receipt — it is retained for that period only, and everything else is deleted or irreversibly anonymised.
• An erasure reference number is issued so the guardian has documentary proof of the request and its completion.
• Automated retention sweeps delete data whose retention period has expired, without waiting for a request.

Available today:

• A guardian can link a child's existing ABHA number to their KidsHealth360 profile after guardian authorisation.
• Verified ABHA demographics can pre-fill the Add-a-child form, so the guardian re-types nothing.
• Every ABHA action — lookup, authorisation, link, unlink — is written to a dedicated, append-only ABHA audit log.

Deliberately not built:

• We do not create ABHA numbers, and we do not store Aadhaar numbers — only the last four digits, where the guardian chose Aadhaar-based verification.

Roadmap:

• Consent-manager based record exchange, so a guardian can pull records from, and push records to, other ABDM-linked providers.
• Health-record linkage with participating hospitals and labs.
• Alignment with ABDM health data standards as they are finalised for paediatric records.

• Digital Personal Data Protection Act, 2023 — verifiable guardian consent for a child's data, purpose limitation, data minimisation, storage limitation, and no tracking, behavioural monitoring or targeted advertising directed at children.
• Data principal rights — access, correction, erasure, nomination and grievance redressal are all implemented in-product, not just promised on paper.
• Breach notification — an internal dual-clock runbook targets CERT-In reporting within 6 hours and Data Protection Board notification within 72 hours, with draft reports generated automatically.
• Statutory school health programmes — RBSK and RPwD Act screening workflows follow the prescribed forms and referral pathways.
• Grievance Officer — Baldeep Singh, Data Protection Officer & Grievance Officer, info@kidshealth360.com, +91 78145 24624. If you are not satisfied with our response, you may approach the Data Protection Board of India.

Security researchers can report a suspected vulnerability to info@kidshealth360.com. Please give us reasonable time to remediate before any public disclosure, and never access or retain another family's data while testing.