Contact

One inbox, read by a person

Everything below goes to hello@crowdroll.cam. There is no ticket number and no bot: it is a small operation, which is the bad news on a Sunday and the good news every other day. Pick the line that fits and the subject arrives already sorted.

Something is going wrong at an event right now

The roll will not develop, photos are missing, guests cannot get in. This one goes to the top of the pile.

Worth including: The event name or join code, roughly when it started, and what you are seeing on your own screen. If guests are affected, how many.

Email about this

A question before you commit a real wedding to this

Guest numbers, what happens on a venue with no signal, whether it suits the thing you are actually planning.

Worth including: The kind of event, roughly how many people, and the date if you have one. Most of these are already answered on the FAQ, so it is worth a look first — but a sentence is quicker than reading, and that is fine.

Email about this

You run a venue, an agency or a production company

Repeat events, your own logo on the join cards, a live wall on a screen in the room, printed cards in a box. Say what you need and it is a conversation rather than a checkout.

Worth including: How many events a year, typical headcount, and whether you need it branded as you rather than as us.

Email about this

Your data, or somebody else’s

A copy of what we hold, a correction, deletion, or an objection. This is the address in the privacy policy and it reaches the operator named at the bottom of this page.

Worth including: Which account — the email or Apple ID you signed in with — and what you want done. We may have to ask one question back to be sure it is you, which is a protection rather than an obstacle.

Email about this

Reporting a photo, a message or a person

If you are in the app, report it from the photo itself: that path is faster, it tells us exactly which photo you mean, and it is reviewed within 24 hours. Mail is the fallback for when you cannot get to it.

Worth including: The event, what you are reporting and roughly when it was posted. You do not have to explain why — “this should not be here” is enough.

Email about this

Before you write

The FAQ answers most of what people ask, including the two that come up at every event: what happens when the venue has no signal, and what happens when more guests turn up than the host paid for. Pricing has the guest caps and the add-ons. If you are holding a code and just need the box to type it into, that is the join page.

If you are a guest at somebody else’s event and the problem is a photo you would rather was not there, the host can remove any photo from their own event in seconds. Asking them is usually faster than asking us.

What we cannot do from here

Refunds. Purchases are made through Apple, so Apple handles refunds under the App Store terms and we have no ability to process one. Writing to us first only adds a day: request it from Apple directly. The terms set out what happens to an upgrade if Apple does refund it.

We also cannot recover a deleted event. Deleting one takes its roll with it, deliberately and irreversibly, and there is no copy on our side to restore from. That is the argument for saving a roll the morning it develops rather than the month after.

Where else we are

Nowhere, and that is deliberate for now rather than an omission. There is no support phone line, no live chat and no social account that answers questions, because a channel nobody is watching is worse than no channel — it looks staffed and is not. Email is the one place, and it is watched.

Correspondence in English or Maltese. We are based in Malta, so a mail sent late on a Saturday is read on a Sunday morning in Central European Time.


Who you are writing to

Published under Article 5 of the e-Commerce Directive and Articles 11–12 of the Digital Services Act, and the same details Apple shows on the EU App Store listing.