PRIVACY NOTICE

How RSVP4Events uses information.

Updated November 3, 2026. This notice describes the information handled by RSVP4Events and the choices available in the current service.

Account and event information

We store the name and email used for an account, a protected password representation for email accounts, session records, and the event pages you create. Passwords and recovery codes are stored as protected representations rather than as readable originals. A secure session cookie keeps an email account signed in. ChatGPT sign-in uses the identity information supplied by that provider.

Event information can include titles, dates, locations, page content and access settings. A published public event can be read by people with its link. A private event requires its access code. Sharing a private link that includes the code also shares access. Unpublishing or archiving stops the guest page from being available; it does not delete your account or event records.

Guest responses and service requests

When a guest submits an RSVP, we store their name, email, attendance, party size and any offered meal preference. The event organizer can view the responses for that event. A private edit link lets the guest change their response, so it should be kept private.

We store add-on and marketing requests, their notes and review status. Seminar marketing inquiries include your name, firm, email, phone, event location, anticipated date, topic, attendance goal, selected services and optional budget range. Support requests include the contact information, topic and message you submit. The site owner can review requests in the administration area. Do not include passwords, recovery codes, payment details or private RSVP edit links in support messages.

Analytics and service providers

Google Analytics is used on the public homepage and template gallery and for selected signup and organizer actions. The tracking code sends bounded action labels and campaign information. It does not deliberately send event titles, account identifiers, form values, guest details, access codes or private edit links. Test-workspace actions are excluded from these action events. Analytics cookies may be set by Google, subject to browser settings.

For public event pages, we store aggregate counts of visits, RSVP starts and successful new submissions, primary-action clicks, directions clicks and calendar downloads. These counters do not store visitor identifiers, IP addresses, names, email addresses or form values and do not use analytics cookies. Private events, sandbox events and private RSVP edit visits are excluded from browser activity tracking. Organizers can view their event’s totals. Counts describe activity rather than unique people.

OpenAI Sites and its hosting infrastructure provide the website, database and authentication services. Google supplies analytics and mapping destinations. Opening an external research or map link takes you to that provider's service. Live card checkout is not enabled, and this site does not currently collect card numbers.

Retention and your choices

Account, event, guest-response and request records remain stored while needed to operate and support the service. The thirty-day event hosting period describes page availability, not an automatic deletion of all underlying records. Organizers can delete their event and its associated responses through the dashboard. Session records expire, and expired session and authentication-rate-limit records are cleaned up during account operations.

You can control cookies in your browser and use its privacy controls. For an access, correction or deletion question, submit a privacy request. Requests are reviewed manually, and identity or authority may need to be established before records can be changed.