Skip to main content
Bell Path

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
25 April 2026
Contents01–08
  1. 01Roles
  2. 02Categories of data
  3. 03Student data
  4. 04Processing purposes
  5. 05Subprocessors
  6. 06Cross-border processing
  7. 07Administrative access and audit records
  8. 08Deletion and return

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, availability, duties, meetings, constraints, and school operational preferences.
  • Class, room, subject, timetable structure, generated timetable, validation, export, and saved-version data.
  • 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 timetable generation. If a school chooses to enter student-related information, the school remains responsible for authority, notices, consents, retention decisions, and compliance with its own legal and policy obligations.

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.

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.

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.

Data Processing | Bell Path