- Record runs live, or import GPX, FIT, TCX and CSV files
- Races in one calendar: road, trail, cycling, ultra
- Streaks, badges, goals, rankings and a community feed
- Downloadable offline maps
Pick your island.
Race discovery on RunXRoam. Every open play and tournament on Dinkzo. Two free apps from two people who play.
Run a club or a venue? See free organizer tools ↗Two apps. Each one complete on its own.
- Open play where courts fill from the queue, so nobody waits around
- Tournaments: single elimination or round robin, with categories
- Per-category fees in ₱, with payment tracking for organizers
- Clubs, match history, stats and "How to play" guides
Badges that travel between islands.
One Nomad account, one passport. Earn pins on RunXRoam and Dinkzo and keep them in one place. Tap a pin to see the reveal.
Running pins use badge names already in RunXRoam. Cross-app pins are a proposal and need a shared account first.
NOMAD PASSPORT
Free tools for people who make games happen.
Run open play without the group-chat roll call. Run a tournament with categories, fees and payments in one place. List your run club's group runs next to every race in the country.
Two people, one island, a lot of ideas.
Pixel Nomads is Luna and Yuki, turning ideas into useful apps. No niche, just ideas, and a habit of turning everyday hassles into free apps.
Meet Luna and YukiCo-founder · Web developer
Co-founder · Software developer
Something is forming in the fog.
Every new app becomes a new island on this map, with the same account and the same passport. Want to hear first?
Every run counts toward something.
Record your runs, walks, hikes and rides. Find your next race among the race calendar. Earn streaks and badges your club can see.
Record in the app · import a GPX or FIT file · sync your phone's health app
However you run, it lands in one place.
Record live
Hit Record in the app and go. Distance, pace and route save automatically.
Import files
Add GPX, FIT, TCX or CSV files, or enter a run by hand. Duplicates are flagged for review.
Phone health apps
On iOS and Android, connect your phone's health app to bring activities in.
Race discovery, in one calendar.
208 events across road, trail, cycling and ultra. Mark Interested or Going, and races you're going to show up on your home screen 90 days out.
Showing 6 of 208 · event names and dates as listed in the app on 30 Oct 2026
See the whole year, not just today.
Goals, personal records, 12-month trends, gear mileage and month-on-month comparisons. Sample numbers shown.
No signal on the mountain? Still mapped.
Save routes your club loves, and download offline maps for your next adventure before you head out.
Your club sees you show up.
A feed of runs, walks and badges. Groups, athletes and rankings. React and comment. Sample posts shown.
Watch your trail grow.
Each kilometre adds a pixel to your island trail. Cross 10 km and you earn the 10 KM Runner badge.
0 / 10 km
Badges for showing up, not just going fast.
Free to use. Optional support for the studio.
Use RunXRoam on the web, or get the iOS and Android apps for live recording and health-app sync.
Does it connect to Strava or Garmin?
Not today. Record in the app, import GPX, FIT, TCX or CSV files, or sync your phone's health app.
Is it free?
Core use is free. Supporter options are voluntary.
Who can see my activities?
You choose an audience for each activity in Privacy and sharing.
Privacy, terms and your data.
Read how RunXRoam handles your information, the terms for using the app, and how to request account or data deletion.
Less coordinating. More playing.
Courts fill from the queue as people arrive. Tournaments run with categories, fees and live rounds. Your club finally has one place.
No draw. Nobody knocked out.
Singles or doubles courts, formed as people arrive. When a game ends, the next four from the queue step on. Everybody keeps playing.
- Create an open play and share the link in your group chat
- Players join and check in at the venue
- The board assigns courts from the queue automatically
- Scores save to everyone's match history and stats
From sign-ups to a champion.
A drawn field playing the structure you set: singles or doubles, round robin or knockout, with standings and a champion at the end.
SEMIFINALS
FINAL
CHAMPION
Formats
Single elimination or round robin, singles or doubles.
Categories
Mixed doubles, men's doubles and more, each with its own field.
Fees and payments
Set a fee per category and record who has paid.
Know who has paid before the first serve.
Thirty days of games, one swipe.
Your club, finally organized.
Members, owners and every event in one place. Each player gets match history, wins, losses and win rate, filtered by open play or tournament.
Sample profile figures
How to play
Scoring, serving, the kitchen and the rest, in 8 short guides for new players.
Ladders
Season ladders with challenges are on the way. Join the waitlist to try them first.
Bring your DUPR
Add your DUPR to your profile so organizers can balance courts. A Dinkzo rating comes later.
Move your club in an afternoon.
- Create your club and invite members with one link
- Set up your weekly open play from a template
- We'll help you run the first session if you want
Free to use in the browser. Optional developer support helps maintain the studio.
Privacy, terms and your data.
Read how Dinkzo handles your information, the terms for using the app, and how to request account or data deletion.
Free tools for people who make games happen.
Spend game night playing, not managing a spreadsheet, a group-chat roll call and a whiteboard queue.
What changes on game day.
"Who's next?"
A whiteboard, a shouted list and players who never get on court.
AFTERCourts fill from the queue automatically.
"Did you pay?"
Screenshots of transfers scattered across chats.
AFTERFees per category, and payment status per player.
"When's the next run?"
Group runs buried under memes.
AFTEREvents next to 208 races, with Interested and Going.
For pickleball clubs and venues
- Open play with an automatic court queue
- Tournaments with categories and brackets
- Fees in ₱ and payment tracking
- Club pages with members and events
For run clubs and race organizers
- Groups, a community feed and rankings
- Event submissions to the race calendar
- Badges and streaks members share
- Offline maps for club routes
Email us. We'll set up your first event with you.
Send us a few details about your club. Luna or Yuki will reply with your first open play, tournament or group run ready to share.
Subject: Set up our club on Dinkzo / RunXRoam Club or venue name: City: App: Dinkzo, RunXRoam or both Typical turnout: When you play or run: What you'd like set up first:
Two people, one island, a lot of ideas.
Pixel Nomads is an independent studio. We turn everyday hassles and shared interests into useful apps, and keep the core free.
Co-founder · Web developer
Co-founder · Software developer
Make it easy for people to move together.
Every game and every run in the region starts on a Pixel Nomads island.
How we build.
Free core, always
Core use is free. Optional support and any digital extras depend on the app and release.
Built with organizers
Features start from game nights, not roadmaps.
Honest data
Your activities, your audience, your call. Delete anytime.
The trail so far.
Luna and Yuki start Pixel Nomads
A studio with no niche, just ideas.
RunXRoam launches
Activity tracking, then a race calendar that grew past 200 events.
Dinkzo launches
Open play queues, then tournaments with fees and payments.
Ladders, the Nomad Passport and island three
Add real dates here as they're confirmed.
Build with us.
How can we help?
Pick what you need and we'll route it to the right place.
Are the apps free?
Yes. Core use of RunXRoam and Dinkzo is free. Supporting the studio is optional.
How do I delete my account?
Each app has an Account and Data Deletion page linked in the footer.
Do Dinkzo queues reserve a court?
No. Queue positions and court assignments are not venue reservations.
Does RunXRoam work without a watch?
Yes. Record with your phone, import files, or sync your phone's health app.
On this page
RunXRoam Privacy Policy
1. Who is responsible
Pixel Nomads operates RunXRoam and is the personal information controller for information handled through the app. Contact our privacy team through our contact form.
This policy covers our web and mobile services. Features and controls may vary by platform and installed app version. It explains our processing under applicable privacy law, including the Philippine Data Privacy Act of 2012. External services have their own policies.
2. Information we handle
- Accounts: email address, account identifier, sign-in provider, verification status, and account authentication information. Google or Apple sign-in, where available, supplies the identity details you authorize. Authentication is handled through Firebase Authentication.
- Profiles: display name, biography, profile photo, location, country, team, preferred activities, appearance settings, featured badges, and privacy preferences. Date of birth is requested when saving profile information and is used for age-related features. Its visibility is separate from age-group display.
- Activities: activity type, title, dates and start time, elapsed, timer and moving time where available, distance, elevation, calories where supplied, source, import identifiers, notes, audience and route data. Records come from manual entry, supported GPX, TCX, FIT or CSV files, native GPS recording and health workouts you review and import. Strava-export files can be imported without connecting a Strava account. A chosen file may contain more data than the activity summary saves. Original account-saved GPX files are retained as described below. We calculate progress, pace, records, streaks, goals and achievements from saved records.
- Equipment: gear names and details, activity assignments, starting mileage, calculated use, targets and reminders. Earlier imported equipment may remain; the current app no longer fetches gear from the Strava API.
- Race planning and spending: private race notes and reflections, planning choices, budget items, amounts, currencies, paid-entry information and recorded spending totals. When you create a shared plan, we store a separate copy of selected budget information, event details, member names and identifiers, viewer/editor roles and edit history metadata.
- Events and clubs: saved participation choices, selected distances, linked completion activities, event submissions, club memberships and roles, group events, club photos, meetup schedules and locations, pace groups, RSVP choices, and race or virtual-challenge tracking. Browsing and filtering use the location, preferences, or search input relevant to the feature.
- Community: shared activities and achievements, event ratings and reviews, follows and follow requests, reactions, comments, reports, blocks, and in-app notification preferences and read status.
- Merchant listings: store names, descriptions, official links, locations, showcase and product photos, product details and supplied starting prices. For assigned store managers, we also store account identifiers and management assignments.
- Rankings: submitted race results, distances and finish times, evidence links, review decisions, ranking preferences, age groups, calculated performance information, and optional ITRA profile links and retrieved public runner statistics.
- Developer support through Google Play: optional one-time support product, account identifier, random purchase-account key, purchase token and its hash, Google order identifier, purchase and refund status, confirmation timestamps, supporter points, tier and badge choices. Where Google supplies a verified amount, we also store the charged amount, currency and a private support-total summary. Pending or test transactions are distinguished from confirmed support. Google handles checkout and your payment credentials; RunXRoam does not receive your card details, Google password, PIN or one-time code. Earlier support recognition may be retained separately and is not relabelled as a verified Google Play payment.
- Training plans: private plan settings, scheduled workouts, training notes, completion choices and links to your recorded activities.
- Optional health features: steps, distance, workout time, dates, time zone, originating app/provider and workout identifiers, connection and permission choices, optional step goals, workout links and import-removal preferences. Supported sources include Android Health Connect (including data Samsung Health shares into it), Apple Health on supported iOS builds, and authorized Polar Flow workouts. Native device reads, optional daily-summary cloud storage and reviewed workout imports are separate actions.
- Optional Insights usage statistics: only after you opt in, event types such as opening a card or explanation, fixed module identifiers, ready/insufficient counts, access state, app/platform and engine versions, timestamps and random session/event identifiers. These statistics exclude your name, email, account ID, activity text, route coordinates and exact performance values. Authentication and the device queue are still account-scoped; we do not describe the system as anonymous.
- GPS recording and saved routes: precise coordinates, sample timestamps, accuracy and available altitude, recording/pause/gap events, selected sport and goal, calculated metrics, device recording files and pending uploads. Account-saved GPX routes include the original file, filename, title, size, content hash, track summary, optional location and synchronization metadata. An original GPX may include timestamps, waypoints and extensions that are absent from its simplified preview.
- Ask RunXRoam and AI planning: messages and bounded conversation context, training goals and dates, recent training volume/results, experience, available days and session limits, restriction choices and notes you supply, and an explicitly selected saved workout or generated draft. We keep consent/adult-confirmation records, usage and request/recovery metadata, structured setup facts and private generated results. Do not include names, contact details, home locations, passwords or medical records in AI text.
- Optional activity recaps: cadence and delivery preferences, timezone, closed-period activity totals and sport breakdowns, comparison with the previous equivalent period, saved summary text and its origin, calculation/provider metadata and delivery status.
- Private messages: conversation members, text, selected pictures, sender and timestamps, message status, last-message previews, unread counts, mute/block choices and report evidence. Reports include the selected message and up to ten preceding messages, report reasons, optional notes and review decisions.
- Apple developer support, where offered: product and transaction identifiers, a random purchase-account token, signed transaction verification, store environment, purchase/revocation state, timestamps, supporter credit and available price/currency. Apple handles checkout; we do not receive your card or Apple Account payment credentials.
- Service operation and support: the messages and attachments you send, consent document versions and acceptance times, and request, error, security and operational records. Hosting and infrastructure providers receive connection information such as IP addresses when handling requests.
3. Location, files and health access
Location and recording
Nearby discovery, course-position and forecast actions request location when you choose them. You can deny permission and use supported search or manual alternatives. Native Android and iOS builds can also record a workout after you choose Record, grant permission and start the session. Recording captures precise GPS positions and times, including available accuracy and altitude, and stores session data on the phone. A GPS readiness check uses your position before Start without saving a workout track.
A user-started recording can continue when you navigate away, lock the screen or put the app in the background, using Android’s foreground location service/notification or the iOS location background mode/indicator. These builds request while-in-use location rather than Android background-location or iOS Always authorization. Leaving the recording screen does not pause it. Use Pause, Finish or Discard to stop capture. OS restrictions, force-stop, reboot, poor GPS or lost service can interrupt recording; a recovered session may contain a gap. This is workout recording you initiate, not general-purpose continuous tracking.
Recording data is saved locally first. Saving an activity queues its record and route chunks for your account; offline or failed uploads can retry on reconnect or a later app session. Discarding a recording is different from deleting an already saved activity. Do not assume that turning off permission or uninstalling deletes a cloud copy. Routes and activity times can reveal home, school and daily routines.
Files, maps, photos and calendars
Selected files supply activities or routes; selected photos supply profile, community or permitted listing media. Account-saved GPX import keeps the original on the device and queues an upload to your private account, up to 20 MB per file. Existing device-only routes can be backed up when you choose that action. Remove offline download removes that device’s copy; Delete from account removes the account route and queues related file cleanup. A disconnected device or an externally exported copy may retain data until it reconnects or you remove it.
Map and place requests can include the displayed area, location or search text. Offline map downloads store tiles and course/region data on the device. A weather request sends a representative point rounded to approximately one kilometre and the relevant dates to the weather provider, rather than your whole route; direct requests expose your IP address. External directions pass the destination to your chosen maps app.
System file/photo pickers, sharing and download permissions vary by platform. Calendar access is used when you choose to add an event; the feature does not upload your existing device calendar. The private RunXRoam training calendar is separate from your phone’s calendar. Where offered, a device widget displays a locally saved progress snapshot; consider who can see your home screen.
Optional health connections
Supported native builds read steps, distance and exercise/workout records from Android Health Connect or Apple Health with your requested type selections and system authorization. Samsung Health/Galaxy Watch information reaches RunXRoam only when it is shared into Health Connect; RunXRoam does not require your Samsung password or a direct Samsung cloud connection. Apple read authorization may not reveal whether an empty result means denied access or no data. Missing data is not treated as a measured zero.
Native health reads run in the foreground on Sync now or when opening Health on an existing connection. They do not request health write access, background health collection, health-route access or heart-rate streams. Device-only reading is separate from optional daily-summary uploads: these uploads are off until you explicitly enable cloud storage, and one primary installation supplies summaries. Recent workout candidates require your review before an import or link; imported copies start private. These features do not feed advertising or verified rankings. A saved activity you later include in a recap is processed as explained in the AI section.
Polar Flow is a separate optional browser-authorized cloud connection, available where configured. The backend holds Polar identifiers and access credentials, retrieves eligible recent workout summaries when you ask, and lets you review/import or link a workout. It does not import Polar GPS routes or continuous heart-rate streams. Provider history limits apply; connecting does not promise a complete backfill.
Pause or disconnect to stop future sync, and revoke native permission in Health Connect or Apple Health settings. Use the offered keep/remove controls or Delete imported health data for saved copies. Disconnecting does not automatically erase imported activities or the provider’s own records. Polar disconnection disables new reads first and attempts provider deregistration; if that fails, a disabled credential can remain for retry. Native integration availability depends on the installed binary, device and OS; a web page update alone cannot add a missing native module.
4. Why we use information
We use account and profile data to provide access and personalize your profile; activity data to organize your history and calculate progress; event and club information to manage your selections and memberships; and shared content to provide community features. Gear information supports usage calculations and reminders. Race planning data supports personal preparation, spending summaries and the shared plans you choose to create. Reviews and merchant content support event feedback and store discovery. Results and evidence support ranking calculations and review. Support records enable supporter recognition. Correspondence and operational information help us answer requests, investigate problems, moderate abuse and protect the service.
For ordinary personal information, the applicable basis depends on the purpose: providing the service you request, complying with law, your consent, or legitimate interests such as service security after considering your rights. For sensitive information, including age and health-related information, an applicable sensitive-information ground is required; ordinary legitimate interests alone are insufficient. Where consent is the basis, it must be specific and may be withdrawn by using the relevant control or contacting us. Accepting the Terms is not blanket consent to unrelated processing.
Notification preferences control in-app notices. Optional digest delivery by push or email is attempted only when the relevant channel is enabled for the release and you select it. Native push requires device permission and a push token; email digests use a verified email address and a configured delivery provider. Browser and device capabilities differ. A queued email is not a confirmation of delivery.
Statistics, achievements and rankings are informational calculations, can contain errors, and are not medical assessments. We do not use your activity information to make decisions about employment, credit or insurance.
Training records support your private planning calendar. Health data supports the private progress and explicit import features you choose. Supporter Insights calculates explanations on your device from your activity history; it does not send your history to an external AI service. Separate, optional usage statistics help us understand feature reliability and usefulness. You can switch Insights usage collection off in Settings → Privacy; collection stops and unsent events are discarded. Changing this choice does not automatically erase already-uploaded records.
RunXRoam is a convenient directory for finding events, registration pages, stores and gear links. It never collects, holds or processes payments on behalf of listed events, organizers or stores. Event entry and store purchases use the organizer’s or seller’s official channels. Personal budgets, shared plans and paid-status notes are records supplied by users, not transactions or proof of payment. Optional platform-store developer support is a separate transaction for maintaining RunXRoam.
Optional AI assistance and recaps
Ask RunXRoam and AI training planning use OpenAI to answer supported app/training questions and generate a draft from information you confirm. Some fixed app-help answers are supplied without a model request. AI features require the separate in-app consent and adult confirmation, and may be disabled or limited by release configuration. Accepting this policy alone does not enable AI or authorize unrelated data use.
For model requests we send the bounded messages/context and structured training facts needed for the action. Explaining an explicitly selected workout can include its title, date, target, effort and notes; a selected draft can also be supplied. The adapter does not add your account identifier, email, profile name, full activity library or GPS route. Free text you type, or notes in a selected workout, can still contain identifying or sensitive information; avoid including it. AI drafting does not automatically write your calendar: review the preview and confirm Add to calendar.
Weekly, monthly and yearly activity recaps are independent, off-by-default choices in notification settings. When enabled for a release, we aggregate saved activities in the closed period, save a report and attempt the selected notifications. When AI consent, adult confirmation and service controls allow a model request, OpenAI receives period dates, activity counts, active days, distance/time totals, sport totals and the previous-period comparison. It does not receive activity titles, notes, names, identifiers or route coordinates for this recap request. Totals can reflect health-imported workouts that you saved in your library. Recaps use the existing AI authorization record; there is no separate recap-specific provider-consent record in the reviewed implementation. Review this disclosure before enabling recaps. Turn the cadence off to stop future scheduled reports. If AI is unavailable or the authorization/capacity check fails, the report uses a labelled factual template; a template label after a provider error does not mean no provider request occurred.
OpenAI requests use the API with response storage disabled (store:false). This is not zero provider retention: provider security/abuse-monitoring and applicable contractual retention may still apply. We do not use these AI requests to train our own models; OpenAI states API data is not used for model training by default. No health-connection data is used for advertising, sold to data brokers or supplied for unrelated marketing. Local supporter Insights calculations are distinct from these optional external AI requests.
5. Visibility and sharing
Core profiles are discoverable by signed-in members. Activity audiences are “Everyone,” “Connections,” and “Only me.” The current default for new profiles is Connections; in the social system this means approved followers. Badge visibility defaults to Everyone, and achievement posting defaults to asking first. Existing accounts and individual activities may have different saved settings. Review each audience before sharing.
Date of birth is hidden by default and has a separate visibility setting. An age group may still appear in relevant ranking features. ITRA links have their own visibility setting. Hiding a link does not make the underlying ITRA public record or shared cache private. Ranking leaderboard participation and activity privacy are separate controls.
Community content, club membership and event attendance can be visible to the audience of the relevant feature. Administrators can access information needed for support, moderation, submission review and service administration. A hidden field in a screen is not necessarily a private record; contact us with questions about particular data or to request restricted processing.
Private planning and shared plans: personal budgets, spending entries, race reflections and equipment records are kept in your account rather than published to the social feed. Creating a shared budget makes a separate plan accessible to the specific members you invite from mutual connections; it does not publish your original private budget. Members can see plan contents and member information. Viewers can read, editors can change the plan, and the owner can change roles or remove access. Shared plans have no public-link sharing. Review the copied information before inviting someone.
Routes and exports: recorded tracks and account-saved GPX routes are stored under your private account. Sending a route to another user, publishing an activity or exporting a GPX, image or screen recording is a separate sharing choice. An original GPX can contain more detail than the simplified map, including timestamps and waypoints. Share templates can reveal routes and activity details. Check start/finish points and the audience first. In-app privacy changes cannot recall downloaded files, pictures, recordings or copies held by others.
Reviews, meetups and stores: event reviews and ratings are intended for other users to read. Club session information, RSVP choices and uploaded club photos are visible within the relevant club feature. Merchant descriptions, photos, product details and supplied prices are displayed to people viewing the store. Do not put private information in these submissions.
Changing an audience cannot remove screenshots, downloaded share images or copies already held outside RunXRoam. External registration links take you to the organizer or registration service, which handles information you provide under its own terms. Selecting Interested, Going or Completed in RunXRoam does not itself register you with an organizer.
Private messages are not end-to-end encrypted. The service stores message text and pictures. Ordinary conversation access is restricted to its members; a conversation can be started between mutual followers, and blocking stops new messages. Unfollowing alone does not close an existing conversation. When a member reports a conversation/message, authorized administrators gain access to that reported conversation and its evidence for safety review, including the conversation beyond the copied report excerpt. Resolving a report does not automatically remove that administrative-access marker. Do not send passwords, payment credentials or sensitive medical records in chat. Notification previews may reveal message content on a recipient’s device.
6. Connected services and recipients
- Google Firebase and Google Cloud: account authentication, database storage and synchronization, uploaded profile, club and merchant media, backend processing and operational logging. See Firebase privacy information and Google's Privacy Policy.
- Strava: the current app uses user-supplied Strava-export files instead of new Strava API connections, automatic activity syncing or route/gear fetching. A retirement path attempts to revoke and remove old stored credentials; older API imports and associated data may remain until reviewed or removed. We do not claim that historical cleanup or provider-side revocation has completed for every account. You can remove RunXRoam access in Strava’s connected-app settings and ask us about legacy data. File imports and data retained by Strava remain subject to your rights and Strava’s policy.
- Google Maps Platform and external maps apps: map display, place searches, location lookup, nearby trip suggestions and directions. Requests can include the location or search input used by the feature. Google Maps use is also subject to Google Maps terms and Google's privacy policy.
- ITRA and Apify: optional runner matching and retrieval of public ITRA statistics. The runner name and optional nationality used for a search are sent through Apify. A confirmed runner identifier and retrieved public statistics are cached. This does not require your ITRA password. See Apify's Privacy Policy and ITRA.
- Google Cloud Vision: event-source text extraction and, in iOS releases offering pre-upload image moderation, safety classification of the image submitted for checking. A selected image can be sent to Google Cloud for this check. Automated moderation is not a guarantee that every harmful item will be detected.
- Google Play Billing: processes optional developer-support checkout in supported Android releases. A random account key links a purchase to the signed-in account without sending its email or RunXRoam user ID as that key. Our backend sends purchase tokens to Google to verify purchases, reconcile pending states, and handle refunds or reversals. Google provides purchase/order status and available amount/currency details. Google applies its own payment, order-history and privacy practices. See Google’s Privacy Policy and Google Play Terms.
- Merchants and external stores: opening a store website, social page or directions sends the relevant request to that provider. Information you submit there, including inquiries, orders and payment information, is handled under that provider’s terms and privacy policy. RunXRoam’s store showcase does not provide an in-app checkout.
- Apple, Google, GitHub and external sites: optional sign-in providers, platform services, and hosting or delivery of our public legal pages receive the requests needed to provide their services. Opening a link or loading content directly from another provider can expose your IP address and request information to that provider.
- OpenAI: optional assistant, training-draft and recap processing described above. Our backend sends the necessary bounded input and receives output plus operational usage/response metadata. See OpenAI’s API privacy information.
- Apple Health / HealthKit and Polar Flow: optional read/import sources with the scope and controls above. Polar receives authorization, workout-fetch and deregistration requests; native Apple health reads occur on the device before any optional RunXRoam upload. See Apple’s privacy policy and Polar’s privacy notice.
- Apple App Store: where supported iOS developer-support purchases are enabled, Apple processes checkout and signed transaction verification/status. A random app-account token binds the purchase; our backend verifies transaction identity, environment and reversals. Apple keeps its own payment records under its policies. This is App Store in-app purchasing, not event or store checkout.
- OpenFreeMap / OpenStreetMap and Open-Meteo: map tiles/styles and weather data where those features are enabled. Requests disclose IP/network information and the requested map area or rounded weather point/date to the provider. Downloads can persist locally; retain the supplied map attribution. See OpenFreeMap, OpenStreetMap Foundation privacy and Open-Meteo’s terms.
- Contact form / Netlify: contacting Pixel Nomads through the website submits your name, reply email, topic and message to Netlify Forms and our company inbox so we can respond. See the website Privacy Policy. Never submit passwords, full payment credentials or a complete health file with a general inquiry.
We may disclose relevant information when required by law or necessary and lawful to address abuse, protect people, or establish or defend legal claims. We do not sell personal information. A new unrelated use or new data-sharing purpose requires an updated disclosure and any consent required by law.
Notification delivery: where enabled and selected, Expo’s push service and the device platform deliver push notifications, and the configured email service processes the address and digest content needed for email delivery. Operational delivery status may be saved. No delivery provider is required to browse listings.
Following an event, registration or store link sends your browser request to that destination, which may receive your IP address and referral information. Details you enter there, including registration, shipping and payment details, go to that provider under its own policies, rather than through a RunXRoam checkout. RunXRoam and Pixel Nomads are independent of the listed events and stores; a listing is not an affiliation, sponsorship or endorsement.
7. Storage, security and retention
Account-linked information is stored in cloud systems. Device or browser storage also supports sessions, preferences and caches. Infrastructure providers may process information outside your country. We remain responsible for information under our control and use access controls and provider arrangements to protect it. No service can guarantee absolute security; legally required breach notifications will be provided.
We retain profiles, activity history (including imported routes), equipment, planning records and associated settings while needed to provide your account and requested features, or until you delete them or request erasure. Connection tokens are needed while a connection remains active. Community content is kept while needed for its publication and related interactions. Support, security and payment-related records may need retention to resolve an open request, investigate an incident, meet a legal recordkeeping obligation, or handle a claim. We assess those purposes when you request deletion and explain any specific exception rather than treating it as permission to keep everything indefinitely.
Deletion from active systems may not immediately remove restricted infrastructure logs or provider recovery copies. We do not promise a fixed backup-expiry period here because retention depends on the relevant provider and configured service. Ask us for the retention details applicable to your request. Retained copies must not be used to restore a deleted public profile or resume unrelated processing.
Health summaries, imported workout records and training plans remain in your account until removed through the relevant controls or account deletion; health day records are not automatically pruned. Optional Insights usage events are marked to expire after 90 days. Expiry processing may take additional time, and operational logs have separate provider retention. Because those uploaded usage events contain no account identifier, deleting an account may not identify every prior event for individual removal; contact us about a privacy request.
Unused support-purchase intents are scheduled for removal after 14 days. On account deletion we remove account-linked purchase intents, raw purchase tokens, private receipts, support totals and account bindings. A restricted minimum purchase record remains for up to 400 days before scheduled removal to prevent a consumed purchase from being credited again and support order/refund obligations. It retains the token hash, Google order identifier, product, catalog/points information, test/state flags and necessary timestamps, but no RunXRoam user ID, account key, intent ID or raw purchase token. This record is not treated as anonymous. Google keeps its own payment records under its policies.
New feature records and their retention
Local recording sessions, tracks, route originals, offline maps and pending uploads remain on the device until saved, discarded, removed or cleared by the applicable account/device action. Synced activities and original GPX files remain in your account until you delete them or the account. GPX deletion records prevent another device from recreating a deleted route; file deletion can retry and an orphan-cleanup job is a backstop. Old device-only routes backed up from a simplified copy may lack the original timestamps/extensions. Exported files and another person’s saved copies require separate removal.
Full assistant chat history is held in session memory, not restored as a persistent chat transcript. This does not mean no AI content is stored: private generated answers/drafts and structured intake facts are recoverable for seven days. Expired content becomes unreadable through recovery, and scheduled purge normally follows within the next day. Minimal request/session authorization metadata is retained for 40 days. Usage counters, consent records and saved calendar workouts have separate account lifetimes; deleting an unsaved draft does not reset usage. Saved recap reports retain their frozen statistics, summaries, origin/provider and delivery metadata in your account; switching off a cadence stops future reports but does not erase earlier ones. Request removal or delete the account for those records.
Direct-message text and pictures remain for the conversation until removed through supported controls or account cleanup. A removed message becomes an empty marker. Account deletion removes that account’s message content/pictures and closes its conversations; the other participant’s own messages remain. Copied report text, conversation/member references and moderation evidence can remain for safety review and lawful claims. The reviewed code has no automatic expiry for those reports or their access markers. A proposed 90-day picture-storage rule requires separate infrastructure configuration, so this policy does not promise automatic deletion at 90 days. Contact us for review or erasure of retained evidence; we will assess and explain any lawful limitation.
Apple purchase records are separate from the Google Play 400-day rule. In the reviewed iOS implementation, account deletion removes linked intents, private supporter records and rate counters, and replaces each linked Apple purchase record with a restricted transaction-derived hash key, account-deleted state and timestamp. It removes the user ID, transaction details and app-account token from that record. No automatic expiry for these replay-prevention markers is implemented; request review of retention through our contact form. Apple’s independently held records follow Apple’s practices.
8. Deletion and privacy requests
Go to Profile → Settings → Delete Account, review the information about groups you own, then follow the typed confirmation and Permanently Delete Account action. If a group has other members but no other administrator, promote an administrator or close the group before retrying. A group where you are the only member can be closed; eligible groups can transfer to another administrator.
You can also request deletion without opening or installing the app through our contact form. Choose “Account and data deletion” and specify RunXRoam. Identify your account and the scope of your request; never send your password or payment credentials. Uninstalling the app is not account deletion.
The current deletion workflow removes the account’s profile, private activity library and routes, equipment, training and health records, planning records, birthday, ranking preferences/results, ITRA account link, legacy Strava credentials, Polar connection records, account-linked support records, relevant follows and interactions, reviews, reports, submissions, feedback, uploads and merchant-manager assignments. Owned shared budget plans are deleted; your membership and named member entry are removed from others’ plans. Group ownership and shared content are handled as described here rather than deleting other members’ accounts.
Authentication deletion is completed only after the workflow’s cleanup and verification steps succeed. If a step fails, some data may already be gone while the sign-in account remains; follow the app’s retry instructions or contact us. An interrupted request must not be assumed complete. Background verification handles late writes, and a restricted deletion marker remains until verification succeeds and for 30 days afterward.
This cleanup also covers recorded cloud tracks, account-saved GPX originals and route metadata, health summaries/links, AI recovery facts/results and account usage records, and saved recaps/preferences. Direct-message content and safety evidence have the separate treatment above. The supported iOS deletion path also removes Apple-linked purchase data and iOS report/moderation records, with restricted purchase replay markers retained as described above.
Shared merchant profiles and public event facts may remain without your account attribution; a username may stay reserved to prevent impersonation. Ranking audit references are de-identified, and the shared public ITRA cache is not your account record. The restricted Google Play purchase record and independently held provider records follow the retention explanation above. Other members’ free-text copies, externally shared images, restricted logs and backups may need separate review. These limitations do not remove your right to request erasure.
Legacy Strava cleanup and Polar deregistration attempt provider-side disconnection, but remote failures can occur; use the provider’s connected-app controls to verify revocation too. Native health permissions are managed in the OS and source records remain with that source. Account deletion does not erase records held by Google Play, Apple, event organizers or stores, cancel their registrations or orders, or create a refund.
For access, correction, erasure, blocking, objection, applicable portability, or withdrawal of consent, use our contact form. We may verify ownership proportionately. We will explain the scope, expected handling time, completion or any lawful limitation. You may complain to the Philippine National Privacy Commission and seek remedies available under applicable law.
9. Younger users and families
RunXRoam is for athletes of all ages, including younger athletes with appropriate parent or legal-guardian involvement. If you are under 18, ask your parent or guardian to read these documents with you, supervise your use and approve sharing and payments. Where applicable law requires verified parental authorization before collecting a child's information, do not submit that information until the required authorization has been arranged with us. Contact us before creating an account if this applies to your child.
The current app does not provide a verified parental-consent workflow or a dedicated child account with separate privacy defaults. A standard legal-agreement checkbox does not verify parental permission. Families should use private activity settings, keep birthdays hidden, avoid identifying home or school details, and review club and event audiences. These choices do not replace our legal obligations.
A parent or guardian can contact us to request information about a child's account, correction, restricted processing or deletion, subject to appropriate verification and the child's applicable rights. Report suspected unauthorized collection or unsafe contact so we can investigate and take appropriate action.
The optional AI assistant and AI training planner require a separate confirmation that you are 18 or older; they are not offered as a child coaching service. Do not bypass this confirmation. Parents and guardians should also review messaging audiences, picture sharing, location recordings and notification previews.
10. Changes and contact
We update this page and its version when our practices change. Material changes will be brought to your attention through appropriate service notices; we seek additional consent where required. You may contact Pixel Nomads about any part of this policy at the email and address below.
On this page
RunXRoam Terms of Use
1. Your agreement with Pixel Nomads
These Terms govern the RunXRoam web and mobile services operated by Pixel Nomads (“we,” “us”). By accepting these Terms and using RunXRoam, you agree to them. If you do not agree, do not create an account or continue using the service. The Privacy Policy explains how we handle information; acceptance of these Terms does not authorize unrelated uses of personal information.
2. Younger athletes, parents and guardians
RunXRoam is for athletes of all ages. Younger athletes may use it with appropriate parent or legal-guardian permission and supervision. If you are under 18, review these Terms and the Privacy Policy with your parent or guardian before using the service. The parent or guardian should approve the child's participation, sharing and any payment, and assist with privacy controls.
Use remains subject to any applicable minimum age or parental-authorization requirement in your location and in connected services. Where verified parental authorization is required before collecting a child's information, use our contact form before submitting that information. The current standard sign-up checkbox is not a verified parental-consent process. You must not bypass a third-party provider's age restrictions. Event organizers may impose separate participation requirements.
3. Accounts and security
Provide accurate account information, use only accounts and connected-service identities you are entitled to use, and keep your credentials secure. Do not impersonate another athlete or share an account to evade restrictions. Notify us if you suspect unauthorized access. You are responsible for activity you authorize through your account, subject to rights and protections provided by law.
4. Activities, progress and rankings
RunXRoam supports running, trail running, walking, hiking, cycling, jogging and other supported activities through native workout recording, activity imports or manual entry, progress and achievement features, event discovery, virtual-run tracking, clubs and social tools. Feature availability can vary by platform or connected provider.
Imported records, duplicate detection, estimated metrics, achievements, event completion and rankings may contain errors or change after correction, deletion or recalculation. Submit honest activity and race information, and only evidence you are entitled to provide. Do not fabricate results, claim another athlete's identity, or manipulate rankings. We may review evidence and correct or remove unsupported results. Contact us to request review of a mistake.
RunXRoam's road-running rankings are its own informational system. An ITRA link or displayed ITRA statistic does not make RunXRoam an official ITRA ranking service or imply endorsement. Linking an account to public results does not establish ownership of the underlying event or organization.
Equipment mileage, replacement targets, reminders and suggested lifespans are estimates based on recorded activities and your entries. They do not certify equipment condition or guarantee safe use; inspect equipment and follow manufacturer guidance. Personal records and spending summaries can change when underlying entries are corrected.
Private training plans, health summaries, supporter explanations and educational tips are general planning or informational tools, not personalized medical advice, diagnosis or an assurance of safe training. Health connections and optional supporter features depend on the installed build, granted permissions and release availability. Supported builds offer read-only Android Health Connect, Apple Health and Polar workout connections; device/build/provider and authorization limits apply. Do not treat an unavailable or incomplete measurement as a measured zero.
Recording, routes and weather
Native GPS recording can continue away from its screen or with the phone locked until you pause, finish or discard, subject to OS limits. It is not live safety monitoring. GPS accuracy, gaps, battery/storage limits and upload failures can affect a result. Offline records and routes are not confirmed as account-saved until synchronization succeeds; keep backups of important originals.
Account-saved GPX routes can include their original file and sensitive locations. Remove offline download differs from Delete from account. Share/export only routes you are entitled to distribute and inspect originals for private points, timestamps and other embedded information. Map lines, course-position estimates, forecasts and historical weather are informational, may be incomplete/outdated and do not certify a route is safe, accessible or open.
5. Physical activity and safety
Exercise, outdoor travel and event participation involve risks, including injury, weather, terrain, traffic and equipment hazards. Choose activities appropriate to your abilities, follow organizer instructions and local restrictions, and seek qualified medical advice when needed. Parents and guardians should assess activities and events for younger participants.
RunXRoam does not provide medical advice, emergency response, live safety monitoring or rescue. Do not rely on a map, ranking, badge or estimated performance metric as a safety assessment. If you need urgent help, contact the appropriate emergency service. Nothing here excludes responsibility that cannot lawfully be excluded.
6. Events, virtual challenges, clubs and travel
Listings may come from public sources, organizers, community submissions or automated extraction. Dates, distances, prices, registration deadlines, race-kit details, locations and availability can change or be incomplete. An approximate date is not confirmed. Check the organizer's official information before registering, paying, booking travel or attending.
Interested, Going, Completed or Cancelled selections in RunXRoam record your status within the app. They do not purchase entry, reserve a place, submit an official race result, cancel an organizer's registration, or obtain a refund. Marking a virtual challenge completed does not require its provider to issue a medal or reward.
External registrations, accommodation, transport, purchases and event participation are governed by the relevant provider's terms. RunXRoam does not become the organizer or travel provider merely by displaying a listing or link. Club administrators and event submitters must provide accurate information and have permission to publish supplied material. Do not publish another person's contact details, a private meeting location, or a child's information without appropriate authority.
Club meetups and pace-group RSVPs help coordinate participation. A displayed capacity, RSVP or reminder does not guarantee admission, supervision, route safety or organizer availability. Confirm arrangements with the host and arrange appropriate adult supervision for younger participants.
Personal budgets, recorded spending, race reflections and shared plans are planning tools. A shared plan is a separate estimate worksheet, not a payment, settlement, booking or debt-collection service. Figures and currencies depend on user entries and may be incomplete. Creating or editing a plan does not authorize payment or bind another member to spend money. Owners choose viewer/editor access and may remove it; keep independent copies of information you need because an owner may delete the plan, including by deleting their account.
Independent directory; no event or store payments
RunXRoam brings discovery links together so users can find where to register for events and where to buy gear without searching multiple websites. RunXRoam and Pixel Nomads are not affiliated with, sponsored by, endorsed by, or acting as agents for the events, organizers and stores listed in the app. Listing a name, logo, product or link does not create such a relationship.
RunXRoam never collects, receives, holds, processes or settles payments on behalf of events, organizers or stores. All event registration and event payments must take place through the organizer’s official registration and payment channels. All store orders, payments and other purchase transactions must take place through the store’s official channels. RunXRoam does not sell tickets or gear, operate a store checkout, or issue an organizer’s or seller’s receipt.
Verify that a linked destination is the organizer’s or store’s official channel before providing information or paying. Registration acceptance, entry, stock, delivery, cancellation, returns, warranties and payment disputes are handled by the relevant organizer, store or payment provider under their terms and applicable law. A RunXRoam status, budget figure or completion marker is not proof of registration, payment or a purchase. Report misleading or incorrect links to us.
7. Your content and community conduct
You retain ownership of the content you contribute. You grant Pixel Nomads a non-exclusive, worldwide, royalty-free permission to host, store, technically adapt, display and distribute that content only as needed to operate RunXRoam and honor your sharing choices. This permission ends when the content is removed from our active service, except for limited lawful retention, technical recovery copies and copies others have independently retained. It does not transfer ownership of your content to us.
Only upload or link content you have the right to use. Respect the privacy of people shown in photos or mentioned in posts, especially children. Do not use RunXRoam for harassment, threats, stalking, exploitation, sexual content involving minors, hate or discriminatory abuse, scams, spam, impersonation, unlawful conduct, copyright infringement, or disclosure of someone's sensitive information without authority.
Do not attempt unauthorized access, bypass security or access controls, distribute malicious software, disrupt the service, or collect members' personal information for unrelated purposes. Use the available report and block tools or use our contact form about unsafe or infringing material. We may restrict or remove content or accounts when reasonably necessary to investigate a report, enforce these Terms, protect people or comply with law. You may ask us to review a moderation decision.
Reviews and ratings should reflect honest experiences and clearly distinguish opinion from fact. Do not post fabricated reviews, undisclosed promotional endorsements or another person’s private information. Reviews express the contributor’s views and are not a guarantee of an event’s quality or safety.
Share-image exports may include your activity details and, when you choose Route-art, an imported route. Check the image and its intended audience before sharing, especially for home or school locations and information about children. External copies cannot be recalled by changing an in-app privacy setting. Respect the connected provider’s terms and other people’s rights when exporting or reposting content.
Direct messages and safety reports
Private text/picture conversations can be started by mutual followers. Existing conversations may continue after an unfollow; use Block to stop messages, and Mute to change conversation alerts. Messages are stored on the service and are not end-to-end encrypted. A member report permits authorized administrators to review that conversation and retain evidence, including copied surrounding messages, for safety handling. Removing a message or deleting your account does not automatically remove report evidence or the other member’s own messages. See the Privacy Policy for retention and review requests. Do not use messaging for harassment, unsolicited commercial messages, scams or sharing another person’s sensitive information.
Automated text/image checks and human moderation may reject or remove content in supported releases. Detection can be incomplete or mistaken; report abuse and contact us to request review. Do not treat the presence of an account or message as verification of a person’s identity or trustworthiness.
8. Optional developer support through platform stores
RunXRoam’s core app remains free. Developer support is optional and is intended to help the developers maintain and improve the app, including hosting, infrastructure, testing and development. Support uses Google Play Billing on supported Android builds and Apple App Store in-app purchasing on supported iOS builds where enabled, replacing the former external-wallet flow. Availability depends on the installed release, region, account and configured products. This does not imply a published store listing or offer web checkout.
Each support option is a repeatable, one-time digital in-app purchase, not an automatic subscription. It may be described informally as a donation or voluntary contribution, but is not a tax-deductible charitable donation. Purchases award the supporter points, badge recognition and any optional digital extras clearly described in the current app. Core use does not require support. Support does not buy event entry, gear, investment rights, ownership in Pixel Nomads or a promised future feature.
The applicable platform store shows the product, localized price, currency and checkout terms before you confirm. Where an amount is entered, the app resolves it to an available fixed-price option; review the actual charge shown by the store. Store fees and applicable taxes apply, so the full price is not received by the developers. Use an authorized payment account; a minor needs appropriate parent or guardian approval.
Supporter credit is awarded only after backend verification with the relevant store. Opening checkout, seeing a client success screen or having an older badge is not independent proof of a new confirmed purchase. Pending payments or delayed confirmation may take time; use Check confirmation or contact support rather than paying again solely because confirmation is delayed. Points and tiers are recognition measures, not cash balances, transferable currency or independently verified totals of all historic support.
Refunds, cancellations, unauthorized charges and reversals are handled through the applicable platform-store and developer support processes under applicable terms and consumer law. See Google Play’s refund information and Apple’s refund information. Use our contact form with the order reference if help is needed; never send payment credentials. A verified refund or reversal can remove the associated supporter points and affected digital recognition, while preserved legacy recognition may remain. Nothing in these Terms removes mandatory consumer rights. Developer support payments are entirely separate from event registrations and store transactions.
9. Connected services and external content
Optional services include Google or Apple sign-in where available, maps/weather, ITRA information, supported health connections, OpenAI assistance, notification delivery and platform-store billing. The current Strava flow imports files that you export yourself, rather than creating new API connections or automatically syncing activities/gear. Legacy data and revocation are addressed in the Privacy Policy. Their availability, access permissions and terms may change. Authorize only connections you want, follow the provider's terms, and disconnect when appropriate. We may modify or stop an integration when access is withdrawn or a provider changes its service.
External brands, race names, logos, photos and results belong to their respective owners. Their appearance does not imply affiliation or endorsement. For Google Maps features, the applicable Google Maps terms and Google Privacy Policy also apply.
Gear Shop and merchant showcases: store and product listings provide information and external links. Supplied starting prices are not binding quotes, stock checks or guarantees of availability. Confirm the final price, currency, product suitability, delivery, returns and warranty directly with the seller. RunXRoam does not process store checkout or collect payment on the seller’s behalf; orders and payments made through external stores are governed by the seller’s terms and applicable law. Assigned managers must be authorized to represent the store and keep submitted descriptions, prices, links and images accurate and lawful. A listing does not itself establish endorsement or a commercial affiliation.
10. App rights
Pixel Nomads or its licensors own the rights they hold in RunXRoam's software, original designs, branding and original service content. We allow you to use the service for its intended purposes while you comply with these Terms. Do not misuse our branding or represent an unofficial service as ours. These Terms do not override rights expressly granted by an applicable open-source license or rights that the law permits.
11. Availability, responsibility and limitations
We aim to provide a useful service but cannot promise uninterrupted availability or that every imported record, map, listing or calculation is accurate. Maintenance, network failures, third-party changes and software faults can affect access. Keep independent copies of records important to you.
To the extent permitted by applicable law, the service is provided as available without additional guarantees of fitness for a particular purpose or error-free operation. We are not responsible for an independent organizer's performance or an external provider's conduct merely because we link to it. Responsibility for loss is determined by applicable law and the facts; nothing in these Terms excludes or limits liability for fraud, willful misconduct, gross negligence, or any liability or consumer right that cannot lawfully be excluded or limited.
Optional AI assistance and activity recaps
Ask RunXRoam and AI training drafts are optional, adult-only features subject to separate consent, monthly allowances and service controls. Current ordinary-account allowances are 15 successful general AI answers and two valid generated plan drafts per UTC calendar month, with independent balances and no rollover. Required structured intake is separate from general answers. A plan credit is used when a valid draft becomes recoverable, even if you later discard or do not save it; regeneration uses another plan credit. Confirmed technical failures/invalid outputs do not spend a public credit, but internal capacity controls may still make the feature temporarily unavailable. The app displays the applicable allowance. Manual planning remains available; no future allowance or uninterrupted AI access is promised.
AI outputs can be inaccurate, incomplete or unsuitable. Automated training-rule checks do not establish medical safety or qualified-coach review. Do not use the assistant for diagnosis, injury treatment, emergencies or training around a restriction requiring professional advice. Do not submit sensitive personal/medical details in prompts. Review every draft and explicitly confirm Add to calendar; a model reply does not save a workout or change your external device calendar.
Weekly, monthly and yearly recaps are optional closed-period summaries, with independent cadence choices. They can include an OpenAI-generated explanation from aggregate saved activity totals when authorized, or a labelled template when AI is unavailable. A template fallback may follow an attempted provider call. Reports are not a medical/fitness assessment, live coaching or a guarantee that all source records were available. Turning a cadence off stops future scheduled reports but does not erase saved reports. Recap attempts use internal AI capacity rather than the public message/plan balance; timing and notifications are not guaranteed.
12. Ending use and account deletion
You may stop using RunXRoam, disconnect services, or request account deletion using Account & Data Deletion. We may suspend or end access for serious or repeated misuse, security risks or legal requirements. Where appropriate, we will explain the reason and provide an opportunity to seek review; urgent protective action may come first.
Account deletion is permanent once completed. The deletion workflow, shared-content handling, failure/retry behavior and restricted retained records are explained in the Privacy Policy. If you administer a club, contact us or arrange a transfer of ownership so other members are not left without an administrator. Deleting RunXRoam does not delete accounts or registrations held by independent services.
13. Changes, disputes and contact
We will publish revised Terms with an updated date and provide appropriate notice of material changes. If renewed acceptance is required, the app may ask you to review the current version before continuing. Changes do not retroactively remove rights that have already accrued.
Philippine law governs these Terms, subject to mandatory protections that apply in your location. Please contact us first so we can try to resolve a concern. You retain access to competent courts, regulators and other remedies available under law; this section does not impose mandatory arbitration or waive collective remedies.
If a provision is unenforceable, the remaining provisions continue to apply to the extent permitted by law. Contact Pixel Nomads through our contact form or the correspondence address below.
Dinkzo Privacy Policy
1. Who operates Dinkzo
Dinkzo is operated by Pixel Nomads, the personal information controller. Contact our privacy representative through the contact form.
This policy covers Dinkzo's web and mobile services and explains how we handle information under applicable privacy law, including the Philippine Data Privacy Act of 2012. Features vary by platform and version. External providers apply their own policies.
2. Information we handle
- Account information: name, email address, account identifier, sign-in provider and authentication information. Firebase Authentication handles email/password and supported Google sign-in. A display name or username may initially be derived from your sign-in details, including the part of your email before the @ sign; review it before participating.
- Player profiles and preferences: display name, username, biography, skill level, recreational or tournament preferences, singles/doubles preferences, selected city or place, playing schedule, notification choices, follow approval and statistics visibility.
- Locations: foreground device coordinates used for nearby discovery; saved profile or venue locations, including address components, map coordinates and place identifiers; and search inputs used to find places.
- Events, courts and tournaments: event details, hosting and official roles, join requests, invitations, participant names and identifiers, teams, divisions, attendance, check-in status, queue positions, court assignments, match pairings, scores, results, standings and event history.
- Event fee records: fees, recorded amounts paid, payment status and waivers entered for event administration. These records are distinct from payment-provider confirmation.
- Community and communication: club details and membership roles, follow relationships and requests, event-chat messages and sender details, message-read information, notifications, and feedback or support correspondence.
- Technical information: session and local-storage information, app preferences, and connection or operational information needed to deliver and troubleshoot the service. Hosting, authentication and map providers may receive IP addresses, request information and device/browser details when serving requests.
Provide only information needed for a feature. Do not put passwords, payment credentials, medical information or another person's private contact details into profiles, event descriptions or chat. If you contact us or a payment recipient, we also receive the correspondence or transaction information you provide through that channel.
3. Location, camera and local storage
Nearby discovery uses your device's foreground location with permission. After permission has been granted, Dinkzo can obtain a current position again at startup without another prompt. The app can remember the position during the session. It does not provide continuous background location tracking.
You can deny or revoke permission in your device or browser settings and continue browsing events using other filters. A manually selected profile or venue location is different from a temporary device position: its address and coordinates can be saved with the relevant record and used for display, distance calculations and maps. Avoid selecting your home or another sensitive place as a shared venue.
The camera is used to scan event check-in QR codes where available. Check-in processes the scanned event information and your participation status; it is not a video-recording feature. You can control camera access through device settings.
Dinkzo and its authentication services use local storage or equivalent device storage for sessions, preferences and relevant caches. Clearing local data may sign you out or reset preferences; it does not delete cloud records. In-app event, invitation and reminder settings control the available notification features and do not by themselves establish that operating-system push notifications are enabled.
4. Purposes and processing grounds
We use account details to authenticate you; profile and location information for discovery and player preferences; event, court and participant records for organizing play; scores for results and statistics; and communication records for event chat, invitations and support. Fee records help organizers administer participation. Operational information supports reliability, moderation and security.
Depending on the purpose, processing of ordinary personal information rests on providing the requested service, legal obligations, consent or legitimate interests such as security, subject to your rights. Sensitive information requires a separately applicable legal ground. Consent, where relied on, can be withdrawn through the relevant control or by contacting us. Agreeing to the Terms does not give blanket permission for unrelated processing.
Pairings, queues, rankings and statistics are feature calculations, not medical assessments or decisions about credit, employment or insurance. Organizers may correct results and scores. Contact the organizer or us if information is wrong.
5. Information other people can see
Players may see names, relevant player details, shared locations, event participation, scores, standings, accepted follow relationships and club information through the features they can access. Event organizers and authorized officials use participation, check-in, fee and scoring information to administer play. Club administrators manage membership and club content. Event-chat messages are available to eligible participants in that event, rather than being private one-to-one messages.
Statistics visibility: Settings offers Everyone, People who follow you, and Nobody for profile record and match-history displays. The default is Everyone. Follow approval is a separate control. These settings control what Dinkzo's normal screens display; they do not make the underlying shared match records private. Signed-in users can access shared match records, and event results remain available for event operation. Do not rely on the Nobody setting as a guarantee that results cannot be reconstructed from those records.
Dinkzo does not provide a universal private-account setting that makes all event, match and club information invisible. A private club's membership controls do not automatically make every linked event or match confidential. Review a feature's audience before joining, posting or selecting a location.
Authorized administrators can access information necessary for service administration, moderation and support. Recipients can retain screenshots or copies outside Dinkzo; we cannot directly remove those copies.
6. Providers and disclosures
- Google Firebase and Google Cloud: account authentication, application database storage and synchronization, and related infrastructure. See Firebase privacy information and the Google Privacy Policy.
- Google sign-in: supplies the identity information authorized through that sign-in service. Your Google account remains subject to Google's terms and controls.
- Google Maps and places services: process map, venue, place-search and location requests. Opening an external maps app passes the destination to that provider. See Google Maps terms and Google's privacy policy.
- GCash: optional developer support uses an external GCash QR/app flow on supported platforms. Dinkzo does not receive your PIN, password or one-time code and does not receive automatic payment confirmation from this flow. The recipient may see transaction details supplied by GCash. See GCash's Privacy Notice.
- Hosting and external websites: providers serving the app or these legal pages, including GitHub for repository-hosted pages, receive requests needed to deliver them. External event or provider links are governed by their own policies.
We may disclose relevant information when required by law or necessary and lawful to investigate abuse, protect people, or establish or defend claims. We limit disclosures to their purpose.
We do not sell personal information. Dinkzo does not currently operate a third-party in-app advertising program or intentionally use advertising SDKs to profile users across unrelated services. Necessary infrastructure and map processing still occurs.
7. Storage and security
Information is stored in cloud systems and, where needed, on your device. Providers may process information outside your country; locations depend on the configured service. We remain responsible for information under our control and use appropriate provider arrangements and access controls.
Dinkzo uses authenticated accounts and database access rules. No system is completely secure, and not every display-visibility setting is a server-enforced confidentiality restriction, as explained above. We investigate security incidents and provide notifications required by law.
8. Retention
We retain account information while needed to provide the account and requested features. Event and match records support shared history, statistics and dispute resolution; account deletion requires assessing identifying information in those shared records rather than treating them as indefinitely exempt from erasure.
Our existing policy allows support and privacy correspondence to be retained for up to three years after a matter closes, unless a specific legal, security or dispute need requires longer retention. Technical records are kept only as needed for operation, security and applicable obligations.
Restricted recovery copies may remain after active-system deletion until their lifecycle expires. Our target maximum backup retention is 180 days, subject to the actual settings of the infrastructure service; this is a target, not a verified guarantee for every provider. Ask us for retention details relevant to your request. Recovery copies must not be used to resume unrelated processing of deleted information.
Where we retain information after a deletion request, we will explain the applicable purpose and retention criteria. Technical cleanup limitations do not justify indefinite retention.
9. Account deletion and requests without the app
Open Profile → Settings → Delete account and follow the confirmation shown. If a recent login is required, sign out, sign back in and retry. Dinkzo's confirmation flow may differ from other Pixel Nomads apps.
The current self-service process removes the authentication account after deleting covered account records, notifications, hosted events and matches booked by that account. It does not automatically erase every shared or separately stored record. Matches you participated in can remain with names and participant identifiers to preserve other players' records; follows, chat, club records and other identifying references may require additional cleanup.
For complete account-and-personal-data deletion, or if the app flow fails, use the contact form and selecting Account and data deletion, naming Dinkzo in your message. You do not need to install or open Dinkzo. Identify your account, preferably using its email address, and specify complete deletion or the particular records concerned. Do not send a password, PIN or one-time code. We may verify ownership proportionately.
We aim to complete verified requests within 30 days, subject to identity verification, lawful retention requirements and request complexity. We will explain any delay or limitation; applicable legal deadlines still apply. Shared-record cleanup may require administrator review, including removal or de-identification of your information while protecting other people's legitimate records. This does not make all shared content exempt from deletion.
If you manage an event or club, tell us about any transfer or closure needed. Deleting your account is not an automatic fee refund or cancellation with an external venue. Uninstalling Dinkzo does not delete your account. Copies independently held by recipients or payment providers are subject to their own controls.
10. Your rights
Subject to applicable law, you may request information about processing, access, correction, objection, erasure or blocking, portability and withdrawal of consent. Email our privacy representative to exercise these rights. We will explain any lawful restriction. You may complain to the Philippine National Privacy Commission and seek remedies available under law.
11. Younger users
Dinkzo's current account policy is intended for users aged 18 or older. An under-18 person must not independently create or maintain an account without the legally valid authorization and arrangements required under applicable law. A parent or legal guardian should contact us before providing a child's information or arranging account access.
This policy does not claim that Dinkzo has an automated age-verification or verified parental-consent system. Contact us if a child has provided information contrary to these requirements. We will investigate and arrange appropriate restriction, correction or deletion, respecting applicable rights. An organizer's youth event or age division does not itself authorize creation of a child's Dinkzo account.
12. Changes and contact
We publish updated policies with a revised date. Material changes receive appropriate notice, and any consent required for a new purpose must be obtained before that processing. Contact Pixel Nomads using the email and correspondence address below.
Dinkzo Terms of Use
1. Agreement and operator
These Terms govern the Dinkzo web and mobile services operated by Pixel Nomads (“we,” “us”). By agreeing to these Terms when presented and using Dinkzo, you accept the applicable Terms. If you do not agree, do not use the service. The Privacy Policy explains how we handle personal information; agreement to these Terms is not blanket consent to unrelated processing.
2. Eligibility and accounts
Dinkzo's current account policy is intended for users aged 18 or older. A younger person must not independently create or maintain an account without the legally valid authorization and arrangements required under applicable law. A parent or legal guardian should use the contact form before arranging a child's account access. An organizer's youth division does not automatically change account eligibility.
Use accurate information and an identity you are entitled to use. Protect your credentials, do not impersonate another player, and tell us if you suspect unauthorized access. Do not use another person's account to bypass restrictions. You are responsible for actions you authorize, subject to protections provided by law.
3. What Dinkzo provides
Dinkzo provides tools for finding and hosting pickleball events, managing participants and invitations, coordinating courts and queues, organizing teams and tournament stages, recording scores, viewing standings and history, managing clubs, following players and participating in event chat. Availability varies by platform and version.
Player preferences, skill labels, calculated statistics, pairing suggestions and rankings are informational. They can change after score corrections or event updates. They are not guaranteed measures of ability or official ratings issued by a sports federation or external rating provider unless expressly identified as such.
4. Events, participation and courts
Confirm dates, venue access, court availability, fees, capacity, equipment needs, format and cancellation rules with the organizer before attending or paying. A listing is information supplied or managed by its organizer; Dinkzo does not become the venue operator or event organizer simply by displaying it.
A join request, invitation, waiting-list place or queue entry is not guaranteed entry. Follow the event's acceptance and check-in process. A court assignment inside Dinkzo coordinates play; it is not necessarily a reservation with the venue. Do not assume that a simulated preview, bracket or suggested match creates a real booking.
Organizers are responsible for accurate event details, necessary venue permission, clear fee and refund rules, appropriate participant eligibility, safe administration and truthful payment records. Obtain appropriate authority before adding someone else's personal information. Cancel or update an event promptly when circumstances change.
Players must follow reasonable organizer and venue rules, use check-in information honestly, respect other participants and notify the organizer when withdrawing. Any event-specific terms must be disclosed by the organizer and cannot remove mandatory legal rights.
5. Scores, tournaments and officials
Organizers and authorized scorers administer teams, formats, courts, scores and tournament progression. Submit honest results and raise discrepancies promptly. Do not manipulate scores, impersonate an official or interfere with another match.
Different events can use different scoring, tie-break and qualification rules. Verify the selected format before play begins. A software calculation can contain an error; the organizer should review disputed results and coordinate any correction. Dinkzo does not guarantee a result will be accepted by an external league, competition or rating service.
6. Event fees and voluntary support
Event fees and recorded payments are managed by the relevant organizer. A Paid, Unpaid or Waived label reflects an app record and is not independently verified settlement by a bank or wallet. Confirm the recipient, amount, due date and refund terms before sending funds. Fee disputes and cancellations should first be raised with the organizer or payment provider; contact us if misuse of Dinkzo is involved.
Optional developer support, where available, uses an external GCash QR/app flow. It is voluntary and does not unlock core features. Dinkzo does not automatically receive payment confirmation; opening GCash or seeing a thank-you screen does not prove a payment succeeded. Never send a PIN or one-time code through Dinkzo.
Support does not buy event entry, an investment, ownership in Pixel Nomads, a subscription or a guaranteed future feature unless an express offer states otherwise. We do not represent it as a tax-deductible charitable donation. Contact us and the payment provider promptly about mistaken, duplicate or unauthorized transfers. Refunds and reversals depend on the circumstances and applicable law; mandatory consumer rights remain intact.
7. Community and content
Respect other players in profiles, clubs, events and chat. Do not harass, threaten, stalk, exploit, impersonate, discriminate unlawfully, distribute sexual content involving minors, send spam, run scams, infringe others' rights or publish private information without authority. Do not distribute malware, access accounts without permission, bypass access restrictions, disrupt the service, or collect player data for unrelated purposes.
You retain ownership of content you supply. You give Pixel Nomads a non-exclusive, worldwide, royalty-free permission to store, technically adapt, display and distribute it only as needed to operate Dinkzo and provide your requested sharing. This does not transfer ownership or allow unrelated commercialization of your content. Permission ends when the content is removed from active use, subject to necessary lawful retention and technical recovery copies.
Only contribute material you have the right to use, including event graphics, club details and messages. Shared event results and messages can involve other people; account deletion and erasure are handled as described in the Privacy Policy. Other people may retain independent copies outside our control.
Report abusive or infringing content through available feedback tools or the contact form, identifying the event or content concerned. We may investigate, remove content or restrict access where reasonably necessary for safety, security, legal obligations or enforcement of these Terms. You can contact us to request review of a moderation decision.
8. Physical activity and safety
Pickleball involves physical risks such as injury, collision, heat and equipment hazards. Assess your ability and conditions, follow venue safety instructions and seek qualified medical advice when appropriate. Organizers should plan appropriate supervision and emergency arrangements.
Dinkzo's guides and statistics are general information, not personalized coaching or medical advice. Dinkzo is not an emergency service and does not monitor player safety. Contact the appropriate emergency service if urgent help is needed. Nothing here excludes responsibility that cannot lawfully be excluded.
9. External services and app rights
Authentication, maps, payments, venues and linked websites have their own terms and privacy practices. Their services can change or become unavailable. Google Maps features are also subject to the Google Maps terms and Google Privacy Policy. References to outside brands or organizations do not imply endorsement.
Pixel Nomads and its licensors retain their rights in Dinkzo's software, branding and original service material. You may use the service for its intended purpose while complying with these Terms. Do not misrepresent an unofficial app or service as Dinkzo. Applicable open-source licenses and rights permitted by law are not overridden by these Terms.
10. Availability and responsibility
We aim to provide a useful service but cannot guarantee uninterrupted access or error-free event information, scores, maps or calculations. Connectivity, maintenance and third-party outages can affect use. Keep independent copies of important event and payment records.
To the extent allowed by law, Dinkzo is provided as available without additional guarantees of suitability for a particular purpose. We do not take responsibility for an independent organizer's performance merely by displaying its event. Responsibility for loss depends on applicable law and the facts. Nothing excludes or limits liability for fraud, willful misconduct, gross negligence, or any liability or consumer right that cannot legally be excluded or limited.
11. Ending use and deletion
You may stop using Dinkzo or request deletion through Profile → Settings → Delete account. See account and data deletion instructions for the email route and the treatment of shared records. Uninstalling the app does not delete the account.
Before leaving, coordinate any event cancellation, club administration or fee matter you manage. Account deletion does not automatically refund fees, revoke an external venue booking or remove every shared match record. You may request review and removal of identifying data as explained in the Privacy Policy.
We may suspend or end access for serious or repeated misuse, security threats or legal requirements. Where appropriate, we explain the reason and offer a review route; urgent protective action may occur first.
12. Changes, disputes and contact
We publish revisions with an updated date and provide appropriate notice of material changes. Where renewed acceptance is required, it must be obtained through an appropriate process. A new version does not retroactively remove accrued rights.
Philippine law governs these Terms, subject to mandatory protections applicable in your location. Contact us first so we can try to resolve a concern. You retain access to competent courts, regulators and remedies available under law; these Terms impose no mandatory arbitration requirement. If one provision is unenforceable, the remaining provisions apply to the extent permitted by law.
Contact Pixel Nomads through the contact form or the address below.
Website privacy information
This information describes this studio website. RunXRoam and Dinkzo are separate products and may handle information differently.
Your messages
When you submit this form, Netlify processes your name, email address, selected topic and message to deliver your inquiry to Pixel Nomads. Netlify also processes technical request information and applies spam filtering. We use your message to respond, manage support and continue the conversation by email. Our team can reply using the email address you supply.
Storage and service providers
Submissions may be stored in Netlify Forms and our company inbox, with access limited to those handling inquiries. Netlify and our email providers may process data outside your country. We keep correspondence while needed for the inquiry and any applicable legal or security requirement; you can request access, correction or deletion through this form. Do not include passwords, payment credentials or unnecessary sensitive information. See Netlify’s privacy information.
Cookies and browser storage
This website uses browser storage to remember your privacy choice for six months on this browser. The record contains your font preference, the notice version and the time it was saved. It does not contain your name, email or form entries. You can change the choice using Cookie preferences in the footer or remove it by clearing site data. If browser storage is blocked, the choice applies for the current page and the panel may appear again on another visit.
No analytics or advertising trackers are installed. The only optional category is appearance: Accept all permits Google Fonts, while Reject optional uses system fonts. Contact forms and navigation work with either choice. Closing the panel or pressing Escape does not save consent. Before introducing optional services requiring consent, we will update this notice and request a new choice. Your choice here applies to this studio website; it does not change consent inside RunXRoam or Dinkzo. Hosting services may process technical requests to serve the site, and submitting a contact form uses the processing explained above.
App privacy and requests
Use the product-specific policy links when they are available. For a privacy question, visit Get in touch and choose Privacy request.
Operator and contact
Pixel Nomads is founded by Luna and Yuki. For website privacy questions or requests, use the contact form. Product account requests are explained in each app’s privacy policy.
Optional web fonts
With your permission, we load Google Fonts to display the site’s typefaces. Your browser contacts fonts.googleapis.com and fonts.gstatic.com, which receive your IP address and request information needed to deliver the fonts. Reject optional to use system fonts instead. Change this choice using Cookie preferences; withdrawing permission stops future font loads on the current page but cannot undo requests already sent or erase the browser’s font cache. See Google’s Privacy Policy.
Requests for updates
If you submit a next-app or Dinkzo ladders notification request, we use the email you provide to respond with the updates you requested. These requests use the same Netlify submission service as contact messages. Ask us through the contact form to withdraw your request or remove your address; submitting does not create an app account or promise a release date.
Website information
This website introduces Pixel Nomads and its products. App availability, supported platforms, and pricing should be checked on the linked product or store page when available.
Product terms
Studio information does not replace an app’s own terms or privacy policy. Refer to the product-specific documents before using its services.
Ideas and feedback
Please keep initial inquiries general and do not include passwords, confidential business information, or sensitive personal information.
Questions
Visit Get in touch for support and general inquiries.
About Pixel Nomads
Founded by Luna and Yuki, Pixel Nomads builds free, nonprofit apps. Event fees charged by independent organizers and optional voluntary developer support are separate from free app access.
Information and links
Features and external services can change. Confirm event information with the organizer and review the app-specific terms before using a product. Contact the contact form to report incorrect website information.
HELP / FEEDBACK / PRIVACY
Let’s get you moving.
Find an answer or reach the team through the contact form.
12 help topics
RunXRoam · Does RunXRoam record live GPS workouts?
RunXRoam brings together imported activities and manual entries. It does not currently record live GPS workouts. Foreground location can help find nearby events.
RunXRoam · Which activity files can I import?
GPX, FIT, TCX and CSV files are supported. You can select several files and review each activity and duplicate before saving. Keep a copy of the original file.
RunXRoam · Where do I send feedback?
Open Profile → Support → Feedback & contact. Follow your conversation under My Feedback; replies appear in the app. If you cannot access your account, use the website contact form.
RunXRoam · An import or share image looks wrong. What should I include?
Tell us the file type or share-card style, your device and browser or app version, the steps you took, and what you expected. Remove private routes and personal information from screenshots before sharing.
RunXRoam · Does RunXRoam take payments for events or stores?
No. It brings useful links together. Register and pay through the event organizer’s official channels, and buy gear through the store’s official channels. RunXRoam is independent of listed organizers and stores.
RunXRoam · How can I support the developers?
Optional one-time developer support uses Google Play Billing in supported Android builds. It is separate from event and store payments. Core use stays free; the app explains any supporter points, badges or optional extras before purchase.
Dinkzo · Does joining an event reserve a court?
A join request or queue position does not guarantee entry or a venue reservation. Check acceptance, court availability, fees and cancellation rules with the organizer.
Dinkzo · Does Dinkzo charge event fees in the app?
Event fees are settled with the organizer. Dinkzo records fee status; a Paid label is not independent confirmation of a bank or wallet transfer.
Dinkzo · Where do I report a problem with Dinkzo?
Open Profile → Settings → Feedback. For an event score or participation question, contact the organizer first. You can also use the website contact form.
Dinkzo · Can I start a new bracket?
The bracket builder is currently unavailable for new brackets. Existing event brackets can remain accessible. Check the tools available in your event.
Both apps · How do I delete my account?
Follow the product-specific deletion instructions below. Uninstalling an app does not delete your account. You can also request deletion through the website contact form without installing the app.
Both apps · What should a bug report include?
Include the app name, device, operating system, browser or app version, steps to reproduce, expected behavior and actual behavior. Never include passwords, PINs or one-time codes.
Account and data deletion
Still need help?
WEBSITE / UPDATES
What’s new here.
October 29, 2026
RunXRoam’s Privacy Policy and Terms now cover native recording, health connections, saved GPX routes, private messages, optional AI assistance and recaps, Strava file imports, and platform-store developer support.
October 15, 2026
Meet Luna and Yuki on our new About us page. RunXRoam’s policies now explain Google Play developer support, independent event and store links, and the latest privacy controls.
October 8, 2026
Product pages now link to both web apps and explain activity imports, event organization and scoring. New support guides cover feedback and deletion, and both apps’ policies are easier to find.
These are website updates. App features can differ by platform and version.