LogPoint is built for Australian tradies, sole traders, subcontractors, and small crews who drive between sites and want cleaner mileage records.

Does it work with multiple vehicles?

Yes. LogPoint supports multiple vehicles inside the app so users can keep work vehicles organised separately.

Is it only for the cents-per-kilometre method?

No. The product is useful for general mileage record-keeping, while the export flow currently emphasises ATO-ready tracking.

What if I care about privacy?

Privacy is a core part of the product. LogPoint is designed around local storage so users do not need a cloud-first workflow just to track trips.

How much does LogPoint cost?

LogPoint is free to use for core mileage tracking. Premium features are available for tradies who need advanced reporting.

LogPoint

Privacy Policy

Last updated: 9 July 2026

Overview

LogPoint is a mileage tracking app for tradies and small businesses. Most trip, vehicle, receipt, and settings data stays on your device. When you create an account, buy Pro, or buy iBeacon hardware, we process the account, billing, and fulfillment details needed to provide that service.

What We Store on Your Device

If you use LogPoint as an individual, app records such as trips, vehicles, receipts, receipt photos, settings, and local profile details are stored on your device. Account and billing records are stored in Supabase and Stripe so purchases can attach to the correct LogPoint user. If your organisation uses LogPoint Teams, some of your business-trip data is also shared with your organisation — see “LogPoint Teams” below. Receipts and receipt photos are never uploaded.

Accounts, Payments, and Hardware Orders

Web checkout requires a Supabase account. We use your Supabase user ID as the app user ID across Stripe and RevenueCat. Stripe processes payments and tax; RevenueCat manages Pro entitlement state; Resend may send account, billing, and fulfillment emails. Hardware orders store shipping and tracking details needed to ship from Australia.

Permissions and Why We Need Them

Location (including background)— to calculate trip distance via GPS while you drive. For individual users, location data is processed on-device and stored locally as part of your trip history. If your organisation uses LogPoint Teams, location from your business trips is also shared with your organisation as described in “LogPoint Teams” below.
Bluetooth — to detect when you connect to your vehicle and automatically start or stop trip tracking.
Camera and photo library — to capture or import receipt photos. Photos are stored locally and never uploaded.

LogPoint Teams (Organisation Accounts)

This section applies only if your organisation uses LogPoint Teams and you are a member of that organisation. If you use LogPoint as an individual, the data sharing described here does not apply to you — your trip and location data stays on your device as described above.

Who controls your data in Teams.When your organisation enables LogPoint Teams, your employer decides that tracking is used, who can see it, and why. Your employer is the controller of the trip and location information shared through Teams, and Kaizen Arc acts as a processor handling that information on your employer's instructions. Requests to access or correct your records, or questions about why your organisation uses tracking, may need to be directed to your employer as well as to us.

What is shared with your organisation. For business trips you log as a member of the organisation, the following is uploaded from your device and made visible to authorised managers and admins in your organisation:

trip start and end times, and total distance;
the approximate GPS route of the trip, and the start and end locations (coordinates and, where available, addresses);
the vehicle used and whether the trip was detected automatically;
the identifier of any LogPoint iBeacon paired to the vehicle.

We also periodically upload a device status report so your organisation can see that tracking is working. This report contains your app version, device platform, whether trip monitoring is switched on, your location-permission setting, and the recent proximity times of paired iBeacons. This status report contains no location or coordinates.

What is not shared with your organisation.

Personal trips are never shared as location.When a trip is marked personal, only its distance and times are uploaded — no route, no start or end coordinates, no addresses, and no beacon identity. This redaction is enforced both on your device and again on our servers.
We do not share your trips, routes, or location with an organisation you are not a member of, or after you leave one.
We do not track you when no trip is active.

Who can see it. Within your organisation, shared business-trip information is visible to members with manager or admin roles, scoped to your organisation only. Members of other organisations cannot see it.

How long it is kept.Trip records shared with your organisation are kept for as long as your organisation's LogPoint Teams account is active, and afterwards only for as long as required by Australian tax and record-keeping law or to resolve disputes. If your organisation's account is closed, or you are removed from it, shared data is handled in accordance with our agreement with your organisation and applicable law.

Your controls.Marking a trip personal removes its route and location from what your organisation sees. You can revoke location or Bluetooth access in your device Settings > LogPoint at any time (this may stop automatic trip detection). You may ask us or your organisation to access or correct your records.

Service providers. To provide LogPoint Teams we share the information above with service providers who process it on our behalf under contract, including Supabase (database and authentication), Amazon Web Services (hosting), Stripe (payments), RevenueCat (subscription entitlement), Resend (email), and Sentry (crash and error reporting). A current list is available on request at privacy@logpoint.com.au.

Workplace tracking and your rights. Your employer is responsible for notifying you about workplace tracking in advance and as required by law before tracking begins. If you have a concern about how your location or trip data is handled, contact us at privacy@logpoint.com.au or raise it with your employer. You may also complain to the Office of the Australian Information Commissioner at oaic.gov.au.

Crash Reporting

LogPoint sends crash and error reports to Sentry, our monitoring provider. We use this for one reason: automatic trip detection is technically complex, and crash reports are how we find and fix the bugs that cause missed or inaccurate trips — without relying on you to report them manually.

These reports include crash details, device metadata, and technical breadcrumbs — for example, Bluetooth connect and disconnect events and trip start/stop steps — that help us trace what went wrong. Reports are not tied to your name or your payment details.

Crash reporting is optional. You can turn it off at any time in the app under Settings > Crash reporting. With it off, no crash or error data leaves your device.

Deleting Your Data

Deleting the app removes local app records from your device. If you created an account or made a purchase, contact us to request account deletion or billing-record help. Some tax, fraud-prevention, and transaction records may need to be retained where the law requires it. To revoke location, Bluetooth, or camera permissions, go to your device's Settings > LogPoint.

Contact

Questions about privacy can be sent to privacy@logpoint.com.au.