RunParty is an app for running, hiking and riding together: people host routes (a way to go, a time, a pace and a number of places), others join, and each route has a chat and a schedule. Runners can also form clubs. It is made by an independent developer. This policy explains, in plain words, what stays on your phone, what goes to RunParty's server, who can see it, and how to delete it.
In short
- Your runs, your GPS tracks, your steps, your photos and your videos stay on your phone.
- The server holds only what is needed to run together: your profile, the routes and clubs you host or join, their chat, your check-ins, and a short public summary you can switch off.
- No ads, no advertising ID, no analytics and no tracking. Nothing is sold.
What stays on your phone
- Your position, with the phone's location permission, to show you on the map, record the route you are running (also with the screen locked, while a run is on) and plan routes. Your track is not sent anywhere.
- Steps and activity, from Health Connect (Apple Health on iPhone) if you allow it, for your streaks, level and daily goal. Steps never leave the phone.
- Photos from your gallery, if you allow it, only to put the ones taken during a run on that run's route in the pictures and videos you make. They are not uploaded.
- Pictures and videos you make are saved in your gallery (Pictures and Movies, RunParty).
- The compass, only to turn the map with the phone while you choose that.
- Reminders, the step notification and your recent searches are kept on the phone.
What goes to the server
RunParty's server runs on Supabase (in Seoul, South Korea). It keeps:
- Your account: an anonymous sign-in made by the app, and, if you link one, your Google or Apple account's email address.
- Your profile: the name you choose, your profile photo if you add one (made small, 256 pixels), your country, a few words about you, and your Instagram name if you add it.
- Routes and clubs you host or join: their way, meeting point, time, pace and members, and the chat messages, replies and emoji reactions written in them.
- Your RunParty ID and invites: a short ID made for your account, which friends type to invite you to a route or club. Looking an ID up shows only that runner's name, photo and level. An invite (who sent it to whom, for which route or club, when, and whether it was answered) is seen only by its sender and the runner invited, and goes away from the Invites list after 14 days.
- Check-ins: when the host starts a route's run, each member is checked in. Check-ins count towards your level, badges and the leaderboards (distance gone with routes). To show the leaderboard near you, the app sends your position at that moment; it is not kept.
- A short public summary, unless you switch it off: your level and your run-streak weeks. The phone works them out from your check-ins, the days you met your step goal and the runs Health Connect (Apple Health) knows of, and sends only the two numbers, never your steps or runs themselves.
- Who you have blocked or muted, and reports you send.
- A notification token, if instant alerts are on, so the server can tell your phone about new chat lines and route changes through Firebase Cloud Messaging (Google). The message text is the only content sent.
All of this travels encrypted (HTTPS).
Purchases
RunParty Pro and tips are bought through Google Play or the App Store, which handle the payment; RunParty never sees your card or bank details. The purchase is checked by RevenueCat (revenuecat.com, see their privacy policy), which receives your RunParty account id and the purchase. RunParty's server keeps which products you bought and when, so it knows you are Pro and your supporter badge. Other runners see that badge, not what you paid.
Other services the app uses
- Maps from OpenFreeMap (tiles.openfreemap.org): the app asks for the pieces of the map on the screen. See openfreemap.org/privacy.
- Routes and place search from OpenRouteService, through RunParty's server: the points of a route you plan, or the words you search for, are sent to it, without your account.
- Profile pictures of the sample runners come from DiceBear (api.dicebear.com).
Like every internet connection, these requests carry your phone's IP address.
What other people see
- Public routes, with their way, meeting point and time, can be seen by everyone using RunParty. Private routes only by the host, its runners and people with its code; club routes by the club's members.
- Other runners see your profile (name, photo, country, Instagram, the summary above, your badges earned with route runs, your Pro or supporter badge and your clubs), and your messages and reactions in the chats you are in.
- Invite links and codes you share open the route or club for whoever gets them.
Sharing
Pictures and videos of your runs are shared only when you choose to, through the phone's share menu, to the app and people you pick.
Children
RunParty is for people 18 and older and is not directed at children. See also the child safety standards in the terms of use.
Keeping and deleting your data
- What is on your phone is deleted when you clear the app's storage or uninstall it. Pictures and videos you saved stay in your gallery until you delete them.
- You can delete your own chat messages, take back reactions, leave routes and clubs, and change or remove your profile photo and details in the app.
- Delete my account (Profile, Settings, at the bottom) deletes your account and everything the server keeps about you at once: your profile and photo, the routes you host, the clubs you own, your messages, reactions, invites and check-ins. Purchase records needed for refunds and tax stay with Google Play, the App Store and RevenueCat under their own policies.
- You can also write to us (below) with your RunParty name, and we delete it within 30 days.
Changes
If this policy changes, the new version is posted on this page and the date at the top changes too.
Contact
Questions about this policy or about RunParty: support@runparty.app