Policy

Child safety

Last updated 31 July 2026Applies to AspireACE

In plain words

  • Learners may be minors, so account authority and consent cannot be assumed.
  • Public pages must not expose a learner's identity, contact details, precise location, private learning record, or family relationship.
  • Safety, privacy, support, and account actions use governed authenticated routes.
  • The complete legally reviewed child-safety policy and escalation contacts are still pending approval.

Publication status

Technical boundaries are published; the complete policy is pending human approval. A named safeguarding role is in place — see “Who to contact” below. Legal and privacy review is still required, and the direct line is not live yet.

Consent and account authority

Age, guardian relationship, purpose, consent, revocation, and visibility must be checked by the owning account service. A payment relationship does not automatically grant access to a learner's private record.

Data minimization

Public surfaces do not need a minor's private identity, exact address, direct contact, payment record, or personal learning history. Any collection must be tied to a specific approved purpose.

Safety and support

Urgent safety concerns require a human-owned support and escalation path. Automated guidance must not present itself as emergency, medical, legal, or safeguarding authority.

Who to contact

Safeguarding concerns about a learner are owned by the Counsellor at ATRIYA Systems Pvt Ltd. That role is named and accountable; it is not an automated queue.

A direct line is being set up and is not published yet. We would rather say that than print a number that does not answer. Until it is live, write to support@aspireace.in and mark it safeguarding, and it is routed to that role.

If a child is in immediate danger, contact the emergency services or Childline India on 1098 first. We are not an emergency service and must not be used as one.