From a hard no to a policy you own
The old rule was blunt: under 18, no photo. It protected everyone, including academies that never asked for the protection and families who would happily have said yes. The new rule keeps the protection and moves the decision. Photos of minors are an academy-level setting, and it ships off. Nothing changes until you change it.
Turning it on does not allow a single photo by itself. It opens a second gate: a recorded consent from a parent or legal guardian, one per child. No consent on record, no photo, exactly as before.
You see what you are taking on. Enabling the policy shows a clear disclaimer of your responsibilities before it takes effect. It is your academy and your call, and MatPilot makes sure it is an informed one.
Three gates, in order
Every profile picture of a minor passes the same ladder. Is the academy policy on? Is a guardian's consent recorded for this child? Only then is the photo allowed. Any no, at either gate, and the member simply shows as initials, the way every member without a photo does.
Withdrawn means removed
Consent is not a one-way door. A guardian can withdraw it, and you can switch the whole policy off. Either way the pictures are removed, not hidden. Not greyed out, not archived behind a flag, gone. There is no state where a photo you no longer have permission for sits quietly in storage.
When nobody knows the age
Date of birth is optional in MatPilot, so some members have no age on file. For photos, that member is treated conservatively: possibly under 18, so the consent rules apply. The doubt resolves itself the moment an adult date of birth is added, or when the person plainly is not a child, because they run the academy or hold a staff role.
That is the whole system: your policy, the guardian's consent, and a bias towards caution whenever the facts are missing. No photo of a child ever exists in MatPilot because somebody forgot to say no.