Privacy Center
How Moto Event Hub handles event, rider, and check-in data
Plain-language privacy details for riders, organizers, assistants, beta testers, and sponsors.
Full privacy policy
Riders and passengers
What organizers can manage
- Participant name or account identity for people attached to their event.
- Rider/passenger type, present/listed/no-show/removed status, and paid/unpaid status.
- Poker-card entries and poker-hand results for managed poker-run events.
- Final-stop readiness for poker-card handling when check-ins are enabled.
GPS check-ins
What GPS is used for
- Checked-in riders/passengers may use Stop Check-In when the organizer enables the feature for a route event.
- The browser asks for location permission at check-in time.
- The server compares that one GPS point to the selected stop and saves whether the check-in was verified.
- Stop Check-In records are used for event operations and reporting; Moto Event Hub does not provide live tracking between stops.
QR codes
What QR codes do
- Event QR codes help riders open event pages, scan event check-in codes where enabled, and may be counted for event/flyer analytics.
- Registered account QR codes help organizers add a rider faster during event registration.
- Assistant codes are event-specific and expire automatically 24 hours after the event ends.
Waivers
How waiver visibility works
- Waivers are optional and controlled by the organizer for each event.
- If enabled, riders can view the waiver on the public event page.
- Organizers can choose whether riders may sign ahead of time.
- Individual signed waiver details are only visible after that rider/passenger has been checked in.
Contact privacy
Organizer contact controls
- The Contact organizer form routes messages through the site by default.
- Direct email, phone, website, and Facebook fields only show publicly when the organizer chooses to show them.
- Rider names for saved/interested/going counts are never shown on the public event page.
Beta site
What beta tracking means
- Beta page visits and actions may be logged so issues can be traced during testing.
- Beta tracking is separated from live/test environments.
- Beta users can view the detailed beta changelog and submit beta feedback.