For charter operators and network operations
Public money brings a second audience nobody else in education has to answer to
A district school answers to a district. An independent school answers to a board. You answer to an authoriser who can decline to renew you, and — because the money is public — to members of the public who can ask you for records. Your imagery sits inside both of those.
What public funding does not change
The age rules. A student under thirteen is held off the open web before any permission is consulted, on a charter campus exactly as in a district school or a fee-paying one. Public funding does not lift the floor and it does not lower it.
That matters more here than it does in a district school, and the reason is enrolment. A district school has a catchment. You have to recruit, which makes imagery an operational need rather than a nice-to-have, and puts a K-8 charter in exactly the position an independent lower school is in: a marketing obligation and a student body you cannot photograph for it.
What a serious enrolment collection is actually made of is your campuses in use, student work without names on it, staff who agreed for themselves, and students over the age floor with their family’s specific permission. That is a real collection and it is worth building deliberately rather than discovering the constraint in the week the open evening is announced.
What public funding does change
Two things, and neither has an equivalent on any other host in this family.
An authoriser
Somebody renews your charter, on a schedule you do not set, and can decline.
A district school has a superintendent. A private school has a board that it appoints. Neither of those is an external party with the power to end the school, and the difference in how carefully you document things follows directly from that.
For imagery the useful observation is that almost nothing an authoriser needs is a photograph of a child. It is counts, states and documentation, plus — where imagery genuinely helps — the place and the work rather than the students.
Public-records expectations
A member of the public can ask you for records. A private school never faces this.
Whether a photograph of a student is reachable by such a request, and how a student’s own education record interacts with it, is genuinely unsettled and varies by state and by material. We are not going to answer it for you and you should be wary of a vendor who does.
The operational point is separate and it is ours to make: holding imagery as records with permissions attached means you can state precisely what exists and what governs it. Producing a folder under a statutory clock is a much worse position than answering precisely, and the difference is decided long before the request arrives.
Several campuses, one office
Structurally you are closer to a small district than to a single school.
Most charters of any size run more than one campus through one back office, with some staff scoped to a campus and some not. That makes the cross-campus wall a daily operational question rather than a theoretical one, and it is enforced in the storage layer rather than in a screen — a request from outside a campus’s own area returns no student rows because the storage refuses it.
The design question worth asking yourself is narrower and more useful: does your network-level staff actually need image access to do the job? Usually the answer is counts and states, and the least risky access is the access nobody needed.
Your own family agreement
You write it, which puts you closer to an independent school than to the district.
A charter does not inherit a district release form. It writes its own family-facing agreement, usually once at network level, and applies it across every campus. One clear document beats four inherited ones and you can revise it without waiting on anybody.
The limit is the same as everywhere: whatever it says, it does not lift the age floor. Under-thirteen students stay held whichever document you wrote.
Where the six collections stand
Counted from this site’s own list rather than typed. Two of the six are worth noticing before anything else: one is closed by the age floor, and one is explicitly marked as your call rather than ours, because it is a legal question and we do not answer those.
Each of the six is written out on across campuses, with what it reaches and where it stops.
What is switched off
Nothing here can be bought. Live payment is not turned on, so there is no checkout, no price and no order form. The platform is free to the school, so there is no purchase to route through a network budget either.
No AI decides who appears. Face matching is off unless a parent switches it on for their own child, and it is never bundled into a publication permission.
We do not write your authoriser report. We hold imagery and what governs it; assembling a report is your team’s job, and what we can do is make sure what they can include is already only what may be included.
We will not answer a public-records question for you. That varies by state and by material, and it belongs to your counsel. Any vendor giving you that answer in a brochure has told you something about the vendor.
What an operator asks first
We are publicly funded. Does that change the rules on student photographs?
Not the age rules. A student under thirteen is held off the open web before any permission is consulted, on a charter campus exactly as in a district school or an independent one. What public funding changes is what else you are exposed to: public-records expectations, and an authoriser with a reporting schedule and the power not to renew you.
Is a photograph of a student a public record?
That is genuinely unsettled, it varies by state and by material, and we are not going to answer it for you -- be wary of any vendor who does. What we can say is the operational point: imagery held as a student record with a permission attached puts you in a much better position to answer such a request precisely, because you can state what you hold and what governs it rather than searching folders against a deadline.
We run four campuses on one back office. How is that handled?
Campus-scoped roles, with the separation held in the storage layer rather than in a screen -- a request from outside a campus's own area returns no student rows because the storage refuses it, and that is re-checked every build. The more useful design question is whether your network-level staff need image access at all to do their jobs. Usually they need counts and states, and the least risky access is the access nobody needed.
We have to recruit. Can we use student photographs to do it?
Where those students are under thirteen, no, and no agreement reaches it. This lands harder on a charter than on a district school because you actually have to fill seats. What a serious enrolment collection is made of is your campuses in use, student work without names, staff with their own agreement, and students over the age floor with their family's specific permission.
How is this different from your private school site?
Both cut across the grade ladder on governance rather than age, and there the similarity stops. A private school answers to a board and tuition-paying families. You answer to an authoriser and, through public funding, to the public. That produces two obligations this site is about and that one does not have: reporting up on a schedule, and records requests from people who are not part of your community.