Skip to main content

Privacy

Privacy Policy

What information Bell Path collects from schools, what we do with it, who we share it with, and how long we keep it.

Operator
Dimitrios James Gregory Hooke ABN 59 429 101 462 trading as Bell Path Timetabling
Effective date
19 September 2026
Contents01–13
  1. 01Who this policy covers
  2. 02The information we collect
  3. 03Student information
  4. 04How we use it
  5. 05Product analytics
  6. 06Your advertising measurement choices
  7. 07Account-free CRT and teacher access
  8. 08Who we share information with
  9. 09Where data is stored
  10. 10Security and Bell Path staff access
  11. 11How long we keep information
  12. 12Season reminders
  13. 13Access, corrections and complaints

Who this policy covers

Dimitrios James Gregory Hooke ABN 59 429 101 462 trading as Bell Path Timetabling runs Bell Path, a school timetabling and operations platform. This policy explains how we collect, use, share and protect personal information when schools, their staff and visitors to our website use Bell Path.

Bell Path is built for Australian schools. It is written to work alongside the Privacy Act 1988 (Cth), the Australian Privacy Principles, state privacy laws, school policies and any contract a school has with us.

The information we collect

  • Account details: names, email addresses, sign-in records, roles, which school a person belongs to, and billing contact details.
  • School setup: the school name, the shape of the timetable, estimated enrolment, classes, rooms, subjects, staff names and roles, staff availability, staff emails if entered, meetings, duties, constraints, and each generated timetable version.
  • Week-to-week records where a school uses those features: daily cover plans, the context of an absence, relief teacher contact details, school maps, yard duty rosters, class handovers, linked teaching resources, PDFs Bell Path prepared, print windows a person opened, paper copies a person confirmed as ready, recorded paper locations, optional return handovers, wet day plans and event timetables.
  • Student-related records where a school chooses to use those features: student names, year levels, classes, support minutes, funding context, Education Support assignments, limited verified CRT support instructions relevant to the assignment, and support notes.
  • Support requests: messages, descriptions of a problem, and any screenshots or exported diagnostic files a person chooses to send us.
  • How the product is used: which pages are opened, which steps are completed or fail, session keys, school and user IDs, and a privacy-safe hash of visitor details (a one-way code that cannot be turned back into the original). This helps us understand where schools get stuck.
  • Advertising measurement on public marketing pages and the account sign-up page: Google click and browser identifiers, and whether a page view, walkthrough request or registration happened. Bell Path does not send names, email addresses or school information to Google. These tags are never on the login or password pages, or inside the school workspace, and they never receive timetable, staff, student, support, health or free-text information.
  • Payment and invoice records: Stripe checkout and subscription status, Stripe customer and subscription identifiers, billing email, Bell Path bank-transfer invoice and payment status, billing contact details, purchase order number, invoice dates and amounts, and payment, correction, refund or reversal records. Bell Path never stores full card numbers or a school’s bank account details.
  • Technical records: request metadata including IP-related details, browser information, security logs, error reports and system diagnostics.

Student information

Bell Path does not need student names to build a timetable. Some features, such as Education Support, let a school record named students if it chooses to. Student support in a CRT brief is limited to verified, action-focused instructions relevant to that assignment. It is not a copy of the student’s medical file or whole profile.

If a school enters student-identifying, health, disability, wellbeing, funding or other sensitive information, the school is responsible for having the authority, notices and consents it needs to do so.

Please keep sensitive information out of free-text fields unless it is genuinely needed for that part of Bell Path and suitable for storing in a cloud service.

How we use it

  • To provide, secure, run and improve Bell Path.
  • To create, save, check, export and manage school timetables and the plans built on them.
  • To sign account holders in, manage school workspaces, apply roles and keep unauthorised people out.
  • To provide support, diagnose problems, contact a school about its account, and reach out to schools that look stuck.
  • To handle billing, subscriptions, agreed discounts, renewals and payment records.
  • To monitor reliability, detect misuse, investigate security issues and meet our legal obligations.
  • To measure whether Google advertising leads to genuine enquiries or registrations, and to decide where to advertise. Google measurement runs only after you allow it. Google advertising personalisation and enhanced conversions stay off.

Product analytics

Bell Path keeps internal usage records that are linked to school and user accounts. We use them to see whether schools are completing the key steps, where they get stuck, and what needs improving.

For website visitor statistics, we store a one-way hash made on our server from the request details rather than the visitor’s raw IP address.

These internal records are identifiable, and we do not pretend otherwise. If we ever publish product insights, benchmarks, case studies or marketing claims, we use information that is aggregated, de-identified (stripped of anything that points to a person or school) or shared with permission.

Your advertising measurement choices

Google advertising measurement is off until you choose Allow Google measurement. This permits Google to store advertising identifiers and receive visit and conversion information, including advertising user data needed to match a walkthrough request or registration to an ad. Bell Path does not send names, email addresses or school information to Google. Google enhanced conversions and advertising personalisation remain disabled.

Open Privacy choices to allow or stop Google measurement. Your choice is stored in this browser. Stopping measurement prevents future Bell Path conversion events. Bell Path works the same either way. Bell Path no longer uses OpenAI advertising measurement.

