How guest consent works
You can put a short confirmation in front of a guest s first upload. They read what it covers, tick a box, and only then send.
It is off by default. Without it a guest uploads immediately and the page asks for nothing beforehand.
What the step asks
It tells the guest that the host may use what they are about to send, and asks them to agree before anything leaves the phone. The wording is short by design, because a paragraph on a phone screen at a party is read by nobody.
A guest who does not agree does not upload. There is no partial state where the file goes through anyway.
- Decide whether you need it. For a private party among invited guests it is not what you want.
- Switch it on for the event. It sits with the guest-page settings and applies to the next guest who opens it.
- Expect it to cost contributions. Every step before an upload does. Turn it on for a reason you can name.
Why it is off by default
Every question before the first upload costs contributions, and at a party the cost is high — people are holding a glass and deciding in seconds. So the default is the shortest possible path, and the step exists for hosts who have a reason to add it.
That reason is a public venue, a client event or anything you expect to publish more widely than the room.
What gets recorded
When the step is on, the agreement is recorded against that guest s session for the event, so there is a record that it happened rather than an assumption. With the step off, nothing is recorded because nothing was asked.
It is tied to the session rather than to a person, since guests upload without an account.
| Step | When it appears | Default | What it costs |
|---|---|---|---|
| Consent | Before the first upload | Off | A tap, before anything is sent |
| Name question | After sending | Off | Nothing — the upload is already done |
The name question is the cheaper of the 2, because the contribution is safe before it is asked.
Consent is not retention
These 2 get confused constantly. Consent settles whether you may use what a guest sent. Retention decides how long the file exists at all, and it runs on the event s own clock whether or not anybody agreed to anything.
Switching consent on does not extend an album, and switching it off does not shorten one.
When a guest changes their mind
Guests cannot remove their own contributions, because without an account there is nothing that proves a file is theirs. So a withdrawal comes to you, and the honest response is to delete rather than hide — hiding keeps the file with you, which is not what was asked.
Act quickly. A guest who has to ask twice stops contributing.
Saying it out loud instead
For many parties a sentence beats a checkbox: tell guests the pictures become visible to everyone at the event. That sets the expectation without adding a step, and it is the part people actually want to know.
If you need a record rather than an expectation, that is when the step earns its cost.
Common questions
Is the consent step on by default?
No. Without it a guest uploads immediately.
What happens if a guest declines?
Nothing is sent. There is no partial state.
Is the agreement recorded?
Yes, against that guest s session for the event, when the step is switched on.
Does consent affect how long files are kept?
No. Retention runs on the event s own clock either way.
A guest wants their photo removed — what now?
Delete it in the dashboard. Guests cannot remove their own contributions.
Still open? Contact
Choose what guests can upload
Where the 2 optional steps are switched.
How long media is kept, and when it goes
The other clock, and the one that deletes.
Hide or delete uploads
Which of the 2 a withdrawal request means.
A guest album for a company event
Where a recorded agreement earns its cost.
You are unsure whether to switch it on
Tell us what kind of event it is and how public the room is. That decides it.