Trust
Your presence at an event is yours to control
RSVME was built around a simple rule: nobody should have to trade their privacy for the ability to show up to something.
Visibility stays yours
Guests choose how visible they are — fully identified, shown under a display name only, or hidden entirely from anyone but the host. Access beyond that is scoped by role: hosts and event owners see what they need to run the event; anyone else with a limited role sees only what that role requires, never the full guest list by default.
This isn't a setting buried in a menu. It's how the system is built underneath: identity is resolved per-viewer, not stored and shown the same way to everyone.
We'd rather tell you plainly what RSVME does and doesn't protect against than oversell it. If a limitation exists, it belongs on this page, not in the fine print.
Three identity tiers
- Full — guests appear with the display name associated with their ticket. This is the default when hosts do not need extra discretion.
- Pseudonymous — peer-facing surfaces show a pseudonym (for example VIP labels) instead of a harvestable email or personal name where the product applies the tier.
- Hidden — the guest is kept off guest-facing roster views that would otherwise list them, while hosts still run the event.
What this does not protect against
Identity privacy keeps other guests from seeing (and harvesting) emails: peer-facing surfaces show display names or pseudonyms only. The workspace owner retains full operational visibility; other staff see tier-appropriate labels unless granted a per-ticket reveal. It raises the bar against casual exposure and screenshots, but does not protect against a compromised organizer account, a breach of RSVME, legal compulsion (e.g. a subpoena), lock-screen or shoulder-surf exposure, or a sophisticated/resourced adversary. For high-stakes source-protection or safety contexts, use professional measures beyond what this tool claims to provide.
How hosts use data day-of
Workspace owners retain full operational visibility so they can run the guest list, resolve issues, and check people in at the door. Anyone with a limited role sees only what that role requires — tier-appropriate labels unless a host grants a per-ticket reveal. Check-in and roster tools exist so the people running the event can confirm who is expected and who has arrived — not so other guests can harvest contact details.
Full policy
For collection, subprocessors, retention, and request rights, read the Privacy Policy. Questions: contact us.