Compliance Overview
Overview

Australian law

Australian Privacy Act 1988 and New Zealand Privacy Act 2020

Aligned

Compass IoT operates in accordance with the Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs). The APPs govern how we collect, use, disclose, store, and provide access to personal information. Compass IoT also operates in accordance with the New Zealand Privacy Act 2020 and its Information Privacy Principles (IPPs), which govern how we collect, use, disclose, store and give access to personal information. Connected vehicle data is de-identified when we receive it, as described below. Individuals can ask to access or correct their personal information by contacting trust@compassiot.com. Notifiable privacy breaches are reported to the Office of the Privacy Commissioner and affected individuals as soon as practicable

Connected vehicle data processed by Compass IoT is anonymised at the point of ingestion — individual drivers are not identified, and we do not hold data in a form that would allow re-identification. Where personal information is collected directly (such as contact details from platform users), it is handled in accordance with our Privacy Policy. Road Intelligence trip start and end points are removed, persistent vehicle identifiers are removed or replaced, and outputs are aggregated so that no individual vehicle or driver can be singled out. We do not attempt to re-identify individuals, and our customer terms prohibit re-identification.

  • We collect only the personal information necessary to provide the platform and fulfil our contractual obligations.
  • Personal information is not disclosed to third parties except where required to operate the service (see Subprocessors) or where required by law.
  • Individuals have the right to access, correct, or request deletion of their personal information. Requests are handled within 30 days.
  • We maintain a Privacy Policy that is publicly available and updated to reflect our current practices.
  • We assess any suspected data breach within 30 days. Where a breach is likely to result in serious harm (an eligible data breach), we notify the Office of the Australian Information Commissioner (OAIC) and affected individuals as soon as practicable.

United Kingdom

UK GDPR

Aligned

Compass IoT's UK operations are aligned with the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018. The UK GDPR applies to the processing of personal data relating to individuals in the United Kingdom.

Where Compass IoT processes personal data of UK residents, we do so on a lawful basis as defined under UK GDPR Article 6. Data processed in connection with UK customers is stored in UK or EU-equivalent regions and is not transferred outside of the UK without appropriate safeguards.

Lawful basis
Contract performance; legitimate interests; legal obligation
Data storage
UK / EU-equivalent regions via Google Cloud
Data transfers
Only with appropriate safeguards: the UK International Data Transfer Agreement (IDTA) or the UK Addendum to the EU standard contractual clauses
Subject rights
Access, rectification, erasure, portability, objection — handled within 30 days
DPA available
Yes — Data Processing Addendum available on request (email-verified)

United States — California

CCPA

Aligned

Compass IoT's operations are aligned with the California Consumer Privacy Act (CCPA) as amended by the California Privacy Rights Act (CPRA). The CCPA grants California residents rights over their personal information held by businesses operating in or serving residents of California.

Compass IoT does not sell personal information. We do not share personal information for cross-context behavioural advertising. California residents may exercise their rights by contacting us at the address below.

  • Right to know what personal information is collected and how it is used.
  • Right to delete personal information (subject to certain exceptions).
  • Right to opt out of the sale or sharing of personal information — note that Compass IoT does not sell or share personal information.
  • Right to non-discrimination for exercising CCPA rights.
  • Right to correct inaccurate personal information.

Data sharing

Subprocessors

Compass IoT uses a limited number of third-party subprocessors to deliver the platform. A subprocessor is any third party that processes personal data on our behalf. We conduct due diligence on all subprocessors before engagement and contractually require them to maintain appropriate data protection standards.

We do not sell personal data to any third party. Data shared with subprocessors is limited to what is necessary to provide the service.

Google Cloud Platform
Cloud infrastructure, data storage, and compute. Data stored in region of origin.
HubSpot
CRM and customer communication. Contact data only.
MailerLite
Email marketing. Subscriber contact data only.

Subprocessor changes

We will provide notice of material changes to our subprocessor list with reasonable advance notice. Customers with data processing agreements in place will be notified directly.

Data sharing

De-identified road intelligence data

Compass turns connected vehicle data into insights about how roads are used. We share that de-identified data with customers and partners to support:

  • mapping and wayfinding
  • infrastructure planning
  • road safety planning
  • understanding how road networks are used
