Choose the occasion, set the scene, send a link. Your guests reply with a name and a number — nothing else to install, nothing else to fill in.
Six drawn cards — a party, a wedding, a game night and the rest.
A theme, a title, the venue and the hour. Four fields, no more.
Share the link. Names and head counts arrive on their own.
Pick one. It sets the drawing on the card — you can change everything else next.
{{ requestLine }}
{{ cardNote }}
Collecting RSVPs needs a host account; we'll ask you to sign in when you make the link.
{{ requestLine }}
{{ cardNote }}
{{ shareText }}
On a phone the card picture and message go together in one share. On desktop the picture is saved for you to attach.
Replies land on your cards page as guests answer, from any device you sign in on.
Names and head counts are for the host only. Guests see the totals above.
| {{ r.name }} | {{ r.status }} | {{ r.countLabel }} |
{{ guestError }}
{{ requestLine }}
{{ cardNote }}
{{ myReplyLine }}
{{ countLine }}. The host has your reply.
Your name, and how many of you there'll be.
A sample card. Yours carries your own names, date and venue, and the replies above are what your guests will see.
| {{ r.name }} | {{ r.when }} | {{ r.status }} | {{ r.countLabel }} |
No replies yet. Share the link and they'll appear here.
Make an invitation and it will show up here with every reply.
{{ authLead }}
Demo mode — no backend is configured, so the Google button signs you in as a demo host and nothing is saved beyond this tab.
We keep your email to show you your cards, nothing more.
We'd like to use Google Analytics to see how the site is used. Nothing is set until you choose.
digi Invite makes invitation cards and counts replies. This page says exactly what that involves. Last updated 16 September 2026.
Hosts. When you sign in with Google we receive your email address and Google account id. We use them to show you your cards and nothing else. We don't see your password or contacts.
Guests. When you reply to an invitation we keep the name and head count you type, attached to that card, so the host can count. We don't ask for anything else. Your browser also remembers that you replied and that you opened the link, so you aren't asked twice and can cancel your reply.
Cards. The text and design of each card, and a picture of it, are stored so the link works and previews properly in chat apps.
Usage. We use Google Analytics to see which screens are used and for how long. Where the law requires it (the EU, EEA, UK and Switzerland) it stays off until you accept. We don't use advertising cookies.
Cards and replies are stored with Supabase in Mumbai, India, under their data processing terms. The site is served by Vercel. Analytics data goes to Google Analytics. If you are in Europe, this means your data is transferred outside the EU under standard contractual clauses.
A card and its replies stay until the host deletes the card or their account. A cancelled reply is removed at once. Analytics data is kept by Google Analytics for the limited period set in our analytics account.
Guests can cancel a reply from the invitation link on the device they replied from. Hosts can delete any card from My cards, which removes its replies and picture, and can delete their account there too.
Questions, or a request to see or remove your data: write to {{ privacyContact }}.