Privacy Policy

Effective date: 18 October 2026 · Version 2.7
Publisher: 3rd and Forward · Contact: support

English is the authoritative version of this policy. 日本語版はこちら（参考訳）。

1. Who we are

Pole Lap Logger (the "App") is developed and published by 3rd and Forward (the "Developer", "we", "us"). This policy explains what the App does with data. It applies to the App only.

The App is distributed through the Apple App Store and, for the Android version, through Google Play. The store you installed from is the seller of record for any purchase you make; we never receive your payment details.

2. What we collect

No account, and no server of ours for your recordings

The App has no account system and no login, and there is no server of ours that your recorded sessions are sent to. We do not collect, store or receive your name, email address, contacts, advertising identifiers, the sessions you record, or your videos.

Anonymous usage data, only if you say yes

The first time you open the App it asks, in a single question, whether you are willing to share anonymous usage data. If you decline, nothing is collected and the analytics component is never started at all. If you accept, you can turn it off again at any time with the “Share anonymous usage data and error reports” switch in Settings, and collection stops immediately.

While it is on, the App sends the following eleven events. Every value is a fixed choice from a short list, a number, or a yes/no — never text you typed.

• A recording is started — whether the circuit is a built-in one, one you made, or free cruising; whether the GPS source is a Bluetooth receiver or the phone itself; and whether a target session was set.
• A recording is finished — the number of laps, which of five duration bands the session fell into, and the circuit's country.
• A circuit is created — its latitude and longitude rounded to two decimal places (roughly 1.1 km, a precision that identifies a circuit rather than a place), the country, and whether the circuit has sectors and a pit lane. If no lines have been drawn yet, no coordinates are sent at all.
• The circuit editor is closed — how many times each editing action was used during that visit: placing a point by tapping the map, selecting a line on the map or in the list, dragging a pin or a whole line, typing coordinates, reversing a line's direction, reordering, deleting, undo and redo; and whether the circuit was saved. These are counts only — no coordinates, circuit name or country are sent with this event. Nothing is sent if you neither used an editing action nor saved the circuit.
• The analysis screen is closed — how long was spent in each of the two map modes and at what average zoom, how long speed annotations were visible, which graph axes were shown, and whether comparison, rev lines, the acceleration plot and vehicle gearing were in use.
• A session is exported — the file format only: GPX, CSV or NMEA.
• A video is linked to a session — whether it was chosen from the photo library or from files, whether it replaced a video that was already linked, how many video files it is made of (one, two or three, or four or more), and which of six length bands the video falls into.
• A video is exported with Video Overlay — which layout was used, which of five resolution bands the exported video falls into, which of the same six length bands the exported part falls into, and how the video was synchronised with the session: from the GoPro's GPS, from the capture time, by hand, or not at all.
• Linking or exporting a video fails — whether it was the link or the export that failed, and the kind of failure from a short fixed list, such as an unsupported format, photo access being denied, not enough storage, an interrupted export or a video that could not be encoded; for an export, also the same four details as for a completed export. Cancelling something yourself is not counted as a failure.
• The Premium screen is opened — where it was opened from.
• A purchase completes — which plan was bought: monthly, yearly or lifetime. No price and no currency.

None of the video events includes the video itself or any frame of it, its file name, where or when it was shot, its exact length, size or resolution, or the driver name or text you add to the overlay.

The analytics library additionally reports, on its own, that the App was installed, opened, updated, or sent to the background, together with the App's version and build number.

If the App crashes or hits an error it did not expect, and you have opted in, the App also sends a report of that error: the kind of error, its message, and the position in the App's own code where it happened. This goes to the same analytics service, under the same consent, and stops when you turn the setting off. The report is built from the App's code, not from your data: it does not include your recordings, the names you typed, your location or the contents of any file.

Every event also carries technical context that the analytics library attaches automatically and that the App cannot alter: the App's name, version and build number; the device's manufacturer, model, type and the name the device has been given; the operating system name and version; language and time zone; screen size and density; whether Wi-Fi, mobile data and Bluetooth are on; the analytics library's own version; and a random identifier it generates on the device for the session. We single out the device name because on Android it is a label you chose yourself, and some people put their own name in it; it is sent, but not kept — a filter on our PostHog project discards it as the event arrives, so no device name is ever stored, and like the IP anonymisation described in section 5 that is a property of our project configuration rather than something the App's own code can enforce.

