Privacy policy

Information we collect

• Account information. If you sign in with Google, Google gives us your name, your email address and your profile image. If you sign in by phone, we store your phone number.
• Google connection records. When you sign in with Google we also store the linking record Google returns for that connection: the Google account identifier, the access, refresh and identity tokens, the permissions granted and when they expire. These let the connection keep working. We do not use them to read anything else in your Google account.
• Profile information you enter. A first and last name, and a Venmo handle if you choose to add one.
• Sign-in security information. A one-time code, stored only as a keyed digest and never in readable form, the number of times it has been tried, and rate-limiting records. Those records hold a one-way keyed value derived from your phone number and your IP address, not the number or the address itself. We do not store your raw IP address for rate limiting.
• A session cookie. When you sign in, your browser is given a signed cookie that keeps you signed in for up to 30 days. It carries your user identifier and the time you signed in. It is not stored in our database and we do not read it for any purpose other than signing you in.
• Event information. Events you create, including the name, description, venue, start and end times, time zone, total cost, currency, how many places there are, and a Venmo handle if the host adds one.
• Invitations and responses. Who has been invited to an event, by link or by personal invitation, and whether each person has accepted or declined.
• Event conversation. Comments you post on an event, and whether a host has pinned a comment to the top of that conversation.
• Payment records. The amount owed, the payment method, whether it has been settled, and, for a card payment, the Checkout session and payment identifiers Stripe returns to us. Card numbers never reach 123RSVP. Stripe collects them on its own hosted payment pages.
• Payment history records. When a host marks a payment received or corrects it, we append a record of who made the change, when, and what the status changed from and to. Those records are kept and are not edited afterwards. If a payment situation needs a host's review, we record that the host acknowledged reviewing it. Acknowledging is a record of review only. It does not move money and does not issue a refund.

Why we collect it

• To sign you in and to keep you signed in, and to keep your account secure.
• To run events, which means invitations, responses, amounts owed and event conversation.
• To keep an accurate record of payment changes a host makes, so a disagreement about what was marked paid can be checked.

123RSVP shows no advertising and runs no analytics or advertising services, so none of this information is used to build an advertising profile.

Text messages

If you sign in by phone, we send you a one-time authentication code by text message. We send you a code only after you ask for one. Loading the sign-in page sends nothing.

Your mobile number, SMS consent, and opt-in data are not sold or shared with third parties or affiliates for marketing or promotional purposes. We disclose mobile information only to service providers as needed to operate phone authentication and deliver a text message you requested, including our hosting, database, messaging provider, and participating carriers.

Carriers are not liable for delayed or undelivered messages.

Who else processes your information

We use a small number of service providers to run 123RSVP. Each one receives only what it needs for its part of the service, and each one is permitted to use what it receives only to provide the service we have contracted it for. None of them is permitted to use your information for their own marketing, and we do not sell your information to any of them.

• Vercel, for application hosting.
• Neon, for the PostgreSQL database.
• Google, when you choose to sign in with a Google account.
• Twilio, to deliver authentication text messages.
• Resend, to deliver email.
• Stripe, for card payments and for the hosted payment pages that collect card details.

No analytics service and no third-party error tracking service is connected to 123RSVP.

How long we keep information

• A one-time sign-in code expires 10 minutes after it is sent and cannot be used after that.
• A session cookie is valid for up to 30 days from the last time it was refreshed, and signing out of every device stops the existing ones from working.
• Payment history records are kept as an unedited record of what a host marked and when.
• Account and event information is kept while it is needed to operate your account and the service, or to meet legal, security and recordkeeping obligations.

Apart from the ten minute expiry above, we do not promise an automatic deletion schedule.

Your choices and your requests

• Phone sign-in is optional. You can use a Google account instead.
• Reply STOP to a 123RSVP text message to stop authentication messages to that number. Phone sign-in will stop working for that number. Reply START to the same sender to resume. Reply HELP for help.
• You can sign out of every device from your account page.
• To ask us to provide, correct, export or delete your information, email info@123rsvp.com. A person handles these requests. 123RSVP has no self-service delete button today, and we do not promise a fixed completion time.

How we protect it

We store one-time codes only as keyed digests, we limit how often a code can be requested and how many times it can be tried, and we do not log phone numbers, codes or session cookies. No service can promise perfect security, and we do not.

Changes to this page

If this page changes, we will update the effective date at the top. This page describes how 123RSVP works today.