Subprocessors and recipients

1What this list is

Two lists. The first are the subprocessors for organisers: parties that process data an organiser is responsible for and we are the processor of, as the data processing agreement describes. The second are the other recipients: parties that receive data from what PartyPPL does itself as a controller, as the privacy statement describes.

Per party you find the purpose, which data, where it is based and the safeguard for transfers outside the European Economic Area (EEA).

The safeguard is the same rule everywhere: EU-US Data Privacy Framework where the supplier is certified, otherwise standard contractual clauses. Which of the two applies per supplier we are still checking. Until that check is done, we do not claim it per party. The one exception is our second server in Canada: there the safeguard is the European Commission's adequacy decision.

2Subprocessors for organisers

For the guest list, door scans, exports and tickets from another shop we use these five:

OVHcloud · France, server in Germany

Purpose: our server, for hosting, database, file storage, realtime chat, backups and the server log. Data: everything in the portal, so also guest lists, door scans and tickets from another shop. Since 18 October 2026 an extra OVHcloud server in Germany joins in at busy times with a read copy of the database; the same party and the same country. Safeguard: the servers are in Germany, inside the EEA; there is no transfer.

OVHcloud (OVH Hosting) · Canada, server in the Montreal/Beauharnois region

Purpose: our second server, since 16 October 2026: a continuous standby copy of the database and the stored files, so the site can carry on from there if the server in Germany fails. Data: the same as at OVHcloud in Germany; older versions of the database stay there for at most 3 days, an erased file is gone there within a quarter of an hour too. The traffic between the two servers is encrypted. Safeguard: the European Commission's adequacy decision for Canada (Decision 2002/2/EC, commercial organisations under PIPEDA).

Cloudflare · US, with data centres worldwide

Purpose: DNS, CDN and attack protection. All traffic to and from the portal passes through Cloudflare, which decrypts it on the way and encrypts it again. Data: what is in the requests and answers, so also a guest list or export you open. Safeguard: EU-US Data Privacy Framework where the supplier is certified, otherwise standard contractual clauses. We have not set an EU region at Cloudflare.

Resend · US

Purpose: e-mail, such as the message that a ticket from another shop is waiting and invitations to your team. Data: e-mail address, name, the event and the kind of ticket. Safeguard: EU-US Data Privacy Framework where the supplier is certified, otherwise standard contractual clauses.

Apple · Ireland and US

Purpose: push notifications to the iPhone app and Apple Wallet pass updates, also for tickets from another shop. Data: the device's push token and the text of the notification (the event and the ticket). Safeguard: EU-US Data Privacy Framework where the supplier is certified, otherwise standard contractual clauses.

3Other recipients

For what PartyPPL does itself: your account, the agenda, tickets, the apps and our channels.

OVHcloud, Cloudflare, Resend and Apple

The same four as above, for the whole platform: hosting and storage of everything at OVHcloud, including our own mail server with webmail where mail to addresses on partyppl.nl arrives, all web traffic through Cloudflare, all our outgoing e-mail (login codes, tickets, cancellations, alerts, digests, marketing mail to people who turned it on themselves, support's answers and what our team sends from our addresses) through Resend, and push notifications, Live Activities, Wallet and Sign in with Apple. Sign in with Apple and the App Store are services Apple itself is responsible for.

OVHcloud (OVH Hosting) · Canada, server in the Montreal/Beauharnois region

Purpose: our second server, also for what PartyPPL does itself. Since 16 October 2026 it makes smaller versions of pictures from the standby copy above and draws the share cards of the site. The traffic between the two servers is encrypted. It also holds a closed archive of the counts Umami, our statistics from 12 to 16 October 2026, made on that server. Umami is switched off, the archive is not online and nothing is added. OVHcloud only hosts the server. Data: the pictures and the data on the share cards; in the archive, per page view the path without query string, the referring site, browser, operating system, kind of device, screen size, language, and country, region and city derived from the IP address, with a session id that is a hash with a secret value that changed every day. No IP address, no cookie, no id of the person. Those counts go at the latest 25 months after collection. Safeguard: the European Commission's adequacy decision for Canada (Decision 2002/2/EC, commercial organisations under PIPEDA).

Stripe · Ireland, parent company in the US

Purpose: payments, refunds and payouts to organisers through Stripe Connect. Data: amounts, your e-mail address and what you enter at Stripe; we never see your card number or IBAN. With Apple Pay and Google Pay in the order screen, Stripe's script loads in your browser and Stripe sees your IP address and details of your device against fraud. At the door (Tap to Pay on the organiser's iPhone) Stripe processes your card payment, with the venue's address. Stripe itself is responsible for your payment data. Safeguard: EU-US Data Privacy Framework where the supplier is certified, otherwise standard contractual clauses.

