# Whose event is it? Why Luma, Eventbrite, Meetup and Partiful will not let a site like PrompTugal.news show the public events their organisers want seen, what their terms actually say, who owns an event listing, what UK, EU and Portuguese law allows, what organisers expect, and how PrompTugal.news now collects events with a legal basis and the evidence for every one, sgit.ai

> Our agents found something I find strange. The platforms where most events are published, Luma, Eventbrite, Meetup and Partiful, do not let a site like PrompTugal.news include their events. If I published an event, I would want it shown as widely as possible, and a site that lists it and links back sends people to the platform, where they still register. So I asked for the analysis. What the terms say: Eventbrite forbids scraping outright; Partiful forbids scraping and copying; Luma allows access only through its supported interfaces and forbids republishing images; Meetup's API needs a paid Pro plan. Who owns the listing: the organiser, not the platform; each platform takes a non-exclusive licence, which means the organiser can give us the same right. What the law says: bare facts, the date, time, place and title, are not protected by copyright; descriptions and photographs are, and belong to the organiser or the photographer; database right and the platforms' contracts are the real constraints on copying a platform's listings wholesale; guests' names are personal data and stay out. So the distribution organisers are promised is distribution to partners the platform chooses. Our principle is that we publish only what we have a legal basis to publish, with the evidence. The routes that meet it are the organiser's own permission, official agendas we may read, and the facts with a link, as a search engine shows them; and PrompTugal.news's new events site and register of sources already work that way. One more finding: part of what blocked us was our own house rule, not the platforms' terms.

*Source: <https://newsroom.sgit.ai/articles/whose-event-is-it.html> · sgit.ai v0.7.87 · this file is generated from the same content as the page, so the two cannot drift. Every page on this site has a `.md` twin; internal links below point at them.*

---

[Home](../index.md) / [Articles](index.md) / Whose event is it? Why Luma, Eventbrite, Meetup and Partiful will not let a site like PrompTugal.news show the public events their organisers want seen, what their terms actually say, who owns an event listing, what UK, EU and Portuguese law allows, what organisers expect, and how PrompTugal.news now collects events with a legal basis and the evidence for every one

# Whose event is it? Why Luma, Eventbrite, Meetup and Partiful will not let a site like PrompTugal.news show the public events their organisers want seen, what their terms actually say, who owns an event listing, what UK, EU and Portuguese law allows, what organisers expect, and how PrompTugal.news now collects events with a legal basis and the evidence for every one

