This page is written for the parents deciding whether to enroll a child and for the agencies deciding whether to fund one. It says what we collect, who can see it, and what happens when something is wrong.
These are not statements of aspiration. Each one maps to a specific workflow in the record system the program runs on.
Mandatory reporting of suspected child abuse or neglect. Staff who work with a cohort have a documented path to raise a concern; the system timestamps it and routes it, rather than depending on someone remembering who to call.
Immunization and health requirements for children in program settings. Health information supplied at enrollment is stored as restricted data, visible to the roles that need it for a child's safety during physical activity and to no one else.
Behavioral health services for minors, including the consent conditions that apply. Where a child's needs exceed what a training program should be handling, the referral path and its consent requirements are part of the workflow rather than an informal judgment call.
Access is role-restricted, not account-restricted. Six roles exist in the system — administrator, clinician, facilitator, program manager, analyst, and intake coordinator — and each one can reach only the fields its job requires.
A facilitator running a Tuesday cohort can see what they need to keep a child safe on the floor. They cannot browse clinical history. An analyst studying whether the program works never sees a name at all.
Analytics run against a separate de-identified view, with direct identifiers cryptographically protected at the database layer. The analyst role is granted on that view and not on the source tables, so producing an outcome report does not require — or permit — access to the children behind it.
This is how a funder can receive real evidence about the program without a single child's identity leaving the system.
Facilitators are instructors, not clinicians. Licensure and mandated-reporter status are recorded per staff member in the system, and access follows from the role. When a child needs behavioral health care, the referral goes to a licensed professional — the program does not treat.
Guardian consent is captured as its own timestamped record, tied to the specific version of the consent language that was shown. If the language changes, prior consents are not silently reinterpreted — they remain attached to what was actually agreed to.
We do not sell, trade, or share enrollment data with third parties. We do not use a child's information for anything outside operating this program and reporting on it in de-identified form. We do not retain records longer than the program and applicable Ohio requirements call for.
If you want a record removed, contact us and we will tell you plainly what can be deleted, what must be retained by law, and why.