Legal

Privacy policy

Last updated: October 29, 2026

1. Who we are

NextInvite (nextinvite.app) is operated by [Operator legal name — fill in src/lib/legal.ts]. Privacy questions go to hello@nextinvite.app.

2. What we collect

Three kinds of personal data, all tied to a specific event:

  • Host details. Your name and email address so you can sign in to the dashboard and receive notifications about your event.
  • Guest details. The names and email addresses you add to your guest list, plus a unique RSVP token we use to render each guest’s personal RSVP link.
  • RSVP responses and comments. Each guest’s Yes / No / Pending status and any comment they leave. Timestamps are recorded.
  • Images. Any artwork you upload or generate for your event is stored as part of that event.
  • Delivery status. For every email we send on your behalf, we record whether the recipient’s mail provider accepted it (Sent, Delivered, Delayed, Bounced, Complained). We do NOT record opens or clicks.

3. Why we use it

Only to send invitations and the automatic reminder for your event, show RSVP status in your dashboard, and support you if you email us. Nothing on this list is sold, rented, or shared with advertisers.

4. Who processes it

NextInvite uses a small number of named service providers to deliver the product. None of them receive more data than they need to do their part.

  • Resend — sends every outgoing email (invitations, the automatic reminder, RSVP notifications). Receives recipient email addresses, your “from” address, and the message body for the duration of delivery.
  • OpenAI — generates optional AI artwork when you opt in on the Design tab. Receives only the text prompt you type, not your guest list.
  • Turso — hosts the database that stores your event, guest list, RSVPs, and images.
  • Vercel — hosts the application and runs the background job that sends your reminder.
  • Google Analytics (GA4) — measures aggregate traffic to the public pages. Does not track RSVP content, guest email addresses, or anything inside the dashboard.
  • Payment processor — none at the time of this policy update. Payment is not currently collected on this site. When billing goes live, the processor used will be named here before it ever processes a payment.

5. How long we keep it

Your event data is kept for 1 year from the date you create your event. Thirty days before expiry we email you three options: renew for $14.95 CAD, download everything as CSV + images (free), or let the data retire (free). If we do not hear from you by the deadline, the data is deleted.

Note: the renew / download / delete flow is a stated policy that applies to your event data; the engineering to automate it ships with the full billing build. In the meantime, reaching out via the email below triggers the same options manually.

6. Access, export, and deletion

At any point you can:

  • Export your guest list and all RSVP responses to CSV from the dashboard.
  • Email hello@nextinvite.app to request a copy of everything we hold about you, or to delete it before the 1-year mark. We respond within 30 days.
  • Guests can click the one-click unsubscribe link in any email we send to stop receiving further messages for that event. Their RSVP record is retained for the host’s reference but no more emails go out to them.

7. Cookies

The only cookie we set ourselves is a dashboard sign-in cookie (admin_auth) so you don’t have to re-enter the password on every page load. Google Analytics sets its own cookies to measure aggregate traffic.

8. Security

Data is held with the service providers listed in Section 4, which use industry-standard encryption in transit (TLS) and at rest. We do not store payment card details ourselves.

9. Children

NextInvite is not intended for use by anyone under 13. If you think a child has provided information to us, email the address above and we will delete it.

10. Changes to this policy

If we materially change what we collect or how we use it, we bump the “Last updated” date at the top. Big changes that affect existing hosts will be sent by email as well as reflected here.

See also: Terms · Contact · Home