Student data privacy checklist for placement software

Privacy reviews often arrive late in class placement season. The roster is ready, teachers have sent notes, and everyone wants the lists before move-up day. That is exactly when a principal needs plain questions, not a thirty-page vendor questionnaire copied from another system.

Use this checklist before uploading student data to any placement tool, including Shibutz. It is practical procurement work, not legal advice. Your district, school board, data protection officer, or counsel should decide what your school may share.

Start with the procurement checklist

The best privacy question is usually small: "Do we need this field to place children fairly?" If the answer is no, do not upload it. A balanced class list can need support signals, required placements, and separation rules. It rarely needs a full case history.

Decide what student data should leave school systems

A student placement file should be boring on purpose. Names or local IDs, grade or cohort, current school or group, destination classrooms, capacity, and placement rules may be enough. Friend requests, keep-apart rules, required placements, and short support signals can be legitimate placement data when the school has approved them.

Be much slower with free-text notes. Do not export medical narratives, discipline records, family details, legal history, or counseling notes into a placement tool just because someone once used a spreadsheet as a dumping ground. If a note is needed, translate it into a placement instruction staff can defend: "separate from Student 18," "place near a trained teacher," or "avoid same class as a sibling conflict." Keep the richer record in the system where it belongs.

Shibutz supports a narrower approach. Its privacy policy says full names are not required; schools may use partial names, initials, or internal IDs when that fits local policy. The same policy also warns that other roster fields can still be personal or educational records, so changing names alone does not make the dataset anonymous.

GDPR questions for schools subject to GDPR

This section is for schools whose processing is governed by the EU GDPR or a closely related local framework. Do not treat it as a worldwide rulebook. US schools may be working under FERPA, COPPA, state student privacy laws, district policy, and contract terms instead. Ask your own counsel which rules apply before buying or configuring software.

• Data minimization: list every placement field and remove anything that is not needed for class-list decisions.
• Lawful processing: identify the controller, the lawful basis or local education authority for processing, and whether any special-category data is involved.
• Retention and deletion: record how long school copies, vendor records, exports, logs, and backups are kept. Shibutz does not currently claim configurable retention controls.
• Sharing permissions: name who may upload rosters, generate draft placements, export XLSX files, and distribute final lists.
• Auditability: keep the source roster, review notes, approved placement rules, export recipient list, and signoff date.
• Processor obligations: ask for the vendor terms that cover confidentiality, security, assistance with data-subject requests, breach notification, deletion or return of data, and audit support.
• Sub-processor visibility: ask which services may process student data and whether changes are announced before they affect your school.

Notice the tone of those questions. They do not assume the software is compliant because a page uses privacy language. They also do not assume the software is unusable because one answer is contractual. The job is to separate verified product behavior from open review items.

Source-to-claim notes for Shibutz

Here is the current public evidence a Shibutz reviewer can use today. Anything missing stays visible as an open question until the school or vendor reviewer resolves it.

For the broader data-flow summary, read the student data privacy and compliance page. For exports, the most useful operational page is Exporting to Excel, because downloaded spreadsheets often become the file that travels outside the dashboard.

Owner, evidence, action worksheet

Print this section or copy it into your procurement notes. The value is not the table itself; it is the named person beside each privacy decision. "Someone checked it" is how weak controls survive busy seasons.

How to use this with Shibutz

Start with a minimal roster. Build the placement in Shibutz only after the school has approved which fields belong there. Before generation, review the student roster, separation rules, and required placements. After Shibutz returns a draft, review the result with authorized staff before exporting or sharing it.

If your team is still shaping the manual workflow, pair this privacy review with the free class balance checklist or the class placement readiness quiz. Those resources help staff decide what belongs in the process before software makes the work faster.

New to Shibutz? Sign up free and test a small, approved placement workflow before importing your full roster.