Frequently Asked Questions

Yes.

Trackaroo uses Stripe, a PCI DSS Level 1 certified payment provider (the highest level of certification).

All card and Direct Debit details are securely collected and stored by Stripe. Trackaroo does not store or process card numbers or bank account details on its own systems. This keeps PCI scope minimal for both Trackaroo and operators.

Stripe provides the relevant PCI Attestation of Compliance documentation where required.

In addition, Trackaroo is Cyber Essentials certified, meaning our systems are independently verified to protect against common cyber threats across the wider platform — not just payments.

Trackaroo supports:

  • Debit & credit card payments
  • Apple Pay & Google Pay (where enabled)
  • Pay by Bank (secure bank-to-bank payments)
  • UK Direct Debit (Bacs) for instalment plans
  • Hybrid models (e.g. upfront card payment followed by Direct Debit)

Operators can choose the structure that best suits their commercial model. Payment processing is handled securely via Stripe, allowing flexibility without requiring multiple payment providers.

Direct Debit mandates are created and securely stored by Stripe.

Trackaroo does not store bank account numbers or sort codes. Stripe manages mandate confirmation, compliance with Bacs rules and dispute handling.

Trackaroo is hosted on UK-based cloud infrastructure with:

  • Encrypted data in transit and at rest

  • Role-based access controls

  • Multi-factor authentication for administrative access

  • Segregated company data within the platform

Security is continuously reviewed and forms a core part of the platform’s ongoing development.

Yes.

Where required, we can provide:

  • Confirmation of Stripe’s PCI DSS Level 1 certification

  • Details of our cloud hosting and security architecture

  • Data processing information for GDPR purposes

We are committed to transparent security practices and are happy to support operator due diligence processes.

No. Tracking is only one part of Trackaroo.

Trackaroo includes:

  • Digital bus passes (QR codes)

  • Ticket scanning & attendance

  • Route & student management

  • Real-time vehicle tracking

  • Parent-facing live maps (optional)

  • Operator reporting and compliance support

Trackaroo is built for operators, including:

  • School transport operators

  • Coach companies

  • Independent PSV operators

  • Multi-route school services

It is not designed for parents to manage transport — parents only see what the operator enables.

Yes. Trackaroo supports digital QR passes for students, viewable on a phone or printable if required.

Each scan can be logged against:

  • Route

  • Vehicle

  • Date

  • AM / PM run

Yes. Many operators use Trackaroo as a full replacement for:

  • Paper passes

  • Manual registers

  • Spreadsheet attendance logs

Yes. Trackaroo is designed specifically for the UK school transport market and supports:

  • UK operators

  • Term-based passes

  • AM / PM runs

  • BODS AVL compatibility (where required)

Yes — if the operator enables it.

Parents can:

  • View live vehicle location

  • See service updates

  • Access student passes

Operators remain in full control.

Trackaroo is designed to work alongside existing systems, not replace everything overnight.

Tracking sources can include:

  • Driver app

  • Third-party vehicle tracking

  • BODS / AVL feeds (where applicable)

Yes. Trackaroo works for:

  • Single-route operators

  • Multi-school operations

  • Growing fleets

Pricing scales with usage, not fleet size alone.

The easiest way is to request a demo.

We’ll:

  • Understand your operation

  • Show relevant features only

  • Help you decide if Trackaroo is a good fit

👉 Request a demo via the homepage

Yes.

Trackaroo is a dedicated UK platform focused specifically on school transport. The platform is live with multiple operators and supports thousands of students daily.

Our pricing model is transparent and designed to scale sustainably alongside operators, without hidden module charges or compulsory long-term lock-ins.

No.

Each operator’s data is fully segregated within the system. Operators only have access to their own routes, students and reporting. No data is shared between operators.