COPPA and a Child’s Image: Why Photos and Video Count as Personal Information

A security camera in a school hallway, a youth center lobby, a camp check-in area, or an EdTech event booth may feel like ordinary operational equipment. But when the footage includes children under 13 and is collected through an online service or later uploaded, shared, or published through a covered online workflow, the privacy question becomes more serious. Under the Children’s Online Privacy Protection Act, known as COPPA, a child’s image in a photo or video can qualify as personal information.

For organizations subject to COPPA that record, store, review, or publish children’s visual material, this is not just a legal definition. It affects camera design, field of view, retention schedules, access controls, and the decision to blur faces before footage leaves a controlled environment. The practical goal is data minimization: collect only the visual information needed for a defined purpose, keep it only as long as necessary, and reduce unnecessary identification of children wherever possible.

Why COPPA Treats a Child’s Image as Personal Information?

COPPA applies to covered operators of websites and online services directed to children under 13, and to general-audience online services that have actual knowledge they are collecting personal information from children under 13. The Federal Trade Commission’s COPPA Rule includes within “personal information” a photo, video, or audio file that contains a child’s image or voice.

That language matters for any organization using web portals, cloud-based upload tools, online galleries, app-based media submission, connected camera systems, or digital publishing workflows involving children. A child does not have to be named in the file for the image to raise a COPPA issue. A visible face can identify a child directly, and surrounding details may reveal more: a school logo, classroom setting, team jersey, pickup lane, playground, time of day, or group activity.

The final COPPA Rule amendments announced in 2025 also added biometric identifiers to the definition of personal information in certain contexts, including data derived from facial data when used for automated or semi-automated recognition of a specific person. This does not mean every routine image file is treated the same way in every situation. It does, however, reinforce the operational lesson: photos and videos of children should be handled as sensitive media assets, especially when technology systems process, store, or distribute them.

Where CCTV Footage Fits Into the COPPA Conversation?

Traditional closed-circuit video used only for on-site security may not always involve an online collection by a covered operator. However, many modern camera environments are no longer purely local. Footage may be viewed through a web dashboard, stored in a hosted video management system, exported to a vendor support portal, attached to an incident ticket, shared with a contractor, or reused in training or communications.

Those steps can change the risk profile. A school vendor, youth program platform, children’s entertainment venue, tutoring center, camp operator, or EdTech provider may use camera footage for operational safety, product demonstrations, facility monitoring, parent communication, or marketing. If children’s images enter an online service covered by COPPA, the footage should be reviewed through a privacy lens before it is retained, shared, or published.

Even where COPPA is not the only applicable consideration, its definition gives compliance, security, and communications teams a clear baseline: if a child is visible in a recorded image or video file, treat that file as potentially privacy-sensitive and design the workflow accordingly.

Data Minimization Starts Before the Camera Is Installed

Many organizations think about privacy only after footage has been captured. That is too late for true data minimization. The best time to reduce over-collection is during CCTV design, before camera placement, lens selection, resolution, retention, and user access are finalized.

For child-facing environments, the core design question should be simple: what security or operational purpose does this camera serve, and what is the least intrusive way to meet that purpose?

Camera Placement: Record the Security Need, Not the Whole Environment

Camera location determines how much child imagery is collected. A camera intended to monitor a building entrance may not need to capture close-up views of every child waiting nearby. A camera used for hallway safety may not need to see inside classrooms. A camera used to protect equipment may not need to cover a playground or seating area.

Practical placement decisions should include:

• Avoiding camera angles that capture areas unrelated to the stated safety purpose.
• Positioning cameras toward doors, gates, exits, or equipment rather than faces whenever possible.
• Keeping cameras out of locations where children have a higher expectation of privacy.
• Checking whether a camera captures neighboring homes, sidewalks, driveways, or parked vehicles unnecessarily.
• Using physical layout, signage, barriers, and lighting improvements to reduce the need for broad video coverage.

For example, a youth facility that wants to document access to a locked storage room may be able to aim a camera at the door and handle, not across an entire activity space. A school lobby camera may need to capture entry and exit movement, but not a detailed view of every child sitting in a waiting area.

Field of View: Narrow the Frame to Reduce Identifiable Detail

Field of view is one of the most important privacy controls in CCTV design. Wide-angle coverage can feel efficient, but it often captures more children, more background context, and more family information than necessary.

