2026-08-25

Cutting out student photos for classroom displays — without handing them to an unvetted server

Teachers and room parents make an enormous amount of photo-based classroom material: birthday charts with each kid's face on a balloon, "star of the week" boards, reading-corner name tags, end-of-year slideshows, the class page of the yearbook. Almost all of it starts the same way — cut the student out of a photo so the face can sit on the decorated background. And that first step is where many teachers do something their own district's rules quietly frown on: paste a child's photo into whatever free background-removal website came up first, which usually means uploading it to a server nobody at the school has ever heard of. This post is about why that specific step deserves more caution with student photos than with your own — according to the US Department of Education, the FTC, and school districts' own policies — and what an on-device cutout changes about it.

A child's photo is not legally "just a picture"

Two US federal reference points make this concrete, and neither is folklore.

First, FERPA. The Department of Education's Student Privacy Policy Office publishes an FAQ specifically on photos and videos, and it states a two-part test: a photo of a student is an education record when it is "directly related to a student" and "maintained by an educational agency or institution or by a party acting for the agency or institution." Not every classroom snapshot qualifies — the same FAQ distinguishes photos where a student is the focus from ones where "the student's image is incidental or captured only as part of the background" — but the photos teachers cut out for displays are, by definition, the directly-related kind: one child, centered, identifiable. Once a photo is an education record, disclosing it outside the school runs into FERPA's consent-or-exception machinery, which is precisely why districts formalize which outside services are allowed to touch student data at all.

Second, COPPA. The FTC's COPPA FAQ notes that the 2013 amendment to the COPPA Rule added "a photograph, video, or audio file that contains a child's image or voice" to the definition of personal information. COPPA itself regulates online services collecting from children, so it is usually not the statute that catches a teacher's upload — but the definition is the point: US federal rules treat a photo of a child's face as personal information in its own right, the same category as a name or address, not as a mere picture.

Why districts keep approved-app lists

This legal backdrop is why "just use whatever website works" is officially discouraged. ConnectSafely's Educator's Guide to Student Data Privacy puts the practical rule plainly: if your school or district has an approved list of ed-tech products, services, and websites, check that the service you use is on it — and it reminds educators that COPPA and FERPA both apply to online sites and apps used in the classroom. In New York this is state law: Education Law 2-d has district after district publishing vetted-tool lists and data-privacy agreements for any service that handles student data. The UK's regulator says something similar from the parental side — the ICO's advice for schools recommends granular consent (parents choose which uses they agree to, not all-or-nothing) and is blunt that withheld consent must be respected.

Korea, for Korean readers, is stricter still, and the KO version of this post walks the statutes; the short version is that schools are public institutions under the Personal Information Protection Act, a separate education statute restricts providing student information to third parties without consent, and processing a child's data under 14 requires a legal guardian's consent, not the child's.

What uploading to a cutout site actually does

Run a student photo through a typical cloud background remover and a copy of that photo now exists on a third party's server, governed by that company's retention policy — a policy neither you nor your district has probably read, from a vendor that has signed nothing with your district. That doesn't automatically make it a FERPA violation; it makes it exactly the kind of disclosure the vetting process exists to evaluate, done without the vetting. The cautious default most district guidance converges on is simple: don't send student photos to services that haven't been approved to receive student data.

The difference is custody of copies. A cloud cutout adds a third-party copy of the child's photo — the disclosure app-vetting exists to evaluate. On-device processing adds none. Neither path replaces the parental consent that covers the display itself.

What on-device processing changes — and what it doesn't

NearBG's segmentation model is downloaded to the browser and runs there; the photo is never transmitted anywhere. There is no third-party copy, no vendor retention policy to read, no data-processing agreement that would need to exist, because no data leaves the device you already control. For student photos, that removes the specific leg of the trip that the rules above are about.

What it does not do matters just as much. On-device processing does not replace parental photo consent: whether a child's face can appear on a hallway display or in a yearbook at all is governed by the consent forms your school collects (the ICO's granular-consent advice is about exactly this), and a family's "no" applies regardless of which tool made the cutout. It also doesn't override your district's own rules — some districts require review of any website used with student work, even one that uploads nothing, so the approved list still gets the last word. NearBG changes the risk of the tool step; the display step keeps its own rules.

What NearBG actually does, teacher edition

One photo in, one transparent-PNG cutout out — automatic removal, then a touch-up brush with a size slider (and a reset) to erase what the model got wrong before you download.
One photo at a time. A class of 25 means 25 passes. There is no batch mode — for a full-class board, budget it like a repetitive task, not a bulk one.
No layout, no compositing, no resizing. Arranging the cutouts on the balloon chart or the slideshow happens in PowerPoint, Google Slides, Canva, or whatever your school prints from — NearBG hands those tools a PNG with real alpha transparency and stops there.
Known model limit: fine hair edges come out simplified (the full explanation is in this blog's hair post). On a bulletin board viewed from six feet away it rarely matters; for a large print, a pass with the brush helps.
It works the same on a locked-down school laptop as anywhere else — it's a web page, nothing to install, and after the first load the processing needs no network at all.

The honest summary

The rules quoted here are real and checkable: the Department of Education's own FAQ sets out when a student photo is a FERPA education record ("directly related" plus "maintained by" the school or a party acting for it), the FTC's COPPA Rule has counted a photo containing a child's image as personal information since 2013, ConnectSafely's educator guidance and Ed Law 2-d districts tell teachers to stick to approved tools, and the ICO tells schools parental consent must be granular and respected. None of that says a background remover is forbidden; it says an unvetted third-party copy of a child's photo is the thing to avoid. NearBG's contribution is narrow and honest: the cutout happens on the device, so that copy never gets made — one photo at a time, touch-up brush included, with the layout left to your slides or print tool and the consent form still taped to the filing cabinet where it belongs.