PaceMate

Privacy Policy

Effective date: 30 September 2026 · Last updated: 30 September 2026

1. Who this policy covers

This policy covers PaceMate, a New Zealand, native-first average-speed pace-awareness app for Android, and the account and sync services behind it. PaceMate is operated by Lowburn Ventures Limited, of 52 High Street, Invercargill 9810 ("PaceMate", "we", "us"). PaceMate is currently distributed as an invite-only beta via Google Play's internal testing track; this policy applies to that beta and to any later public release unless replaced by an updated version.

2. What we collect

We collect only what is needed to run the app, keep your trip history, and find and fix problems during the beta:

  • Email address. Used solely to sign you in via a one-time passcode (OTP) sent to your inbox. We do not use a traditional password.
  • Device information. Basic technical information (platform, app version, device model) used for support, compatibility, and diagnosing problems reported to us.
  • Trip summaries, sent after each trip ends. When you're signed in and a trip through a covered zone ends (whether completed or cancelled), a summary of that trip is sent to our servers so it appears in your trip history. The summary includes which zone and direction, start and finish times, duration, your estimated average speed and pace margin against the limit, the outcome, and a confidence rating. It is sent once, after the trip, and contains no GPS trace or coordinates. If the trip can't be sent straight away (for example, no signal), the app keeps it on your device and retries later.
  • Product analytics (PostHog). The app and our servers include PostHog, a product-analytics service. It is only active in builds and server environments where we have configured it. When active, it records a small set of usage events: app opened, sign-in succeeded or failed, trip started, trip completed (zone, outcome, duration), trip cancelled, and trip synced. These are linked to your account's internal ID, not your email address. It also records session replays of the app's non-driving screens (such as onboarding and choosing a zone), with text inputs and images masked. Session replay is switched off while a trip is live. No GPS coordinates are sent to PostHog.
  • Crash reports (Sentry). The app and our servers include Sentry, a crash-reporting service. It is only active where we have configured it. When active, it sends Sentry an error message, a stack trace, coarse device, OS and app-version details, and recent technical log entries, but only when something goes wrong. Location-like fields are removed before a report leaves your device.

PostHog and Sentry are overseas service providers that process this data on our behalf. Both store it in the European Union (EU).

3. What we explicitly do not do

  • We never transmit your live location while a trip is in progress. All pace and gate-crossing calculation happens entirely on your device.
  • We never upload a raw GPS trace. What reaches our servers is a post-trip summary, not a location trail.
  • We never sell your personal information to third parties, for any purpose.
  • We do not use your location or trip data to build a profile of your driving for any purpose other than showing you your own pace.

4. Background location, specifically

PaceMate requests background location access for two things. First, it can notice when you're approaching one of its known average-speed corridor zones, even when the app isn't open, so it can alert you. Second, once you've opened PaceMate, it can detect when you enter and exit a zone and calculate your pace across it, even with the screen off or the app in the background. That detection runs on-device. Background location is never streamed off your device, logged to our servers, or used for any purpose beyond that on-device detection, the pace calculation, and the corresponding on-device notifications.

5. Data retention and deletion

We retain your account and any synced trip summaries for as long as your account is active. You can request deletion of your account, and of any trip history synced to our servers, at any time by contacting us (section 7). We will action a deletion request within a reasonable time and confirm once it's complete. Deleting your account does not affect trip data that was never synced (for example, a trip still waiting to be sent), since we never had it — it only ever existed on your device.

6. Aggregate and de-identified data

We may use aggregated, de-identified trip data (for example, how many trips completed on a given corridor zone) to maintain and improve the route/zone data PaceMate ships with. Our internal admin tooling has no visibility into any individual's live or real-time position, ever — see PaceMate's own published product boundaries at docs/product-boundaries.md in the project's source repository for the full detail of this constraint.

7. Your rights and how to contact us

PaceMate is a New Zealand product, and where the New Zealand Privacy Act 2020 applies, you have the right to access the personal information we hold about you and to request its correction, consistent with the Act's Information Privacy Principles. To make a privacy request — including access, correction, or deletion — contact us at hey@logged.co.nz. If you're not satisfied with our response, you may complain to New Zealand's Office of the Privacy Commissioner (privacy.org.nz).

8. Changes to this policy

We may update this policy as PaceMate's beta evolves — for example, if what analytics or crash reporting collect changes (section 2). We'll update the "last updated" date above when we do. Material changes will be reflected in the app or on this page before they take effect.

9. Children

PaceMate is intended for licensed drivers and is not directed at children. We do not knowingly collect personal information from children.