Privacy Policy

Effective date: 11 July 2026 · Last updated: 7 September 2026
Who we are: Analemma Labs Pty Ltd ABN 78 701 798 398 ("TerraADV", "we", "us", "our")
Contact: [email protected]

1. Introduction

This policy explains how we handle personal information when you use the TerraADV mobile apps for iOS and Android, our web route planner, and related services (together, the "Service"). We handle personal information consistently with the Australian Privacy Principles (APPs) under the Privacy Act 1988 (Cth).

TerraADV is designed to work offline, and you can plan and navigate without creating an account. An account is needed to sync between your phone and the web planner, and to take part in community features. If you don't create one, the information described below simply stays on your device.

We also hold a small amount of information about people who are not users of the Service — people who joined our waiting list, and landholders whose contact details a user has recorded for a track that needs permission. Section 9 explains how those people can ask us what we hold and have it removed.

2. What we collect

Information you give us

• Account details: your email address, and your name if you provide it. If you sign in with Apple or Google, we receive an identifier and the email address associated with that account (which may be a private relay address if you choose that option with Apple).
• Your garage: details of the vehicles you add — type (motorcycle, four-wheel drive, side-by-side), make, model, year, nickname, tyres, fuel capacity, weight and seat height, and fuel consumption. We use these to calculate fuel range on your routes.
• Waiting list: if you asked to be told when TerraADV opens up, we hold the email address, device model and region you gave us, and what access we offered you. You can ask us to delete this at any time, and we delete it once it is no longer needed.
• Anything you send us directly, such as support messages, beta feedback or bug reports.

Location information

This is the part people ask about most, so we want to be precise about it.

• While you are navigating, your position is processed on your device. Routing, rerouting and guidance all run locally. We do not receive a live feed of where you are.
• Searching for a place, or naming a point on the map, uses an outside mapping service. When you search, or when the app needs a name for a pin or for the town you are in, the search text and the coordinate are sent to a mapping service to look up — on iPhone that is Apple's; on Android it is your phone's Google geocoder and OpenStreetMap's Nominatim service. Where we have offline place data downloaded, we search that first and show those results immediately. Those services receive the query under their own privacy terms. We do not receive it, and it is not a continuous feed — it happens when you search or drop a pin, not while you ride.
• While you are recording a track, the app builds a continuous trace of where you have been. That trace is held on your device. It is something you switch on deliberately, the app shows you while it is running, and it does not reach us unless you choose to submit it as a community track.
• Location data reaches our servers when you choose to save or submit it. Specifically: routes you save to your account, rides you record and keep, routes you import as GPX, community tracks you submit, and hazard or road-condition reports you submit — including the position of your device when you took an attached photo. Each of these contains location information, because that is what makes them useful.
• A ride you record and keep is saved to your route library, and syncs to your account like any other saved route — so it is available on your other devices and in the web planner. If you don't want a recording kept, delete it; if you are not signed in, it stays on the device.
• Why it is stored: so your saved routes and garage are available on both the app and the web planner, and so reports and tracks can be shown to other people.
• If you use the Service without an account, none of the above leaves your device.

Photos

If you attach a photo to a hazard report, we receive the image, the position your device reported when you took it, the time it was taken, and whether it was taken live in the app.

The image is stripped of its embedded metadata on your device before it is uploaded, including any location your camera recorded. The only location attached to the photo is the one the app read at the time of capture.

Photos are held in private storage while we review them, and are published with the report only if we accept them. Section 5 explains what that means.

Community contributions

• Reports you submit — the report type, its location or the stretch of road it covers, any note you add, and when you submitted it.
• Community tracks you submit — the recorded line, its difficulty, direction, vehicle type, and what you told us about land access, together with the choices you made about overlay routing and OpenStreetMap.
• Permission contacts — where you record contact details for a landholder or land manager, we store that person's name, phone number, email address and any note, against the track. This is personal information about someone who is not a user of the Service. Section 8 of the Terms sets out the rules for recording it, and section 9 below explains how that person can have it removed.
• Confirmations and disputes you record on other people's reports. We store which account cast each vote so that the same person cannot vote twice and cannot confirm their own report.
• Reviews and correspondence — where a report of yours is disputed and we review it, we keep the review, its outcome, and any reply you send us. We may also keep an internal note about the review, which is not shown to you or to other users.
• Routes you publish, ratings and comments on the web community hub.

See section 5 for how this content is shared with other people.

Group rides

