This Acceptable Use Policy (“AUP”) governs how schools, principal-administrators, teachers, students, parents, and other users interact with ProofSchool. The AUP is incorporated into our Terms of Service and a material breach is grounds for suspension or termination.
ProofSchool is built around two things that don't work if you bend the rules: anonymity (so students give honest feedback) and good-faith assessment (so teachers learn from the result). This AUP is what keeps both intact.
1.Anonymity is non-negotiable
Anonymous responses must remain anonymous.
- Do not attempt to identify individual respondents, whether by inspecting timestamps, language fingerprints, response volumes from a section, or any other side channel.
- Do not pressure students or parents to share their response text outside the platform.
- Do not use ProofSchool data alongside another tool (a Google Form, a paper register, an attendance log) to de-anonymise a respondent. Combining data sources to identify is a breach even if no single source identifies.
- Where the platform shows verbatim quotes in reports, those quotes are stripped of identifying detail and attributed only by stream (student / peer / self). Do not re-attribute them to a named individual in any internal communication.
2.No retaliation
ProofSchool reports support teacher growth. They are not instruments for adverse employment action driven by single feedback cycles.
- Schools may not terminate, demote, or financially penalise a teacher based solely on a single ProofSchool report. Reports should be read alongside the teacher's response, classroom observation, and longitudinal evidence.
- Anonymous student or parent feedback may not be used as a disciplinary trigger against an individual respondent where identification has been attempted.
- Teachers must be given a meaningful opportunity to read their report and write a self-reflection before the school management committee discusses it.
3.No synthetic or coerced responses
- Do not submit feedback on behalf of students or parents.
- Do not pressure respondents to give particular ratings or particular comments.
- Do not generate fabricated responses (mass submissions, bot-driven traffic, IP-spoofing). The platform's rate-limiting and consent capture are designed to make this difficult; circumvention is grounds for immediate suspension.
- Do not use a single device to submit responses on behalf of multiple students; the per-token rate limit is designed to allow legitimate computer-lab and parent-slip flows but not industrialised submission.
4.Parental consent for minor data
Students under 18 are Children under the DPDP Act 2023. ProofSchool requires parental consent before processing any response from a minor.
- Schools must ensure parental consent is captured (digital consent in the form, or paper-slip-home consent on file) before sharing the section's response link with students.
- Schools must honour parental revocation of consent and pass revocation requests to ProofChain in a timely manner.
- Schools must not coerce parents or students into participating.
5.Report distribution
- Each teacher's report is visible to the teacher themselves and to the school's principal-administrator. Distribution beyond these two audiences (other teachers, parents, governing body, peer assessors, the public) requires the subject teacher's written consent.
- ProofSchool reports may be uploaded to the SARAS portal as supporting evidence for the school's self-assessment — this is explicitly permitted and does not require separate teacher consent.
- Reports may not be posted publicly, on social media, or in marketing material in identifiable form.
6.No misuse of the platform
- Do not use ProofSchool to harass, intimidate, or discriminate against any teacher, student, parent, or staff member.
- Do not upload content that is illegal, infringes third-party rights, contains malware, or violates applicable laws including the IT Act 2000.
- Do not attempt to access, probe, or scan the platform beyond what is necessary for normal use. Security research is welcome — please contact security@proofchain.in before testing.
- Do not reverse-engineer, decompile, or attempt to extract ProofSchool's source code or AI prompts.
- Do not re-sell ProofSchool, white-label it, or wrap it inside another product without a written commercial arrangement with ProofChain.
7.AI-generated content
- AI-generated reports are advisory. The principal-administrator's human sign-off is the authoritative output, not the AI text itself.
- Do not present AI-generated reports as if they came from an external auditor or accreditation body. Every report carries a disclaimer; that disclaimer must not be removed or obscured.
- Do not prompt-inject artifacts to manipulate the AI evaluator's output (e.g. instructions in the lesson plan text telling the AI to grade it differently). Detection of prompt injection in submitted artifacts is grounds for the report to be voided and the teacher contacted.
8.Reporting violations
If you become aware of a violation of this AUP — by your school, by another user, by a respondent, or by a third party — please report it to abuse@proofchain.in or grievance@proofchain.in. We acknowledge reports within 24 hours and investigate promptly. Schools that habitually violate the AUP may be suspended without refund.
9.Updates
We may update this AUP from time to time. Material changes take effect on 30 days' notice to the principal-administrator at their registered email; other changes take effect on publication. The current AUP is always published at /aup.