What we collect today
This website does not currently create Runnerz accounts or collect payment information. If you request an insider-testing place, register interest in a future merchandise drop or email us, we receive the information you choose to provide. This may include your name, email address, runner type, home city, intended test-phone platform, the product and likely size you selected, and your message. Merchandise interest is not a preorder, reservation or purchase, and Runnerz does not take payment through that form. You may separately choose to provide a WhatsApp number for personal insider invitations; this is optional and is not required to join. Hosting and security systems may also process limited request data such as IP address, browser information, timestamps and abuse signals needed to deliver and protect the service.
Android and iPhone testing
Android field testing opens first. Choosing iPhone does not reduce or remove an insider place: it lets Runnerz reserve that person for the first iOS testing wave and invite them to suitable previews, interviews or feedback sessions while TestFlight access is being prepared. People who use both platforms may be invited to each relevant wave.
Private app testing
When private testing opens, Runnerz may process information needed to create and operate a runner profile, including:
- account and profile details;
- running preferences, pace bands, route interests and availability;
- an optional self-reported gender preference, including “Prefer not to say” or a short self-description, stored only in private account settings and never shown on a public profile;
- run proposals, meetup participation and mutual confirmations;
- approximate or precise location only when a feature clearly requests it and you grant permission;
- technical diagnostics needed to keep the test stable and secure.
Mobile number and WhatsApp choices
Runnerz account creation remains email-first. When mobile verification is enabled, adding a Namibian number is optional. The app accepts the national 081–085 electronic-communications range, converts a valid local number to international +264 format and requires a one-time code before treating it as verified. The number remains in the private authentication system and is not displayed on a public runner profile. Permission to contact you on WhatsApp is a separate, optional choice that can be withdrawn; an unverified number is never used as identity proof.
Location and route privacy
Runnerz is designed to support approximate starting areas, public meetup points and a protected-home state. When you deliberately start a recorded run and grant location permission, the Android field-test app uses device location to draw your trail and calculate run metrics. Raw active-run points and completed trails stay in private Runnerz app storage on that device; they are not uploaded to Runnerz or Supabase, exposed through Running Nearby or turned into a public live-location feed. The Android map uses OpenFreeMap to load the map area displayed on screen, so that map provider receives normal network requests for the requested map tiles or style area. When an authenticated runner finishes a run, aggregate facts such as time, distance, elevation and accepted-fix count may sync to their account for history, badges and eligible weekly leaderboards. The Runnerz cloud record contains no trail coordinates. Dismissing a completion card does not delete the saved run. Pausing or finishing stops active recording, subject to the operating system completing that request. A route privacy setting does not replace normal personal-safety judgment.
Running Nearby is optional and deliberately coarse. An opted-in runner is represented by a broad public area and a short-lived availability signal, never by exact coordinates, direction, pace, selected route or recorded trail. Signals expire automatically. Women-only runs are invite-only by design. Runnerz never infers gender from a name, photo, document or activity. An optional self-reported onboarding preference stays in owner-protected settings, is omitted from public profile and meetup views, and does not automatically admit anyone to a protected run.
Emergency quick dial
The SOS quick-dial control passes the selected official emergency number to your device’s native phone dialer. Runnerz does not request call-log access, place the call automatically or receive confirmation that a call was made. Your device and mobile operator handle the emergency call.
UNIFIED music sessions
A Runnerz music-session handoff is user-triggered. Runnerz receives only the session title, planned duration and a bounded track count needed to describe that session. It does not receive track identities, the private UNIFIED Vault or a person’s listening history, and it does not merge Runnerz and UNIFIED accounts. If the confirmation surface is dismissed, the pending request is not armed. If the runner explicitly arms it, Runnerz stores only the bounded session identifier, title, duration, track count and coarse movement/weather labels needed to return elapsed time and distance after a completed run; raw trail points and track identities are never part of that relay. Playback remains in UNIFIED.
How information is used
Information is used to reserve one insider place per email address, measure stated interest in future merchandise without taking an order, plan suitable testing cohorts, operate requested features, help explain compatible runs and routes, improve the private test, respond to support requests, prevent abuse and meet legal obligations. If you opt in to WhatsApp invitations, that number is used only for selected Runnerz insider contact. Runnerz does not sell personal information.
Service providers
Runnerz may use carefully selected providers for infrastructure, authentication, transactional email, hosting, maps and diagnostics. Resend processes insider and merchandise-interest contact requests and related email delivery. DigitalOcean hosts the website, Cloudflare supports domain delivery and security, and Supabase provides app authentication and database infrastructure. If optional mobile verification is enabled, the notice will identify the selected message-delivery provider. MET Norway supplies the public Windhoek weather feed. The Android app requests its displayed basemap area from OpenFreeMap, whose style uses OpenMapTiles and OpenStreetMap contributor data. The website may serve packaged map data from Runnerz-controlled infrastructure using OpenStreetMap and Protomaps tooling.
Retention and deletion
We keep information only for as long as reasonably needed for the purpose collected, security, dispute handling and legal obligations. You can request deletion—including removal from future merchandise updates—through the account deletion page.
Contact
Privacy questions can be sent to [email protected]. This launch-readiness notice will be reviewed as features and providers change and before wider public release.