Resilience — Trust Centre — Compass IoT
Overview

Trust Centre

Resilience

How we keep Compass systems available, recover from disruption, manage change safely, and operate sustainably — across our cloud architecture, operational practices, and governance commitments.

Last updated May 2026 · Compass IoT Pty Ltd

Section 01

Cloud infrastructure and architecture

The design principles, platforms, and controls underpinning the Compass IoT platform's availability and security at the infrastructure level.

Vulnerability Management Policy
Defines our process for conducting vulnerability scans, penetration tests, and remediating findings on a risk-based schedule.
View policy →
Change Management Policy
How we request, test, peer-review, and approve changes to production systems — ensuring controlled, auditable deployments.
View policy →

Section 02

Reliability, availability, and recovery

Our commitments and plans for keeping Compass platforms available, recovering quickly from disruption, and responding effectively to security incidents.

Business Continuity & Disaster Recovery Plan
How we ensure systems remain operational or recover quickly following an outage, data loss event, or major disruption.
View plan →
Incident Response Plan
Procedures for detecting, reporting, containing, and recovering from security incidents — including customer notification obligations.
View plan →

Section 03

Governance and sustainability

Our approach to ethical procurement, workplace health and safety, environmental responsibility, data stewardship, and third-party oversight. These policies reflect our obligations as a responsible operator across the jurisdictions we serve.

Sustainable Procurement Policy
How we evaluate and select suppliers with consideration for environmental impact, social responsibility, and ethical practices.
View policy →
WHS Policy
Our workplace health and safety commitments — ensuring a safe working environment for all employees and contractors.
View policy →
Environmental Policy (Net Zero)
Our commitment to minimising our environmental footprint and working toward net zero emissions across our operations and supply chain.
View policy →
Data Classification & Retention Policy
How we classify data by sensitivity (public, internal, confidential, restricted) and when and how data is securely disposed of.
View policy →
Vendor Management Policy
How we evaluate, onboard, monitor, and offboard third-party vendors — including risk assessment and contractual obligations.
View policy →

Infrastructure

Platform architecture and availability

Google Cloud Platform

Compass IoT's platform is built on Google Cloud Platform (GCP), designed from the ground up for high availability. Our architecture uses managed GCP services with built-in redundancy, autoscaling, and regional failover capabilities. We do not rely on single points of failure in any critical data path.

Planned maintenance is communicated in advance and scheduled to minimise impact. Unplanned outages are communicated via our status page as soon as they are detected.

  • Managed GCP services with built-in redundancy and autoscaling across availability zones.
  • Regional data storage — data does not leave the originating region without justification.
  • Automated health monitoring and alerting on all critical services, 24/7.
  • Load balancing and traffic routing managed via GCP global infrastructure.
  • Infrastructure changes are tested in staging before deployment to production.

Recovery

Business continuity and disaster recovery

BC/DR plan in place

Compass IoT maintains a documented Business Continuity and Disaster Recovery (BC/DR) Plan that defines how we respond to and recover from significant disruptions — including infrastructure failures, data loss events, and force majeure scenarios.

Our recovery objectives are defined at the service level. All production data is backed up daily, with backups stored in a geographically separate GCP region. Backup integrity is tested on a regular schedule.

  • Recovery Time Objective (RTO): < 4 hours for critical platform services.
  • Recovery Point Objective (RPO): < 24 hours — maximum data loss in a worst-case scenario.
  • Daily automated backups stored in a geographically separate GCP region.
  • Backup restoration is tested at least annually.
  • BC/DR plan is reviewed annually and following any significant incident.
  • Key personnel responsibilities are defined and communicated ahead of any incident.

Upstream resilience

Data source disruption handling

Compass IoT ingests data from third-party connected vehicle data sources, including OEM telematics providers and roadside infrastructure operators. Disruptions to these upstream sources — whether planned or unplanned — are a normal operational consideration that we manage proactively.

Our platform is designed to degrade gracefully when upstream data sources become unavailable. Historical data and cached signals remain accessible during ingestion outages. Customers are notified of significant data source disruptions that materially affect platform output.

  • Platform continues to serve historical and cached data during upstream source outages.
  • Monitoring detects upstream disruptions automatically and triggers internal alerting.
  • Material data source outages affecting customer outputs are communicated proactively.
  • Data source SLAs and reliability terms are reviewed as part of our Vendor Management Policy.

Note on OEM dependencies

Some connected vehicle data streams are dependent on OEM and third-party infrastructure outside Compass IoT's direct control. We document these dependencies in our BC/DR plan and work with data partners to obtain advance notice of planned maintenance windows wherever possible.

Questions

Talk to the team

Policy documents, availability queries, and vendor assessment requests.