It is important to add that this does not mean photographs of sleeping children are always wrong, or that parents never share such photographs themselves. Many parents do share photographs of their own sleeping child with grandparents or close friends, and many find those photographs tender and meaningful. The difference in this account is not the subject alone. It is the context: a teacher, not a parent; a class app, not a family chat; several children, not one; and a sharing decision made by someone other than the child's own family. The same image can feel different depending on who took it, who decided to share it, and who can see it. That context-dependence is why blanket rules — "never photograph nap time" or "always photograph nap time" — are less helpful than clear, consent-based policies that ask, for each child, what that family is comfortable with.
Chapter Eight: Many Children, Many Families — Consent Is Not One-Size-Fits-All
The photograph, according to the source, showed multiple children. That detail is not incidental. It changes the consent question entirely.
When a photograph shows one child, the consent question is relatively straightforward: what does that child's family allow? When a photograph shows several children, the question becomes: what does each family allow, and what happens when families disagree? One family may be happy for their child's photograph to be shared in the class app. Another may allow photographs for internal use — a classroom display, a learning journal — but not for sharing with other families. A third may have opted out of photographs altogether, for reasons that may be personal, cultural, religious, or related to safety, such as a family court order, a fostering arrangement, or a concern about a child's image appearing online. A teacher who posts a group photograph without checking each family's permission risks overriding the most restrictive preference in the group, even if most families are comfortable.
The source makes this point directly: consent differs per family. That is a simple sentence with large practical implications. It means a teacher cannot assume that because most parents are happy, all parents are happy. It means a photograph that is fine for one child may not be fine for another child in the same frame. It means the default, when in doubt, should be not to share a group photograph, or to share it only in a form that protects the children whose families have not consented — for example, by cropping, by framing to show hands or backs rather than faces, or by using a text update instead.
Good practice, as described in guidance from education privacy bodies and child-welfare organisations, is to collect consent in writing at enrolment and to revisit it regularly. A consent form should not be a single tick box for "photographs." It should distinguish between uses: photographs for the child's own learning record; photographs for display inside the classroom; photographs for sharing with other parents in the class; photographs for the school's public website or social media; photographs for external media or marketing. A family may consent to the first two and not to the last two. A form that lumps them together forces a family to either accept all uses or refuse all uses, which is neither fair nor informative.
Consent should also be easy to change. A family that consented in September may change its mind in January, after a change in circumstances. A family that declined may later decide to allow a specific use. Schools should make it simple to update a preference, and should ensure that the updated preference reaches the people who take photographs — not only the office that files the form, but the classroom teacher, the teaching assistant, and any supply teacher who may cover the class. A form that sits in a file and is never checked is not consent in practice. It is paperwork.
There is also a question of how consent is sought. A form sent home in a pile of enrolment paperwork, with no explanation of what "sharing" means in practice, is less meaningful than a short conversation, a clear example, and a chance to ask questions. Parents should understand, in plain language, where a photograph might appear, who might see it, how long it might be kept, and whether it can be deleted on request. They should understand that a photograph shared in a class app can be screenshotted, even if the school's policy says it should not be. A school that is honest about that limit — "we will ask parents not to forward or screenshot, but we cannot technically prevent it" — gives families a more realistic basis for consent than a school that promises control it does not have.
For the teacher in this account, the multiple-children detail is a reminder that good intentions are not a substitute for checking permissions. A warm update that includes several children is a warm update only if each of those children's families would have welcomed it. If any family would not have, the warmth is unevenly distributed. The teacher's later realisation — that she had not intended wider sharing — is part of this same lesson. Intention is about the sender. Consent is about each recipient's family, and about each child in the frame.
Chapter Nine: What the Law Actually Says — FERPA, COPPA, and Their Limits
The source account discusses two United States laws: the Family Educational Rights and Privacy Act, known as FERPA, and the Children's Online Privacy Protection Act, known as COPPA. Both are relevant to children's photographs, but neither works in the simple way it is sometimes described. This chapter explains what each law does, what it does not do, and why the distinction matters for schools and parents. It is general information, not legal advice, and it is based on guidance published by the United States Department of Education and the Federal Trade Commission.
FERPA is a federal law that protects the privacy of student education records. It applies to schools and educational agencies that receive funds from the United States Department of Education. It gives parents — and, when a student turns 18 or enters post-secondary education, the student — certain rights over education records, including the right to inspect them and, in many cases, the right to control disclosure. The source notes, correctly, that photographs can be education records in some circumstances, according to United States Department of Education guidance. That "in some circumstances" is important.
Not every photograph taken in a school is automatically a FERPA-protected education record. Whether a photograph counts as an education record depends on whether it is directly related to a student and maintained by the school or by a person acting for the school, and on how it is used and stored. A photograph taken by a teacher and kept in a child's learning file, or a photograph used to document a child's progress, is more likely to be treated as an education record than a casual photograph taken on a teacher's personal phone and deleted seconds later. A photograph that is shared in a class app, but not retained by the school, sits in a greyer area. The Department of Education's Privacy Technical Assistance Center has published guidance on photographs, video, and FERPA, and it stresses that context matters — who took the image, why, where it is kept, and who can access it.
FERPA also has exceptions and nuances that are often overlooked. For example, schools may designate certain information as "directory information" — such as a student's name, grade level, or participation in an activity — and may disclose it without prior written consent if they have given parents notice and an opportunity to opt out. Whether a photograph counts as directory information depends on the school's policy and on how the photograph is used. A school cannot simply label every photograph as directory information and share it freely. It must follow its own policy, give notice, and respect opt-outs. FERPA also does not generally prevent a parent from sharing a photograph of their own child, or a teacher from sharing a photograph with a parent of a child in the photograph for a legitimate educational purpose. It is a law about records maintained by the school, not a blanket ban on all photographs in schools.
COPPA is different. It is a federal law, enforced by the Federal Trade Commission, that protects the online privacy of children under 13. It applies to operators of websites and online services — including apps — that are directed to children under 13, or that knowingly collect personal information from children under 13. It requires such operators to give notice and obtain verifiable parental consent before collecting, using, or disclosing a child's personal information. The source notes, correctly, that under Federal Trade Commission guidance, photographs can be personal information. A photograph of a child's face, a voice recording, or a geolocation that identifies a child's location can count as personal information under COPPA, depending on context.
COPPA's limits are equally important. COPPA applies to operators of online services, not directly to every teacher or school in every situation. A school that uses a third-party app to communicate with parents is not automatically the "operator" under COPPA, and the app provider may be the operator. The Federal Trade Commission has issued guidance for schools on COPPA, noting that schools can, in some circumstances, consent on a parent's behalf to the collection of a child's personal information for the educational use of a service, but that this consent is limited to that educational use and does not authorise commercial use or wider disclosure. Schools should therefore vet the apps they use: what personal information does the app collect, who can access it, is it used for advertising or commercial purposes, how long is it retained, and can it be deleted when a child leaves the school?
Neither FERPA nor COPPA, on the facts given in the source, provides a simple answer to whether the nap-time photograph was lawful or unlawful. The source does not say the school was in breach of either law, and this article does not claim it was. What the laws do provide is a framework for thinking about the incident: schools should know what records they maintain, should obtain and respect consent, should vet the platforms they use, and should be transparent with parents about how children's images are handled. A school that follows that framework is less likely to find itself in the position described in this account, and more likely to be able to explain its actions clearly when a concern is raised.
Parents outside the United States should note that other countries have their own laws — for example, the United Kingdom's Data Protection Act and UK GDPR, the European Union's GDPR, and Australia's Privacy Act — and that those laws may treat photographs of children differently. The principles, however, are similar across jurisdictions: obtain consent, limit sharing to what is necessary, be transparent about use and retention, and respect a family's right to withdraw consent. The specific legal duties depend on where the school is located, and schools should seek advice that is specific to their jurisdiction.
Chapter Ten: "Not Independently Verified" — Why Uncertainty Must Stay in the Story
The source account, as noted at the beginning of this article, repeatedly stresses that it is not independently verified. There is no publicly available evidence confirming the teacher, the school, the identity of the children, or the exact circumstances. There is no verified evidence that the photograph caused harm. It was not, per the account, widely shared beyond the parent group.
That caution is not a footnote. It is part of the story, and it should stay in any retelling of it. In an age when a vivid anecdote can travel faster than the evidence behind it, it is easy to treat a story as fact because it feels plausible, because it resembles something that has happened elsewhere, or because it confirms a worry we already hold. The source itself resists that temptation by stating its limits plainly. This article follows the source in doing so.