What is left the morning after.

Not just numbers, but sentences.

The recap lists every track that played — all of them, not the first twenty — and says where each one came from: requested by a guest, pulled forward by you, or added by the Auto DJ. Alongside that, the make-up by genre and the plain figures: how many guests, how many tracks, how long.

And it writes out what follows from that. Whether your guests carried the night or the Auto DJ did, whether a handful of people shaped the list or many, whether the genre held or wandered.

Not one guest name.

During the party the name each guest chose sits next to their request — that is part of the fun. Afterwards it does not: neither the recap nor any export carries a name, not even an initial.

That is deliberate and cannot be switched off. A page you pass around must not give away who asked for something at three in the morning.

The address exists before the party starts.

The link is created with the event, not afterwards. While the music is playing it says the night is still going; the recap itself appears once things have gone quiet. So you can share the address on the night instead of hunting for it the next day.

If your event runs permanently — in a bar, say — every party still gets its own recap. The split follows longer breaks in playback, not calendar days.

After that it stays reachable for 30 days and then disappears on its own.

In both editions, in the same place.

In Juqed Go the route sits in the event and history tabs; in Juqed Web beside the guest access. Your guests also find it on the closing screen when the event ends.

At the foot of the page there is a single question: how happy you were. One number, an optional comment, no form.

What people ask about the recap.