Who receives it
Government agencies, transport and infrastructure planners, and mapping and navigation providers.
How we protect it
Before data leaves our platform, we trim the true origin and destination of each trip, so start and end points such as homes and workplaces aren't exposed. We also apply minimum thresholds, so data is only released when there are enough vehicles in it that no single vehicle stands out. Together, these steps mean the data can't reasonably be used to identify an individual or a specific vehicle.
What recipients agree to
Customers and partners are contractually prohibited from reverse engineering the data to identify individual vehicles, and agree to use it only for the purposes in their agreement with us. Our minimum thresholds and de-identification process back this up, so re-identification is both prohibited and hard to do in practice.

Camera data

Camera-derived and biometric data

Anonymisation-first approach

Camera imagery may incidentally include pedestrians, other road users and vehicles. We process the imagery under legitimate interests (improving road safety and infrastructure), and only to the extent needed to blur faces and licence plates and extract road features such as signage, line marking and road defects. Anyone can contact trust@compassiot.com with questions or to exercise their rights.

Compass IoT receives camera-derived data from third-party vehicle data sources. Where that data contains potentially identifying information — including facial geometry, driver images, or licence plate data — those elements are automatically detected and blurred by Compass IoT within our in-region processing pipeline, before the imagery is stored or made available in our platform. We use detection only: no face templates or embeddings are retained or used to identify anyone. This anonymisation-first approach underpins our compliance posture on biometric data law across all jurisdictions. Because these people cannot practically be contacted individually, we provide this public notice instead.

Biometric data laws vary significantly across the jurisdictions we operate in. The following reflects our current position across each relevant framework.

  • Australia — Privacy Act 1988 — Biometric information and biometric templates are classified as sensitive information under the APPs. Compass IoT does not collect, store, or process biometric identifiers in their raw form.
  • Illinois — BIPA (Biometric Information Privacy Act) — BIPA imposes strict consent and data handling requirements on entities collecting biometric identifiers. Camera-derived data entering the Compass IoT platform is anonymised prior to ingestion, such that no biometric identifiers are retained within our systems.
  • Texas — CUBI (Capture or Use of Biometric Identifier) — Texas law prohibits the capture of a biometric identifier without prior informed consent. Our anonymisation approach means Compass IoT does not capture biometric identifiers as defined under CUBI.
  • California — CCPA (sensitive personal information) — Biometric data is classified as sensitive personal information under the CPRA. Compass IoT does not collect biometric data that would trigger CCPA sensitive PI obligations.
  • UK — UK GDPR (special category data) — Biometric data processed for the purpose of uniquely identifying a natural person constitutes special category data under UK GDPR. Compass IoT's anonymisation-first design means we do not process data at this level of identification.

Vendor obligations

Compass does not collect data directly from drivers. Compass IoT provides guidance and education on notice standards to all vendors, applicable local laws and GDPR. We and our partners ensure compliance with your rights and update our terms regularly to ensure best practices in privacy, compliance and security. Compass does not collect data directly from drivers. We receive connected vehicle and camera-derived data from vehicle manufacturers, telematics providers and fleet operators under written data sharing agreements. Under those agreements, each data partner is responsible for:

  • telling drivers and vehicle owners about data collection and its use by third parties, through its vehicle, app or fleet terms
  • having a lawful basis, and consent where required, to share the data with us
  • giving drivers of fleet vehicles any notices required under workplace surveillance laws. Compass IoT does not receive audio.
  • Documentation

    Compliance documents

    The following documents are available depending on your access tier. Email-verified documents require a business email address. On-request documents are available to qualified customers and prospects.

    Privacy Policy
    Public · No verification required
    View →
    Activity & Training Records
    On request · Logs and certificates showing employees have completed mandatory training, including cybersecurity and compliance programmes
    Request via email →
    Penetration Test Results
    On request · Executive summary and findings from our most recent independent penetration test
    Request via email →
    Assessment & Incident Reports
    On request · Audit trails, testing reports, and records of compliance issues and how they were resolved
    Request via email →

    Questions

    Talk to the team