Anthropic · US

Purpose: Claude, to complete public event data and, when switched on, to rewrite our marketing team's weekly proposal. Data: title, date, venue, line-up and the organiser's name and website; for the weekly proposal only counts without people (such as "I'm going" per night, city or genre) and the names of nights, cities, audiences and channels. Nothing about any one visitor. Safeguard: EU-US Data Privacy Framework where the supplier is certified, otherwise standard contractual clauses.

Your browser's push service

Purpose: web push notifications. Which service that is, your browser decides (for example Apple, Google or Mozilla). Data: the push address and the text of the notification. Safeguard: EU-US Data Privacy Framework where the supplier is certified, otherwise standard contractual clauses.

Meta (Facebook, Instagram, Threads) · Ireland and US, TikTok, YouTube (Google), X, LinkedIn, Bluesky · US, a Mastodon server, Discord · US, a webhook

Purpose: posts on our own channels, as far as we have connected them, including a channel in the PartyPPL Discord server; and once a day the numbers of our own accounts, such as followers and reach, through each platform's official connection. Data: public data of nights (title, date, venue, city, genres, price, poster, link) and posts our team writes itself. Never data of visitors.

Discord · US, if you link

Purpose: your roles in the PartyPPL Discord server, if you link yourself with /koppel. Data: your Discord user id and a few yes/no attributes for your roles. Safeguard: EU-US Data Privacy Framework where the supplier is certified, otherwise standard contractual clauses.

Apple Maps (MapKit) · Ireland and US

Purpose: the map in the apps, and looking up a venue's address. Data: your device's IP address and that address. Safeguard: EU-US Data Privacy Framework where the supplier is certified, otherwise standard contractual clauses.

European Commission (VIES)

Purpose: checking a business customer's VAT number for an invoice. Data: only that number. Inside the EU.

OpenFreeMap

Purpose: map tiles, loaded directly in your browser. Data: your IP address, as with any website. No cookies. Location: an open-source project; its location and safeguard we are still working out.

YouTube (Google), SoundCloud and Mixcloud

Purpose: videos and sets, only after a tap on play. Data: your IP address and whatever that service records itself. The still image of a video and the cover of a set come from our own server, so those services only see you once you tap. After your tap their rules apply.

Spotify · Sweden

Purpose: if you link Spotify: reading which artists you follow there, with a key valid for at most 15 minutes. And the player of a PartyPPL playlist, only after a tap on Play here. Data: for the player, your IP address and whatever Spotify records itself, cookies included. After your tap their rules apply. Artist photos and how popular an artist is we fetch from our server, without visitor data.

An app you connect yourself

Purpose: doing what you allow the app through our API or MCP server, for example Claude by Anthropic. Data: what you request through the app: the public agenda, and if you connect on behalf of an organisation, that organisation's data your rights allow. The app's provider is itself responsible for what the app does with it; you choose the app.

The organiser's ticket shop, with Pre-Buy

Purpose: buying a ticket in your name. Data: the names you give per ticket. The shop itself is responsible for what it does with them.

Organisers

Receive what they need to let you in: the name on your ticket, the type, the scan status and on the door list the buyer's e-mail address; the ticket export has no names and no e-mail addresses. See the privacy statement.

Without visitor data

OpenStreetMap (Nominatim), PDOK (venue addresses), MET Norway (the weather forecast for a night), Ticketmaster's Discovery API, MusicBrainz, ListenBrainz, Wikipedia and Wikidata, Deezer and iTunes Search only receive requests from our server about public data of venues, events and artists. The YouTube Data API (popular music videos in the Netherlands), Google Search Console and Bing Webmaster Tools (how partyppl.nl does in search results, as totals) we read from our server once they are connected; no visitor data goes there either.

