Privacy Policy

What we collect

• Account data: your email address and a unique account ID, created when you sign in (with Apple, with Google, or with email). If you use Apple’s “Hide My Email”, we only receive the relay address; if you sign in with Google, we receive the email address of your Google account.
• Session and lap data: the recording files your lap timer produced, whether the app downloaded them or you imported them yourself, including GPS traces of your driven laps, lap and sector times, speed, and vehicle sensor channels. These files contain precise location data recorded by your lap timer (not by your phone).
• Lap timer details: when the app connects to a lap timer over WiFi or Bluetooth, it reads the timer’s model, serial number and firmware version. The serial number is stored with the session that timer recorded and is sent with that session, so a session can be traced back to the hardware that made it. Nothing else comes out of the timer: it holds no personal data of yours. If your RaceBox has a memory security code, that code stays on your phone and is never sent to us.
• Session files: the recording file itself is uploaded to your own private storage when you have Pushlapp Apex, which is what makes cloud backup and restore work. Without Apex the file stays on your phone and only your session, lap and vehicle records sync. Two cases upload the file on every plan: a session that imported with no laps, and a session whose track we could not identify with confidence. Those are the two we cannot diagnose from the records alone.
• Vehicle details: the vehicle type, brand, model, and year you enter.
• Session notes: the free text you write under a session (setup, feel, what to try next). Notes sync to your account so they follow you to a new phone. They are private to your account, never travel with a lap you publish or send, never appear in the Paddock, and are never read by any automatic feature.
• Profile data (optional): if you choose a username to use the Paddock (Pushlapp’s social features), we store that username, your optional display name, who you follow, who you block, laps you publish, share or send, and reports you file about other users’ content.
• Usage events: feature-usage events (for example: app launch, session downloaded, lap published, racer followed, lap shared or exported, leaderboard viewed), stored as just the event name tied to your account ID and used to count active users and feature adoption. An event carries nothing else: no location, no lap times, no track names.
• Diagnostics logs: when the app connects to a lap timer, or downloads or imports a session, it sends a technical log of that attempt, tied to your account ID. The log contains the timer’s model, serial number and firmware, your phone model and operating system version, the app version, timings, the name the timer gave the session, and any error that occurred. Where a session was imported it also names the track the session was matched to and how many laps it produced. It never contains your GPS trace, your lap times, or the session file itself. These logs are part of the service and cannot be switched off; they are sent only while you are signed in, and they are deleted automatically after 90 days.
• Feedback you send: if you send us feedback from the app, we receive the message you typed, your account ID, and the app version.
• Subscription status: if you subscribe to Pushlapp Apex, the App Store or Google Play confirms the purchase to our server so your account is unlocked. We receive the purchase identifier and which subscription it is. We never see your card or payment details.
• Session digests: for every session you import, the app uploads a small diagnostic sketch (about 3 KB): your GPS line reduced to five samples per second, the lap time records, and the track name your lap timer stored. We use it to verify and improve the track database and to diagnose import problems. It cannot reconstruct your full session and is not a backup. Digests are deleted automatically after 90 days.
• Coaching Insights facts (Apex): when you open Coaching Insights for a track day, the numbers behind the analysis (lap, sector and corner times and speeds, computed on your device) are sent to our server together with the track name, the date, and the times of day your sessions ran. See “Coaching Insights” below for how they are processed.
• Track gap reports: when you import a session recorded at a track the built-in track database does not recognize, the app reports a coarse location for where you were riding (rounded to roughly 110 meters), the month of the recording, the approximate lap length, and the app version, so missing tracks can be added to the database. The report contains no lap times, no GPS trace, and no session content; it is sent at most once per track per device; and we do not store it linked to your account.

We do not collect your phone’s location, contacts, photos, advertising identifiers, or any data for advertising or tracking purposes.

Why we collect it (legal basis)

• To provide the service (GDPR art. 6(1)(b), performance of contract): cloud backup of your sessions, your session notes, the Paddock social features you opt into, leaderboards, Coaching Insights, your subscription, synchronization across your devices, and the track contributions and start/finish lines you choose to submit.
• To improve the app (GDPR art. 6(1)(f), legitimate interest): the usage events, track gap reports, diagnostics logs, and the feedback you send us, to understand how many people use Pushlapp, to keep the track database accurate, and to find and fix connection and download failures on hardware we cannot reproduce.

Coaching Insights

Coaching Insights (part of Pushlapp Apex) turns a track day’s numbers into a short written analysis. The numbers are computed on your device. Our server sends them, with the track name and your app language, to Anthropic, a large language model provider, which phrases the analysis. Anthropic receives no account details: no name, email address, username or account ID, and no GPS traces or session files. The resulting text is cached in your account so the same day is not processed twice.

The track database

