When the parent says the email you sent in October was different from what they show you in March.
Education runs on documented communication that's reviewed months or years after the fact: a plagiarism case appealed at end-of-semester, a parent communication contested at a school-board meeting, a Title IX intake reviewed by district counsel a year later. The screenshots in your inbox or your LMS are technically evidence, but inboxes get migrated when the district changes vendors, LMS contracts roll over each summer, and a screenshot without provenance is the easiest thing to dismiss in an emotionally-charged hearing. Sealing the screenshot at the moment of capture — same browser session — locks the file cryptographically. The receipt timestamp predates any later challenge, and the verification works on a personal device if your school account is suspended pending the appeal. It doesn't decide the academic case (that's the academic-integrity committee); it just makes the underlying screenshot un-disputable so the conversation moves to the substantive question.
Workflows educators actually run
- 01
Plagiarism intake: seal the side-by-side at the moment of detection.
When you spot a likely plagiarism (student paper vs. source), screenshot the side-by-side in your detector tool (Turnitin, Copyleaks, manual side-by-side) and seal in /seal in the same session. The receipt timestamp is now part of the academic-integrity case file. When the student appeals at end-of-semester, the evidence is dated and signed; the appeal turns on whether the match is plagiarism, not on whether you fabricated the screenshot.
- 02
Parent communication: seal high-stakes emails and parent-portal messages.
Emails about IEP changes, behavioral incidents, accommodation requests — anything that might be contested at a future IEP meeting or in a Section 504 dispute — screenshot from your inbox and seal. The receipt URL goes into the student's file alongside the original. When the parent disputes the content months later, the receipt removes 'maybe the email was edited' from the discussion.
- 03
Conduct documentation: seal student-online-content evidence at first review.
Bullying screenshots forwarded from student-to-student, Instagram comments, Discord messages — the kind of evidence that ends up in a Title IX or conduct review. Seal at intake; the receipt is dated to your custody, the original screenshot stays in your file. When the case is reviewed by district counsel weeks later, the evidence chain is intact.
- 04
LMS migration: seal critical artifacts before the platform sunset.
When the district migrates from Canvas to Schoology (or vice versa), some artifacts get exported partially, some don't transfer at all. Seal screenshots of grades, comment threads, submission histories that matter for end-of-year appeals before the migration cutover. The receipt URLs are stable; the LMS isn't.
What it maps to in your world
- FERPA-adjacent intake: image bytes never leave the educator's device — only a SHA hash. There's no PII in our records that wasn't already in your inbox; the data-minimization argument simplifies FERPA-compliance reviews.
- Receipts outlast academic-year SaaS cycles. The receipt URL works after Canvas migrates to Schoology, after the district changes email vendors, after your school account is rotated.
- Verification works on personal devices and from home — useful during summer when school accounts are dormant or during appeals where you're not on duty.
- Free at any educator-relevant volume. Rate limits accommodate a typical school year's documentation load comfortably.
- Open-source verifier client. Districts that want to integrate verification into their case-management tooling can do so without licensing.
Questions this page answers
- “teacher plagiarism evidence preservation”
- “parent email screenshot evidence”
- “student misconduct screenshot proof”
- “title ix screenshot intake evidence”
- “school discipline appeal evidence”
- “academic integrity screenshot timestamp”
- “lms migration evidence retention”
- “ferpa compliant evidence preservation”
Specific answers
Is this FERPA-compliant for student-record material?
We never receive student PII. The image bytes stay on your device; we receive a one-way hash. FERPA's restrictions on disclosure of educational records concern transmission of the underlying content; a hash that cannot be reversed to the content is generally not a 'disclosure' under FERPA. For specific FERPA compliance review, consult your district's general counsel — but the architecture is materially less risky than uploading screenshots to a third-party cloud-storage tool.
Can I use this in a Title IX hearing?
Title IX hearings accept image evidence under standard documentary-evidence rules. A signed, timestamped, externally-anchored screenshot is stronger evidence than a raw screenshot — verification is one-click for the hearing officer and the cryptographic layer rebuts 'this screenshot was edited' allegations directly. Your district's Title IX coordinator will have specific procedural requirements; the receipt slots into the documentary-evidence section of the case file.
What if the student claims the social-media screenshot I provided is doctored?
The receipt's verification page shows the timestamp, hash, and signature. Anyone — including the student, their parents, and their counsel — can drop the screenshot file on /verify and confirm match. The verdict ladder distinguishes byte-identical from recompressed (platform re-encoded) from mismatch (different image). Most 'this is doctored' claims evaporate when verification is one-click.
Should I seal communications proactively or only when an issue arises?
Proactively for high-stakes channels: IEP communications, parent emails about behavioral concerns, conduct-related online content. Reactively for routine communications. The 10-second cost of a seal is small; the cost of unsealed evidence in a disputed appeal is high. Many educators batch a small sealing routine at end-of-week for any communication that touched a sensitive topic.
Can I share receipts with parents or students directly?
Yes — the receipt URL is shareable. Sharing the receipt URL with a parent during a conversation pre-empts 'I don't believe that email said that' before the formal-appeal path. Some educators find this de-escalates; others prefer to hold the receipt until the formal hearing. That's a relational call, not a technical one.
Does the district need an account or contract with you?
No. Receipts.you is free, no signup, no account, no contract. Any educator can use it from their school browser. If your district later wants a formal agreement (data-processing addendum, etc.), reach out at [email protected] — given the hash-only architecture, most DPA requirements are already satisfied by the technical posture.
Are receipts admissible if the case escalates to civil court?
Yes — cryptographic timestamp evidence is admissible under standard documentary-evidence rules (FRE 901 in the US, equivalents elsewhere). The signature + OpenTimestamps anchor simplifies authentication; the court still decides weight. For high-stakes civil escalations, your district's counsel will likely add corroborating evidence (email-server logs, LMS audit trails) — the receipt fits inside that broader evidentiary package.
Seal communications when they happen. Appeal them, calmly, with the receipt.
Free, FERPA-friendly, no district contract required. The receipt outlasts the LMS, the school year, and the staff rotation.