Measurement is never active on login or password pages, on invitation or registration links that carry a token or a prefilled school name, inside the school workspace, in the free calculators, on the School Approval Pack review form, or on the support and procurement contact forms. On the contact page, only the walkthrough-request form is measured. The confirmation page sends a Google conversion only for a successful walkthrough submission, with permission, not for an ordinary visit or refresh.

Account-free CRT and teacher access

An assigned CRT can open a non-sensitive day outline from the random booking link issued for that assignment without a Bell Path account or verification code. Class handovers, student support instructions, restricted files and School access vault values open only after one possession check: the first open of the booking text Bell Path sent to the assigned CRT’s stored mobile number within the last twelve hours, or a six-digit code sent to that number, with verified school email as a fallback.

A teacher without a Bell Path account can use an expiring contribution link limited to the date, class or session they own. It does not open the wider school workspace.

The resource shelf has its own short code and contains only lesson resources already attached to that CRT brief. Its code cannot open student support instructions or School access vault values.

Who we share information with

We share information only where we need to in order to run Bell Path, support a school, take payment, comply with the law, protect the service, or act on the school’s or the user’s instructions. The providers we rely on are:

  • Cloudlets (VPSBlocks) in Melbourne for the website you sign in to, the database holding your school information, the timetable generator, and virus scanning of uploaded files
  • Amazon Web Services in Sydney for storing the files staff upload for a CRT and for encrypted database backups
  • Railway, in Singapore, which held Bell Path until 22 September 2026 and still holds a copy of the database and of files staff uploaded, kept so the move can be reversed and deleted once it is settled
  • Cloudflare for the bellpath.com.au domain name records, which is how a browser finds Bell Path; web requests go straight to Melbourne and do not pass through Cloudflare
  • Stripe for payment processing, hosted checkout, invoices, and subscription records
  • Resend for transactional email delivery where configured
  • ClickSend for SMS delivery to casual relief teachers where a school uses CRT notifications
  • Sentry for application error monitoring where configured
  • Google for optional Google sign-in, related authentication services, and consent-based advertising conversion measurement where enabled
  • xAI for transcribing voice handovers that teachers and casual relief teachers choose to record or upload
  • TypeSafe for finding help guides, suggesting absence details and organising handover transcripts when a user asks for those features
  • OpenAI for reading staff-list photos a school chooses to upload, to extract names during setup

Where data is stored

Bell Path is an Australian business run from Victoria, and its servers are in Australia: the website you sign in to, database holding your school information, timetable generator and virus scanning of those files run in Melbourne, and the files staff upload for a CRT and database backups are stored in Sydney.

Bell Path moved its servers to Australia on 22 September 2026. A copy of the database and of files staff uploaded is still held by Railway in Singapore, kept deliberately so the move could be reversed without losing anything a school had entered. It is being deleted once the move has settled, and this page will say so when it is gone. Email, SMS, payments and the optional AI features come from separate companies, so Australian servers on their own do not make every part of the service Australian. The companies Bell Path relies on are named in this pack.

Bell Path's own servers are in Australia. A copy of school data from before the move is still held by the previous provider in Singapore and is being deleted. Other providers may process limited information in Australia or overseas in regions they use, so we do not promise that all data stays in Australia.

If a school needs a particular hosting region, a data residency commitment, or a restriction on which providers we use, that must be agreed in writing before the school relies on it.

Security and Bell Path staff access

We protect school data with technical and organisational measures. School workspace users sign in, roles decide what each person can change, and the server checks every request. Account-free CRT and teacher links are random, limited in scope, expire and can be revoked. Protected CRT information needs the separate possession check described above: first use of the booking text just sent to the stored mobile, or a six-digit code. We monitor for security problems, and access by Bell Path staff is kept to a minimum.

Platform administration is limited to authorised Bell Path staff, and their access to sensitive areas is recorded so it can be reviewed.

Bell Path does not claim any sector certification, audit result or government panel approval unless we have stated it in writing.

How long we keep information

We keep account, school, timetable, billing, support, audit and analytics records for as long as we reasonably need them to provide the service, meet legal and accounting obligations, resolve disputes, keep the service secure and improve Bell Path.

If a school asks us to delete or export its data, we will take reasonable steps to do so, within legal, security, backup and operational limits. How long backups and logs are kept depends on our hosting settings at the time.

Season reminders

If you ask us to remind you when timetabling season comes around, we store the email address you enter, the reminder time you choose, and the page you asked from. We use this only to send you that one reminder email.

Because the form does not need an account, we first send one email to confirm the address is yours. The reminder is set only when you click the confirm link. Every reminder email has a cancel link, and cancelling affects only that reminder. It does not change any account, billing or support email.

These records are deleted automatically. If a reminder is never confirmed, we delete it 7 days after you asked. Once a reminder has been sent or cancelled, we delete it 30 days later.

Access, corrections and complaints

To access, correct, export or delete personal information, or to make a complaint, email hello@bellpath.com.au. We may need to confirm who you are and that you have authority for the account or school before we act.

If we cannot resolve a privacy complaint with you directly, you can contact the Office of the Australian Information Commissioner or another relevant regulator. This policy is governed by the laws of Victoria, Australia.

Privacy Policy | Bell Path