Privacy policy
MovenRun is a walking and running game. It uses your location while you play to draw your route and measure your progress. This policy explains exactly what we collect, why, who processes it, how long we keep it, and how to delete it.
Who we are
MovenRun is developed and operated by Team MovenRun ("we", "us"). For any privacy question or request, email info@movenrun.xyz.
Summary
- Location is used only while the app is open and you are in a movement session, or when you tap Locate me on a map. MovenRun never tracks you in the background.
- You can play without an account. Your progress then stays on your phone.
- You can sign in with Google or with a crypto wallet. With Google we receive your email address and basic profile; with a wallet we receive only your public wallet address. We also store a summary of each session you save. We do not store your raw GPS route on our servers.
- We do not sell your data, show ads, or use advertising or analytics trackers.
- You can delete your account and its data in the app or on our account deletion page.
What we collect and why
| Data | When | Why | Where it goes |
|---|---|---|---|
| Precise location (GPS points: latitude, longitude, accuracy, time) | While a movement session is running in the foreground, or a single fix when you tap Locate me | To draw your route, measure distance and time, and decide whether a mission was completed | Kept on your phone. If you are signed in and save a session, the points are sent once over HTTPS to our server to verify it (see below) |
| Session summary: distance, duration, pause time, movement mode, start and end time, the coarse map cells your route passed through (about 0.7 km² each), and the verification result | When a signed-in player saves a session | To keep your verified progress in your account and prevent the same session counting twice | Stored on our server with your account |
| Google sign-in: your Google account's email address, name and profile picture, and a Google account identifier | When you choose Continue with Google | To create your account and recognise you when you sign in again. We do not use your name or picture in the app | Held by our sign-in provider (Supabase Auth); our server keeps your email address and the sign-in provider's user id |
| Wallet sign-in: your public wallet address and the signed sign-in message | When you choose Continue with Wallet | To prove you control the address and recognise you when you sign in again. We never receive your private key or recovery phrase, never read your balance and never request a transaction | Held by our sign-in provider (Supabase Auth); our server keeps the sign-in provider's user id, and the signed message for up to a day |
| Sign-in sessions: a device label such as "Android device", a one-way hash of the app's user agent, sign-in times | When you sign in or refresh your session | To keep you signed in and let you see and sign out your devices | Stored on our server |
| Security records: events such as sign-up, sign-in, new and ended sessions, with the sign-in method used. No email address, network address or route | When those events happen | To protect your account and investigate misuse | Stored on our server with your account |
| Your network address | When the app or this website contacts our server or sign-in provider | To limit repeated sign-in attempts and protect accounts from abuse | Used in memory by our server; not stored in our database. Our hosting and sign-in providers see it and may keep it in their own logs (see below) |
| Game progress: XP, level, streak, quests, badges, saved route reviews (without coordinates) | As you play | To run the game | Stored on your phone only |
How the server handles your route. When a signed-in session is verified, the server reads the GPS points in memory to calculate distance, time and the map cells crossed, then discards the points. Only the summary in the table above is written to the database. Our servers do not log request bodies, so route points are not written to logs either.
Sharing a route image. If you choose to share a session, the app creates an image of your route on a map and passes it to the app you pick. Start and end points are hidden by default. The image is not sent to us.
Service providers
We use these providers to run MovenRun. Each processes data only to provide its service to us.
- Google Maps SDK for Android (Google LLC) displays the map. When a map is on screen, Google receives the map area being shown and standard device and network information. See the Google Privacy Policy.
- Google Sign-In (Google LLC) authenticates you when you choose Continue with Google, and shares your email address and basic profile with our sign-in provider.
- Supabase (Supabase, Inc.) provides sign-in (Supabase Auth) and hosts the database that stores the account data described above, in the United States (us-east-1).
- Render (Render Services, Inc.) runs the MovenRun account service, in the United States.
- Vercel (Vercel Inc.) hosts this website, including the sign-in and account deletion pages. It receives standard request information such as your network address and browser type.
- Google Fonts (Google LLC) serves the typefaces used on this website, so your browser requests them from Google.
- Your wallet app (for example MetaMask, Coinbase Wallet or Trust Wallet) shows you the sign-in message and signs it. It is your app, run under its own terms; MovenRun sends it nothing but the message.
- Google Play distributes the app and may provide us with aggregated crash and performance statistics under Google's terms.
The app contains no advertising SDKs and no third-party analytics or crash-reporting SDKs.
How long we keep data
- Account data (your Google email address or wallet sign-in, verified session summaries and security records) is kept until you delete your account.
- Sign-in sessions are deleted by an automatic clean-up once they are more than a week past their expiry, or with your account if that is sooner.
- Wallet sign-in messages expire after 5 minutes. Expired messages are cleared out once they are a day old, when the next wallet sign-in starts. One-time codes that carry a wallet sign-in back to the app are stored only as a one-way hash, expire after 5 minutes and are deleted after a day.
- Used Google sign-ins: so that one Google sign-in cannot be used twice, our server records its sign-in session identifier and an expiry time, with no email address or account id, and keeps that record for 30 days.
- Sign-ins that never become an account: if a sign-in is abandoned, a wallet code is never collected, or new accounts are closed, the record it created at our sign-in provider is removed automatically, normally once it is about an hour old. Our service sleeps when it is idle, so this clean-up can run later than that.
- Unsent sessions waiting for a connection are kept on your phone for up to 7 days, and are deleted when they are sent, expire, are discarded, or you sign out.
- On your phone, game progress stays until you reset progress, delete your account in the app, or uninstall the app.
- Provider logs: our sign-in, hosting and website providers keep their own operational logs (for example network address, browser or device details and the time of a request or sign-in) for the periods their own terms set.
- Backups: our database plan does not give us automatic backups or point-in-time recovery. We may make occasional encrypted copies of the database ourselves to protect against data loss; a copy made before you delete your account still contains your account data until that copy is deleted. Any copies our providers keep for their own operations are governed by their terms.
Deleting your account
In the app: Profile → Account → Account security → Delete account. Or use the account deletion page, which works without the app, with Google or with your wallet. Deletion permanently removes your account, your sign-in record at our sign-in provider (email address or wallet address), sign-in sessions and every verified session summary. Your sign-in record at our sign-in provider is removed straight after, and the removal is retried automatically if the provider cannot be reached at that moment. We keep only an anonymous count that a deletion happened, with nothing that identifies you. If you cannot sign in, you can ask by email; the team handles those requests by hand, and we do not promise a fixed time.
Your choices and rights
- Location permission is controlled in your phone's settings. You can deny it; the app then explains that a movement session needs location and you can still browse the rest of the app.
- You can play without an account, sign out at any time, and sign out all devices from Account security.
- You can ask us for a copy of your account data, or to correct or delete it, by emailing info@movenrun.xyz. Depending on where you live, you may have further rights under local law, including the right to complain to your data protection authority.
Security
All traffic between the app and our server uses HTTPS. Sign-in tokens are stored in Android's secure keystore. Session tokens and one-time codes are stored on the server only as hashes. Google sign-in uses PKCE, and wallet sign-in uses single-use messages that expire after 5 minutes. No security measure is perfect; if we learn of a breach affecting your data, we will notify you as the law requires.
Children
MovenRun is not directed at children under 13, and we do not knowingly collect their data. If you believe a child has created an account, contact us and we will delete it.
No payments or tokens; wallets for sign-in only
This version of MovenRun has no purchases, no payouts, no tokens and no digital ownership. A crypto wallet can be used to sign in, and for nothing else: MovenRun does not hold, create or manage wallets, does not read balances, and never asks for a transaction or payment. XP, levels and badges are in-app progress with no cash value.
Changes to this policy
If we change how MovenRun handles your data, we will update this page and tell you in the app before the change applies to data already collected.