Authorities

Only when the law requires it, such as on a valid order from the police or the public prosecutor, and no more than asked.

4Transfers outside the EEA

Some of these parties are based in the US or process data there. If personal data goes to a country without an adequate level of protection, the rule is: EU-US Data Privacy Framework where the supplier is certified, otherwise standard contractual clauses.

Our second server is at OVHcloud in Canada. For Canada the European Commission has adopted an adequacy decision (Decision 2002/2/EC, for commercial organisations under PIPEDA); that is the safeguard there.

Which safeguard applies per supplier we record in our record of processing activities. Ask us through privacy@partyppl.nl and we will send it to you.

5Changes

If a subprocessor for organisers is added or replaced, we announce it at least 30 days in advance: on this page with the date, and by e-mail to the owners of every organisation. Organisers can object within that period, as the data processing agreement describes.

A new recipient for our own processing goes on this page and in the privacy statement, with what changed at the bottom.

Last change, 19 October 2026: no new subprocessor for organisers. Added: Stripe in your browser and at the door, the Discord link, Apple Maps in the apps, VIES, the extra OVHcloud server in Germany (the same party and country as our server), marketing mail through Resend, our marketing team's weekly proposal at Anthropic, new channels of our own (Threads, TikTok, YouTube, X and LinkedIn) and the services without visitor data for trends and search figures.

Before that, on 17 October 2026: no new party. The list now also names our own mail server (at OVHcloud in Germany, so no new subprocessor), the app you connect yourself and the services without visitor data, and we are called PartyPPL: the trade name of the same business as before.

Before that, on 16 October 2026: our second server at OVHcloud in Canada now also keeps a continuous standby copy of the database and the files, which makes it a subprocessor for organisers. No organiser had an account at that moment, so there was nobody to notify in advance; whoever starts now agrees to this list.

And on 30 September 2026: the database and the files are on our server at OVHcloud in Germany instead of at Cloudflare. Since then Cloudflare only does DNS, CDN and attack protection.

Announced changes: none. The Android app does not exist yet. When it does, Google (Firebase Cloud Messaging) becomes the service for push notifications to that app; we will announce that here and by e-mail at least 30 days in advance.

What changed

• 19 October 2026: added Stripe in your browser (Apple Pay and Google Pay) and at the door (Tap to Pay), the Discord link and our channel on Discord, Apple Maps in the apps, VIES for VAT numbers, and the extra OVHcloud server in Germany. Also: Resend sends marketing mail to people who turned it on themselves; Anthropic, when switched on, rewrites our marketing team's weekly proposal without visitor data; our channels on Threads, TikTok, YouTube, X and LinkedIn with their own numbers; the YouTube Data API, Google Search Console and Bing Webmaster Tools without visitor data. No new subprocessor for organisers.
• 17 October 2026: our own mail server added, mail to partyppl.nl no longer passes through Cloudflare, support's answers go through Resend; an app you connect yourself; PDOK, MET Norway and Ticketmaster among the services without visitor data. Corrected: the still image of a YouTube video comes from our own server, and the buyer's e-mail address is on the door list, not in the ticket export.
• New: this list as a page of its own, with per party the purpose, the data, the location and the safeguard for transfers.
• OVHcloud added for hosting and storage, on a server in Germany. Cloudflare now only does DNS, CDN and attack protection.
• Spotify: also the player of a PartyPPL playlist, which only loads after your tap.
• 12 October 2026: OVHcloud in Canada added, for our own statistics server with Umami. The safeguard is the European Commission's adequacy decision for Canada.
• 16 October 2026: OVHcloud in Canada added as a subprocessor for organisers, for the continuous standby copy of the database and the files on our second server.
• 16 October 2026: Umami is switched off, so our second server in Canada is no longer a statistics server. It holds the closed archive of the counts from 12 to 16 October 2026 and since 16 October 2026 makes smaller versions of pictures and the share cards of the site.