Legal
Privacy Policy
Version 0.1.0-draft · Effective date: 13 October 2026
Draft for legal review — not legally binding and not production-ready. This document is a first draft containing unverified placeholders (shown in [BRACKETS]). It has not been reviewed by a qualified Australian lawyer, it does not establish that BusMate complies with any law, and every placeholder must be resolved against verified facts before this page is published or relied upon.
This Privacy Policy is a first draft prepared for legal review. It is not legal advice, it does not establish that BusMate complies with any law, and it must not be published or relied upon until every remaining placeholder has been completed with verified facts and the document has been approved by a qualified Australian lawyer.
This Policy describes, on a qualified basis, how Noel Benson Swarna (ABN 19 833 739 158) ("BusMate", "we", "us") may collect, hold, use and disclose personal information in connection with the BusMate school transport platform. Where BusMate is acting on the instructions of a school as a service provider rather than as the entity primarily responsible for handling personal information, the school's own privacy policy and its agreement with BusMate will govern and may take precedence over this Policy.
1. Who we are
This Policy is issued by Noel Benson Swarna (ABN 19 833 739 158) ("BusMate"), of Melbourne, Victoria, Australia.
Privacy enquiries can be directed to Noel Benson Swarna (Founder) at support@busmate.com.au.
Whether BusMate is an "APP entity" for the purposes of the Privacy Act 1988 (Cth) depends on facts including annual turnover and the nature of information handled. This Policy is drafted on a cautious, qualified basis and should not be read as a concession that the Privacy Act applies in every respect described below.
2. Scope of this Policy
This Policy applies to personal information handled through the BusMate platform, including the BusMate website, iOS application, and related administrative tools, where BusMate determines the purpose and means of handling that information.
Where a school, transport provider, or other customer determines what personal information is provided to BusMate and why, that organisation may be separately responsible for its own collection notices and privacy obligations. This Policy does not describe or stand in for any school's own privacy policy.
3. Information we collect
Depending on how BusMate is used, the following categories of information may be collected. Not every category applies to every user.
- Identity and contact information, such as name, email address, phone number, and school or organisation affiliation.
- Account and authentication information, such as login credentials and account identifiers.
- Student information, such as a student's name, enrolled school, year group, home or pickup address, and assigned route, stop or schedule, provided by a school or parent/guardian.
- Location and route information, such as bus GPS location, stop times, and route status, used to provide live transport updates.
- Device and technical information, such as device identifiers, IP address, app version, and diagnostic logs.
- Communications, such as messages sent through or to BusMate support channels.
BusMate does not intentionally collect health, medical, or disability-related information, nor does it use personal information for analytics or marketing purposes. BusMate accounts are created and operated by adults (school staff, transport providers, and parents/guardians) subject to the minimum age requirements described in section 6; the service does not permit direct account creation by children.
4. How we collect information
- Directly from schools, administrators, and transport providers who set up and manage accounts, routes, and student records.
- Directly from parents, guardians, and authorised users, where they create or interact with an account.
- Automatically, through use of the website or app (for example, device information and usage logs).
- No third-party student information system (SIS) integrations are currently active. If integrations are added in future, this Policy will be updated to describe them.
5. Why we collect, use and disclose information
Information is collected, used, and disclosed to provide the BusMate service, including:
- operating and maintaining route, stop, and schedule information;
- providing live transport status updates to schools, parents, guardians and students;
- verifying identity and managing accounts;
- providing customer support and responding to enquiries;
- maintaining the security and integrity of the service, including audit logging;
- meeting legal, regulatory and contractual obligations, including obligations under a school's service agreement.
BusMate does not currently use personal information for analytics or marketing purposes. BusMate does not use personal information for any purpose unrelated to those described above without a lawful basis for doing so, such as consent or another applicable exception under the Australian Privacy Principles.
6. Children and student users
BusMate applies minimum age requirements to each account type:
- Administrator accounts require a minimum age of 21 years. Administrator accounts are created by BusMate on behalf of the school, not by self-registration.
- Driver accounts require a minimum age of 21 years. Date of birth is collected and validated at account creation via the BusMate administrator interface.
- Parent and guardian accounts require a minimum age of 18 years. Date of birth is collected and validated at account creation via the BusMate administrator interface.
- Student records have no minimum age requirement. Student records are created and managed by school administrators or authorised parents and guardians; students do not hold direct BusMate accounts.
Where student information is provided to BusMate, it is provided by the relevant school or by a parent/guardian on the student's behalf, on the basis that the school or parent/guardian has the authority and any consent needed to provide that information.
7. Role of schools and parents/guardians
Schools that use BusMate are generally responsible for: providing any notices required to parents, guardians and students about the use of BusMate; obtaining any consents required under their own policies or applicable law; and ensuring the accuracy of information they provide to BusMate.
Parents and guardians who create or use a BusMate account are responsible for the accuracy of information they provide and for supervising their own account access.
BusMate's role in relation to student information is, in general, that of a service provider acting on the instructions of the relevant school, subject to the terms of the applicable Subscription Agreement. This Policy does not override the terms of that agreement.
8. Who we disclose information to
Information may be disclosed to:
- the relevant school, transport provider, or organisation that set up the account or student record, so it can manage its own transport operations;
- parents and guardians linked to a student's account, so they can receive relevant updates;
- service providers that help BusMate operate the platform (for example, hosting, data storage, and email delivery providers) — see the Overseas disclosures section below;
- a professional adviser, regulator, or law enforcement body, where required or authorised by law;
- a successor entity in connection with a genuine business transaction, such as a sale of the business, subject to confidentiality obligations.
BusMate does not sell personal information to third parties.
9. Security
BusMate takes the following steps to protect personal information from misuse, interference, loss, and unauthorised access, use, or disclosure, consistent with APP 11.1:
- All data in transit between users and BusMate's services is encrypted using TLS (HTTPS). Data at rest in Firebase Firestore and Firebase Storage is encrypted by Google by default.
- Access to the BusMate administrative backend (Firebase console and Supabase dashboard) is restricted to authorised personnel and protected by account-level authentication controls.
- Firebase security rules are used to enforce role-based access to Firestore data, so that each user class (administrator, driver, parent) can access only the data relevant to their role.
- Audit logging is maintained for key administrative and driver actions within the BusMate application.
- Authentication uses passwordless magic links and user-set passwords. Multi-factor authentication (MFA) is enforced via Firebase Authentication for all user accounts.
No method of storage or transmission is completely secure, and this Policy does not represent or guarantee that BusMate's systems are free from risk.
10. Retention, deletion and de-identification
Under APP 11.2, where BusMate holds personal information that is no longer needed for any purpose for which it may be used or disclosed under the Australian Privacy Principles, and BusMate is not required by law or a court/tribunal order to retain it, BusMate must take reasonable steps to destroy the information or ensure it is de-identified. This is an obligation to take reasonable steps in the circumstances, not an unconditional or immediate right to deletion, and it is subject to legal, regulatory, and record-keeping exceptions, including those that may apply to school and student records.
BusMate retains personal information for the following periods, subject to any longer retention period required by law or by a school's record-keeping obligations: active account data is retained while the account is active and for 12 months after closure; attendance and route records are retained for 7 years after the end of the school year to which they relate; support communications are retained for 3 years; technical and log data is retained for 90 days. After these periods, BusMate will take reasonable steps to destroy or de-identify the information in accordance with APP 11.2.
To request deletion of personal information, contact support@busmate.com.au. Users of the BusMate iOS application may also use the in-app account deletion feature. BusMate will take reasonable steps to verify your identity and authority before acting on a request. Deletion may be refused or delayed where retention is required by law, by a school's record-keeping obligations, or under a current service agreement.
Where a school has its own record-retention requirements, BusMate will have regard to those requirements and, where relevant, to any authorisation required from the school before deleting student-related records.
11. Access and correction
Individuals may request access to, or correction of, their personal information by contacting support@busmate.com.au. Requests relating to student information may need to be directed to, or confirmed with, the relevant school, where the school holds the primary relationship with the student and parent/guardian.
BusMate will respond to access and correction requests within a reasonable period and may charge a reasonable fee for giving access, in each case consistent with APP 12 and APP 13 and subject to applicable exceptions.
12. Complaints
Complaints about how BusMate handles personal information can be made to support@busmate.com.au or notices@busmate.com.au. BusMate will acknowledge and seek to resolve complaints within a reasonable time.
If a complaint is not resolved to the individual's satisfaction, they may be able to raise it with the Office of the Australian Information Commissioner (OAIC).
13. Eligible data breaches
Where the Notifiable Data Breaches scheme under Part IIIC of the Privacy Act 1988 (Cth) applies to BusMate, BusMate will assess suspected data breaches and, where an eligible data breach is identified, notify affected individuals and the OAIC in accordance with that scheme.
BusMate will also have regard to any separate notification obligations owed to a school under the applicable Subscription Agreement.
14. Overseas disclosures and processing
BusMate uses third-party service providers to operate the platform. Some of these providers process or store information outside Australia. This section is drafted on a fact-specific, qualified basis: not every interaction with an overseas provider is necessarily a 'disclosure' for the purposes of APP 8 (as opposed to a 'use' by BusMate through a service provider acting on its behalf). The characterisation depends on the contractual and operational arrangements with each provider.
Where APP 8 applies, BusMate will take reasonable steps to ensure that an overseas recipient does not breach the Australian Privacy Principles in relation to the information, or will rely on an applicable exception under APP 8.2 or section 16C, as confirmed by legal review.
The following service providers are used. Processing regions are based on current project configuration and default provider settings; each must be verified against the relevant provider dashboard before publication.
Firebase / Google (mobile app backend)
- Contracting entity
- Google LLC (1600 Amphitheatre Parkway, Mountain View, CA 94043, USA)
- Service used
- Firebase Authentication (user login), Cloud Firestore (database — named instance 'busmate-db'), Firebase Storage (file storage). Firebase Cloud Messaging (push notifications).
- Data categories
- Account credentials, student records, route and schedule data, attendance logs, driver and administrator identifiers, push notification tokens.
- Purpose
- Authentication, real-time data storage, file storage, and push notifications for the BusMate iOS application.
- Configured processing/storage region
- Firebase project 'busmate-de66c' is configured to use australia-southeast2 (Melbourne, Victoria, Australia). Data is stored and processed in Australia.
- Likely overseas recipient countries
- Australia (primary). Google subprocessors may operate in other countries — see Google Cloud subprocessor list at cloud.google.com/terms/subprocessors.
- Subprocessors
- Google publishes its Cloud subprocessor list at cloud.google.com/terms/subprocessors. CONFIRM: review the current list before publication.
- Contractual and technical safeguards
- Google Cloud / Firebase Data Processing and Security Terms (incorporated into the Google Cloud Terms of Service). Data encrypted in transit (TLS) and at rest (AES-256) by Google by default. CONFIRM: review the current Google Cloud DPA before publication.
Supabase (website backend)
- Contracting entity
- Supabase Inc. (970 Toa Payoh North #07-04, Singapore 318992). CONFIRM: verify current registered address in Supabase's Terms of Service before publication.
- Service used
- PostgreSQL database (storing demo request submissions from the BusMate website contact/demo form).
- Data categories
- School name, contact name, email address, student count, and message content submitted via the BusMate website demo request form.
- Purpose
- Storage of demo and enquiry data submitted via the BusMate website.
- Configured processing/storage region
- Primary: ap-southeast-2 (Sydney, New South Wales, Australia). Backup/replica: ap-northeast-1 (Tokyo, Japan). Primary data is stored in Australia; backup data is replicated to Japan.
- Likely overseas recipient countries
- Australia (primary storage). Japan (backup replica). Supabase subprocessors may operate in other countries — see Supabase's subprocessor list in its privacy documentation.
- Subprocessors
- Supabase publishes its subprocessor list in its privacy documentation. CONFIRM: review the current list before publication.
- Contractual and technical safeguards
- Supabase Data Processing Agreement (DPA) available at supabase.com/privacy. Data encrypted in transit (TLS) and at rest. CONFIRM: review the current Supabase DPA before publication.
Resend (email delivery)
- Contracting entity
- Resend Inc. CONFIRM: verify current legal entity name and registered address in Resend's Terms of Service before publication.
- Service used
- Transactional email delivery (demo request notifications sent to BusMate).
- Data categories
- Email addresses, contact names, school names, and message content included in demo request notification emails.
- Purpose
- Delivery of internal notification emails when a demo request is submitted via the BusMate website.
- Configured processing/storage region
- ap-northeast-1 (Tokyo, Japan). Confirmed by Noel, 13 October 2026.
- Likely overseas recipient countries
- Japan (ap-northeast-1 processing region) and Resend subprocessor locations.
- Subprocessors
- CONFIRM: review Resend's current subprocessor or infrastructure list (available in Resend's privacy or legal documentation) before publication.
- Contractual and technical safeguards
- CONFIRM: review Resend's current Data Processing Agreement (if available) before publication. Data transmitted via TLS.
Vercel (website hosting)
- Contracting entity
- Vercel Inc. (340 Pine Street, Suite 700, San Francisco, CA 94104, USA). CONFIRM: verify current registered address in Vercel's Terms of Service before publication.
- Service used
- Hosting and delivery of the BusMate website and server-side rendering.
- Data categories
- Technical and log data (IP address, request headers, page URLs) generated by users visiting the BusMate website. No personal data is stored by Vercel beyond standard request logs.
- Purpose
- Hosting, content delivery, and server-side rendering of the BusMate marketing and legal website.
- Configured processing/storage region
- ap-southeast-2 / syd1 (Sydney, New South Wales, Australia). Confirmed by Noel, 13 October 2026. Vercel's Edge Network may serve cached content from nodes in multiple countries globally.
- Likely overseas recipient countries
- Australia (primary serverless region). Vercel Edge Network nodes operate globally — cached content may be served from overseas nodes.
- Subprocessors
- CONFIRM: review Vercel's current subprocessor list (available at vercel.com/legal/privacy-policy) before publication.
- Contractual and technical safeguards
- Vercel Data Processing Addendum (available at vercel.com/legal/dpa). Data transmitted via TLS. CONFIRM: review the current Vercel DPA before publication.
15. Changes to this Policy
BusMate may update this Policy from time to time. The version number and effective date at the top of this page indicate the current version. Material changes will be notified in accordance with the applicable Subscription Agreement, or by posting an updated version on this page.
Version 0.1.0-draft · Effective date: 13 October 2026


