LapSense

Privacy.

LapSense privacy policy · Effective November 1, 2026

  1. No account needed. Without one, sessions, laps and GPS traces stay on your phone unless you export them or move to a new phone.
  2. Cloud features start off. Backup, sharing, statistics and automatic crash reports have switches. Posting, publishing and Pit Wall need your action.
  3. Two things start on. Track naming, and the Google map when online, even without an account. You can turn both off.
  4. No ads. No ad tracking. We do not sell your data or share it for advertising.
  5. Delete your account. In the app, or by email from here. Some records and copies stay, as listed below.

01Who we are

LapSense is a lap timer for kart drivers. It reads positions from a GPS receiver over Bluetooth and times your laps. LapSense Studio, United States, makes the app and is responsible for your data ("we").

Privacy questions: privacy@lapsense.app. We answer within 30 days.

02Feature by feature

Without an account, your sessions, laps and GPS traces stay on the phone unless you export them or move to a new phone. Track naming, maps, local logs and feedback email work without an account. Cloud account features need sign-in.

For uploads to your LapSense account: turning a feature off stops new uploads. It does not erase old ones, and a send already in progress may finish. To remove old uploads, use a delete control in the app, write to us, or delete your account. Deleting your LapSense account does not delete request records held by the map or track name services.

The "Who sees it" lines describe access by app users. We can also read your cloud data, but only as section 06 describes. Google stores and processes it for us.

Track name lookup

On
Sends
One rounded position per saved track. It shows the area, not your exact spot. Also the app version and your internet address.
Who sees it
An OpenStreetMap search service, run by FOSSGIS e.V. in Germany, a separate organization. We do not run it.
Turn it off
Turn off track naming in the app's settings.

Google map

On when online
Sends
Requests for the map area on screen, to load map images, and your internet address.
Who sees it
Google
Turn it off
Choose "Track only" in the app's map settings.

Account

You choose
Sends
Your account number, email address, display name, how you sign in, whether your email is verified, and the app version at your last sign-in.
Who sees it
You. Your display name shows where you share.
Kept
Until you delete your account. Google keeps sign-in internet addresses a few weeks. Other sign-in data takes up to 180 days to remove after you delete your account.

An account is optional. You can sign in with Google, or with an email address and password. We use it to let you sign in and keep your data apart from everyone else's. We do not read your Google profile photo, contacts or anything else from your Google account.

Season backup

Off
Sends
This account's sessions and GPS traces, plus your drivers with their birth years, tracks, notes and settings.
Who sees it
Only you
Kept
Recent backups and one per month, until you delete your account.

Copies your season to your account, so you can restore it on a new phone. If you record your child as a driver, their data is in the backup too. Automatic backup waits for Wi-Fi or another connection without a data limit, unless you allow mobile data.

Sharing a driver's sessions

Off
Sends
After you turn sharing on, each finished session of that driver uploads with its laps and GPS trace. Earlier finished sessions upload too.
Who sees it
You, and people you give access. Access ends after 90 days, and you can end it sooner.
Kept
Shared sessions stay until you delete them or your account. Shared sessions you reset in the app move to a private archive, where they stay until you delete your account.

Lets a coach, team mate or parent see a driver's sessions. You turn it on for one driver at a time. You confirm that you are that driver, or the adult responsible, and give the driver's birth year. We check that birth year before sharing. We do not verify age. When someone opens a shared session, the app tries to record it, so you can see who looked. This is not a complete access history.

Leaderboard

Off, per lap
Sends
Your best lap on a track: driver name, lap and sector times, track and date. Never positions.
Who sees it
Every signed-in LapSense user
Kept
Until you delete them or your account.

Track catalog

Off
Sends
A track you learned, so others can time laps on it: its map and its name. The map is made from your GPS traces.
Who sees it
Signed-in users, if you publish it as public
Kept
Until you delete it or your account.

A public track needs a venue name from OpenStreetMap. That name does not prove the whole track is a public place, so check a track before you publish it.

Pit Wall

When you create or join
Sends
Your display name and account number, messages, whether they were seen, and whether each phone is online.
Who sees it
The two people in the channel
Kept
A channel ends after 12 hours. Its messages can stay while either person keeps an account. Google keeps connection records a few days.

Connects a pit crew phone to a driver's phone for short messages. You join with a short code. Ending a channel does not delete its history. The other person can still see it after you delete your account.

Usage statistics

Off
Sends
One record a day: how many sessions, laps and screens you used, which tracks you used, phone model, app version, account number.
Who sees it
You and us
Kept
Until you delete your account.

The session and lap counts cover every session on this phone that day. We use it to see which parts of the app work for drivers.

Diagnostics and crash reports

Off
Sends
The app's log and crash details, phone model, app version.
Who sees it
You and us
Kept
Logs uploaded with Send now or Send after a crash: about 90 days. Logs attached to emails follow the email rule in section 07. Crash reports: Google starts removing them after 90 days. Removal from all its systems can take longer.

