Data processing
Data Processing Summary
A procurement-friendly summary of how Bell Path handles school operational data.
- Operator
- Dimitrios James Gregory Hooke ABN 59 429 101 462 trading as Bell Path Timetabling
- Effective date
- 6 May 2026
Roles
For school workspace data, the school decides what information is entered into Bell Path and why it is used. Bell Path processes that information to provide the service, support the school, secure the platform, and meet legal obligations.
Categories of data
- School identity, workspace, billing, and account records.
- Staff names, roles, emails if entered, availability, duties, meetings, constraints, salary or costing inputs, and school operational preferences.
- Class, room, subject, timetable structure, generated timetable, validation, export, and saved-version data.
- Student-related records where a school uses relevant features, including student names, year levels, funded minutes, education support assignments, and support notes.
- Daily cover, absence planning, CRT contact, yard duty, wet day, event timetable, and operational handover records where those features are used.
- Support requests, issue context, screenshots, and debug exports if provided by a user.
- Identifiable internal analytics linked to school and user accounts for workflow support and product improvement.
Student data
Bell Path does not require student names for core timetable generation. If a school chooses to enter student-related or student-identifying information into education support, operational planning, notes, support, or other features, the school remains responsible for authority, notices, consents, minimisation, retention decisions, and compliance with its own legal and policy obligations.
- Core timetable workflows can use staff, class, room, subject, and year-level records without student names.
- Education Support includes an initials mode to reduce visible student identification on screens and printouts.
- Schools should avoid entering health, behaviour, family, or enrolment information unless the school has approved that use and the information is genuinely needed for the workflow.
School procurement and sector requirements
Schools should assess Bell Path against any applicable sector requirements, procurement rules, privacy impact assessment requirements, ST4S or equivalent security review expectations, data residency needs, and local policy obligations before relying on the service for live school data.
Bell Path is intended as specialist timetabling and operational-planning software. It is not positioned as a replacement for Department-provided administration, identity, email, finance, or learning systems.
Any special data residency, subprocessor, certification, security questionnaire, service level, or deletion commitment must be agreed in writing before the school relies on it.
Processing purposes
- Providing school timetable, yard duty, daily cover, wet day planning, export, billing, and support features.
- Maintaining account security, access controls, audit records, abuse prevention, and service reliability.
- Understanding product usage, identifying schools that need help, and improving the Bell Path workflow.
- Complying with legal, tax, accounting, dispute, and regulator obligations.
Subprocessors
Bell Path uses service providers only where reasonably needed to operate, support, secure, monitor, or bill for the service.
- Railway for application hosting, database, Redis, deployment, and infrastructure services
- Stripe for payment processing, hosted checkout, invoices, and subscription records
- Resend for transactional email delivery where configured
- Sentry for application error monitoring where configured
- Google for optional Google sign-in and related authentication services
Cross-border processing
Bell Path and its service providers may process or store data outside Australia, including the United States and Singapore. Region-specific commitments must be agreed in writing before they are relied on.
Schools with data residency concerns should review and print the Bell Path risk assessment at /risk-assessment before entering live data.
Administrative access and audit records
Bell Path restricts platform administrative access to authorised personnel. Administrative access to sensitive operational areas is logged with the actor, action, route, target school or user where applicable, and timestamp.
School-scoped audit records are also kept for selected sensitive school actions, including exports, timetable lifecycle changes, member changes, account deletion, and selected operations calendar changes.
Deletion and return
Schools can request export, deletion, or account assistance by contacting hello@bellpath.com.au. We may retain records where required for legal, accounting, security, backup, audit, or dispute reasons.