By [Dinis Cruz](https://sgit.ai/about/index.md) · 2026-11-18 · [article v1.0.0](versions/whose-event-is-it.md) · [newsroom v0.14.156](https://newsroom.sgit.ai/admin/versions.html) · eventsdatatermscopyrightdatabase-rightgdprpromptugalplatformsarticle

***Abstract:** Our agents found something I find strange. The platforms where most events are published, Luma, Eventbrite, Meetup and Partiful, do not let a site like PrompTugal.news include their events. If I published an event, I would want it shown as widely as possible, and a site that lists it and links back sends people to the platform, where they still register. So I asked for the analysis. What the terms say: Eventbrite forbids scraping outright; Partiful forbids scraping and copying; Luma allows access only through its supported interfaces and forbids republishing images; Meetup's API needs a paid Pro plan. Who owns the listing: the organiser, not the platform; each platform takes a non-exclusive licence, which means the organiser can give us the same right. What the law says: bare facts, the date, time, place and title, are not protected by copyright; descriptions and photographs are, and belong to the organiser or the photographer; database right and the platforms' contracts are the real constraints on copying a platform's listings wholesale; guests' names are personal data and stay out. So the distribution organisers are promised is distribution to partners the platform chooses. Our principle is that we publish only what we have a legal basis to publish, with the evidence. The routes that meet it are the organiser's own permission, official agendas we may read, and the facts with a link, as a search engine shows them; and PrompTugal.news's new events site and register of sources already work that way. One more finding: part of what blocked us was our own house rule, not the platforms' terms.*

The organiser owns the event; each platform holds a non-exclusive licence, so the organiser can license us too.

## In short

- **The platforms will not let us include their events,** even though organisers want them seen.
- **Their terms:** Eventbrite and Partiful forbid scraping; Luma allows only its supported interfaces; Meetup's API is paid.
- **The organiser owns the listing;** the platforms hold non-exclusive licences.
- **Facts are free; descriptions and photos are not;** database right and contracts limit wholesale copying.
- **Guests' names are personal data,** and never ours to show.
- **Our routes:** the organiser's permission, official agendas, and facts with a link.
- **Part of the block was our own rule,** not their terms.

## The puzzle

When our agents built Lisbon Tech Fringe during the storm, and again this week when PrompTugal.news started listing events town by town, they kept running into the same wall: the platforms where most events are published would not let us include them ([a guide born in a storm](a-guide-born-in-a-storm.md)). I find that strange. If I hosted an event on Luma, I would want it on every site that might send people to it. A site like ours lists the event and links to it; the person still registers on Luma. We would be sending the platform traffic.

So I asked for the analysis: what the terms say, who owns the data, what the law allows, what organisers expect, and what we should do.

## What the platforms say

What each platform's terms say about automated access, reuse and images, and the interfaces they offer.

- **Eventbrite:** "You have no right to, and you agree not to, scrape, crawl, or employ any automated means to extract data from the Sites." It offers an API with its own terms, an embeddable checkout and an affiliate programme.
- **Partiful:** no "data mining, robots, scraping, or similar data gathering or extraction methods", and no copying "information about other users". No public API.
- **Luma:** "you must not access the Service by any means other than our publicly supported interfaces", and users are "prohibited from downloading, republication, retransmission, reproduction, or other use of any image". Its API works only for the calendar its key was made on, on a paid plan. It does publish iCal feeds, per calendar and per city; its terms do not say whether a third party may republish from them.
- **Meetup:** its API needs a paid Pro subscription, and its robots.txt blocks its own event feeds.

Oddly, the robots.txt files of Eventbrite, Luma and Meetup allow ordinary event pages to be crawled; Partiful blocks AI crawlers but allows search engines. The terms are stricter than the robots.

## Who owns an event

Here the answer surprised me less. The organiser writes the listing, and the platforms say so: Partiful's users "own all right, title and interest" in their content; Luma's hosts are "solely responsible" for what they post. What each platform takes is a licence, non-exclusive, worldwide and royalty-free, and in Eventbrite's and Partiful's case transferable and sublicensable.

Non-exclusive matters. It means the organiser keeps the right to give the same listing to anyone else, including us. Sublicensable matters too: it is how Eventbrite can pass events to the partners it chooses. Eventbrite tells organisers it will "publish to Eventbrite and our partners' sites in a single click", naming Facebook, Spotify and Google. So organisers are promised wide distribution, through partners the platform picks. An independent site is not one of them unless the platform says so.

## What the law allows

What may be shown, and on what basis: facts, descriptions, photos, the platform's database, and guests' names.

This is not legal advice, and some of it is unsettled. As I understand UK, EU and Portuguese law:

- **Facts are not protected by copyright:** an event's date, time, place and title can be stated by anyone. The description and the photographs are protected, and belong to whoever wrote or took them, the organiser or a photographer, not the platform.
- **Database right** protects the platform's investment in obtaining, verifying or presenting its listings, not in creating them, which is the organiser's work (the CJEU in *BHB v William Hill*). The CJEU held that a dedicated meta-search engine querying a whole database re-uses it (*Innoweb v Wegener*), but that a database maker can stop an aggregator only where it harms the maker's ability to recoup its investment (*CV-Online Latvia v Melons*, 2021): a balancing test that favours sites that send traffic rather than replace the source. It is also not clear that a US-incorporated platform holds the EU right at all.
- **Contracts can bite where intellectual property does not:** the CJEU allowed a site's terms to restrict use of unprotected data (*Ryanair v PR Aviation*). Whether terms bind someone who never clicked "agree" depends on national contract law.
- **Text and data mining exceptions** cover analysis, not republishing, and can be opted out of by machine-readable means; the UK's covers only non-commercial research.
- **Guests' names and photos are personal data.** A listing of who is going is never ours to show; organisers' public, professional names can be, with care.

In short: stating the facts and linking is low risk; copying descriptions and photos needs the author's permission; systematically scraping a platform is risky under its contract and, possibly, its database right.

## What organisers expect

I found no organised complaint from organisers that platforms stop independent sites listing their events; the expectation mostly goes unspoken. What I did find is the other side of it: in March 2026 a games-industry party list accused an AI company of copying it, and the company said it had compiled its list from public sources such as Eventbrite and Luma. And commercial scrapers of these platforms are sold openly, which says enforcement is patchy and the demand is real.

My own view stands. An organiser who publishes publicly wants to be found. The honest way to serve that is to ask them, and to make it easy for them to say yes.

## What we found about ourselves

Reading PrompTugal.news's new register of sources, I found something I did not expect: for Luma, Eventbrite and Meetup, our agents have never read the terms. A house rule written during the storm, never machine-read those platforms, also stops the agents reading their terms pages, so the register says "house rule; terms not read by machine". It was a sensible precaution on a busy day. But part of "they do not let us" was us, not them; and for Luma in particular, whose public iCal feeds may be a supported interface, the question is open. A person should read the terms, and the request on the record should ask it.

## How PrompTugal.news collects events now

How events are collected now: official agendas, discovery, facts and a link, organisers, the register.

The team has turned this into a method, today, across its sites: the data site, weather, travel, civic, startups, and now [events.promptugal.news](https://events.promptugal.news/), "what's on, town by town".

- **Official agendas first:** councils' and theatres' public agendas that may be read, Lisbon's cultural agenda, Lagos, Faro's municipal theatre, Tavira: 138 events read, with their details.
- **Discovery for leads:** a daily question per place to an AI search engine, which returns events and the pages that mention them: 109 more found.
- **Facts and a link, nothing more,** where the source does not let us copy: "events found through Perplexity show only their title, date, place and the links that point to them".
- **Organisers asked to send their own:** a submission from the organiser is published as theirs, credited and dated, under their permission.
- **A register of every source,** read or not, and why not, quoting the terms or robots.txt with the date read: [the sources](https://events.promptugal.news/sources/).
- **Requests on the record:** to Luma, Eventbrite and Meetup, drafted by an agent, sent by a person, asking whether a site like ours may show their public events for a place, linked back and credited, and through which interface; the answer, or none after 14 days, goes on the register.

Every event then carries its legal basis and its evidence: read from a source that allows it; given to us by its organiser; or stated as facts with a link.

## What I would do next

- **Read the terms properly,** by a person, for every platform on the register, and record what they allow.
- **Ask the organisers, not only the platforms:** they own the listing, and a one-line permission, with their images, is the cleanest basis there is.
- **Try the interfaces the platforms offer** to organisers, with the organiser's agreement.
- **Keep guests out,** always.
- **Publish the answers,** whatever they are.

## What this does not claim

- **This is not legal advice;** several points, the reach of database right and whether terms bind a non-user, are unsettled.
- **Some platform terms** were read from archives or summaries where the primary pages refused automated reading.
- **No platform has answered yet;** the requests are drafted, not sent.

## Where this comes from

The terms of [Luma](https://luma.com/terms) and [Partiful](https://partiful.com/terms); Eventbrite's terms as archived by [ConductAtlas](https://conductatlas.com/platform/eventbrite/eventbrite-terms-of-service/provision/CA-P-039158/scraping-and-automated-data-extraction-prohibited/) and its [distribution page](https://www.eventbrite.com.au/blog/solutions/reach-more-people-event-distribution/); [Luma's API](https://docs.luma.com/reference/getting-started-with-your-api) and [iCal](https://help.luma.com/p/ical-syncing) help; [Meetup on API access](https://help.meetup.com/hc/en-us/articles/41467209211917-What-happens-to-my-API-access-when-my-Meetup-Pro-subscription-expires); the robots.txt files of [Luma](https://luma.com/robots.txt), [Eventbrite](https://www.eventbrite.co.uk/robots.txt), [Meetup](https://www.meetup.com/robots.txt) and [Partiful](https://partiful.com/robots.txt); on the law, [Innoweb v Wegener](https://ippt.eu/items/ippt20131219-cjeu-innoweb-v-wegener), [CV-Online v Melons](https://www.twobirds.com/en/insights/2021/uk/cv-online-latvia-cjeu-complicates-the-enforcement-of-database-rights), [BHB v William Hill](https://curia.europa.eu/en/actu/communiques/cp04/aff/cp040089en.pdf), [Ryanair v PR Aviation](https://ippt.eu/items/ippt20150115-cjeu-ryanair-v-pr-aviation), the [DSM Directive, article 4](https://www.legislation.gov.uk/eudr/2019/790/article/4), [CDPA section 29A](https://www.legislation.gov.uk/ukpga/1988/48/section/29A) and the [ICO's journalism code](https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/data-protection-and-journalism-code-of-practice/journalism-code/apply-the-journalism-exemption/); [GamesBeat](https://gamesbeat.com/the-battle-of-the-gdc-party-lists-ty-taylor-tangles-with-blueberry-ai/) on the party lists; all read on 18 November 2026. PrompTugal.news's [events site](https://events.promptugal.news/) and its register of sources, and the team's briefs of 18 November in the PrompTugal.news repository. Earlier on this site: [a guide born in a storm](a-guide-born-in-a-storm.md).

## Threads

Agents & policy[This article as a graph →](graphs.md#whose-event-is-it)

### Builds on

- [A guide born in a storm: when Storm Charles cancelled Web Summit's second day, the whole team built Lisbon Tech Fringe, a guide to the city's side events, from a spoken brief at 10:00 to its own address by about 12:57, 179 events and 104 communities each re-read at its source, one conductor per person, terms respected source by source, a guest-list hold, every agent traced, and a graph you can query in your browser](a-guide-born-in-a-storm.md) Lisbon Tech Fringe: a guide to the city's side events, built by the whole team in hours when the storm cancelled Web Summit's day two.

### Continued by

- [Ten days to a data platform: how PrompTugal.news went from a newsroom at Web Summit to twelve public data sources, a register of 92 sources read and not read, a dozen sites on its own domain and two cyber-threat feeds cleared to run, with a security agent on every change, and why each step made the next one cheaper](ten-days-to-a-data-platform.md) How PrompTugal.news went from a Web Summit newsroom to twelve data sources, a register of 92 and a dozen sites in two weeks.
- [Paying the sources: the business model behind PrompTugal.news's data, a reader's money flowing back to the sources the reader actually read, worked out in the open and simulated for now, a licence link on every value, a public register of who we read and who we do not, and why a platform built on public data with no lock-in can be a positive loop for everyone who feeds it](paying-the-sources.md) The business model: a reader's money flowing back to the sources they read, simulated in the open, with a licence on every value.
- [Gaining speed: a series on what happens when you productise the way you build, PrompTugal.news going from a newsroom at Web Summit to a data intelligence platform for Portugal's places in two weeks, a factory that turns one commit into a site with its owner, money that flows back to the sources, sites built on the data in minutes, the librarian, and a team like this for sale](gaining-speed.md) A series on what happens when you productise how you build: PrompTugal.news from a summit newsroom to a data platform in two weeks.
- [A team like this, for sale: what we sell is not the platform, it is the agentic team that built it, its roles, its behaviour policies, its security passes and its speed, with the code open and the data public, and who I want to talk to now that PrompTugal.news is a working data platform and not an experiment](a-team-like-this.md) What we sell is not the open platform but a team like the one that built it, and who I want to talk to now.

[All articles](index.md) · [All graphs](graphs.md)

Article No. 473 · [start a reading list with it](https://newsroom.sgit.ai/for/make.html#r=473)

**Posting this article on LinkedIn?** The cover is [whose-event-is-it.jpg](banners/whose-event-is-it.jpg) (1920×1080, title and key ideas on it). Upload it as the article cover, paste the title, then select and copy the body from this page.

**Want the next issue by email.** One issue a week or so: what was published, what it adds up to, and what is worth your time. [Subscribe to the SGit Newsroom →](../subscribe/index.md)

[← All articles](index.md)


---

*[Site index for agents](../llms.txt) · [HTML version](https://newsroom.sgit.ai/articles/whose-event-is-it.html)*
