Privacy Policy

Your trip data deserves careful handling.

Effective 17 September 2026 · Kmlog is operated in Australia.

1. What Kmlog does

Kmlog records the work trips you choose, lets you review trip details, and creates trip images and date-range reports. This policy explains the data used to provide those features and the Kmlog website.

2. Data we collect

  • Account information: email address, account identifier, sign-in provider, and a name when your sign-in provider supplies one.
  • Precise location and trip data: latitude, longitude, timestamp, accuracy, altitude, speed and heading while a trip is active.
  • Trip records: start and end times, distance, selected addresses, place labels, stops, optional work purpose, per-kilometre rate, calculated amount, selected vehicle and optional odometer readings you choose to enter.
  • Vehicle profiles and settings: vehicle names and details, stable profile identifiers, default and archived status, kilometre or mile units, recording preferences, report preferences, rate settings and place aliases used to recognise familiar locations.
  • Purchase information: subscription product, status and expiry information made available by Apple App Store or Google Play so Kmlog can unlock and restore KmPro access.
  • Website technical data: security, request and device information processed by our hosting provider to deliver and protect Kmlog.au.

Kmlog does not include third-party advertising and does not sell personal information.

3. How we use data

We use the information above to:

  • authenticate your account and keep you signed in;
  • record, calculate, display and synchronise your trips;
  • match routes to roads and suggest nearby addresses or businesses;
  • create images, PDF reports and immutable saved report snapshots you request;
  • apply and synchronise saved recording, report, rate, vehicle and place settings;
  • provide, restore and display subscription access;
  • deliver and protect the website and service; and
  • investigate errors and comply with legal obligations.

4. Location and background recording

Kmlog asks for precise foreground location to start a trip and background location so an active route can continue when the app is not visible or the screen is locked. Kmlog starts location recording only after you choose Start a trip and stops the location task when you choose Stop trip.

Your device may display a location indicator or an ongoing Android notification while recording. You can change location permission in system Settings, but disabling precise or background access may create route gaps.

5. Storage and service providers

Active trip data is written to the device first. When you are signed in and a connection is available, account settings, recording preferences, vehicle profiles and trip records are synchronised to Kmlog's Supabase-hosted cloud database. Row-level access controls restrict signed-in users to their own records.

Kmlog uses Apple services for iOS sign-in, maps, nearby places and App Store purchases; Google services for optional sign-in, Android maps and Google Play purchases; and Google Roads through an authenticated Kmlog server function to align recorded routes with roads.

Kmlog.au is delivered through Cloudflare-based hosting infrastructure, which may process request information and use essential security mechanisms to prevent abuse. These service providers process data under their own terms and privacy policies.

6. Sharing and generated files

Trip images and reports are created only when you request them. A saved report snapshot keeps the trip and vehicle values used when it was created, so later profile or preference changes do not rewrite that historical report. If you save or share a file, it leaves Kmlog through the destination you choose in the system share sheet. That destination then controls the copy you shared.

7. Retention and deletion

Trip and account data is kept while your account is active so it can remain available across devices. A trip you delete is removed from normal app views and marked for deletion during synchronisation. You can delete your account and associated cloud data from Settings > Account > Delete account and data. Local records for that account are also removed from the device.

Limited records may be retained where required for security, fraud prevention, financial reconciliation or legal compliance.

8. Your choices

You can stop a trip at any time, change location and notification permissions in system Settings, choose recording preferences, edit or archive vehicle profiles, omit optional odometer readings, edit optional trip details, archive or delete completed trips, sign out, export reports and delete your account.

9. Children and sensitive information

Kmlog is a work-recording tool and is not directed to children. Do not place participant health information, NDIS numbers or other unnecessary sensitive information in place labels or work-purpose notes.

10. Contact

For privacy questions or requests, email contact@qbwebsite.com.au.

11. Changes to this policy

We may update this policy when Kmlog changes or legal requirements change. The effective date at the top of this page identifies the current version.