Back

Privacy Policy

Last updated: 2026-11-19

English · Svenska

Loop (“we”, “us”, “the app”) is a route-generation running and walking app operated by Martin Roman (“the developer”). This policy explains what personal data Loop collects, why, who it’s shared with, and what rights you have.

1. What we collect

Account information. If you create an account (email/password, Google sign-in on Android and the web, or Sign in with Apple), we store your email address, display name, the sign-in method you used, your subscription status (plan, trial period), and, for email sign-in, a hashed (not readable) password handled by our authentication provider. You can also use Loop without an account (“Continue without account”). In that case we don’t store any account-linked data, and settings/history are not saved between sessions on new installs.

Sign in with Apple. If you sign in with Apple, Apple confirms your identity and gives us a stable Apple user ID, your email address and, the first time only, your name. If you choose “Hide My Email”, we only receive a private relay address from Apple, which forwards to your real address. When you delete your Loop account, the app asks you to confirm with Apple once more and our server revokes Loop’s access to your Apple ID with Apple, so Loop no longer appears under Sign in with Apple in your Apple ID settings.

Location data (GPS). While you have an active running/walking session open, Loop uses your device’s GPS to generate your route and track distance, time, and pace. Location tracking continues in the background (for example with the screen locked) only while a session is active. On Android this is shown by a persistent notification; on iPhone, by the location indicator in the status bar. We do not track your location when no session is running.

Session and route history. If you’re logged in, completed sessions and any routes you choose to save are stored to your account so you can view your history and reuse saved routes. A session contains its route path (GPS points with time, speed, altitude and accuracy), distance, time, pace, maximum and average speed, elevation gain, and a name or note if you add one. GPS points and sessions are kept until you delete them or your account; we do not delete them automatically.

Copy on your device during a session. While a session is running, Loop keeps a copy of it (including its GPS points) on your device, updated about every 15 seconds, so the session can be recovered if the app closes unexpectedly or the phone restarts. When you finish a session, it is kept on the device until it has been saved to your account (if you are not logged in, until you log in, for up to 7 days). The copy is removed as soon as the session is saved or you discard it. It stays on your device and is not sent anywhere until it is saved to your account.

Subscription and payment status. If you subscribe to Loop PRO, our payment processing partner (RevenueCat, working with Google Play Billing on Android and Apple’s App Store on iPhone) tells us your subscription status (active/expired, plan type). RevenueCat identifies you by your Loop account ID, a random identifier (not your email address), which the app shares with RevenueCat to link purchases to your account. We never see or store your payment card details. Google Play or Apple handles the transaction directly.

Purchase verification (Android). Before a PRO purchase on Android, the app asks Google Play Integrity for a token proving that the app is genuine and unmodified, and our server checks that token with Google. This check does not include your location or session history.

Technical server logs. Our server functions (route requests, routing capacity control and purchase checks) run on Cloudflare. Cloudflare logs technical request data for each call, such as IP address, time, device and browser type (user agent) and the requested function. We use these logs only for operation and troubleshooting, never to build profiles of users, and they are deleted automatically after at most 7 days.

Advertising data. If you use the free version of Loop, you may be shown ads served by Google AdMob. AdMob may use an advertising identifier, an approximate location (derived from your IP address, or from your phone’s approximate location if you have allowed location access) and technical data to serve and measure ads. PRO subscribers never see ads. Users in the EEA, UK, and Switzerland are shown a consent screen before any personalized ads are shown, with an option to decline (“Do Not Consent”). On iPhone, Loop also asks for your permission through Apple’s App Tracking Transparency (ATT) prompt. The advertising identifier (IDFA) is only used if you allow it; if you decline, ads are still shown but are not personalized and the identifier is not shared. Your sessions, routes and precise location are never used for advertising.

We do not use any other third-party analytics tools (such as Google Analytics) in the app beyond what’s described above.

2. Who we share data with

