Privacy

Effective date: April 25, 2026

LAN Party Scheduler stores the organizer, attendee, event, billing-support, and operational data needed to run hosted LAN party schedules and support organizers during the beta.

Who Controls Event Data

Each organizer is responsible for the event content and attendee data they collect for their LAN event. LAN Party Scheduler acts as the hosted service operator for authentication, scheduling, support, billing, security, and reliability.

Data We Collect

• Organizer account details such as name, email, authentication state, organization, and billing support metadata.
• Attendee profile details such as event nickname, email, Steam identifiers when linked, avatar URL, attendance, session signups, and event preferences.
• Event content such as schedules, sessions, comments, custom pages, map layouts, payment records, and organizer configuration.
• Security and support records such as login throttling, account recovery, service-email delivery state, activation events, support actions, and restore-drill evidence.

How We Use Data

Data is used to authenticate users, display schedules, enforce player caps, operate paid-beta tenants, prevent abuse, support account recovery, diagnose hosted incidents, and help organizers understand whether their event is ready to share.

Service Providers

Hosted operation may use infrastructure, payment, email, monitoring, and support providers. Those providers are used only to operate the service, process organizer billing, deliver service email, detect abuse, or diagnose incidents.

Retention And Deletion

Tenant event data is retained while the organizer account is active or while support needs it for billing, security, recovery, or incident review. Organizers can export tenant data for review, request immediate tenant deactivation, and request deletion review. Final deletion is coordinated after billing, security, abuse-prevention, and account-recovery checks are complete.

Security and operational records such as support actions, abuse events, recovery events, email-delivery diagnostics, and billing evidence may be retained separately when needed to protect the service, respond to disputes, or prove support actions.

Support Access

Support superadmins may inspect tenant activity, email diagnostics, recovery state, billing state, and restore-drill evidence when helping an organizer or investigating a hosted incident. Tenant-changing support actions require a reason and are recorded in the support action log.

Contact

Organizers should contact support from their account email to request data export help, deactivation, or deletion review.