When you take part in a connected group ride, we store the ride session, and for each person in it a display name, the vehicle label they chose, whether they were leading or following, and when they joined or left. We also store each version of the route the leader shares.

We do not receive the live positions of anyone in a group ride. Presence and position are shared directly between phones over Bluetooth and do not reach us.

Camera and Bluetooth

• Camera — used only to take a photo for a hazard report, when you choose to.
• Bluetooth — used to find nearby riders and drivers for a group ride, and to connect helmet comms and vehicle sensors. Group ride discovery broadcasts your display name to nearby phones. None of this reaches our servers.

The iOS app declares microphone and speech-recognition permissions for a hands-free feature we have not finished building. It is not switched on: the app never listens, records, or sends audio anywhere. If we ship it, we will update this policy and the store privacy details before it goes live. If you dictate into a text box using the microphone button on your keyboard, that is your phone's own dictation: the audio goes to Apple or Google under their terms and never passes through TerraADV.

Information collected automatically

• Devices you sign in from. When you sign in, we record an identifier for that installation of the app, the platform, your operating system version, the app version and build, the device model, and when we first and last saw it. We use this for support, for working out which versions are in use, and for spotting misuse of an account.
• Server logs: when the app downloads map regions from our hosting provider (Cloudflare R2), standard server logs may record your IP address, the time of the request and the file requested. These logs are used for delivering files, diagnosing faults and preventing abuse.
• Analytics, advertising and crash reporting: none. TerraADV does not include any third-party analytics, advertising or crash-reporting software. If that changes, we will update this policy and the App Store and Google Play privacy details before the change ships.

Information from the app stores

• If you subscribe, the app store you bought through — Apple or Google — processes the payment. We receive confirmation of the purchase and its status, but not your card or full payment details. We do not process payments ourselves.

3. How we use your information

We use personal information to:

• provide the Service, including planning routes, calculating fuel range and delivering navigation;
• sync your saved routes and garage between your devices and the web planner;
• operate the community features — showing reports, tracks and photos to other people, applying confirmations and disputes, reviewing disputed reports, and deciding which contributions are trusted enough to affect routing;
• submit community tracks to OpenStreetMap, where you have asked us to;
• deliver downloadable map regions and app updates;
• respond to your enquiries and provide support, including working out what is happening on a particular device or app version;
• diagnose faults, prevent misuse or abuse of the reporting system, and keep the Service secure;
• send you emails you have asked for;
• comply with our legal obligations.

We do not use your information to build advertising profiles, and we do not sell it.

4. Marketing communications

We only send marketing or promotional email where you have opted in, and every such email includes an unsubscribe link, consistent with the Spam Act 2003 (Cth). You can withdraw consent at any time. Service messages — for example, notice of a change to these terms or a problem with your subscription — are not marketing and may still be sent.

5. Community content and what other people can see

TerraADV includes features that are public by design. It is worth being clear about which those are.

• Hazard and road-condition reports are visible to everyone using the Service. This includes the location or road stretch, the report type, and any note you added. Do not include personal information in report notes.
• A photo becomes visible to everyone once we accept it. Until then it is private. If we reject it, it is not published.
• Community tracks you submit are shown to others once approved, and the Service may route people along them.
• A track you opt in to OpenStreetMap promotion for becomes part of a public map database, permanently. It can then be used by anyone in the world, and neither you nor we can withdraw it.
• Permission contacts are shown to administrators and to people who have asked for permission to use that track.
• Routes you save are private to your account unless you deliberately publish them to the community hub. Published routes, and any ratings or comments you leave, are visible to other users.
• In a group ride, the people in that ride can see your display name, your vehicle label and whether you are leading.
• Confirmations and disputes are used to score reports, and are not displayed to other users as individual votes.
• Content that is public cannot be fully "unpublished" from anyone who has already downloaded a map region containing it.

6. Who we share it with

We do not sell your personal information. We share it in two quite different ways, and the difference matters.

Service providers, who handle information on our behalf and only as far as needed to run the Service:

• Supabase — our backend database, authentication and file storage (accounts, route and garage sync, community contributions, hazard photos).
• Apple — app distribution, subscription payments, and Sign in with Apple if you use it.
• Google — app distribution through Google Play, and Sign in with Google if you use it.
• Cloudflare (R2) — hosting and delivery of downloadable map regions, and hosting of our website.
• Our email service provider, for messages you have asked to receive.

Outside services the app queries on your behalf, which receive the request under their own privacy terms rather than ours:

