School Approval Pack

This pack is written for principals, assistant principals, business managers, ICT leads, and privacy reviewers who need a practical summary before a school enters live operational data into Bell Path.

Schools can print this page and keep it with internal procurement, privacy impact assessment, security, School Council, or leadership approval records. It supports review; it does not replace a school, sector, ST4S, Department, or legal assessment.

Schools may need to check Arc Software and Safer Technologies 4 Schools assessment material before adopting software that is not provided by their sector or Department. Bell Path should be treated as requiring the school’s normal software approval checks unless a current written Bell Path statement says otherwise.

Bell Path is being documented in a way that supports ST4S-style review: clear data categories, subprocessors, access controls, public-sharing limits, support pathways, and data minimisation guidance. This is readiness material, not a claim that an ST4S assessment has been completed.

Bell Path is operated from Australia but uses cloud service providers. The current repository and deployment posture should be treated as involving offshore processing unless Bell Path has separately agreed and verified an Australian-only residency arrangement in writing.

Schools that require Australian-only data residency should ask for written confirmation covering the application runtime, database, Redis or queue services, export storage, email, monitoring, payment records, backups, and support tooling before entering live data.

Bell Path public calendar links are intended for non-sensitive parent and student visibility. They should only publish items the school has chosen to make visible.

A school code reduces casual access but is not a substitute for authenticated staff access. Staff-only notes, drafts, internal admin notes, reminders, unpublished items, and non-public checklist items are redacted before public exposure.

Schools can request export, deletion, account, or procurement assistance by contacting hello@bellpath.com.au. Bell Path may retain records where required for legal, accounting, security, backup, audit, dispute, or abuse-prevention reasons.

Schools should keep their own copies of published timetable, export, and approval records according to their normal recordkeeping rules.

Bell Path uses service providers where reasonably needed to host, secure, monitor, support, and bill for the product.

Bell Path includes an in-app support form that captures the page, request type, impact level, and recent workflow context so urgent timetable, export, cover, or setup issues can be triaged more quickly.

Schools should still keep local fallbacks for critical operational records, including downloaded timetable PDFs and any information needed to run the school day if an online service is unavailable.