Privacy Policy

Who we are

RSVME (“we”, “us”) provides event hosting and guest coordination software. Contact us about privacy requests through our contact form.

Personal data we collect

Depending on how you use RSVME, we may process:

• Account data — email address and profile fields you provide when signing in (including optional phone when hosts or guests store one).
• Event and RSVP data — event details hosts create; ticket/RSVP status; party size; custom field answers hosts configure (which may include dietary, accessibility, or other guest responses).
• Guest preferences — structured preference data hosts or guests attach to tickets for operations.
• Messages — event chat and broadcast content sent through RSVME.
• Check-in and attendance — check-in timestamps and related operational status.
• Location-adjacent data — event coordinates and map display via Mapbox when hosts set a place.
• Payment-related data — when a host uses Stripe Payment Links, Stripe processes payment details; RSVME stores payment session identifiers needed to issue tickets.
• Contact form submissions — name, email, reason, and message when you write to us via /contact.
• Technical data — IP address (hashed for abuse controls on public forms), user agent, and analytics events as described below.

We do not currently collect SMS content through Twilio or similar SMS providers — that path is not shipped.

Identity privacy tiers

Hosts may set identity tiers (full, pseudonymous, or hidden) that change what other guests and some staff see. Operational detail for guests and hosts is explained on our Trust page. This policy does not replace that explanation.

Identity privacy keeps other guests from seeing (and harvesting) emails: peer-facing surfaces show display names or pseudonyms only. The workspace owner retains full operational visibility; other staff see tier-appropriate labels unless granted a per-ticket reveal. It raises the bar against casual exposure and screenshots, but does not protect against a compromised organizer account, a breach of RSVME, legal compulsion (e.g. a subpoena), lock-screen or shoulder-surf exposure, or a sophisticated/resourced adversary. For high-stakes source-protection or safety contexts, use professional measures beyond what this tool claims to provide.

How we use data

We use personal data to operate the service: authenticate users, deliver invites and lifecycle email, power host dashboards and guest passports, run check-in, process public RSVPs, prevent abuse, and improve reliability. Hosts use guest contact and roster data for their own event operations.

Cookies and analytics

Cookies and analytics are used to operate the site, keep you signed in, and understand product usage and performance. You can use browser controls to limit cookies; some features may not work without essential session cookies for authentication.

Retention

Event, ticket, message, and related operational data are retained while a workspace keeps them in RSVME and for a reasonable period afterward for backups, abuse investigation, and legal obligations. When you request account deletion via contact, we delete or de-identify account-linked personal data we control, except where we must retain records (for example, payment reconciliation or security logs). Hosts control guest lists for their events; deleting a host account does not always erase every historical operational record immediately.

Your rights

You may request access, correction, or deletion of personal data we hold about you by submitting a request through /contact. We will respond within the same 4-business-day contact SLA where feasible, or explain if more time is required.

Children

RSVME is not directed at children under 13, and we do not knowingly collect personal data from them.

Changes

We may update this policy as the product changes. Material updates will revise the effective date and version above. Continued use after an update means you accept the revised policy.