Privacy

Information should serve the weekend—not become the product

This overview explains the MXEvents product’s intended data practices. Deployment-specific contact and legal details should be reviewed before a broad public launch.

Information the product handles

MXEvents may handle account identity, roles, contact information, family and rider profiles, emergency contacts, event activity, registrations, order records, waiver evidence, passes, track claims, reports, and support communications. Some information is provided by organizers or other authorized users.

How information is used

Information is used to operate accounts, publish events, complete registration and waiver workflows, issue passes, communicate official changes, prevent abuse, support users, and improve reliability. Public profiles and event pages display only fields intended for public discovery.

Service providers and payments

MXEvents relies on infrastructure and service providers to host data, authenticate accounts, deliver communications, process payments, and monitor the product. Payment-card details are entered with the payment provider; MXEvents stores transaction identifiers, status, and receipt information needed to operate an order.

Control and retention

Account settings provide controls for profile and notification information. Operational, financial, trust, waiver, and audit records may need longer retention for safety, dispute, compliance, and fraud-prevention purposes. Access is restricted by role and record ownership.

Sensitive information

Do not place passwords, complete card numbers, medical records, government identifiers, or unrelated sensitive details in public event fields, comments, or support messages.