Privacy Policy

Last updated September 16, 2026. Lap Track Racing is a beta project.

Activity files

When you load a FIT, GPX, or TCX file, Lap Track analyzes it in your browser. The file and the resulting analysis are not uploaded to Lap Track’s servers by the file-analysis workflow. Your browser may retain local settings and temporary data until you clear them.

Strava beta integration

The optional Strava integration uses Strava OAuth to access activities you authorize. Lap Track stores the authorization token on its server so it can request the selected activity. Activity summaries may be cached in your browser for 15 minutes for Recent, 6 hours for This year, or 24 hours for an individual past year. Full activity streams are not stored in the browser cache. We do not sell activity data or use it for advertising.

You can disconnect Strava from Lap Track at any time. Disconnecting removes the server-side authorization for the current account and clears the browser’s cached Strava activity lists. Strava access can also be revoked from your Strava settings.

Analytics

Public pages load a privacy-focused analytics script hosted at analytics.henryvandenbroek.com to measure page usage. It is used for aggregate product insights and is not used to read the contents of your activity files.

Contact

For privacy questions, use the contact page.

Legal basis and rights

For the beta Strava integration, processing is based on your authorization and the operation of the requested service. Cloudflare Workers and KV provide the hosting, session, and token storage infrastructure. OAuth tokens are retained only while the Strava connection is active and are deleted when you disconnect or the authorization is rotated out. You may request access, correction, deletion, or clarification about personal data held for the service by using the contact page. You may also revoke Strava access from your Strava settings.