• Apple Maps (on iPhone), and Google's geocoder and OpenStreetMap's Nominatim service (on Android) — place search and turning a coordinate into a place name. They receive the search text and the coordinate; we do not receive what they return about you.

Publication to a public database, which is not the same thing and cannot be undone:

• OpenStreetMap — where you have opted in for a particular community track, we submit that track to OpenStreetMap, where it is published under the Open Database Licence and becomes available to anyone. We do not send your account details or any other personal information with it.

We may also disclose information if required by law, or where necessary to protect our rights, our users, or the public.

7. Where your data is stored

Our backend database and file storage — including accounts, saved routes, garage details, community contributions and hazard photos — is hosted by Supabase in the AWS Asia Pacific (Sydney) region, ap-southeast-2. Your core account data is stored in Australia.

Some other providers operate globally and may store or process limited data overseas — in particular Cloudflare's content delivery network, Apple's and Google's app distribution and payment systems, and our email provider. Where information is handled outside Australia, we take reasonable steps to ensure it is handled consistently with the APPs.

Data published to OpenStreetMap is held on infrastructure we do not control, and is public worldwide.

8. Security and retention

We take reasonable steps to protect personal information from misuse, interference, loss and unauthorised access or disclosure. Data is transmitted over encrypted connections, hazard photos are held in private storage until published, and access to the backend is restricted.

We keep personal information only as long as we need it for the purposes described above, or as required by law. Account and profile data is retained while your account is active. Other retention works like this:

• Reports retire automatically — currently after thirty days, unless we have set a different expiry for a particular hazard.
• Photos we reject are not published, and are deleted from storage.
• Review records — the outcome of a disputed report, any reply you sent, and any internal note we made — are kept while the report is live and for a reasonable period afterwards, so that a decision can be explained or revisited.
• Group ride sessions and rosters are kept for a limited period after the ride ends, and are not needed once it is over.
• Device records are kept while your account is active.
• Waiting-list entries are deleted once they are no longer needed, or sooner on request.
• Permission contacts are deleted when the track is deleted, or on request from the person concerned.

If you delete your account, we delete your account record, your saved routes, your garage, your device records, and any community tracks you had submitted that were not approved. We aim to complete this within 30 days, subject to any legal retention requirement and to routine backup cycles.

Community contributions are treated differently. Because other people rely on them for safety, reports, approved tracks, photos, published routes, ratings and comments that you submitted are retained after your account is deleted, but they are de-identified — the link between the contribution and you is severed, and it is no longer attributed to your account.

Anything already submitted to OpenStreetMap cannot be withdrawn, by us or by you.

9. Your rights and choices

You may:

• Delete your account at any time — in the iOS and Android apps: Settings → Account → Delete account; on the web planner: your account menu → Delete account. Deleting your account works as described in section 8.
• ask what personal information we hold about you and request access to it;
• ask us to correct information that is inaccurate or out of date;
• ask us to delete information, subject to legal exceptions and to the treatment of community contributions described in section 8;
• use the Service without an account, in which case your data stays on your device;
• unsubscribe from marketing email at any time.

If you are not a user of the Service — for example, if a user has recorded your contact details as a landholder, or you joined our waiting list — you have the same rights. Contact us and we will tell you what we hold and remove it on request. We do not need the user's agreement to remove a landholder's details.

To make a request, contact [email protected]. We will respond within a reasonable period. If you are not satisfied with our response, you can contact the Office of the Australian Information Commissioner (OAIC) at oaic.gov.au.

10. Beta testing

While TerraADV is in beta, the apps are distributed through Apple's TestFlight and Google Play's testing tracks. Apple and Google each provide us with information about installs, and about any feedback you submit through their tools, in accordance with their own terms. Beta feedback you email us is read by the developer personally and is not shared further.

11. Children

The Service is not directed at children under 16, and we do not knowingly collect their personal information. If you believe a child has provided us with personal information, contact us and we will delete it.

12. Third-party data and links

Map and routing data comes from third parties including OpenStreetMap contributors, and official road-closure information is sourced from state government feeds. Your use of that data may also be subject to their terms.

Data also travels the other way: where you opt in, community tracks you submit are contributed to OpenStreetMap, as described in sections 5 and 6.

Road and track conditions change constantly, and neither official closure data nor community contributions are guaranteed to be current or complete — see our Terms. The Service may contain links to third-party sites we do not control.

13. Changes to this policy

We may update this policy from time to time. We will post the updated version here and change the "Last updated" date. Where changes are significant, we will notify you in the app or by email.

14. Contact

Questions, requests or complaints: [email protected].