Privacy Policy
How TruckMaps AU handles your information
What the TruckMaps AU website (truckmapau.com) and the TruckMaps AU Android app collect, why, who receives it and how long it's kept — written to match how the service actually works.
Last updated:
The short version
- You can plan routes and navigate without an account on 3 different days. After that, you need a free account to keep using the app on that device. There are no ads, no analytics or advertising trackers, and we don't sell personal information.
- Your position is used on your device for navigation. When you look for a route, the coordinates of your start, stops and destination go to our server and on to the National Heavy Vehicle Regulator (NHVR) to calculate it. Our server doesn't keep your locations or a history of your trips.
- Your vehicle, network choices, recent places and settings are saved on your device, not on our server.
- If you create an account we keep your email address, your name if you give one, and a one-way scrambled (hashed) form of your password. If you use Sign in with Google, we also keep your Google account's ID. We never see your Google password.
- Payments go through Stripe on the website or Google Play in the Android app. We never see your card details.
Who we are
TruckMaps AU ("we", "us", "our") runs truckmapau.com and the TruckMaps AU Android app. The navigator inside them is called HV Navigator. This policy covers both, and our Terms of Service apply alongside it.
We handle personal information in line with the Australian Privacy Principles in the Privacy Act 1988 (Cth). You can contact us about privacy at [email protected].
You can try TruckMaps AU without telling us who you are: routes, NHVR checks, hazards and navigation all work without an account on the first 3 different days you use the app on a device. After that, you need a free account to keep using it on that device. You also need an account to subscribe to TruckMaps AU Pro. An account needs only an email address and a password, or a Google account where Sign in with Google is offered; a name is optional.
What we collect and why
What we collect depends on what you use. Each part below says what is collected, what it's for and where it goes.
Every visit
- Your internet address (IP address). Every request reaches us through Cloudflare, which needs your IP address to deliver the pages. Our server uses it for two things:
- Limits that keep the service available and protect it from misuse — for example, how many route searches or login attempts one connection can make in a minute. These counters live only in the server's memory, cover periods from one minute to one day, are never written to disk and are cleared whenever the server restarts.
- Sharing the free Google Maps allowance fairly. On the free plan, our database records, for each day, your network's address and how often Google Maps and Google address search were used from it. For IPv6 connections only the network part of the address is recorded, not your device's full address. These records are deleted after 35 days.
- Server logs. Our server writes one line for each request: the date and time, the page or service requested, the result and how long it took. The address is logged without the part after "?", so the text you search for never reaches the log, and the line doesn't include your IP address. Diagnostic messages about route searches (for example, how many options were tried or the name of a restriction that was found) never include your coordinates, IP address or account. Account and billing messages refer to an account by its number and to payments by Stripe's or Google Play's references, email messages show only a masked address (the first one or two characters and the domain), and a failed sign-up mail check notes only the email's domain.
Location
- On your device. Once you allow location access, your device's GPS position is used on your device to fill in your starting point, show where you are and guide you turn by turn. Following your progress along the route, spoken directions and warnings all run on your device.
- Route searches. When you search for a route, the app sends the coordinates and names of your start, stops and destination to our server, with your vehicle, the networks you ticked and the details you entered for the checks (gross mass, height and whether you carry dangerous goods). Our server sends the coordinates and place names, the networks and your route options (such as avoiding toll roads) to the NHVR's route planner, and runs the mass, height and dangerous-goods checks itself. During navigation the app sends your current position the same way whenever it needs a new route, for example after you leave the planned route.
- Route checks. To check a route for hazards, bridges and restrictions, the app sends the route's line to our server. These checks run on our server against NHVR open data that it has already downloaded; nothing is sent on.
- Nothing kept. Our server handles route requests in memory while they run and doesn't save them. It doesn't record your coordinates in its database or its logs, and it keeps no history of your trips.
- Address search. While Google Maps is active, your device sends what you type in the search box, and your position to rank nearby results first, straight to Google, and asks Google for the address of your current position. Otherwise our server looks addresses up with OpenStreetMap's Nominatim service: it sends the search text with an approximate area around you, or the coordinates of a point to name. Nominatim sees our server's address, not yours. Our server keeps each lookup in memory for up to 10 minutes, with nothing that links it to you, so repeated searches aren't sent again.
- Your choice. You can refuse or withdraw location access in your browser or Android settings. You can still type a starting point and plan routes, but turn-by-turn guidance needs your position.
Saved on your device
The app saves these in your browser's storage on your device. They are not sent to our server, except where you use them in a request described above (a recent place becomes a route search, for example).
- Your settings (theme, voice guidance on or off), your recent vehicles with the mass, height and dangerous-goods answers you gave for each, the networks you ticked for each vehicle, up to eight recent places, route options, notices you've closed, and a trip in progress so navigation can resume after the page reloads.
- How many different days you've opened the app, the date you last opened it, and whether an account has logged in on this device. The app uses this for the account rule: from the second day, if no account has logged in on this device, it asks you to register each time you open it; from the fourth different day, someone needs to be logged in to keep using the app on this device. This count stays on your device; it isn't a cookie and isn't sent to us. Settings → Clear saved data doesn't remove it; clearing the site data for truckmapau.com in your browser does.
- For the current visit only: the trip you were planning while the page reloads to switch maps, and whether you opened TruckMaps AU from the Android app.
- If Google refuses to load the map for a technical reason, a note of that for 30 minutes so the app doesn't keep retrying. It holds a time and a fingerprint of the map key, nothing about you.
- A copy of the app's own files (pages, code, styles and icons) so it opens faster and can show an offline page. This copy holds no account details, locations or routes.
Settings → Clear saved data removes the items in the first point above. It keeps the count of days you've used the app, so it doesn't restart the 3 days. Clearing the site data for truckmapau.com in your browser (on Android, in Chrome's site settings) removes all of it, including that count.
If you create an account
You can create an account with your email address and a password, or create one or log in with your Google account instead (Sign in with Google, where the app offers it).
- Email address — as you typed it (or as Google gave it), and in lower case to match logins. It's how you log in and how we contact you about your account.
- Name — optional. We use it to greet you in our emails once your address is confirmed, and give it to Stripe if you subscribe on the website.
- Password — stored only as a scrypt hash, a one-way scrambled form. We can't see or recover your password. An account created with Google has no password until you set one with "Forgot your password?".
- Sign in with Google — when you choose it, Google tells us your Google account's unique ID, its email address, whether Google has verified that address, and the name on the account. We don't receive your Google password, your contacts or any other data from your Google account. We store the Google account ID with your account, so you can log in with Google next time. The email address and name are kept as for any account; Google's name is used only if your account doesn't have one yet. If an account with the same Gmail or Google Workspace address already exists, logging in with Google links it to your Google account. If that address had never been confirmed, the account's password is removed, its other sessions end and its unused email links stop working, because Google has shown that you own the address. For any other address we don't link accounts: log in with your password instead.
- Dates — when you created the account, last logged in and confirmed your email address.
- Login sessions — when you log in we set the
tm_sessioncookie and keep a record of that session: a hash of its code, the IP address and the browser and device description (user agent) it was started from, and when it was started and last used. A session ends when you log out or after 30 days without use, and changing or resetting your password ends your other sessions. We keep at most 20 sessions per account. - Email links — confirmation and password-reset links contain a one-time code. We store only a hash of it, the address it was sent to and when it expires, and delete the record 7 days after the link is used or expires.
- Your plan — your subscription's status and billing period (see Payments), and for subscribers how much of the plan's fair-use allowance each billing period has used.
- Sign-up checks — to stop fake and throwaway accounts we check that your email's domain (the part after the @) can receive mail, using a public DNS lookup, and that it isn't on a public list of temporary-email services. For an account created with Google, only the temporary-email list is checked.
Payments
- On the website, payments are made on a payment page hosted by Stripe. We give Stripe your email address, your name if you gave one, and your account number with us, so the payment belongs to your account. Stripe collects your card details; we never receive them. We store the identifiers Stripe gives us for you as a customer and for your subscription, and the subscription's status, price, current billing period and whether it's set to end. We also keep the identifiers of Stripe's notifications to us, so none is processed twice. Stripe's privacy policy covers what Stripe collects.
- In the Android app, payments are made through Google Play with your Google account. Google gives us a purchase token for your subscription, which we check with Google and store with your account together with the product, the subscription's status, its current billing period, whether it's set to end and whether we've confirmed the purchase to Google. We also keep the identifiers of Google's notifications to us, so none is processed twice. We don't receive your card details or your Google account details. Google's privacy policy covers Google Play.
Emails
We send emails only about your account and subscription: confirming your address, resetting your password, telling you your password changed, and when a subscription bought on the website starts, a payment fails, or it is cancelled or ends. For a subscription bought through Google Play, Google Play sends its own messages; we don't email you about it. We don't send marketing emails. Emails are delivered by Resend, which receives your address and the message. We record which subscription emails have been sent (the kind, its status, the number of attempts and the time) so you don't get the same one twice. Our emails contain no tracking images.
If you contact us
If you email us, we keep your message and our reply so we can help you and deal with any follow-up.
How long we keep it
| Information | How long |
|---|---|
| Account details (email, name, password hash, Google account ID, dates) | Until you ask us to delete your account. We don't delete inactive accounts automatically. |
| Subscription records, plan usage and the record of subscription emails | While your account exists. |
| Login sessions, with their IP address and browser description | Until you log out or 30 days after the session was last used; expired sessions are removed within the hour. |
| Email link records | 7 days after the link is used or expires. |
| Daily free-plan counts per network address | 35 days. |
| Limit counters (rate limits) | Server memory only, for periods of up to one day; never written to disk. |
| Address lookups held by our server | Up to 10 minutes, in memory. |
| Route searches and your positions | Not stored: handled in memory while the request runs. |
| Server logs (no IP addresses, positions or search text) | As long as they're useful for fixing faults and investigating misuse. |
| Totals of Google Maps use for the whole service (nothing about you) | Daily totals 400 days; monthly totals are kept. |
| Data saved on your device | Until you clear it. |
| Payment records | Stripe and Google keep theirs under their own policies and legal obligations. We keep records of payments we receive for as long as Australian tax law requires (generally five years), even after an account is deleted. |
Security
Connections to truckmapau.com are encrypted (HTTPS). Passwords are stored as scrypt hashes, session and email-link codes only as hashes, and the login cookie can't be read by page scripts. A Google sign-in is accepted only after our server has checked Google's signature on it, and each one only once. Logins, sign-ups, password resets and other sensitive actions are rate-limited.
No system is perfectly secure, so we can't promise that information will never be accessed without permission. If a data breach is likely to cause you serious harm, we'll tell you and, where the law requires, the Office of the Australian Information Commissioner (OAIC).
Your rights and choices
- Access and correction. You can ask for a copy of the personal information we hold about you, and ask us to correct it. Email [email protected] from your account's address so we know the request is yours. We'll reply within 30 days and don't charge for this. You can change your password yourself in the app; if you created your account with Google, you can set one with "Forgot your password?".
- Deletion. You can ask us to delete your account, or particular information, at any time — see Delete your account.
- Saved data and location. Clear the app's saved data in Settings, and turn location access off in your browser or Android settings whenever you like.
- No marketing. We don't send marketing emails, so there's nothing to opt out of.
- Complaints. If you're unhappy with how we've handled your information, email us and we'll respond within 30 days. If you're not satisfied with our response, you can complain to the Office of the Australian Information Commissioner.
Delete your account
- Cancel any subscription first. If you subscribed in a web browser, log in at truckmapau.com and choose Manage billing in your account. If you subscribed in the Android app, cancel in Google Play (Play Store → your profile → Payments & subscriptions → Subscriptions). Deleting your account doesn't cancel a Google Play subscription.
- Email us at [email protected] from your account's email address, with the subject "Delete my account". We may reply to confirm the request is yours.
- We delete it within 30 days: your account and, with it, the link to your Google account if you used one, your sessions, email link records, plan usage, subscription records and the record of emails sent. If a subscription bought on the website is still running, we cancel it with Stripe. We'll email you when it's done.
Stripe and Google keep their own payment records, and we keep records of payments we received as tax law requires. Data saved on your device isn't on our server: Settings → Clear saved data removes most of it, and clearing the site data for truckmapau.com in your browser removes all of it (see Saved on your device).
Children
TruckMaps AU is made for heavy-vehicle drivers and isn't intended for children. Accounts and subscriptions are for people aged 18 or over. If you think a child has given us personal information, contact us and we'll delete it.
The Android app
The TruckMaps AU Android app opens truckmapau.com full screen in Chrome (as a "Trusted Web Activity"), or in another browser that supports this if Chrome isn't available, so everything in this policy applies to it in the same way. The app passes your position to the page once you give Android location permission, and purchases in the app go through Google Play billing. The app doesn't read your contacts, photos, files, camera or microphone. The app adds a marker to the page address so the page knows it's running in the app; like everything after "?", it isn't logged. Google's privacy policy covers what Chrome and Google Play themselves collect.
Changes to this policy
We'll update this policy when TruckMaps AU or the law changes. The date at the top shows the current version. If a change significantly affects how we handle your information, we'll tell account holders by email or in the app before it applies.
Contact us
Questions, requests or complaints about privacy: [email protected]
TruckMaps AU · truckmapau.com. See also our Terms of Service.