SMS Opt-In & Consent
This page explains exactly how Fancy RSVP collects consent before sending any text message, what guests agree to, and how to opt out at any time.
Who Operates This Program
Fancy RSVP (fancyrsvp.com) is an event invitation and RSVP platform owned and operated by Fancy RSVP, based in San Diego, California. The brand and the operator are the same party, and are the sender of every text message described on this page; there is no other party sending on our behalf.
- Brand: FancyRSVP — also written Fancy RSVP in our logo, on this website, and in the sender identification appended to every text message. The two spellings are the same brand and the same sender; there is no other.
- Operated by: Fancy RSVP
- Based in: San Diego, California, United States
- Website: fancyrsvp.com
- Contact: info@fancyrsvp.com
What Messages We Send
Fancy RSVP sends transactional and informational text messages only, on behalf of the host of an event the recipient was personally invited to. The program covers exactly these five message types and nothing else:
- Event invitations — a personal invitation with the guest’s RSVP link
- RSVP confirmations — confirmation that we received the guest’s response
- RSVP updates — changes to the guest’s own response, or a follow-up when no response has been received
- Event reminders — RSVP deadline and event-date reminders
- Event updates — date, time, or venue changes and day-of logistics
This is not a marketing service. We never send promotional or advertising messages through this program, and we send nothing outside the five types above. The consent language on the checkbox below covers this same set, referring to event invitations as “invitation links” and to RSVP confirmations and RSVP updates together as “RSVP confirmations.”
How a Guest Opts In
- A guest opens their event’s public RSVP form (no account or login required).
- A guest who declines is asked for neither a number nor consent — neither field is shown to them, and neither is required to submit. We send no messages at all to a guest who is not attending, so there is nothing for them to consent to.
- A guest who accepts is asked for a mobile number and shown an unchecked consent checkbox carrying the exact language below. Directly above it the form states why the number is needed: the host sends that guest their table assignment and entry pass by text, and uses the same channel to reach them if the date or venue changes.
- The checkbox is never pre-checked and is never ticked on the guest’s behalf. Consent is never inferred from a guest providing a number, and it is never collected by any other control, button, or agreement on the page.
- For an accepting guest, both the number and the checkbox are required to submit this form, and the form says so before it is submitted. A guest who wishes to attend but not to receive text messages can ask their host to add them to the guest list directly instead, without providing a number — and any guest who has opted in can end all messages immediately by replying STOP, which never affects their RSVP, their seat, or their attendance.
- The guest’s choice is stored as a timestamped record tied to their response, alongside an identifier for the exact version of the consent wording they were shown.
- A guest who leaves the box unticked is excluded from every send, and that exclusion is enforced at the point of sending, not merely in the interface. Their refusal is permanent until they choose otherwise — it cannot be overridden by anyone, including the event host (see “Consent Obtained by the Event Host” below, which is the only other way a number can become messageable).
Guests who decline to provide a phone number, or who leave the box unticked, never receive text messages from us.
Consent Obtained by the Event Host
Event hosts often already hold their guests’ permission to text them about an event — a wedding party, a company roster, a family list gathered long before the host chose our platform. That consent belongs to the guest, and it remains valid regardless of which tool the host uses to act on it. We therefore allow a second, narrower path onto our messaging list, with conditions:
- When a host adds or imports a guest’s phone number, they are shown a separate, unchecked box and must affirmatively confirm: “I have obtained this recipient’s consent to receive event-related SMS messages.”
- That confirmation is recorded against that specific guest, with the host’s identity and a timestamp — not as a blanket setting. If the host does not confirm it, the number is stored on their guest list and is never sent a text message.
- The host warrants under our Terms of Service that the consent is genuine, prior, and express, and they carry responsibility for it.
- A guest’s own decision always overrides a host’s. If a guest was shown our consent checkbox and left it unticked, no host attestation can enable messaging for that number. A STOP reply likewise suppresses the number permanently and platform-wide, whatever any host has confirmed.
Every message sent on this basis carries the same sender identification, rates disclosure, and STOP/HELP instructions as any other, so a recipient can end it immediately. We never purchase, rent, or scrape numbers, and a host’s confirmation is never a substitute for the guest’s right to opt out.
SMS Consent Is Separate From Every Other Agreement
SMS consent is collected by a single dedicated checkbox that asks about text messaging and nothing else. Ticking it agrees to receive texts — it does not accept our Terms of Service, our Privacy Policy, or any other agreement, and no other agreement collects it on our behalf. It is never pre-checked, and it is never inferred from a guest simply providing a phone number.
A guest’s decision about text messages is completely independent from acceptance of our Privacy Policy or Terms of Service. Neither document asks for SMS consent, neither one grants it, and accepting either has no effect on whether a guest receives texts. Equally, a guest who opts in to texts is not required to accept either document.
Where consent is required: when a guest acceptsan invitation through a host’s RSVP form, a mobile number and this checkbox are required to submit that form. The host uses text messages to deliver that guest’s table assignment and entry pass and to reach them if the date or venue changes, and the form states this directly above the checkbox. A guest who declines is asked for neither, and is shown neither, because no message is ever sent to a guest who is not attending. A guest who wishes to attend but not to receive texts can ask their host to be added to the guest list directly, without providing a number.
Opting in on this page is entirely voluntary and is not connected to any RSVP. Wherever consent is given, it can be withdrawn at any moment by replying STOP — which stops every message from every event immediately and permanently, and never affects a guest’s RSVP, their seat, or their attendance.
Opt In to Fancy RSVP Texts
This is a live opt-in form — not a demonstration. It uses the exact same consent language, and the same independence notice, that every guest sees inside their event’s RSVP form. The checkbox is unchecked by default, and submitting the form records your consent together with a timestamp, the version of the consent wording shown, and the phone number you entered:
Message Frequency & Rates
Message frequency varies depending on the event and on your own activity; a typical guest receives approximately 1–5 messages per event (for example, one invitation, one or two reminders, and a day-of update). There is no recurring or scheduled series — we send only when the host has something to tell you about an event you were invited to. Message & data rates may apply depending on your mobile carrier plan. Every message identifies Fancy RSVP as the sender and carries “Reply STOP to opt out, HELP for help.”
What Our Messages Look Like
Every message we send ends with the same sender identification, rates disclosure, and opt-out instruction — it is appended automatically and cannot be removed by a host:
- Hello Alexander, you are cordially invited to Sophia & Julian's Wedding Gala on Oct 24th. Kindly RSVP at: https://fancyrsvp.com/sophia-julian/rsvp?g=8f2c - Fancy RSVP. Msg&data rates may apply. Reply STOP to opt out, HELP for help.
- Hi Alexander, we have your RSVP for Sophia & Julian's Wedding Gala - party of 2. See you on Oct 24th. - Fancy RSVP. Msg&data rates may apply. Reply STOP to opt out, HELP for help.
- Reminder: Sophia & Julian's Wedding Gala is this Saturday at 6pm, Cascade Hall. Doors open at 5:30pm. - Fancy RSVP. Msg&data rates may apply. Reply STOP to opt out, HELP for help.
How to Opt Out or Get Help
- Reply STOP (or UNSUBSCRIBE, CANCEL, END, or QUIT) to any message to stop receiving texts. You’ll receive one final confirmation, then no further messages.
- Reply HELP to any message for assistance.
- Or email info@fancyrsvp.com and we’ll process the request for you.
Opting out never affects a guest’s RSVP or their ability to attend an event — hosts can still reach them by email or other contact methods they’ve shared.
We Never Sell or Share Your Number
Phone numbers and SMS consent records are never sold, rented, or shared with third parties for marketing purposes. No mobile information — including phone numbers, opt-in status, and consent records — is shared with, sold to, rented to, or otherwise disclosed to any third party or affiliate for their own marketing or promotional purposes. The only third party that ever receives a guest’s number is our messaging carrier, Twilio, acting solely as our processor for the purpose of delivering the messages described on this page. Text-message originator opt-in data and consent are never shared with any third party.
Full Terms & Privacy
Complete SMS terms are in Terms of Service — Section 5 (SMS Messaging Terms & Conditions), and full details on phone-number data handling, consent records, and your rights are in our Privacy Policy — Section 3 (SMS/Text Messaging Communications & Consent).