A minimized field of view should be matched to the purpose of the camera. If the purpose is perimeter monitoring, the camera should not capture student seating areas. If the purpose is verifying that a door is secured, the frame should not include an entire hallway of children. If the purpose is monitoring vehicle flow in a pickup area, the design should consider whether license plates, drivers, and children’s faces are being collected beyond what is needed.

Resolution and zoom settings also matter. Higher resolution may be justified for some safety purposes, but it can also make children more identifiable. Security teams should avoid defaulting to maximum detail in every location. The right standard is “adequate for the documented purpose,” not “as much as the camera can capture.”

Audio: Do Not Record Voices Unless There Is a Clear Need

Although this article focuses on images and video, many CCTV systems can record audio. COPPA’s definition also covers audio files containing a child’s voice. In child-facing settings, audio collection can significantly increase privacy exposure because conversations may reveal names, health information, family details, disciplinary issues, or other sensitive context.

If audio is not required for the specific purpose, disabling it is often a strong minimization step. If audio is enabled, organizations should document why it is necessary, who can access it, how long it is retained, and how it is protected.

Retention: Keeping Footage Longer Can Increase COPPA Exposure

Data minimization is not only about what the camera captures. It is also about how long footage remains available. A system that stores routine child-facing footage for months creates more exposure than one that deletes ordinary footage after a short, documented period unless an incident requires preservation.

Retention policies should be practical and specific. Security teams should define different categories, such as routine footage, incident footage, footage under investigation, exported clips, and media prepared for publication. Each category should have a purpose, an owner, an access rule, and a deletion point.

Common retention controls include:

• Setting a short default retention period for routine CCTV footage.
• Requiring approval before exporting clips that contain children.
• Separating original security footage from redacted or blurred copies used for wider review.
• Deleting test exports, duplicate files, and temporary working copies.
• Reviewing old footage libraries before changing vendors or migrating storage systems.

Under the COPPA Rule, covered operators must not retain children’s personal information for longer than reasonably necessary to fulfill the purpose for which it was collected. For visual media teams, that principle translates into a concrete operational rule: do not let child imagery accumulate simply because storage is inexpensive.

Reducing Over-Collection in Real-World CCTV Workflows

Over-collection often happens gradually. A camera installed for access control starts capturing children in a waiting area. A security clip is exported for an internal report, then forwarded by email. A video from a youth event is reused in a promotional reel. A vendor requests sample footage for troubleshooting, and the original file includes children’s faces and vehicle plates.

To reduce this risk, organizations should build privacy checkpoints into the video lifecycle:

1. Before installation, document the purpose of each camera and verify that the placement and field of view match that purpose.
2. Before collection begins, confirm whether the camera system connects to an online service and whether children under 13 are likely to appear.
3. Before exporting footage, ask whether the recipient needs the original file or a minimized version.
4. Before sharing a clip outside the security team, blur faces and license plates when identification is not required.
5. Before publishing any image or video, conduct a manual review for children’s faces, uniforms, name tags, screens, signs, and other identifying context.
6. Before reusing footage for marketing, training, or public communication, reassess consent, purpose, audience, and retention.

This approach helps teams answer a practical long-tail compliance question: how can a school, camp, youth program, or child-facing business reduce COPPA exposure in CCTV footage before storing, sharing, or publishing it? The answer is not one control. It is a combination of narrower collection, shorter retention, controlled access, and visual redaction before broader use.

Face and License Plate Blurring as a Publication Safeguard

Blurring does not make every COPPA obligation disappear. It should not be treated as a substitute for notice, consent analysis, security controls, or retention limits. But it can reduce the amount of identifiable visual information in a file before the file is shared beyond the people who truly need to see the original.

For children’s footage, face blurring is often the most important step because the face is usually the most direct identifier. License plate blurring can also matter in school parking lots, bus lanes, neighborhood streets, parent pickup areas, and youth event venues. A plate may connect a child to a family vehicle, home area, or daily routine.

