Organiser Rules

• An organisation owner and every person with authority to publish or operate its events must be at least 18 years old.
• The person publishing an event confirms that they are authorised to act for the named organiser.
• The organiser - not its Strave profile - is the person or legal entity responsible for the event, entry fees, refunds, prizes, taxes, and participant-facing legal obligations.
• The organiser must provide accurate identity, business, and payment information when Strave, Stripe, or applicable law requires it.

All applications and registrations for an event published on Strave must be submitted and recorded through Strave. This requirement applies to open, closed, qualification-based, and invite-only events.

• Do not require teams or players to register solely through Discord, Google Forms, another website, direct messages, or another off-platform process.
• Use Strave invitations, approval controls, eligibility settings, and custom signup questions for closed or information-heavy signups.
• An external service may be used only for a step Strave expressly allows, such as an approved payment page or required third-party identity check.
• Do not use an external step to hide participants, evade Strave limits or fees, or deprive participants of a reliable registration record.

Custom signup questions are generally available without an additional charge. Strave may apply disclosed limits or pricing based on usage; any charge will be shown before it is incurred.

Publishing an event represents a genuine intention and reasonable ability to host it as advertised. Before accepting registrations, the organiser must clearly state:

• Eligibility, format, schedule, and material participation rules.
• Entry-fee amount, collection method, and refund conditions.
• Prize amounts or items, eligibility conditions, allocation, and expected delivery schedule.
• Disqualification grounds, protest process, and material competitive sanctions.
• Whether participants younger than 18 are permitted in a paid or prize-bearing event and what consent is required.

A rulebook must be accessible before signup and must not contradict the Terms of Service, the Code of Conduct, these rules, or mandatory law. Material changes must be communicated promptly and must not be applied retroactively where that would unfairly disadvantage a participant.

An organiser may disqualify a team or player only on a ground allowed by its published rulebook, the Terms of Service, this Code of Conduct, or applicable law. Rules must be applied consistently and in good faith.

A properly disqualified participant is not entitled to an entry-fee refund solely because of the disqualification, unless the event rulebook or mandatory law says otherwise.

The organiser remains the tournament administrator. A Strave review of refund eligibility does not pause the event, restore the participant, or change competitive results.

A disqualified team or player may ask Strave to review whether the disqualification complied with the event’s published rules for the limited purpose of entry-fee eligibility.

1. The request must be submitted through strave.gg/support or by email within 14 days after the disqualification.
2. The requester must identify the event, decision, relevant rule, and supporting evidence.
3. Strave may request information from the organiser and affected participant.
4. If Strave determines that the disqualification did not follow the published rules, the organiser must issue the entry-fee refund within 30 days after notice is sent to the organisation owner’s registered email address.

Review time depends on complexity, cooperation, available evidence, and staff capacity. Strave does not guarantee a fixed completion date, but will handle the review as promptly as reasonably possible.

The review is an internal contractual process. It does not determine legal liability, prevent either party from pursuing legal remedies, or control how a court or authority evaluates the evidence.

Strave may issue one or more strikes when an organiser or its responsible operators violate these rules. The number of strikes depends on severity, harm, intent, repetition, cooperation, and whether the organiser corrected the violation.

• A lower-impact first violation will ordinarily result in one strike and corrective instructions.
• Serious failures, including an unjustified refusal to refund entry fees or provide prizes, may result in multiple strikes.
• At three active strikes, Strave may prevent the organisation and responsible operators from publishing or operating events.
• Each strike expires two years after issue unless Strave withdraws or invalidates it earlier.

The notice will identify the reason, strike count, expiry date, required corrective action, and available review route. Strave may attribute a strike to related organisations or operators where there is credible evidence that a new profile is being used to evade enforcement.

Organisers may enforce their event rulebooks and are not required to adopt a Strave cheating ban unless their event is Strave-operated, partnered under terms requiring it, or their own rulebook incorporates the ban list.

Strave does not automatically verify or endorse an independent organiser’s local ban. However, Strave may separately act when the same conduct violates platform rules, threatens users or the service, or requires action under applicable law.