The app keeps a short log on the phone to find bugs. It holds events, errors, and lap and sector times. The app does not write GPS positions to it.

  • Send after a crash also turns on Google's crash reporting at once. It receives crash details and a random number for this install. After the app stops unexpectedly, it sends its saved log the next time it runs.
  • Send now sends the log once, when you tap it. This works even when the switch is off.
  • Feedback email: if you attach the log, it goes to us through your own mail app.

03On your phone

The app keeps your season in its own storage on the phone: sessions, laps and sector times, the GPS trace of each session, drivers, karts, tracks and notes. It also remembers which receiver you use.

  • Other apps cannot read it, unless you export a file and choose where it goes.
  • Google's cloud backup of your phone does not include it.
  • Android's phone-to-phone transfer, with a cable or Wi-Fi, can copy it to a new phone.
  • It stays until you delete it in the app or uninstall the app.

04Location

Lap timing needs precise positions. They come from your GPS receiver over Bluetooth, not from the phone's own location.

  • The app reads live positions while your receiver is connected.
  • It saves a GPS trace only while a session records. Android then shows a LapSense notification.
  • Uploads you turned on, such as backup, can run in the background.
  • On older Android phones, Android asks for location permission before an app can look for Bluetooth devices. LapSense uses it only to find your receiver.

A GPS trace shows where you drove. It leaves your phone only through backup or sharing that you turn on, a file you export, or a move to a new phone. A track you publish holds a map made from your GPS traces.

05Google, our cloud

Google runs our cloud service. It receives the data of the features you use, your internet address and your phone type. Google processes it for us, on our instructions. It stores it in the United States and other places where it runs data centers. To use LapSense without account features, do not sign in. Sign-in itself contacts Google. Maps and track naming have separate controls.

Google's cloud terms describe its data protection and security duties. Track name lookup sends requests directly to FOSSGIS, an independent service operator. We do not control how FOSSGIS handles those requests.

Google has its own privacy policy. The app shows no ads. It does not track you for advertising.

06Who can see your data

  • You. Only your account can read your backups, logs and statistics.
  • People you share with, and only what you shared with them.
  • Other LapSense users see only what you post to the leaderboard or publish as a public track.
  • Us. We can read account data to answer a support request, find a bug or stop abuse. We keep a record when we read account data through our support tools. We also see service totals for uploaded sessions.
  • Google, as our service provider. Authorities, only if the law requires us to disclose it.

We do not sell personal data. We do not share it for advertising.

07Other records we keep

Records of access others gave you, and of sessions you opened
In their accounts, until those accounts are deleted
Our record of reading your account
As long as we need it to keep the service secure
Emails you send us
As long as we need them to answer you
Safety copies
Up to 30 days. Then they are gone.

08Deleting your data

In the app
Setup › Account › Account data › Delete account
Only some data
Turn a feature off and delete its data in the app. Or write to us and say what to delete.
The season on your phone
Reset it in the app, or uninstall the app. Resetting also starts moving shared sessions to your private archive. Stay signed in and online until it finishes. Uninstalling does not make shared sessions private.

09Your rights

Wherever you live, you can ask us to:

  • show you the data we hold. The app can export your account records. Ask us for a fuller copy.
  • correct it, or delete it.
  • give it to you in a file you can take elsewhere. The app can export your season.
  • stop a use you agreed to. Turn the switch off. That does not affect what was done before.

You can time laps without an account. Account features need sign-in data. Maps and track naming have their own switches. We do not make automated decisions about you that have legal or similar effects.

If you are in the EU or UK

  • We use your data to provide the features you ask for (contract), with your consent (sharing, usage statistics, automatic diagnostics), and for our legitimate interests (keeping the service secure, fixing bugs, naming tracks).
  • You can ask us to limit how we use your data. You can object to its use for security, bug fixes or track naming.
  • You can complain to us at privacy@lapsense.app, or to your data protection authority.
  • Your data is processed in the United States. Google, which stores it, is certified under the EU-U.S. Data Privacy Framework and its UK extension. Ask us at privacy@lapsense.app for details of these protections.

If you are in California or another US state with a privacy law

You have the rights above. We do not sell personal information or share it for advertising. We will not treat you differently for using your rights.

10Children

LapSense is not made for children under 13 to use on their own. An account is for people aged 13 or older. A parent can record a child as a driver on the parent's own account. That record stays on the phone, and in the parent's backup if backup is on.

We check the birth year you enter before sharing a driver or posting their laps. We do not verify age. If you think a child under 13 made an account, write to us and we will delete it.

11Security

  • Data is encrypted when it travels over the internet and when Google stores it.
  • Each account can reach only its own data, plus the sharing, public posts and Pit Wall access described above.
  • Backups are not locked with a key that only you hold. We can technically read them. We do so only as section 06 describes.
  • No system is perfectly secure. If a breach affects your data, we will tell you as the law requires.

12Changes and contact

If we change this policy, we change the date at the top. If a change matters for your data, we tell you in the app before it takes effect.

Everything else
feedback@lapsense.app
Contents