In recorded photo and video workflows, Gallio PRO (https://gallio.pro/) can support this kind of minimization by automatically blurring faces and license plates. Its automation should be described accurately: it automatically blurs only faces and license plates. It does not automatically detect every type of personal data or every sensitive object in the frame. Items such as name tags, documents, logos, tattoos, screens, posters, and other contextual identifiers still require human review and, when necessary, manual blurring.

According to Gallio PRO, the system does not store logs containing detection data or personal data. For organizations trying to avoid creating unnecessary secondary records during redaction, that design choice can be useful. As with any compliance process involving children’s media, the tool should sit inside a broader review procedure rather than replace it.

What to Review Before Publishing CCTV Images or Video of Children?

Public release is where practical control drops sharply. Once a child’s image appears on a website, social channel, public report, donor campaign, or video platform, it can be copied, indexed, downloaded, or redistributed outside the original context. This is why publication copies should be treated differently from operational security footage.

Before publishing child-facing CCTV footage or still frames, teams should ask:

• Is the organization or vendor operating a child-directed online service, or does it have actual knowledge that it collects information from children under 13?
• Was the footage collected for security, parent communication, training, marketing, or another purpose?
• Does the public audience need to see identifiable children to understand the message?
• Can the same goal be met with a blurred version, a cropped image, a staged photo, or non-identifying B-roll?
• Are there visible school names, jerseys, badges, screens, signs, or vehicle plates?
• How long will the published version remain online, and who owns removal when it is no longer needed?

A good rule for communications teams is to separate “security evidence” from “publication material.” The original may need to be preserved for a documented incident. The public-facing version should be minimized, reviewed, and approved separately.

Building a Practical COPPA-Aware CCTV Policy

A workable policy does not need to be overly complex. It should be clear enough for facilities staff, security teams, IT administrators, marketing teams, and outside vendors to follow consistently.

At minimum, a COPPA-aware CCTV policy for child-facing environments should address:

• Camera purpose: why each camera exists and what area it is allowed to capture.
• Placement and field of view: how the organization avoids recording unrelated children, families, neighboring property, and excessive background detail.
• Audio settings: whether audio is disabled by default and who can approve exceptions.
• Access: which roles can view live feeds, recorded footage, exported clips, and publication copies.
• Retention: how long routine footage, incident footage, exports, and blurred copies are kept.
• Export controls: when clips may be downloaded, transferred, or sent to vendors.
• Redaction workflow: when faces and license plates should be blurred before broader sharing.
• Publication approval: who confirms consent status, purpose, audience, and deletion plans before public release.

The strongest policies connect legal requirements to everyday decisions. A facilities team can understand camera angles. A security team can understand retention. A marketing team can understand the difference between an original file and a blurred publication copy. A vendor manager can understand why original footage containing children should not be sent to third parties without review.

FAQ: COPPA and Children’s CCTV Images

Does COPPA cover a child’s face in CCTV footage?

COPPA’s definition of personal information includes a photo, video, or audio file containing a child’s image or voice. Whether COPPA applies to a specific CCTV workflow depends on the operator, the online service involved, the age of the children, and the method of collection or use. If children under 13 are visible and footage is handled through a covered online workflow, organizations should treat the footage as potentially COPPA-relevant.

Is blurring required before sharing footage?

COPPA does not create a simple universal rule that every image must be blurred in every case. However, face blurring is a practical minimization measure when children are incidental, consent status is unclear, or footage will be shared outside a limited security purpose. License plate blurring can also reduce family and location exposure.

Can camera placement reduce compliance risk?

Yes. Privacy-conscious camera placement can reduce the amount of children’s personal information collected in the first place. Narrower angles, limited zoom, careful positioning, disabled audio, and avoidance of unrelated areas can all reduce over-collection before retention or redaction becomes necessary.

How long should CCTV footage with children be retained?

The retention period should match the purpose for which the footage was collected. Routine footage should not be kept indefinitely by default. Organizations should define separate retention rules for ordinary footage, incident footage, exported files, and publication copies, and delete material when it is no longer needed.

Can automated blurring find all privacy risks in a video?

No. Automated tools should not be described as detecting every type of personal information. In Gallio PRO, automatic blurring is limited to faces and license plates. Other visible identifiers, such as name tags, screens, signs, uniforms, documents, logos, and tattoos, require human review and manual handling where appropriate.

Bottom Line for U.S. Organizations Recording Children

A child’s image in a photo or video can be personal information under COPPA when it is collected by a covered operator through a website or online service, or otherwise handled in a covered online context. For CCTV programs in child-facing environments, the best compliance posture begins with minimization: place cameras carefully, narrow the field of view, avoid unnecessary audio, limit retention, control exports, and blur faces or license plates before footage is broadly shared or published.

The most defensible workflow is not “record everything and decide later.” It is “collect only what is needed, keep it for a defined purpose, and reduce identifiability before wider use.” For schools, camps, youth organizations, EdTech vendors, and child-facing businesses working with covered online services, that approach turns COPPA awareness into practical day-to-day controls.