PedalaPlay Terms of Service
Review-ready terms scaffold for organizers and players using PedalaPlay to manage recurring football groups.
Document status
This draft describes the intended B2C launch product and must be reviewed by qualified legal counsel before public paid launch.
Until approved, it should be treated as operational guidance for beta users, not final legal terms.
What PedalaPlay provides
PedalaPlay is planned as a SaaS for organizers who run recurring football groups and players who join those groups by invite.
- Organizers can create an arena, configure groups, define recurring schedules, publish payment plans, and invite players.
- Players can accept invites, authenticate, pay, review access status, and confirm attendance for upcoming games.
- PedalaPlay is the product source of truth for membership, access, attendance, and operational communication state.
Accounts and roles
A person may be an organizer in one arena and a player in another community. The product must keep those roles separate in navigation, permissions, and user experience.
Users are responsible for keeping login credentials secure and for using PedalaPlay only for lawful group operations.
Payments and subscriptions
Stripe card recurring is the primary launch payment lane. Pix support depends on provider-backed validation before broad exposure.
Organizers and players must review plan price, payment timing, cancellation/refund rules, and provider disclosure before production payments.
Operational communications
Discord can support community access and coordination, but payment and membership truth remain inside PedalaPlay.
WhatsApp, when enabled, is limited to individual transactional reminders with opt-in, approved templates, quotas, and fallback behavior. PedalaPlay does not manage WhatsApp groups or marketing blasts.
Deferred scope
Native mobile, public marketplace discovery, and the future B2B venue product are deferred and should not be treated as live launch promises.
Before public launch
PedalaPlay must replace review placeholders with approved legal copy, keep payment/provider wording aligned with the current runtime, and update these pages whenever launch scope changes.