# When a festival is cancelled, where does the attendee list go?

> An edition gets cancelled and the audience does not disappear. The record of it can. Where it ends up depends on a contract nobody reads until that week.

Source: https://hiipe.io/blog/when-a-festival-collapses
Published: 2026-10-27

An edition gets cancelled and the coverage is all about refunds, suppliers and whether it comes back. The part nobody writes about is quieter: several thousand people who wanted to be there still exist, still want the thing, and may now be unreachable, because the only record of them was inside accounts that stop being paid for.

**Key takeaways**

- The audience does not disappear when an edition does. The record of it can.
- What happens to the data is a contract term, agreed years earlier by someone who was not thinking about this.
- One quarterly export, held outside any vendor, is the whole insurance policy.

## The order in which access actually disappears

It is rarely dramatic. It is administrative, and it happens in a predictable
sequence.

| Weeks | What lapses | What is lost with it |
|---|---|---|
| Immediately | Paid ad accounts | Custom audiences built from your own list |
| Within a month | The email tool subscription | Send history, segments, sometimes the list itself |
| Same period | The ticketing account, if it was the organiser's | The attendee records, or your access to them |
| Two to three months | Domain and inbox renewals | The address people would have replied to |
| Whenever someone notices | The shared drive that held an old export | The only copy that was ever really yours |

Nobody decides any of this. It happens because subscriptions are cancelled in the
order of how large the invoice is, and the audience record is rarely the largest
invoice.

## The contract term that decides it

Under [Article 28 of the GDPR](https://gdpr-info.eu/art-28-gdpr/), a processor
has to delete or return personal data at the end of the service, at the
controller's choice. Two words, delete or return, and which one applies to you was
settled in a contract signed years ago by somebody who was thinking about
onboarding rather than about wind-down.

That is worth reading now, while nothing is wrong, because it is the difference
between an audience you can carry to whatever comes next and one that is deleted
correctly and lawfully at the moment you most need it.

## Why this list is worth more after a cancellation, not less

The instinct after a cancellation is that the audience is spoiled. It is the
opposite.

People who bought a ticket for an edition that did not happen are the most
qualified audience anyone in your genre holds. They demonstrated intent with
money, in public, and did not get what they paid for. When something comparable
appears, whether it is the same festival returning or a different promoter
picking up the date, they are the first four thousand people who should hear
about it.

That is also why the list is often the only asset with residual value when
everything else is being wound down, and why it should never be the asset nobody
thought to keep a copy of.

## The twenty minute insurance policy

Once a quarter, export the audience. Not a report, the records: contact details,
capture source, consent wording and timestamp, attendance history. Put the file
somewhere that is not a vendor account and not one person's laptop.

That is it. It is not sophisticated and it survives every scenario in the table
above, including the ones nobody plans for.

If the export you get back does not contain source and consent, you have found a
different problem and it is a bigger one, for the reasons set out in [first party
fan data and the receipt](/blog/first-party-fan-data-and-the-receipt).

## What this argues for structurally

Not a tool. A separation. The audience record should sit somewhere that does not
depend on any single event happening, any single platform continuing, or any
single subscription being renewed on time.

That is why HIIPE keeps contacts unlimited on every plan including the free one,
and why export is not a premium feature: a fanbase that becomes unreachable when
the invoices stop would fail at the one job it exists for. [How the pieces sit
together](/solutions) is short, and deliberately so.

**Read next** : [The receipt is the part nobody owns](/blog/first-party-fan-data-and-the-receipt) · [What a fan CRM is, and what it is not](/blog/what-is-a-fan-crm)
## Citable facts

- Under GDPR Article 28, a processor must delete or return personal data at the end of the service, at the controller's choice. Which of the two happens is a contract term, decided long before it matters.
  Source: GDPR, Article 28
- When a festival stops, the attendee list disappears with the account that held it. The list survives only where the organiser already holds their own copy, with its consent trail, outside the platform.
  Source: HIIPE, September 2026

## FAQ

### If an edition is cancelled, do we lose the audience?
Not the people. Possibly the record. Attendees do not stop existing or stop being interested, but the list of them may sit in accounts that lapse when the invoices do, and that is a different loss and an avoidable one.

### Who owns attendee data when a festival company folds?
Whoever the contracts say, which is usually the organising entity as controller and the platforms as processors. The practical question is narrower: who still has a login, and who is still paying the subscription that keeps it open.

### What should we do before we ever need this?
One export a quarter, held somewhere that is not a vendor account, containing the contact, the source and the consent record. It takes twenty minutes and it is the entire insurance policy.

### Does a cancelled edition make the list worthless?
The opposite. People who bought for a cancelled edition are the most motivated audience you will ever hold, because they wanted it enough to pay and did not get it. That list is worth more after the cancellation than before.

### Who owns the data if a festival company is liquidated?
The organising entity remains the controller until an administrator decides otherwise, and personal data is not a straightforward asset to sell. The practical answer is simpler and less comforting: whoever still has a login and a paid subscription has access, and everyone else does not.

### Can I keep emailing a cancelled event's list?
About the cancellation and any refund, yes. About a future event, only if the consent covered that, which it usually does if it was collected as marketing consent and usually does not if it came with the ticket. Read what the person actually agreed to.

### How often should we export?
Quarterly is enough for almost everyone, plus once immediately after each event while the data is freshest and someone still remembers what the fields mean. The cadence matters less than the file living somewhere that is not a vendor account.