Never collected: any name, note or free text you typed into the App — session memos, circuit names, vehicle names, file names, and the driver name or text you add to a video; lap times, sector times, speeds or any other telemetry from a recording; your videos and anything in them; your exact location; and any identifier that would let us recognise you. The App never creates a person profile with the analytics provider, and is configured so that no such profile can be created, so the events are not attached to any account or person.

We use this to see which features are actually used, so that the App can be improved, and to see the approximate areas where people create their own circuits, so that we can decide which official circuits to add next.

The App does not track you across other apps or websites and shares nothing for advertising, so it does not present an App Tracking Transparency prompt.

3. Data the App stores on your device

All of the following is created by you, stays in the App's private storage on your device, and is never transmitted to us:

• Recorded sessions: lap and sector times, GPS track points (position, speed, altitude, timestamp), accelerometer / G-force samples, session notes, and which GPS source recorded the session.
• Your circuits, control lines and sector definitions, including any you create or edit.
• Your vehicles and their settings (gear ratios, final drive, rev limit, speed correction).
• App preferences, such as the selected language, display settings, and the last-used circuit and vehicle.
• Bluetooth GPS device profiles, so a previously paired receiver can be reconnected.
• Your answer to the usage-data question, so that the App does not ask you again.

You can delete this data at any time by deleting individual sessions inside the App, or by deleting the App from your device — which removes all of it permanently. We cannot recover it for you, because we never had a copy.

Videos you use with Video Overlay

