Last updated: 31 October 2026
This Data Policy explains how AirTracker handles, stores, processes and protects the data that flows through our platform. It supplements our Privacy Policy and Terms of Service by providing technical and operational detail about our data practices.
For each asset you register, we process and store:
We store the geographic boundaries (geofences) you define, including their names, polygon coordinates and alert rules. This data is used to evaluate whether an asset has entered or exited a zone and to trigger notifications.
We store records of alerts generated by the platform (geofence breaches, movement alerts), including the triggering event, timestamp and notification delivery status.
Authentication data is managed by Clerk, Inc. We store your organisation ID, user role and session metadata. We do not store or have access to your raw authentication credentials.
AirTracker retrieves location data by acting as your authorised agent. The process works as follows:
We do not independently collect or generate location data. All location data we process is data that you already have the right to access through the device's native platform. Our role is to consolidate, display and alert on this data in a way that is useful for fleet management.
Location data and account metadata are stored in a PostgreSQL database with Write-Ahead Logging (WAL) enabled for concurrent read/write performance. The database is hosted on infrastructure in Australia (Sydney region).
Automated backups are performed daily and retained for 30 days. Backups are encrypted and stored in a separate geographic region from the primary database.
| Data Type | Retention Period |
|---|---|
| Location history | 12 months from collection |
| Geofence configurations | Until deleted by you or account closure |
| Alert history | 90 days |
| Account information | Duration of account + 30 days after closure |
| Device credentials | Until device is removed or account is closed |
AirTracker is a multi-tenant platform. Your data is logically isolated from other tenants' data through organisation-level access controls. You may invite team members to your organisation; all members of your organisation can view your organisation's asset locations, alerts and configurations according to their assigned role.
You may request deletion of your data at any time. Upon receiving a verified deletion request:
Our primary data processing and storage occurs in Australia (Sydney). Some auxiliary services (authentication, email delivery, WhatsApp messaging) may process data in the United States. We ensure that all data processors meet our security and privacy standards through contractual agreements.
We use the following third-party subprocessors to deliver the Service:
These subprocessors only receive the minimum data necessary to perform their function. Mapbox receives coordinates solely for the purpose of rendering map tiles in your browser. Resend and Meta receive the alert text and the asset identifier; when the alert includes a location, they also receive its coordinates, and only for organisations that have enabled email or WhatsApp alerts. OpenRouter receives only the messages a visitor types into the website chat, to generate a reply; it receives no account, asset or location data.
In the event of a data breach affecting your information, we will notify affected users within 72 hours of becoming aware of the breach, in accordance with New Zealand Privacy Act 2020 requirements. Notifications will describe the nature of the breach, the data involved and the steps we are taking in response.
We may update this Data Policy to reflect changes in our infrastructure, data practices or legal obligations. Material changes will be communicated to active users. The latest version is always available at this page.
For questions about this Data Policy or our data handling practices, contact us at data@airtracker.co.nz.