Pushlapp ships with a built-in database of race tracks, and recognizing which track you rode happens on your device, against that built-in database: no track lookup leaves your phone. The database is built from open data sources: OpenStreetMap (© OpenStreetMap contributors, licensed under the Open Database License) and Wikidata. Track gap reports (above) are how we learn about tracks the database does not cover yet, and racers can add a missing track from their own laps (see Sharing and visibility).

Start/finish lines. A recording from a RaceBox holds no lap markers, so the app has to work out which start/finish line to cut the laps on. To do that it asks our server which lines are already known at the coordinate where your recording starts, and when the app starts it re-checks the lines your RaceBox sessions were cut on. Those requests carry a coordinate and nothing else: no lap times, no trace, no session content. They travel over your signed-in connection.

Track data updates. About once a day the app asks our server whether newer track data is available, and downloads it if there is. That request carries only the version of the data format and which release channel the app is on: no account details, no location, nothing about your sessions. If an update is refused because it does not fit the tracks in your library, a diagnostics log records the reason, and that reason can name a track you have ridden.

Where your data lives

Your data is stored by Supabase (our hosting processor) in the European Union (Ireland, eu-west-1). A data processing agreement is in place with Supabase. For Coaching Insights we additionally use Anthropic (United States) as a processor, under a data processing agreement, to generate the analysis text; what Anthropic receives is described above. The sign-in codes we email you are delivered by ZeptoMail (Zoho Corporation), which processes them in the European Union, under a data processing agreement; it receives only your email address and the code itself. We use no other data processors. Two other companies see something because of how the app is built: on Android the replay map is drawn by Google Maps, so Google receives the map area you are looking at (on iPhone the map is Apple’s own MapKit and stays with Apple), and if you sign in with Apple or with Google, that provider knows you signed in to Pushlapp. We do not sell or share your personal information with anyone else.

Sharing and visibility

Your data is private by default. Everything you record stays invisible to other users unless you take an explicit action:

• Choosing a username makes your username, display name, membership badges, aggregate riding statistics (session, lap, and track counts, and follower counts), and the list of tracks where you have published laps visible to signed-in Pushlapp users. Without a username you are invisible to other users.
• Publishing a lap (a per-lap, explicit choice) makes that lap, its time, track, vehicle brand and model, and full replay including the GPS racing line, viewable by Pushlapp users, and places it on that track’s leaderboard for its vehicle class, ranked under your username. You can make it private again at any time, with immediate effect; that also removes it from the leaderboard.
• Sending a lap to a specific racer shares it as a reference lap with only that racer, without making it public. You can stop sharing at any time, with immediate effect on our servers; the recipient’s device may retain a previously downloaded copy, as with any shared file.
• Exporting a lap file creates a .lapreplay file (the lap’s replay in a portable format) outside Pushlapp. Anyone who has the file can import and view that lap; an export cannot be revoked. Laps you import from files stay private in your own library.
• Adding a missing track (an explicit, per-track choice) sends us the track’s location, the name you propose, the outline shape derived from your laps there, and how many laps and sessions that outline is based on. It does not include your session, lap times, dates, or speeds. We store it with your account so we can review it and you can delete it. If we add the track to Pushlapp, the outline becomes part of the app’s track database for all users and stays there even if you later delete your account; your name is not attached to it.
• Placing a start/finish line (an explicit choice, offered when a recording came in with no laps) sends us the line you placed and the venue it belongs to. We store it with your account, and until we approve it, it is used only for your own sessions. Once approved it becomes the line Pushlapp uses at that venue for everyone; an approved line stays in place if you later delete your account, with your account unlinked from it.
• Your private laps, your full track history, your email address, your session notes, and your vehicle list are never visible to other users.

You can block other users (hiding you from each other entirely) and report content; reports are reviewed by us.

How long we keep it

Until you delete it. Deleting your account (in the app: Settings → Account → Delete account) permanently removes your account and all stored data: sessions, laps, vehicles, uploaded files, session notes, your profile and username, follows, blocks, shares and reference laps, Coaching Insights texts, pending track contributions, feedback you sent us, usage events, and diagnostics logs. This is irreversible and satisfies your GDPR right to erasure. The exceptions are a track outline we already added to the app’s track database and a start/finish line we already approved, as described under Sharing and visibility; both persist with no account attached. Diagnostics logs are also deleted automatically after 90 days, even if you never delete your account. Data on your own device remains under your control.

Your rights (GDPR)

You can request access to, correction of, or deletion of your personal data, object to processing, or request data portability. Deletion is built into the app; for anything else, email hello@pushlapp.com. You also have the right to lodge a complaint with your data protection authority (in the Netherlands: Autoriteit Persoonsgegevens).

California residents (CCPA)

We do not sell your personal information, and we have not done so in the preceding 12 months. Because we don’t sell data, no “Do Not Sell My Personal Information” opt-out is required. This section serves as that disclosure.

Children

Pushlapp is not directed at children under 16 and we do not knowingly collect their data.

Changes

We will post any changes to this policy on this page and update the effective date above. Material changes will be announced in the app.