Video Overlay draws your lap data on top of a video you choose. The video is processed on your device and is never uploaded — not to us and not to anyone else. The App does not make a copy of it. To open it again later, the App keeps a reference to where the video already is (in your photo library, in Files, or in your Android device's storage), together with its file name, size, length, resolution, format and capture time, how it is synchronised with the session, and your overlay settings, including any driver name or text you enter.

To line the video up with the session, the App reads the time the video was shot from the video file (or, for a video in your photo library, the date the library gives it). If the video was recorded on a GoPro camera, the App also reads the GPS track the camera stored inside the video. This happens on your device; the GPS track is used only to work out the timing and is not kept.

When you export, the App creates a new video with the overlay drawn in and saves it to your photo library (iPhone and iPad) or your gallery (Android, in Movies/PoleLapLogger). A working copy stays in the App's temporary storage so that you can share it, and is removed when you start the next export. Deleting a session also deletes the link to its videos; the videos themselves stay where they are, and exported videos stay in your photo library or gallery until you delete them there.

Data you choose to export or share

The App can export sessions (for example as CSV, GPX or a shareable circuit file) and videos made with Video Overlay, and can open files shared to it from other apps. This only ever happens when you actively initiate it. Where the exported file goes — a messaging app, cloud storage, another device — is your choice, and the privacy practices of the destination service apply to it from that point on.

4. Device permissions and why they are requested

You can change or withdraw any of these permissions in your device settings at any time. Declining Bluetooth, Location or Photos disables the features that depend on them, but no other data is affected.

5. Third-party services

The App uses the following services. Each receives only what is listed and nothing more.

Apple (App Store / StoreKit)

Processes purchases and subscriptions, and provides the localised prices shown in the App. Apple is the seller of record and handles your payment information under Apple's Privacy Policy. We never see your payment method, billing address or Apple Account details.

RevenueCat

Manages the purchase receipt and tells the App whether your Premium entitlement is active. It assigns the App a randomly generated anonymous identifier, which is not linked to your name, your email address, or your Apple Account, and which we do not connect to any other information. RevenueCat also aggregates purchase information into sales and subscription reports that we can see. Those reports show totals — such as how many subscriptions are active — and never tell us who you are. See RevenueCat's Privacy Policy.

PostHog

Receives the anonymous usage events described in section 2 and stores them on its European cloud, inside the European Union. PostHog processes them on our instructions and does not use them for its own purposes. See PostHog's Privacy Policy.

Sending an event necessarily involves an IP address. IP anonymisation is enabled on our PostHog project, so the address is not retained and no location — city, region or postal code — is derived from it.

Google Maps

Maps shown in the App are provided by the Google Maps SDK. Displaying a map necessarily sends the map area being viewed to Google. This is governed by Google's Privacy Policy. We do not receive anything from Google about your use of the maps.

OpenStreetMap Nominatim, through our relay

When you search for a place while creating or editing a circuit, or when the App needs to determine the country of a location, the search text or the coordinates are sent to the OpenStreetMap Nominatim service to resolve them. From version 1.0.4, the App sends these requests to a small relay that we operate at geo.polelaplogger.com, which passes them on to Nominatim and returns the answer. Earlier versions of the App send them to Nominatim directly.

The relay does not record the search text, the coordinates or your IP address. It runs on Cloudflare, which processes each request, including your IP address, in order to deliver it (as it does for this website, section 12). Coordinates are rounded to three decimal places (about 110 metres) before they are passed on or kept. To avoid asking Nominatim the same question twice, Cloudflare may keep a successful answer, together with the search text or rounded coordinates it answers, for up to 24 hours; after that it is discarded. Your IP address may still reach Nominatim with the request, as it did when the App contacted Nominatim directly.

No identifier of you or of your device is attached to these requests. See the OpenStreetMap Foundation Privacy Policy and Cloudflare's Privacy Policy.

6. Purchases

Premium unlocks unlimited session storage and additional Video Overlay options. It is available as an auto-renewable monthly or yearly subscription, or as a one-time lifetime purchase. The entitlement is tied to your Apple Account, so restoring purchases on another of your devices re-enables it there.

Your recorded session data is not transferred between devices, by design — it is stored locally on each device and never synced. Your entitlement travels with your Apple Account; your data does not.

7. Children

The App is not directed at children and we do not knowingly collect any information from children. The optional usage data described in section 2 is anonymous and is not attached to any person, so there is nothing identifying a child for us to hold or to delete on request.

8. Your rights

Privacy laws such as the GDPR (EU/UK), the LGPD (Brazil), the CCPA/CPRA (California) and the APPI (Japan) give you rights to access, correct, delete, or obtain a copy of personal data a company holds about you, and to object to its sale. We hold no data that identifies you. The optional usage events described in section 2 carry no name, no account, no contact detail and no identifier we could match to you — and we keep it that way deliberately, which also means that if you asked us to hand over “your” events, we would have no honest way to find them. What we can offer instead is the control that actually matters: you decide whether they are sent at all, and you can withdraw that consent at any moment in Settings. We do not, and will not, sell or share personal data, because we have none.

The data that matters to you is on your device, under your control: you can view it, export it, and delete it in the App at any time. For anything Apple, RevenueCat, Google, OpenStreetMap, Cloudflare or PostHog holds, please exercise your rights directly with them using the policies linked in section 5.

9. Data security

Your session data is held in the App's private storage area, which the operating system isolates from other apps. Because your recordings and videos are never uploaded to us, there is no server-side copy of them to be breached. The optional usage events described in section 2 travel over an encrypted connection and are held by PostHog in the European Union; they contain nothing that identifies you, so a breach of them could not expose you. Protecting the device itself — a passcode, and keeping the OS up to date — is the most effective safeguard, and that part is up to you.

10. Changes to this policy

If the App starts collecting data that this policy does not describe, this policy will be updated before that version is released, the effective date and version number at the top will change, and the corresponding App Store privacy disclosure will be updated to match. We recommend reviewing this page after a major update.

Version 2.7 (18 October 2026) — in section 2, the list of ways a video can be synchronised with the session no longer includes a control line frame, because the App does not offer that method. Nothing else changed.

Version 2.6 (16 October 2026) — describes Video Overlay. Section 3 explains that videos are processed on your device and never uploaded, and what the App keeps to open them again; section 4 now covers reading the videos you choose from your photo library and saving exported videos, replacing the earlier statement that the App never reads your photo library; section 2 lists three new events about videos and, like section 9, mentions videos alongside your recordings. Section 6 now says that Premium also unlocks additional Video Overlay options, section 8 now also names Brazil's LGPD, the name of the usage-data switch in section 2 matches the App, the Developer's name is written as the registered trading name 3rd and Forward, and one sentence in section 13 was clarified.

Version 2.5 (12 October 2026) — section 2 now lists an eighth event, sent when the circuit editor is closed, with the number of times each editing action was used. Nothing else changed.

Version 2.4 (29 September 2026) — section 5 now explains that, from App version 1.0.4, place searches and country look-ups go to OpenStreetMap Nominatim through a relay we operate, which does not record them. The heading of the first part of section 2 and the list in section 8 were adjusted to match. Nothing else changed.

Version 2.3 (19 September 2026) — section 2 now also covers crash and error reports, sent to the same analytics service under the same opt-in consent. Nothing else changed.

Version 2.2 (6 September 2026) — added section 13, describing the sign-up form for the Android closed test; updated section 1 to say that the App is distributed through Google Play as well as the Apple App Store; and reworded the end of section 12 so that it reads correctly alongside the closed test sign-up page, which links out to a form hosted by Google. This is the first time the policy describes information that identifies you, and it applies only if you fill that form in. Nothing about what the App or this site collects has changed.

Version 2.1 (3 September 2026) — changed the contact address to support@polelaplogger.com. Nothing about what the App collects, where it is sent, or how you consent has changed.

Version 2.0 (27 August 2026) — added the optional, consent-gated anonymous usage data described in section 2, and PostHog as the service that receives it. Version 1.0 described an App that collected nothing at all, which is still exactly what you get if you decline the question shown on first launch.

11. Contact

Questions about this policy, or about privacy in the App, can be sent to support. We will reply as promptly as we reasonably can.

12. This website

Sections 1 to 11 describe the App. This section describes this website, and section 13 describes the sign-up form for the Android closed test.

The site uses Cloudflare Web Analytics to count page views. It sets no cookies, stores no identifier in your browser, and does not follow you between sites or between visits. What is recorded is limited to aggregate request information — the page address, the referring page, browser and device type, and country — from which you cannot be identified. See Cloudflare's Privacy Policy.

The site is served by Cloudflare, which processes the request itself, including your IP address, in order to deliver the page and protect the service. We do not receive your IP address.

There are no advertising or tracking scripts on this site and no cookies of any kind. The site itself collects nothing from you: the closed test sign-up page links out to a form hosted by Google, and what that form collects is described in section 13.

13. Android closed test sign-up

Before Pole Lap Logger goes on Google Play, the Android version runs as a closed test that people join through a sign-up form. This section describes that form. It applies only to people who fill it in — if you never open the form, nothing here concerns you, and it does not change anything in sections 1 to 11.

This form is the one place where we do ask for information that identifies you. We cannot register a tester on Google Play without an email address, so unlike the App, this is not anonymous.

What the form asks for. The Google account email address to register as a tester; a name or handle to address you by; your country or region; your Android phone model and Android version; which GPS you plan to use and, optionally, the receiver model; whether you drive or ride; optionally the circuits you run; whether you have track time coming up; whether you can keep the App installed for at least 14 days; the language you want replies in; and an optional free-text message.

What we do with it. Two things only: register your email address as a tester for the closed test on Google Play, and contact you about that test. The rest of the answers tell us whether the test group covers the devices, GPS sources and vehicle types the App has to work with, and they are used for nothing else. We do not use any of it for marketing, we do not add you to a mailing list, and we do not sell or share it.

Who else sees it. The form is a Google Form and the answers are held in Google Drive, so Google processes them on our behalf. Your email address is additionally entered into the tester list in Google Play Console, which is what allows Google Play to let you install the test version. Nobody else receives any of it.

How long we keep it. The form responses are deleted no later than 30 days after the closed test ends, and in practice as soon as the tester group is closed. Emails we exchange with you stay in our mailbox, as email does; ask us and we will delete those too.

Your choice, and how to withdraw it. Filling in the form is entirely voluntary and the answers are used on the basis of your consent. You can withdraw at any time — write to support and we will remove you from the tester list and delete your responses. You can also ask what we hold about you, or ask for it to be corrected, at the same address. Leaving the test does not affect anything in the App you already installed.

Google's handling of the data it processes for us is covered by Google's Privacy Policy.