For hosts who read the news before they hit send
A fair question in a phishing age, and it deserves a plain answer: what a link exposes, what stays with you, and the settings that make the difference. No reassurance theatre.
What someone typing this really asks is: if my aunt types her name and meal choice into a link I sent, what happens to that information, who sees it, and can strangers get at it? That is a reasonable set of questions. The honest answer describes the machinery exactly — what the page is, what it holds, which parts a guest's answer actually touches. Anything vaguer than that is marketing, and safety is the last topic that deserves marketing.
The facts of a page you control:
A web address behaves like a printed card: anyone holding it can read it. That is the entire risk, and pretending otherwise would be the dishonesty this query is sniffing at. Someone who receives a forwarded link can open the page the same way someone who finds a card on a kitchen counter reads it. What that reader can do is bounded by what you put on the page and by whether you asked for a password — which is why the settings below are the actual answer. And because you can edit anytime, even a page sent weeks ago can be corrected or gated within minutes.
Three levers, all in the host's hands:
No certificate belongs on this page, because none applies — an invitation site is not a bank, and pretending otherwise is how people get caught out. What is true: guest answers go to the host's list and nowhere a guest can see; the page is yours to edit or gate at any moment; the reply form asks what the event needs and nothing more.
Judge that against what you are actually protecting — a dinner's guest names, not a medical record — and the arrangement is more private than the habits it replaced. A card left on a noticeboard, a chat group where every member can screenshot, an email landing on a shared household inbox: none of those carry a password, and all of them travel further than intended.
How it works
Publish the detail guests need and nothing they do not — occasion, timing, venue, reply button. Your own contact line only if you want it reachable.
For a closed list, set a password and hand it out with the invitation, message and mouth to ear, the way you would tell people a door code.
One message per guest or household rather than a group drop. Fewer copies floating around, more context attached to every yes.
Replies land on your live guest list. On the day, QR check-in works from the same list — it never has to become visible to anyone else for any of it to function.
Questions
No. The page shows the invitation; answers land on the host's guest list, which is not a public page. Two guests replying never see one another's names, plus-ones or meal choices through the invitation.
Whoever holds it can see the page — that is how links work, and the same as a forwarded card. If that bothers you, set a password so a forwarded link stops at the door, and rely on the guest list you manage to decide who is actually invited.
You are sending guests to a page you control, on terms you can review at /pricing. The honest framing applies to any web service you already use: what is collected is a name, an answer and whatever you ask for; what is gated, passworded and editable stays in your hands.
An email carries the same detail to the same forwarding risk — forwarded mail happens daily — and its replies sit in a mailbox you also have to secure. Email and chat both reach the same page anyway; neither route is doing anything the other cannot.
Edit the list. The page never displayed guest names to other guests, so a change to your list changes nothing anyone can see until you choose to re-send — no awkward moment of a name vanishing from a screen.
Get Started
A page you control, a password if the occasion wants one, replies that come only to you. Start free and decide exactly who sees what.
