Privacy.

What lapped does

lapped is a personal High Park lap counter. After you review this policy and choose to connect, it reads your Strava activity information and target segment efforts to detect completed High Park laps, then writes the lap receipt to your own Strava activity description. It does not alter activities without a completed matching lap.

Data lapped uses

To provide this, lapped uses the Strava profile information returned during authorization (your athlete ID and display name), authorization tokens, your connection time, the description-display settings you choose, and the activity/segment-effort information needed while an activity is being processed. lapped collects this through Strava OAuth and activity webhooks.

lapped also calculates a private summary for the connected athlete: lifetime High Park laps, current-year laps, and fastest lap. Connection metadata is visible only to the authorized lapped operator for support, security, and account administration. lapped does not sell Strava data, use it for advertising, create a public athlete directory, retain activity history, or show one athlete’s activity data to another athlete. lapped is compatible with Strava.

Retention and security

Your athlete ID, display name, connection time, and encrypted authorization tokens are retained only while you remain connected. Short-lived records used to prevent duplicate activity updates are removed within seven days. Private lap-summary values are cached for up to seven days, then refreshed or removed. lapped does not maintain a permanent activity archive, leaderboards, or cross-athlete rankings.

The iPhone preview uses a separate app session, stored securely on your device and represented by a hashed credential in lapped’s encrypted storage. App sessions expire after 30 days; signing out revokes that app session without disconnecting your Strava authorization. To show your past lapped rides and individual laps, lapped temporarily reads your own receipted activities and caches a history page in server memory for up to 30 minutes after its last scan step. These rides are visible only to your authenticated account.

Your choices

You can view the data lapped currently retains about your connected account at any time. You can disconnect from lapped at any time; disconnecting revokes lapped’s Strava access and deletes your lapped authorization and stored operational records for that account. You can also manage connected apps in your Strava settings.

For a data-access, correction, deletion, or privacy request, submit a request through the lapped home page and begin your message with “privacy:”.

Site requests, waitlist, and visits

lapped keeps limited, privacy-preserving visit counts to understand site reliability. It does not retain raw IP addresses for analytics. If you submit a feature or privacy request, lapped retains the message so it can be reviewed by the lapped operator.

If you join the waitlist, lapped stores the name, email address, optional Strava link, and submission time you provide. These details are visible only to the lapped operator and are used only to contact you when connection space becomes available. You can ask for deletion through the privacy request route on the home page.

Updates

If this policy changes materially, this page will be updated before the change takes effect. lapped is an independent project and is not affiliated with Strava.