We work with the following service providers, who process data on our behalf:

  • Supabase (provided to us through Lovable Cloud): hosts our backend database and authentication system (account data, session history, saved routes). The database is located in the EU (Ireland)
  • Google: Google Sign-In (optional login method on Android and the web), Google Play Billing (subscription payments on Android), Google Play Integrity (Android only: checks that the app is genuine before a purchase), Google AdMob (advertising, free tier only, on Android and iPhone)
  • Apple: Sign in with Apple (optional login method), App Store payments (subscriptions on iPhone), and App Tracking Transparency (your choice about the advertising identifier on iPhone)
  • RevenueCat: manages subscription status by reading purchase data from Google Play or the App Store, and receives your Loop account ID to link purchases to your account
  • Mapbox: provides the maps shown in the app. To draw the map around you and your route, the app requests map tiles for the area being shown from Mapbox, so Mapbox receives that map area (and therefore your approximate location while the map follows you), your device’s IP address, and anonymous usage data about map loads. Your route line itself is drawn on your device. When you search for an address or place as your starting point, the search text is sent to Mapbox’s place search, which also sees your device’s IP address. We use Mapbox’s temporary search, so the results are not stored
  • GraphHopper, and open-source routing services based on OpenStreetMap (BRouter/OSRM): calculate running/walking routes based on the coordinates you provide (your current location and chosen distance). GraphHopper is reached through our own server, so it sees our server’s address, not yours. The app also contacts the public BRouter and OSRM servers directly, which therefore see your device’s IP address together with the coordinates
  • Hetzner (data centre in Helsinki, Finland): hosts our own BRouter routing server, which calculates routes from the coordinates you provide. It may be used for any user, for example when GraphHopper’s daily capacity is used up. The app contacts this server directly, so it sees your device’s IP address together with the coordinates, in the same way as the public BRouter and OSRM servers above
  • Cloudflare: runs our server functions (route requests to GraphHopper, Google Play Integrity checks, routing capacity control), is the server the app connects to, and hosts this privacy policy and our account-deletion page
  • Lovable: hosts the web version of Loop and the endpoint that performs account deletion

These providers only receive the data necessary to perform their function (e.g., routing services receive coordinates, not your email; RevenueCat receives purchase/subscription status, not your GPS history).

Some of these providers are based outside the EU/EEA or operate global infrastructure (for example Google and RevenueCat). Where this involves transferring your personal data outside the EU/EEA, these providers rely on recognized legal safeguards, such as the EU-US Data Privacy Framework or Standard Contractual Clauses, to protect your data to the standard required by GDPR.

3. How long we keep your data

We retain your account, session history, and saved routes until you delete them or your account; there is no automatic deletion of inactive accounts. If you use Loop without an account, nothing is stored in our database after your session ends.

Deleting your account. Deleting your account in the app (Profile → Delete account) removes your login account (including your email address), profile, subscription record, session history, GPS points, and saved routes from our database immediately and permanently. If the option does not work in your version of the app, update Loop from Google Play or the App Store, or use our account-deletion page (/delete-account) or email us at loopsupport.app@gmail.com; we handle those requests within 30 days. Copies may remain in our hosting provider’s daily database backups for up to about 14 days. Deleting your account does not cancel an active subscription: you cancel a Google Play subscription in Google Play, and an App Store subscription in your Apple ID settings (Settings → your name → Subscriptions). If you signed in with Apple, deleting your account also revokes Loop’s access to your Apple ID, as described above. Records that Google Play or Apple keep for tax and accounting purposes are outside our control. RevenueCat may retain subscription records linked to your random account ID in accordance with its own privacy policy. Technical server logs (such as IP address, time and the requested function) are not linked to your account profile, are not removed by account deletion, and are deleted automatically after at most 7 days.

4. Your rights (GDPR)

If you’re located in the EU/EEA/UK, you have the right to:

  • Access the personal data we hold about you
  • Correct inaccurate data
  • Delete your data: you can delete your account directly in the app (Profile → Delete account), or via /delete-account or by email, which removes your account, session history, and saved routes
  • Restrict or object to certain processing
  • Data portability: request an export of your data in a machine-readable format
  • Lodge a complaint with your national data protection authority. In Sweden, this is Integritetsskyddsmyndigheten (IMY)

To exercise any of these rights beyond in-app account deletion, contact us at loopsupport.app@gmail.com.

5. Advertising and the AdMob consent choice

If you’re in the EEA, UK, or Switzerland, Loop shows a consent message the first time ads would be relevant, letting you choose to consent to personalized ads, decline (“Do Not Consent”), or manage detailed options. You can change this choice later on the Profile page (look for “Ad preferences”, shown only where consent is required), or by clearing the app’s data or reinstalling it, which will show the consent screen again. On iPhone, you can change your App Tracking Transparency choice at any time in Settings → Privacy & Security → Tracking.

6. Cookies

This policy covers the Loop app. Our website (loop-web) uses only essential, functional cookies required for the site to work. There are no tracking or advertising cookies.

7. Children

Loop is intended for users aged 18 and over and is not directed at children. We do not knowingly collect personal data from anyone under 18. If you believe a child has provided us with personal data, contact us at loopsupport.app@gmail.com and we will delete it.

8. Changes to this policy

We may update this policy as Loop changes. Material changes will be reflected here with an updated “Last updated” date. Continued use of Loop after changes take effect means you accept the updated policy.

9. Contact

Questions about this policy or your data: loopsupport.app@gmail.com