Privacy
Privacy Policy
How Bell Path collects, uses, protects, and discloses information for school timetabling and support.
- Operator
- Dimitrios James Gregory Hooke ABN 59 429 101 462 trading as Bell Path Timetabling
- Effective date
- 25 April 2026
Who this policy covers
Dimitrios James Gregory Hooke ABN 59 429 101 462 trading as Bell Path Timetabling operates Bell Path, a school timetabling and operations platform. This policy explains how we collect, use, disclose, and protect personal information when schools, staff, administrators, and visitors use Bell Path.
Bell Path is designed for Australian schools. Where the Privacy Act 1988 (Cth), the Australian Privacy Principles, state privacy obligations, school policies, or contractual terms apply, this policy is intended to work alongside those obligations.
Information we collect
- Account information, including names, email addresses, authentication records, roles, school membership, and billing contact details.
- School setup information, including school name, timetable structure, estimated enrolment, classes, rooms, subjects, staff names, staff roles, staff availability, meetings, duties, constraints, and generated timetable versions.
- Support information, including messages, issue descriptions, support context, screenshots or exported debug information if a user chooses to provide them.
- Usage and analytics information, including page paths, workflow events, success or failure states, session keys, school IDs, user IDs, and limited metadata that helps us understand product use and support needs.
- Payment and subscription information from Stripe, such as checkout status, subscription status, Stripe customer or subscription identifiers, billing email, invoices, and payment records. Bell Path does not store full card numbers.
- Technical information, including IP-related request metadata, browser information, security logs, error reports, and system diagnostics.
How we use information
- Provide, secure, operate, and improve Bell Path.
- Create, save, validate, export, and manage school timetables and related planning outputs.
- Authenticate users, manage school workspaces, enforce roles, and prevent unauthorised access.
- Provide support, diagnose problems, contact schools about their account, and help schools that appear to be stuck or struggling in the workflow.
- Process billing, subscriptions, pilot invitations, founder offers, renewals, and payment records.
- Monitor reliability, detect misuse, investigate security issues, and comply with legal obligations.
Analytics and product improvement
Bell Path stores identifiable internal analytics linked to school and user accounts. We use this to understand whether schools are completing key workflows, where they may be getting stuck, and where the product needs improvement.
We do not describe these internal analytics as de-identified on collection. If we publish product insights, benchmarks, case studies, or marketing claims, we will use aggregated, de-identified, or permissioned information as appropriate.
Disclosure and service providers
We disclose information only where needed to operate Bell Path, support customers, process payments, comply with law, protect the service, or with the relevant school or user authority.
- 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
Overseas processing and hosting
Bell Path uses cloud service providers that may process or store information outside Australia, including in the United States, Singapore, or other regions used by those providers. We do not currently promise that all data is stored only in Australia.
If a school requires a specific hosting region, data residency commitment, or subprocessor restriction, that must be agreed in writing before the school relies on it.
Security and administrative access
We use technical and organisational measures intended to protect school data, including authenticated access, role-based permissions, server-side validation, security monitoring, and limited administrative access.
Platform administrative access is restricted to authorised Bell Path personnel and is logged so that administrative access to sensitive operational areas can be reviewed.
Retention
We retain account, school, timetable, billing, support, audit, and analytics records for as long as reasonably needed to provide the service, meet legal and accounting obligations, resolve disputes, preserve security, and improve Bell Path.
If a school asks us to delete or export data, we will take reasonable steps to action that request, subject to legal, security, backup, and operational limits. Backup and log retention depends on the active infrastructure settings at the time.
Access, correction, and complaints
Requests to access, correct, export, delete, or complain about personal information can be sent to hello@bellpath.com.au. We may need to verify identity, account authority, or school authority before acting on a request.
If a privacy complaint cannot be resolved directly, you may have the right to contact the Office of the Australian Information Commissioner or another relevant regulator. This policy is governed by the laws of Victoria, Australia.

