Legal

Organiser terms

The agreement between PartyPPL and clubs, festivals, promoters and booking agencies with an organisation account. In addition to the terms of service.

Last updated: 1 October 2026

Draft. This text has not been reviewed by a lawyer either. Have it checked before you use it as a contract, in particular the articles on ticket money, payouts, VAT, liability and the processing arrangements.

1What these terms apply to

These terms apply to everyone with an organisation account in the portal: posting events, selling tickets, loading tickets from another shop, featuring and the API.

Counterparty
PartyPPL, a product of NEXG3N
Chamber of Commerce number
97359866
VAT identification number
NL005264805B67
Address and further company details
Colophon

The terms of service, the house rules and the privacy statement apply as well. Where these terms differ, they prevail.

You enter into this agreement as a business, not as a consumer. You accept it when you create an organisation in the portal; the data processing agreement is part of it. Whoever creates the organisation declares that they may represent it.

2Organisation account and roles

An organisation has one or more owners and can add team members. This is what each role may do, as the portal enforces it:

Owner
Everything. Only an owner can make someone else an owner, and the last owner cannot be removed.
Administrator
Everything except appointing owners: events, team, settings, verification, featuring, API tokens, cancelling and postponing, the door and scanners, finance, the Stripe connection and every export.
Marketing
Events, studio, the dashboard and the statistics and insights per event, including sales numbers. No finance, no door, no exports.
Door
The door and the scanner, the guest list, and the ticket export and guest list as CSV, with the buyer's e-mail address. This role cannot manage scanners.
Finance
Finance and its export, the Stripe connection, and loading tickets from another shop (with visitors' e-mail addresses).

Every role sees the dashboard and the verification status. You are responsible for who you give access. When someone leaves, remove them from the team, and revoke API tokens you no longer use.

3Verification

An owner or administrator requests verification in the portal with the Chamber of Commerce or VAT number and a Chamber of Commerce extract (PDF, JPG or PNG, at most 8 MB), and optionally a website, contact address and note. The agenda team decides.

The extract sits in shielded storage. Only your team and our administrators can open it.

If you sell tickets through PartyPPL or feature an event, we ask you to get verified. Until that has happened, we may stop sales and featuring.

4Posting events

Posting events is free, unlimited, for all genres, in the Netherlands and Belgium.

You guarantee that:

  • date, time, venue, age limit and prices are correct;
  • the line-up is booked, without names "for illustration";
  • you have the permits and follow the rules of the municipality and the venue;
  • you hold the rights to artwork, photos, site maps and texts you upload.

If anything changes, update it straight away. Cancelling and postponing is done in the portal; visitors then hear it automatically.

5Moderation, import and completion

Every new event you post goes past the agenda team before it becomes visible, usually within 24 hours.

We may refuse, adjust or take an event offline if it is a duplicate, incorrect, not nightlife, breaks the house rules or a third party rightly objects. You hear why.

We also import listings from public sources and publish them automatically. If your event is in the agenda that way and something is wrong, claim it or mail us.

We complete events: a model (Claude by Anthropic) searches your site and your shop for the poster, a site map, the ticket types and the official shop, and writes a description from the facts. A site map only goes live after a person has approved it. If an addition is wrong, change it in the portal or report it.

For repeated misleading information, ghost events or posting on behalf of others without a mandate we may suspend the account.

You can object to a decision within six months through [email protected]. Someone other than the person who decided answers within five working days.

6Image rights and intellectual property

Your artwork, photos, site maps and texts stay yours. You give us a non-exclusive, royalty-free licence to show them on the platform, in the apps, in widgets and Apple Wallet, in notifications and e-mails, and in posts on our own social channels (Facebook, Instagram, Bluesky, Mastodon), and to resize them where technically needed.

That licence continues for past events, because the agenda is also an archive. If you want images removed from the archive, we remove them.

If we receive a claim about images you uploaded, you bear it.

The name PartyPPL, the logo and the design are ours. Saying that you sell through PartyPPL and linking to us is fine.

The agenda as a whole is our database. Systematically copying substantial parts is not allowed, also not through the API.

7Selling tickets through PartyPPL

Selling through PartyPPL is optional. You can also link to your own shop; we ask for no exclusivity.

If you sell through us:

  • you are the seller. The agreement for entry is between you and the visitor; we sell on your behalf and handle payment;
  • you set prices, ticket types, quantities, the maximum per order, sale windows and discount codes;
  • you are responsible for VAT on the ticket price and your own accounts;
  • you have to deliver: hold the event, and refund if that does not work out;
  • we provide ordering, ticket codes, Apple Wallet, the scanner, the guest list and the financial overview;
  • buyers must be able to know who they buy from. Your name is on your events, and we give a buyer your Chamber of Commerce or VAT number from the verification on request.

Visitors have no cooling-off period for tickets to an event on a fixed date (art. 6:230p(e) Dutch Civil Code).

Resale through PartyPPL is always on for tickets sold through us, at the list price of the ticket type. The buyer pays the service fee; that money and the payout to the seller run through us, not through you. Visitors can also pass tickets on. The scan at the door lets a ticket in only once.

8Service fee

PartyPPL charges € 0.99 per ticket plus 2% of the ticket amount after discount. No subscription, no set-up costs, no cost per event.

The visitor pays the service fee on top of your ticket price; it is shown separately in the order screen and at payment. If you want to carry it yourself, lower your ticket price.

The amounts are what is charged, including VAT where VAT is due. You pay the VAT on your ticket price yourself; we withhold nothing for it.

We do not produce invoices automatically at the moment. The portal shows your sales and the service fee, and with Stripe Connect the amounts are also in your Stripe dashboard, but an invoice with a VAT breakdown for the service fee or featuring does not come by itself. If you need one for your accounts, mail [email protected] and we make it by hand.

Payment costs for iDEAL and cards are included in the service fee. Chargebacks and their costs are for the seller, so for you, unless we caused them.

If we change the rates, we announce it at least 30 days ahead. Tickets already sold keep the old rate.

9Payouts

There are two routes:

With Stripe Connect Express (recommended)
An owner, administrator or finance member connects a Stripe Express account once: company details, identity and bank account, at Stripe. After that the ticket money goes straight to your Stripe account on every payment, Stripe withholds the service fee for us and pays out on your schedule. We never see your bank account number.
Without a connection
We collect the ticket money and transfer it by hand, within 3 working days after the event, as the portal says. The portal stores no bank account numbers; we ask for yours by e-mail. The Stripe route is faster and more predictable.

The overview under Finance calculates with the list price. If you used discount codes, what Stripe actually received is leading.

We hold back payouts if an event is cancelled, if there is an investigation into fraud or deception, or if many buyers complain. We say why and for how long.

If you connect Stripe, you make an agreement with Stripe yourself: the Stripe Connected Account Agreement, which includes the Stripe Services Agreement. We are not a party to it. Stripe does its own identity and anti-money-laundering checks; if Stripe blocks a payout, we cannot change that.

If a payout is wrong, report it within 60 days.

10Cancelling, postponing and refunds

An owner and an administrator can cancel and postpone, in the event tools or under Finance.

Cancelling with refunds
The platform refunds every paid order in full, service fee included, voids the tickets and tells buyers, everyone who said "I'm going" and the watchlist in the app, by push and by e-mail, plus a pinned message in the group chat. The ticket price is at your expense: with Stripe Connect it is taken back from your account; if the money was already transferred to you by hand, we offset it or you pay it back within 14 days. We refund the service fee.
Cancelling without refunds
Only in the event tools: you untick refunding. The tickets lapse and visitors read that you handle the refund yourself. Then you have to do so, in full and quickly.
Postponing
The date moves, tickets stay valid and everyone hears it the same way. The platform does not handle money back on postponement; if you want to offer it, mail us.

If you leave refunds unpaid or cancel systematically, we stop your ticket sales and offset outstanding amounts.

11Tickets from another shop

If you sold tickets at Eventix/Weeztix, Paylogic, Ticketmaster, Weezevent or a shop of your own, you can load them with a CSV in the portal or through the API. Owners, administrators and finance can do that.

Per ticket you give the e-mail address, the code, the type, the name and the price. If the address has an account, the ticket is there straight away. Otherwise we send one mail that the ticket is waiting, unless you turn that off. After that we erase the address and keep only an encrypted fingerprint to link the ticket once that person logs in.

You need a legal basis for passing that data to us. We use it only to deliver the ticket and scan it at the door. These tickets cannot be resold through PartyPPL.

12Featuring

Besides the service fee we earn on featured placements:

City · € 149
7 days at the top of the agenda of your venue's city.
National · € 490
14 days at the top of the agenda, in the "Uitgelicht · Landelijk" block on the home page and first in trending.

Featured events also come first in "For you" on the home page, regardless of the visitor's genres.

These are the amounts you pay, including VAT where VAT is due. An owner or administrator books a slot, city or national, in the portal under Featuring and pays in advance through Stripe, by card or iDEAL. The event must be approved. The slot starts on the day of payment.

Featuring is advertising space, recognisable as featured. It buys placement, nothing more: no extra push notification, no editorial attention, no priority in moderation and no promised number of visitors.

If the event is cancelled before the slot starts, or we cannot deliver the slot, you get your money back; if it is already running, pro rata. Refunding a slot is done by hand; mail us.

13Visitor data

At the door
The name on the ticket, the ticket type and the scan status.
In the exports
The ticket export has the columns Code, Type, Houder, E-mail, Status, Gescand, Gekocht and Prijs; it holds the buyer's e-mail address. That and the guest list can be made by owner, administrator and door. The door export per night shows the e-mail addresses of your own door staff, not of visitors.
In overviews
Counts: "I'm going", sales per ticket type, cities. No names.

For what you do with it, you are a controller yourself. You use it only to let people in and to inform buyers about that event. For a newsletter, reselling or combining with other files you need a legal basis of your own.

For guest lists and door data you enter yourself, it works the other way round; see the next article.

14Data processing agreement

For the guest list, door scans, exports and tickets from another shop you are the controller and we are the processor. For accounts, the platform and our own ticket sales PartyPPL itself is the controller.

The arrangements article 28 GDPR asks for are in the data processing agreement. It is part of these terms. In brief:

  • we process only on your instructions, with confidentiality and the security described there;
  • we use only the subprocessors on Subprocessors; we announce a new one 30 days in advance and you can object;
  • we report a breach in your data within 36 hours; you make the notification to the Dutch Data Protection Authority;
  • we delete door scans 12 months after the night, tickets from another shop 13 months after the night, and at the end the rest within 60 days.

What you promise: a valid legal basis, informing your guests yourself, entering no more than needed and no special categories of data.

15The API

With the API you connect your own site, till, scanner or dashboard. Owners and administrators create tokens in the portal, with the scopes read, scan, attendance and tickets. A token sees only your own organisation; we keep only a hash of it. The same rules apply to our MCP server.

The rules, version 2026-09-22, also at /v1/terms. The full terms, with tokens, limits and personal data, are on API terms:

  1. Credit PartyPPL wherever you show this data, with a link back to the event's page on partyppl.nl.
  2. Do not redistribute the catalogue as a whole, and do not resell it as a data product.
  3. Do not present the data as your own, and do not strip the link back.
  4. Cache what you fetch. Stay inside the rate limits rather than working around them with more tokens.
  5. Event data comes from the organisers themselves and from the public agendas listed on Sources; each source keeps its own rights and licence.
  6. We correct and remove events as organisers ask us to. Refresh what you have cached at least once a day.

Limits: 120 requests per minute per token and 10,000 per day by default. Buying, transferring or refunding tickets, chats and data about individual visitors are not in the API. Questions: [email protected].

16Liability and indemnity

The event is yours. You are liable for it going ahead, the programme, safety, permits, the door, the accuracy of what you announce, refunding buyers if it does not go ahead, and the VAT and taxes on your sales.

You indemnify PartyPPL against claims from visitors, buyers, artists, venues, rights holders and regulators arising from your event, your listing, your ticket sales or your use of visitor data, including reasonable legal costs and fines caused by you.

Our liability is limited to direct damage and to the service fees and featuring amounts we earned on your sales and bookings in the twelve months before, per event or series of connected events. Not for lost revenue or consequential damage. This does not apply to intent or deliberate recklessness on the part of us or our management.

We promise no number of visitors, sales or impressions, and no uninterrupted availability of the portal or the scanner.

Force majeure suspends our obligations, including outages at Cloudflare, Stripe, Resend or Apple, attacks, power and network failures and government measures.

A claim lapses if you do not report it within twelve months.

17Ending the agreement

You can close your organisation account at any time. Sold tickets stay valid, payouts continue and we refund a slot that has not started.

We may end the agreement immediately for serious or repeated breaches, fraud, systematically not refunding, bankruptcy or suspension of payments.

Past events stay in the archive. Your organisation page and future events we remove on request.

What by its nature continues, stays in force: liability, indemnity, confidentiality and the processing arrangements while data remains.

18Complaints, governing law and competent court

A complaint about a payout, a rejected event or something else? Mail [email protected]. Within two working days a confirmation, within fourteen days a substantive answer, or a new deadline with a reason.

These terms are governed by Dutch law. The Vienna Sales Convention is excluded.

Disputes go to the District Court of Oost-Brabant, 's-Hertogenbosch location.

These terms were written in Dutch. Where the English translation differs, the Dutch text prevails. If a provision is invalid, the others still apply.

19Contact

Questions about your account, payouts or a rejected event: [email protected]. We respond within five working days, usually sooner.

Company details and how we collect event data are in the colophon.

What changed

  • Roles described as the portal enforces them, including who can make exports with buyers' e-mail addresses.
  • Payouts without a Stripe connection aligned with the portal: by hand, within 3 working days after the event. Requesting them in the portal does not exist and is gone.
  • Service fee on the amount after discount, and the VAT wording for the service fee and featuring aligned: the amounts are what you pay.
  • Cancelling with and without refunds and postponing described as the platform carries them out.
  • New: verification, tickets from another shop, completion by AI, sharing on social channels and the API rules (version 2026-09-22).
  • Corrected: resale cannot be turned off per event, and featuring does not come with an extra push notification.
  • New: the full data processing agreement as a page of its own, which you accept when creating an organisation. We report breaches within 36 hours and announce new subprocessors 30 days ahead.
  • Liability: your responsibility for the event and the indemnity written out.
  • Honest about invoices: we do not produce them automatically yet. With Stripe Connect, Stripe's Connected Account Agreement applies.
  • The API rules are now also a page of their own: API terms.
  • Corrected: you book and pay for a national slot in the portal too, not by e-mail.

Back to top