Terms

Effective date: April 25, 2026

LAN Party Scheduler is provided to organizers for creating and operating LAN party schedules, attendee signup flows, and session coordination during the hosted beta.

Organizer Responsibilities

  • Use the service for lawful event coordination and keep attendee-facing information accurate.
  • Collect only event information needed for scheduling, attendance, payments, or venue operations.
  • Manage public/private event visibility carefully before sharing attendee links.
  • Respond to attendee data requests for the events and communities the organizer operates.
  • Request support actions with a clear reason when tenant access, billing, deactivation, export, or deletion is involved.

Acceptable Use

Do not use the service for unlawful activity, harassment, credential abuse, spam, payment fraud, attempts to bypass tenant isolation, or attempts to disrupt another organizer's event. Accounts or tenants may be rate limited, suspended, or disabled when needed to protect attendees, organizers, or the hosted service.

Service Operation

Hosted beta environments may change as the product matures. Operational maintenance, migrations, rollback, monitoring, and support intervention may be required to keep schedules available and protect tenant data.

Billing And Plan Limits

Hosted beta plans may limit attendee counts or paid expansion until billing is active. Stripe checkout, portal access, invoices, support-grace periods, and manual support interventions may be used to resolve billing state during beta.

Account And Tenant Changes

Destructive support changes require an explicit support reason and are recorded in the tenant support action log. Deletion requests may require an export, deactivation period, and billing or security review before final removal.

Beta Expectations

The service is intended to support real organizer pilots, but beta operation may include planned changes, manual onboarding help, and support-led corrections. Organizers should keep event-critical communication channels available outside the app until their hosted workflow has been proven for their event.