Lope

Lope privacy policy

Last updated: 16 November 2026

Lope is an app for recording and logging runs and walks. This page says what information Lope handles, where it is kept, who else is involved, and how to remove it.

In short

Who runs Lope

Lope is run by Chirag Bhugra, referred to below as "we". You can reach us at ichiragbhugra@gmail.com.

What the app keeps on your phone

These stay in the app's private storage on your phone. We cannot see them.

Information Why the app has it
Your activities: sport, start time, duration, distance, elevation, title, notes and effort rating This is your training log
The detail of each recording: position, altitude, GPS accuracy, speed, pauses and, when available, heart rate, second by second To draw the map, splits and charts
Settings, such as units and appearance To remember your choices
Your precise location, only while a recording you started is running To record your route

Location is read only during a recording you started. Lope never asks for location in the background. The phone's automatic cloud backup of app data is switched off for Lope, so this information is not copied to a cloud drive without you knowing.

What an account keeps on Lope's server

An account exists only if you choose to sign in with Google or Apple. It holds:

Information Why
Your name and email address, as given by Google or Apple when you sign in To show you which account you are signed in to
The identifier Google or Apple uses for you, and which of them you signed in with To recognise you the next time you sign in
Sign-in records: a random session key, when it was created and when it expires To keep you signed in on your phone
The keys Google issues to Lope for your Google account (an access token and a refresh token), stored encrypted To sign you in, and, once you connect Google Health, to let your phone read your heart rate from Google

The server does not hold your activities, your location, your heart rate, a password or your profile picture. It does not keep your network address or the name of your browser with your sign-in records.

When you sign in, Lope asks Google or Apple for your name and email address and nothing else. Access to Google Health is asked for separately, only when you choose to connect it. Before either page opens, the app tells you what will be shared and why.

Google Health data

If you connect Google Health, Lope reads one kind of information: your heart rate, for the times of activities you recorded in Lope. It asks for a single read-only permission. It does not read sleep, steps, weight or anything else, and it never writes to Google Health.

While Google reviews Lope, Google lets only invited testers give this permission, so the app offers Google Health only to them. The email addresses of invited testers are kept in a list in the server's settings, and nowhere else. An address is taken off the list when Google Health opens to everyone, or when its owner asks.

How it travels:

  1. Your phone asks Lope's server for a short-lived key for your Google account.
  2. Your phone uses that key to read your heart rate directly from Google.
  3. The readings are saved with the activity, on your phone.

Lope's server keeps only the encrypted keys. It never receives, stores or passes on your heart rate.

Lope's use of information received from Google Health APIs adheres to the Google Health API Developer and User Data Policy, including the Limited Use requirements. Lope's use of information received from Google APIs also adheres to the Google API Services User Data Policy, including the Limited Use requirements. In particular:

You can disconnect Google Health at any time in the app, under Settings, Heart rate, Disconnect. Disconnecting withdraws Lope's access with Google and removes the keys from Lope's server. You can also remove Lope's access from your Google Account's settings for third-party apps. Heart rate already saved with your activities stays on your phone until you delete those activities.

Sync between your phones

Sync is off unless you turn it on, and for now it is open only to invited testers. With sync on, your phone encrypts your activities, their recordings (including heart rate and notes) and your settings before they leave it, with a key that only your phones hold. Lope's server stores these encrypted copies and cannot read them. Alongside them it keeps what it needs to pass them between your phones: an identifier made from each record that reveals nothing about it, a revision number, its size and when it was uploaded, and your phones' key in a form that only your recovery key opens.

When you turn sync on, the app shows you a recovery key once. It is never sent to Lope's server, and Lope cannot recover it. Without it, nobody can open the copies on the server, Lope included.

Turning sync off, from any of your phones, removes everything kept for it from Lope's server. Deleting your account does the same. Your phones keep their own copies.

Other servers the app contacts

Service When What it receives
OpenFreeMap, for map tiles Whenever a map is on screen The area of the map being shown, and your phone's network address. No account, no route and nothing about your activities. Your route is drawn on your phone
Expo, for app updates When the app starts The app's version, your phone's platform, its network address, and a random identifier made for this installation of the app. Expo uses the identifier to deliver updates and to count how many installations have each one. It is not linked to your account, and it goes away when you remove the app. Nothing about you or your activities
Lope's own server Only if you use an account What is described under "What an account keeps on Lope's server" and, if you turn sync on, under "Sync between your phones"

Cookies, logs and limits on misuse

No advertising, analytics or tracking

Lope contains no advertising, no analytics and no tracking tools. The one count kept is Expo's count of how many installations have each app update, from the random identifier described above. No other company's software in the app can read your location or health information. We do not sell information about you and we do not share it with anyone except the service providers listed below, who handle it only to run Lope.

Who else handles information

Provider What it does for Lope What it handles
Cloudflare Runs Lope's server, and stores the encrypted sync copies Requests to the server, including network addresses, and the encrypted copies, which it cannot read
Neon Hosts the server's database, in Singapore The account information listed above
Google Sign in with Google, and Google Health What you agree to on Google's own page
Apple Sign in with Apple, when you use it What you agree to on Apple's own page
OpenFreeMap Map tiles Map areas requested and network addresses
Expo Delivers app updates App version, platform, network addresses and a random identifier for each installation

Google's and Apple's own privacy policies apply to what you do on their pages.

How long information is kept

Deleting your account and your information

Either way, Lope first withdraws its access with Google, then removes your account, your sign-in records and Google's keys from the server straight away. Nothing about you is kept afterwards, apart from the short database history described above.

Deleting your account does not touch what is on your phone. To remove that as well, delete the activities in the app, or remove the app.

Your choices and rights

You can use Lope without ever creating an account. If you have one, you can see the name and email address it holds in the app, under Settings, Account. They come from Google or Apple, so they are changed there. You can ask us for a copy of the information the server holds about you, or ask us to correct or delete it, at the contact address above.

Depending on where you live, the law may give you further rights, including the right to complain to your data protection authority.

Security

Everything sent between the app and the server is encrypted in transit. Google's keys are encrypted in the database. On your phone, your sign-in is kept in the phone's encrypted store. Lope has no passwords to lose: signing in is handled by Google or Apple.

No system is perfectly secure. If we learn that your account information has been accessed by someone who should not have it, we will tell you.

Where information is processed

The account database is in Singapore. Cloudflare may handle a request at a location near you before it reaches the database. If you use an account, your account information is therefore processed outside your own country.

Children

Lope is not directed at children. Accounts are for people aged 18 or over. We do not knowingly keep account information about a child. If you believe a child has created an account, contact us and we will delete it.

Changes to this policy

When this policy changes, the new version is published on this page with a new date. If a change affects what information is collected or how it is used, the app will say so before the change takes effect.

Contact

Chirag Bhugra ichiragbhugra@gmail.com