overlay.fit

Privacy Policy

Last updated: 16 November 2026 Controller: Lidbit Ltd., a company registered in England and Wales. Contact: [email protected]

The short version

The rest of this policy is the long-form version, written in plain English, to meet UK GDPR / EU GDPR transparency requirements.

1. Who we are

The “data controller” for overlay.fit is Lidbit Ltd., a company incorporated in England and Wales. You can reach us at [email protected] for any privacy question, including requests to exercise your data-protection rights.

2. The data we process

2.1 Data that stays on your device

2.2 Data that leaves your device

WhoWhat they receiveWhy
Our Strava sign-in server (runs on Cloudflare Workers)When you connect Strava, and each time the app renews its Strava access: the one-time sign-in code or the refresh token, plus your device’s IP address. It passes Strava’s reply (your new tokens) back to the app, using the new access token once to look up your athlete ID from your Strava profile. It stores your Strava athlete ID, your current refresh token, when you connected and when the app last used the connection.It adds our app’s secret to the request so the secret never has to be shipped inside the app, and it keeps us under Strava’s limit on how many athletes can connect (see section 4). It never fetches or stores your activities.
StravaThe app’s requests for your activities, made directly from your phone with your access token.To import the activity you choose.
Google Firebase AnalyticsUsage events such as “a render was started”, “an activity was selected” and which source it came from, whether auto-sync worked, paywall views and purchases, and whether you are on the free or Pro tier, plus a random app-instance ID, device model, OS version, app version, approximate country (from IP address) and, on Android, the device’s advertising ID where available.To understand which features are used and where people get stuck.
Google Firebase CrashlyticsCrash reports: what the app was doing when it crashed, device model, OS and app version, and a random installation ID.To find and fix crashes.
Google Firebase Remote ConfigA random installation ID when the app fetches its settings.To switch features on or off without an app update.
RevenueCatAn anonymous app user ID, your purchase receipts and subscription status from Apple or Google, device and app version, and, if you entered a referral code, the code and the partner it belongs to.To validate your subscription and unlock Pro, and to credit referral partners. RevenueCat acts as our processor.
Apple App Store / Google PlayYour purchases, under Apple’s and Google’s own terms. We never see your payment details.Billing.
Google AdMob (free tier only)Device and ad-interaction data, IP address and, on Android, the advertising ID. Includes Google’s consent tool (User Messaging Platform).To show the rewarded ad before a free render.
Esri (only if you use the satellite map widget)Requests for satellite map tiles covering the area of your route, plus your IP address.To draw the map.

On Android, the app also reads the Google Play Install Referrer once, on first launch, to fill in a referral code if you installed from a partner’s link. It stays on your device unless you go on to use the code.

2.3 Apple Health and Health Connect

If you choose to import from Apple Health (iOS) or Health Connect (Android), the app asks for permission to read workouts and the related heart rate, distance, speed, power, cadence or steps, elevation and route data. It never writes to Apple Health or Health Connect.

This data is used only to draw the overlay on your video, on your device. It is never sent to us or to any third party, never used for advertising, and never sold. Our use of data from Health Connect follows the Health Connect Permissions policy, including its Limited Use requirements, and our use of HealthKit data follows Apple’s HealthKit rules.

2.4 Data we can see

Putting the above together, the only data about you that we (Lidbit) can see is:

There is no Lidbit account system, and we do not collect your name or email address in the app.

3. Why we process this data, and our lawful basis

ActivityPurposeLawful basis
Processing your video, workout and health data on your deviceThe rendering you asked forContract
Strava sign-in serverConnecting Strava and keeping within Strava’s athlete limitContract
Subscription validation (RevenueCat, Apple, Google)Unlocking Pro features you paid forContract
Referral attributionApplying a partner’s offer and crediting themContract
Crash reports (Crashlytics)Keeping the app workingLegitimate interests
Usage analytics (Firebase Analytics) and remote settingsImproving the appLegitimate interests
Rewarded ads (AdMob)Funding the free tierConsent for personalised ads in the UK and EEA; legitimate interests elsewhere
Satellite map tiles (Esri)Drawing the map widget you addedContract

Strava remains the controller of the data it holds about your Strava account, and Apple and Google remain the controllers of your billing data.

4. How long we keep things

5. International transfers

Google, RevenueCat, Cloudflare and Esri may process data outside the UK and EEA, including in the United States. They do so under their standard data-protection terms, which include the safeguards UK and EU law require for such transfers.

6. Children

overlay.fit is not directed at children under 13. You must be at least the minimum age required to enter into a binding contract in your country to subscribe. We do not knowingly collect any data from children.

7. Your rights

Under UK GDPR / EU GDPR you have the right to:

Because we don’t know who you are, please include your support ID (Settings → Copy support ID) and, for Strava, your Strava athlete ID or profile link, so we can find your records. Email [email protected] and we will respond within one month.

For data held by Strava, Apple or Google, you can also exercise your rights with them directly.

8. Cookies and tracking

The app does not use cookies or web tracking pixels. The identifiers it uses are described in section 2.2.

This website (overlay.fit) does not set cookies and does not embed fingerprinting scripts. It is served through Cloudflare, which processes your IP address to deliver the site and protect it from abuse.

We use Cloudflare Web Analytics to understand aggregate traffic to this site (page views, referrers, country, browser). It sets no cookies, stores no information on your device, does not fingerprint you and does not build a profile of you across sites. See cloudflare.com/web-analytics.

9. Security

Data on your phone is protected by your phone’s own security (app sandboxing and device encryption). Your Strava tokens are kept in the app’s private storage, which other apps cannot read. All connections from the app to our server and to third parties use HTTPS. Our Strava app secret is held only on our server, never in the app.

10. Changes to this policy

If we change this policy, we will update the “Last updated” date at the top of this page. For material changes we will also say so in the app’s release notes.

11. Contact

Privacy questions, data-rights requests or anything you’d like us to clarify: [email protected].

Postal address available on request.