Privacy policy

Context

This policy covers the Lappr app and lappr.app. We use data to count laps, save workouts, run accounts, process purchases, and fix problems. We do not use your data for advertising.

Camera and workouts

Lappr processes camera images on your device to count laps. Normal lap counting does not send video to our servers.

Your device stores workout details, including dates, time, distance, lap splits, goals, and counting evidence. If you enable diagnostic video, the recording stays on your device unless you choose to share it or send it to support.

Accounts, sync, and purchases

Sign in with Apple gives us an account identifier and any name or email address you share. We store these details and sign-in records to manage your account.

When you sign in, Lappr syncs your workout details and revisions to our servers for backup and restore. This sync does not include diagnostic video.

Stripe processes payments. We store purchase identifiers, amounts, currency, and payment status to verify your upgrade. Lappr does not store your full card number.

Free-workout records include account and device identifiers and allowance use. We use these records to manage the trial.

Apple Health and Strava

These connections are optional. You choose which workouts to send.

• Apple Health: With your permission, Lappr writes swim workouts and distance to Health. Lappr does not read your Health history.
• Strava: We store your athlete identifier, name, and access credentials to send selected workouts through our service. Strava controls the visibility of those activities under your Strava settings.

Crash reports and support

Lappr automatically sends crash and performance reports to Sentry. Reports can include device and app versions, diagnostic identifiers, errors, and recent app actions. They do not include video. Crash reporting currently has no in-app off switch.

Support uploads require your action. They can include your message, reply email, workout details, counting evidence, logs, and device details. You can also include diagnostic video. We use these files to investigate your report.

Service data and providers

The app sends an installation identifier, device model, operating system, app version, and check-in times. We use them to understand app use and maintain the service.

Cloudflare hosts our website and service data. Requests include technical information, such as your IP address, which helps deliver the service and limit abuse.

Pushover sends service alerts to the Lappr team. Alerts can include a name, device details, support reference, or a short part of your support message.

We use HTTPS and restrict access to stored account, workout, and support data. Apple, Strava, Stripe, Cloudflare, Sentry, and Pushover process data for the functions described here.

How long we keep data

• Support uploads are scheduled for deletion after 60 days. Separate diagnostic log uploads are scheduled for deletion after 30 days.
• Workout revisions remain on our servers until you delete your account. Deleting one workout can leave earlier revisions and local recovery copies.
• Account deletion removes your account profile, app sessions, and synced workouts. It does not remove local files or separate support reports.
• Installation records and free-workout records have no automatic expiry. Free-workout records remain after account deletion to prevent repeat trials.
• We keep other diagnostic and service records for support, service operation, and abuse prevention. Stripe keeps its own payment records.

Your choices

Change camera access in iPhone Settings. Change Health permissions in the Health app. Disconnect Strava from Lappr’s Connections screen.

To delete your Lappr account, open Connections, then Lappr Account, then Delete Lappr Account. Delete copies already sent to Health or Strava in those services.

For privacy questions or requests to access, correct, or delete data, email admin@acgao.com. Include your support reference when your request concerns a support upload. We may need to verify that the data belongs to you.

Policy changes

We will update this page when our data practices change. The date above shows the latest revision.