Trust & security
How EveryGuest keeps content permission-first
Guest content should only move forward with clear permission, team visibility, and review controls. Here's how we approach each of those.
Guest permissions and consent
Every guest who uploads goes through a permission flow that makes the consent explicit. They choose whether their content can be used in-venue, on social media, or just stored. Consent is recorded, reviewable, and revocable.
Moderation before publishing
Nothing goes public automatically. Every photo is reviewed by your team in the dashboard before it can be used anywhere. You can approve, reject, or flag for later — on your schedule.
Storage and review visibility
Your content library is stored securely and organised by venue location, date, and status. Your team can always see what has been approved, what is pending, and what has been rejected.
QR simplicity and rollout confidence
The QR-led capture flow is tested before launch so your team knows what to expect. Guests scan once and join the flow without a complex app download. Most rollouts are live in under 10 minutes.
Team access and accountability
Role-based access means the right people can review and publish content, and a clear audit trail shows what was approved, by whom, and when. You always know what happened to every photo.
Privacy and terms
Our full privacy policy and terms of service are available and reviewed regularly. Guests and venues both have their own rights and obligations documented clearly.
Common questions about content safety
What happens if a guest wants their photo removed?
Guests can request removal at any time. The venue has 7 days to remove it from all channels where it was used. A reference number is issued so progress can be tracked.
Can a venue publish photos without guest consent?
No. Every photo requires at least the baseline storage consent before it can be reviewed. Marketing use (social, web, ads) requires a separate explicit consent that the guest controls.
Who can access the content dashboard?
Only team members with dashboard access assigned by the venue owner. Access is role-based, and actions are logged so there's always a clear record of approvals and decisions.
What if a guest uploads something inappropriate?
Nothing is published without manual review. Venue teams see every upload before it goes anywhere public. Content can be rejected with a reason, and the guest is notified.
Questions about how we handle data?
We're happy to walk through the permission model, moderation flow, or data storage before you commit to anything.