This agreement applies when you list or create an event on Next Lap as a club, organiser, or entity representative. It is in addition to our general Terms of Use and Privacy Policy.
TL;DR — These rules apply when you list an event on Next Lap.
- You must provide truthful event details (dates, location, distances, fees, capacity, and policies).
- You are responsible for keeping the listing up to date before and after publication.
- You must not mislead participants about what the event includes.
TL;DR — Tell the truth. Keep your listing current.
- For paid events, you must honour the cancellation policy you select for the listing.
- Payments are processed through our payment partners. You must not bypass platform payment flows for managed listings.
- Refunds and cancellations follow the policy shown to participants at registration, except where this agreement or platform rules require a full refund.
- If a participant cancels, their refund under your policy is reduced by the platform cancellation fee (processing on the original payment and on the refund), calculated on the registration amount.
- Unless your own policy or organiser agreement says otherwise, if you cancel the event, paid participants receive full refunds and you fund the platform cancellation fee from your payouts, holds, or invoice if needed, unless you change the festival’s cancel-fee switch so participants fund that fee from their refund.
- Unless your own policy or organiser agreement says otherwise, if you remove a participant from a paid registration (for example because they are not qualified), they receive a refund of the registration amount minus the platform cancellation fee, unless you turn on organiser-funded removal fees for that festival. When that switch is on, they receive a full refund and you fund the platform cancellation fee from your payouts, holds, or invoice if needed.
- A “full refund” means the participant receives 100% of what they paid. You must fund the platform cancellation fee on the refund from your payouts, holds, or invoice if needed.
- Unless your own policy or organiser agreement says otherwise, if you change a published event date in the listing, you must keep the listing accurate. Existing registrations remain valid for the new date unless a participant cancels within the date-change refund window described in the Event Registration Terms.
- Each event may have only one published date change with participant notice on Next Lap. If you need to move an event date again, cancel the event instead.
- Saving a published date change triggers email notice to registered participants. You cannot save that change without sending the notice.
- If participants cancel after a date change and are owed full refunds, you must fund those refunds using the recovery order below, even when your normal cancellation policy would allow a lower refund.
- When refunds are due, Next Lap may fund them from amounts not yet paid to you, then from any payout hold, then by deducting from your future payouts.
- Next Lap may freeze further payouts (including any hold) until refunds and settlement are complete.
- If those sources are not enough, you must repay the shortfall on invoice within 14 days, or Next Lap may offset it against future amounts owed to you.
TL;DR — Honor your cancellation policy and use platform payments. Unless your own policy says otherwise, fund full refunds if you cancel or move a published date once. Festival cancel-fee and removal-fee switches decide who pays the cancel fee for those actions.
4.
Tax invoices, TCS, and TDS
- You authorise Next Lap to generate GST Tax Invoices or Bills of Supply on your behalf for registrations on managed listings.
- You must provide accurate PAN, entity type (legal status), GSTIN where applicable, and other payout tax details, and keep them up to date.
- Where the law requires it, Tax Collected at Source (TCS) will be deducted from your payouts; you acknowledge this when you accept this agreement.
- Where required under Section 194-O of the Income Tax Act, Tax Deducted at Source (TDS) on e-commerce operator payouts will be calculated when a registration payment is recorded and withheld from amounts paid to you.
- TDS is calculated on the taxable registration value excluding GST, before platform fees.
- For individuals and Hindu Undivided Families (HUFs), TDS applies only after your cumulative registrations in the financial year cross the statutory threshold; for other entity types, TDS may apply from the first sale.
- TDS may be withheld together with TCS from your bank payout. Next Lap will maintain records for compliance and Form 16A where applicable.
TL;DR — Keep tax details accurate; TCS and Section 194-O TDS may be withheld from payouts when the law requires.
- You may receive registration data, including health or medical information when collected, to run the event safely.
- Use it only for this event’s operations, safety, eligibility, and necessary participant communication.
- Do not use it for marketing, advertising, or any purpose unrelated to this event, unless you have a separate lawful basis and the participant’s clear permission.
- Limit access to people who need it for those purposes (including authorised medical/safety staff).
- Follow applicable privacy laws and our Privacy Policy. You are responsible for how your team handles this data on and off the platform.
TL;DR — Event use only — no marketing reuse; keep access tight.
- New or updated listings may be pending until reviewed.
- Next Lap may hide, reject, or request changes to listings that breach these terms or platform rules.
TL;DR — Listings can be pending or changed before they go live.
- You run the event and are responsible for safety, permits, and on-ground operations.
- Next Lap provides listing, registration, and payment tools — not event-day operations unless clearly stated.
- For participants under 18, Next Lap requests parent/guardian consent and shows you its status. You must confirm a parent/guardian has consented before a minor takes part (for example at bib pickup, check-in, or the start line).
TL;DR — You run the event. We provide the platform. Check parent consent before a minor runs.
When you accept this agreement at event creation, we record which version you accepted, the date and time of acceptance, your user account, entity context, and technical metadata for audit and compliance.
TL;DR — We log the agreement version and when you accepted.