The fine print,
in plain English.

data controller

simplyrsvp is run as a sole trader by Dominic M Brause. Postal address and email are under the Imprint tab.

what we store

Two kinds of accounts, two kinds of data.

• Hosts — an email address and any details you add to your profile, plus the events you create and the invitations you send.
• Guests — the name and email you supply when you reply, the event you replied to, and whether you clicked our 12‑hour confirmation message. Two replies from the same address are merged so you only count once.

email scrub at event end

Once an event is over, we replace each guest’s plaintext email with a salted SHA-256 hash and null out the original address. The hash lets a guest later sign up for an account and claim their reply history; if they never sign up, the row isn’t restorable. After event completion neither we nor anyone with database access can contact past attendees again.

what we send by email

• Sign-in links and login confirmations.
• For guests: a single confirmation roughly 12 hours after you reply, plus any event-specific updates the host triggers (e.g. cancellation, time change).

No newsletters. No marketing. No third-party promotions.

what we don’t do

We don’t sell your data. We don’t run third-party ad or tracking pixels. We don’t share your address book with anyone. The one place we look at tastes is a host’s own table matching (below), only to suggest who might enjoy a seat together — never to advertise to you.

table matching

When members ask to join a host’s evenings, we help the host compose the room: interested members are grouped into suggested tables by shared tastes — cuisines, conversation topics and vibes. Your city and any dietary notes help us group locally but are never sent onward. To draft the wording of a suggestion we send a pseudonymised card to our AI provider, xAI (the “Grok” model): it carries those tastes and topics, but never your name, email, account id, city or dietary needs. Suggestions go to the host alone, as a starting point — a person decides who is actually invited, not the machine. You can switch table matching off for your card at any time from your account.

sub-processors

We use a hosting provider for the application and database, a transactional email provider for the messages above, Google as an optional sign-in provider when you choose “sign in with Google”, and xAI (United States) to help compose the table suggestions above. Where a processor sits outside the EU/EEA we rely on Standard Contractual Clauses. The full, current list is on our sub-processors page.

your rights

Under GDPR you can ask for a copy of your data, ask us to correct or delete it, or export your events. Drop us a line and we’ll get back to you within a working week. If you think we’ve mishandled your data you can also complain to the Irish Data Protection Commission.