Privacy Policy

Date polls store the proposed dates, time zone, household names and availability choices for up to 90 days after creation. The poll owner can see household answers. Other participants see only their own saved answers. Choosing a date does not turn votes into RSVPs or automatically send invitations. Private poll links and browser keys control access; no calendar account is connected. Save your private link, or add an email to find the poll again from All your plans.

Private event conversations are available to the household through its RSVP key and to the owner or co-hosts with guest-management permission. They are not public guest notes. A host’s message to a guest is also sent to the email address the guest gave on their reply, and by text to a mobile number we hold for that reply (from a text invitation, a text reply, or one the host added), through our email and text providers; a guest’s message to the host stays on the page, with an email to the host that says a message is waiting when the host has asked for one. Conversations follow event/RSVP retention and deletion practices. Anyone holding a household’s private reply key can read its conversation.

Shopping lists and the headcounts used to create estimates are private to the event owner. Changing RSVPs does not automatically overwrite saved quantities or checked items. Lists follow the event’s retention and deletion practices.

When available, our email provider sends delivery, bounce and complaint reports. Delivery to a mail system does not prove inbox placement or reading. We use these reports to display accurate status and suppress unsuccessful or unwanted email updates. We do not track recipients of copied links or links sent from a messaging app.

Joining a waitlist requires a household name, email, attendance details, and explicit agreement to automatic admission. Waiting households are private to the owner and their own browser access key; they are not counted as attending and cannot access RSVP-only event details. When room opens, a whole household may be marked Going and emailed. Where the host reviews replies themselves, the household is put forward to that host instead, is not on the guest list until the host adds it, and is emailed only if the host adds it. The waitlist stops bringing households up when replies close or the event starts. Waiting details are cleared when the household leaves or comes off the waitlist; waitlist records are removed 30 days after the event.

A guest who is Going may claim a household slot on the host’s bring list. The owner sees the household names; other eligible guests see item availability and their own sign-ups, not other claimants’ names. Changing a reply away from Going or deleting it releases its sign-ups.

A host can deliberately reuse a design and guest settings in a new invitation. Copying descriptions, locations and host contact details is optional. The temporary draft is available for 30 minutes in the same browser session and is cleared when opened in the creator. No replies, answers, photos, purchases, or access credentials are copied. Known suppressed channels are excluded when a host reuses contacts; earlier delivery does not supply permission to contact someone about another event.

Each guest a host adds, by typing or pasting (once the host leaves the box), importing a file or choosing from Past guests, is kept with that event as a contact as soon as it is added, whether or not anything is sent. Only the event owner can see the contact list; co-hosts cannot. It shows the guests of this event, of other events whose private host link this browser holds, and, once the host has confirmed their email in this browser, of every event made with that email. A host can take a contact off the list: it is deleted from that event’s saved contacts and hidden on the host’s other events. Invitations already sent are not deleted; they stay part of each event’s record. Adding or inviting that guest again brings them back. Contacts stay until the host removes them or the event is deleted.

The host email on an event is typed by the host and is not checked when the event is made, so on its own it does not show that the events using it belong to one person. Before contacts from other events made with that email are shown, the host confirms it: by opening the host link in the email sent when the event was made, or with a link and six digit code sent to that address. Codes and links expire, and we keep only scrambled copies of them. Confirming saves a contacts key in that browser that works for one year, and we keep only scrambled copies of the key and the email. The key opens nothing on its own: the list also needs the event’s private host link, so typing someone else’s email into a new event does not show their guests.

The owner can schedule a text-only event-page or email update. Its message and chosen recipient groups are stored until publication or deletion. Actual email recipients are chosen at send time from eligible members of those groups, respecting current email preferences. Unpublished scheduled updates are cancelled if the event is postponed, cancelled, or archived. Scheduling is approximate, not a guarantee of delivery at an exact minute.

Hosts may add up to three RSVP questions. Question wording and choice options are visible to people with the invitation link. Individual answers are stored with the household RSVP and can be seen by that guest using their private RSVP key, the event owner, and co-hosts authorized to manage guests. They are included in the host’s guest-list export, not the public guest list or RSVP-notification email body. A host can opt to share option totals for a choice question with Going and Maybe guests. That question explains the sharing before you answer. Totals count households and do not include names; in a small group, people may still infer who chose an option. Enabling or disabling sharing starts a new question, so earlier private answers are never shared retroactively.

Questions are optional unless the host marks them required for Going or Maybe. A decline does not require answers. Changing questions does not invalidate existing replies or automatically contact guests. Saved answers retain the wording used when submitted, until the guest updates the reply or the RSVP is deleted. Question answers follow the same retention and deletion practices as other RSVP records.

A host may save an optional guest guide with parking, entrance, access, weather and schedule notes. Going and Maybe guests can see the guide using their RSVP access key. Anyone with the guest link can RSVP; this does not verify identity. Host prep tasks and due dates are stored with the event and are accessible only to the event owner. Planning notes follow the event’s retention and deletion practices, not the separate media expiry period.

Event sheets are created in your browser from details you can already access. The host chooses whether to include household names and private prep tasks. Downloads are snapshots: we cannot update or recall copies saved or shared outside PartyWelcome. Keep downloads within the invited group.

A host can invite a co-host with selected permissions to manage guests, post updates, or review media. A co-host may see the private information needed for those tasks, including guest contact details and private notes when guest management is allowed. References to host access in this policy include co-hosts within those permissions. Co-host links expire and the owner can revoke them; co-hosts cannot make purchases or change owner settings.

Recovery uses the email saved with the invitation or poll, or a mobile number attached to an event invitation. A recovery link expires after 30 minutes and changes access only after confirmation. Confirming replaces that host or RSVP key, but does not revoke separately invited co-hosts. We keep only scrambled copies of recovery links, and short-lived records that stop misuse. Email messages may temporarily contain private links while queued for delivery; successful delivery clears the queued message body.

A new event sends a day-before reminder, and a reminder before the RSVP deadline once the host sets one; the host can turn either off. They go by email, or by text to guests the host reached by text when the event has text delivery. Eligible recipients’ email preferences still apply. If a host enables direct email replies, the host email address becomes visible to recipients of invitation and update emails. Contact files are read in the host’s browser; the selected contacts are sent to PartyWelcome when the host submits them for delivery.

Some photo formats need a separate display preview to work across browsers. PartyWelcome may make a smaller preview image, without changing the original uploaded file. Download controls provide the original file.

Hosts provide event details, host contact information, visibility choices, registry links, invitation and update messages, and optional cover or update images. Hosts may add guest names, email addresses and mobile numbers, which are kept as the event’s contacts, and for email or text delivery, the host’s confirmation that each recipient expects the message. Guests may provide a name, email address, attendance answer, household size, number of children, arrival window, private or public notes, photographs, videos, and album links.

A host may add ways to be paid for shared costs (a username in a payment app, an email address or US mobile number for a bank transfer app, and an image of that app’s payment code) with a suggested share and a note. When a host opens shared costs, its members (described below) may record costs, how each cost is split, receipts for costs they added, their own ways to be paid, and payments they made each other.

A person sending product feedback provides the note itself and may optionally provide a public invitation link, recommendation, and email address. For email invitations and updates, we keep recipient addresses and delivery records so hosts can follow up and retry unsuccessful sends without repeating accepted emails. Personal email and text invitation links carry a reference that connects a reply to the invited contact. Hosts can also connect a reply from a general or forwarded link to an invitation themselves. Entering a name or email address does not prove identity or grant access to an existing reply. For text delivery, we keep the message, its delivery status and length, the provider’s reference for it, the opt-out choice and any error the provider reports. To run and protect the service we also keep basic visit records: your internet address, browser type, the time, errors, and how often requests arrive. Our payment processor tells us the amount, the result and a payment reference, but never the full card number.

We use this information to display invitations, collect replies, give hosts a headcount, notify hosts about new or changed replies, deliver requested messages, process payments, review comments and media, prevent misuse, diagnose errors, answer support requests, review product feedback, and meet legal obligations. We use an optional feedback email only to reply about that submission. We do not publish a recommendation without asking first.

If a guest adds an email address to an RSVP, the host can see it and may contact that guest directly about the event. A guest who adds an email address to a new RSVP gets one email with their private RSVP link after replying. Event-update email is a separate guest choice. A guest may RSVP without adding an email address or selecting event updates. PartyWelcome does not use event or guest details for targeted advertising or to train an artificial intelligence model.

When a host adds a guest’s mobile number, before or after paying for text delivery, we keep it with the guest name supplied with it as a contact for that event. Adding a number does not send a text: invitations, updates and reminders go by text only after the host has paid for text delivery for the event, and a recovery text goes only when the number’s own user asks for one. For text delivery we also collect the message text, delivery status, the number of message parts used, the provider’s reference for the message, the opt-out status, and any provider error code. We use a number to send the invitation the host requested, host updates and reminders about that same event, one message when its photos are ready, a thank-you afterwards, and a private recovery link when the number’s user requests one. We do not buy, rent, or sell phone numbers, and we do not use a guest mobile number for advertising.

A host may send a text only after confirming that each guest expects the invitation. A number is added by the host, not taken from a public list or bought. A host may reuse a contact from another event they own; doing so requires the host to confirm again that the guest expects this invitation, and numbers that opted out or were suppressed are left out. Mobile numbers, message content, and text opt-in or opt-out choices are not sold or shared with third parties or affiliates for their own marketing. Our messaging provider and the mobile carriers receive a number only to deliver and report on a message the host requested.

Every text explains how to reply STOP to stop messages. You can reply HELP for help, or email hello@partywelcome.com. A recorded opt-out is kept and continues to apply even if the host later deletes the reply or removes the contact. Message frequency varies by event and is normally a few messages. Message and data rates may apply. Carriers are not liable for delayed or undelivered messages. Agreeing to receive texts is not a condition of creating an invitation, replying to one, or making a purchase.

PartyWelcome uses essential browser storage for the theme you choose and for the private host, RSVP, date-poll or split access key that lets you return without an account. It also remembers invitation links you view on this device, separately from your replies. All your plans shows these saved items, and the splits this browser holds a key to; you can forget an invitation, reply or poll without deleting it. A host who confirms their email also keeps a contacts key here, which works for one year and is used only to show their contact list. A personal invitation reference may be kept for the current browser session; it associates a new reply but does not authorize editing an existing RSVP. We do not use advertising cookies or an advertising analytics service.

To help retry interrupted uploads, your browser may keep a short record of each upload in progress for up to 30 days of active recovery use. This recovery record does not contain file contents, filenames or captions. Retrying after reopening the page requires selecting the original file again. Clearing site data removes this recovery information.

Anyone using the same browser profile may be able to reopen a host dashboard, RSVP, date poll or split. On a shared device, use a private browser profile or clear PartyWelcome site data when you finish.

You may request a private invitation list using an email address or, in the US and Canada, a mobile number already attached to an invitation. The list is delivered to that contact, not shown simply because someone enters it. Links expire after 30 minutes. Phone recovery uses the invited contact’s current event and RSVP association; it does not grant host access. We keep only scrambled copies of these links, and short-lived records that stop misuse. Requested recovery texts are separate from paid invitation delivery and do not subscribe you to marketing.

People holding their own private link can add a missing backup email and request a copy of that link. This does not change attendance or notify the host of a new RSVP. A guest email is stored with their reply or poll answer and may be seen by the host; a host’s recovery email stays private. Email recovery also includes unexpired date polls. Recovery replaces the corresponding private key, so older copies may stop working. A backup copy uses the current key and does not replace it.

Guest pages are unlisted, but anyone with the guest link can open them. Hosts control whether attendee names, totals, comments, and approved media appear. By default, a new or edited guest comment stays private until the host approves it; a host may turn approval off. A host can also keep the street address hidden until a guest replies Going or Maybe.

A guest can reopen their own email address, private note, pending comment, and reply with that guest’s saved RSVP key. The host can see those details through the private host link. They are not shown to other guests. If the guest provides an email address, PartyWelcome may send the host an RSVP notice that can be replied to from the host’s email account. That direct conversation is not stored by PartyWelcome and is also handled by the host’s and guest’s email providers. Delivery details, pending media, and management controls are available only to the host. Hosts are responsible for sharing guest and host links carefully; never publish a host-management link.

An event holds up to 100 guest files or 2 GB, whichever comes first. That limit counts photos and videos on the media wall and a guestbook message’s voice recording or video. It does not include the invitation cover image, an image attached to a host update, or the host’s own music or voice message. A guest photo may be up to 25 MB and a video up to 250 MB; guests can choose up to 25 files at a time. A guestbook voice message, recorded or uploaded as an MP3, M4A, AAC, WAV or WebM file, may be up to 15 MB, and a guestbook video up to 95 MB. PartyWelcome stores the original file without resizing or changing it, so a file keeps whatever its camera or phone wrote into it, which can include the time it was taken and, when the phone’s settings allow it, the place. Anyone who can download an approved file gets that information with it; remove it before uploading if you do not want it shared. Pending contributions are available only to the host. Approved contributions can be viewed and downloaded by anyone with the guest link when the host turns on the media wall. After the event, the first time approved photos or videos are on the wall, each household on the guest list that replied Going or Maybe gets one message saying so, once per event: by text when the event has text delivery and we hold a number for that reply that has not opted out, otherwise by email when the guest chose event updates. The message carries a private link of that guest’s own that opens the event’s photos on any device, and nothing else, while the reply is on the guest list as Going or Maybe, the wall is on, and the photos are kept. Anyone holding the link can see them; we keep only a scrambled copy of it.

PartyWelcome does not scan photos or videos automatically and does not look at them unless someone reports one, a host asks for help, or the law requires it. Reports go to hello@partywelcome.com. Content that breaks the Terms of Service is removed; sexual content involving a minor is reported to the National Center for Missing and Exploited Children and to law enforcement, as United States law requires, and is preserved for as long as that law requires. A parent or guardian who finds a photo of their child on an event wall can ask the host to remove it through the host link, or ask us at privacy@partywelcome.com.

A guest who adds an album link must confirm that it opens without signing in. PartyWelcome requires a secure link and recognizes sharing links from two common photo apps, but cannot verify the access settings or safety of other links. Album owners can change access or remove content at any time. PartyWelcome stores the link, not the outside album, and does not ask for access to a guest’s photo app account.

Hosts choose which RSVP groups can see an update on the event page and whether to send email. Guests must use their saved RSVP key, and their current reply must match a selected group, to read that page update or open its image. The host can also access update images. Email-update preferences apply even to messages marked important. Hosts may follow up with invited contacts whose invitations are not connected to a reply. A household can reply together using one name and a total headcount. Forwarded invitations may be used for a separate reply; hosts should check uncertain matches rather than assume two replies belong to the same person. We cannot track recipients of copied links or links sent from a phone or messaging app.

PartyWelcome never moves, holds or verifies money. A payment app button opens that app with the recipient, and the amount when there is one, filled in. A bank transfer app has no such link, so the recipient, the amount and any payment code are shown to copy or scan. The payment itself happens in that app, under its own terms and privacy practices, and PartyWelcome learns only what a member records afterwards.

A host’s suggested share and its note can be seen by anyone with the guest link. The host’s payment usernames, bank transfer recipient and payment code can be seen by the host, co-hosts, and guests whose reply the host has admitted and who have not declined; PartyWelcome support may see them when helping the host. A payment code image is stored exactly as uploaded and is opened through links that expire.

Shared costs are for the host and for each guest whose reply the host admitted as Going or Maybe, one household each. On the page, a member sees the costs they paid for, added or share first, and every other cost when they ask for it, each with who paid, how it is split and its receipts, and the host sees every cost and receipt; every member can see everyone’s balance and can download every cost and split in the group. A member sees the payments they made or received; the host sees all of them. A member’s own ways to be paid are shown to the members who owe them. A reply that later declines, or waits for the host again, keeps access only while it paid for, added or shares a cost, or sent or received a payment. Changes to costs, receipts, payments, and opening or closing the group are kept in its history with who made them and when.

Costs can also be split without an event, at the split’s own link. Whoever starts a split types their name and the other names, and may give an email address, used only to send them their own private link. Anyone with the split’s link can see its name, the names in it, how many costs it holds, their total and, when it is the same for everyone, each person’s share. Anyone with the link can pick a name that no browser holds yet, or add their own, and then sees what a member sees: the costs they paid for, added or share, and every other cost when they ask for it, each with who paid, how it is split and its receipts; everyone’s balance; the payments they made or received; and a spreadsheet of every cost. A person’s own ways to be paid are shown only to the members who owe them. Any member can add a missing name. Whoever started the split can free a name so it can be picked again, remove a name that has nothing in the split, close the split and delete it. Each person’s key is kept in their browser, and PartyWelcome stores only a scrambled copy of it; an email carrying the starter’s own link holds the key only until it is sent or given up.

Receipts may be photos or PDFs of up to 10 MB each, stored without changes, so a receipt keeps whatever its camera, scanner or store printed on it. Cover or remove card and account numbers before uploading. Receipts are opened only through expiring links given to members.

When a guest marks that they paid, in shared costs or against the host’s suggested share, PartyWelcome keeps the amount, the date, how they paid and, if they add them, a transaction number and a screenshot or PDF of the payment of up to 10 MB, stored without changes and opened only through expiring links. The person paid and the host can see it, and so can a co-host the host has allowed to check payments; other guests cannot. Against a suggested share, the host and such a co-host see which households have paid, can mark a payment for a guest, and can mark any payment Paid or Not paid; the guest sees who last marked their payment, with the host’s name for the host and co-hosts. A guest can remove a payment they recorded unless the host marked it Not paid; removing a reply removes its payments against the share and every payment screenshot it added.

A member who gave an email address gets at most one shared-costs summary a day, and only when someone else changed a cost they paid for or share, or a payment to or from them. Each summary links to a page where it can be turned off.

We use providers for hosting, file storage, security, email delivery, text-message delivery, and payment processing. They receive only the information needed to provide those services to PartyWelcome. Ask us for the list of providers we use at privacy@partywelcome.com.

When you share by a messaging app or your phone, your browser or device passes the invitation text and link to the application you selected. When you choose directions, your device sends the event address to a map service. Opening a registry, a shared album or a payment app sends you to that provider, and a payment button passes it the recipient and the amount. A payment app that takes a note also receives the event name. Those transfers happen at your direction and are governed by the other service’s privacy practices.

We may disclose information when required by law, to protect people or the service, or as part of a business transaction. We do not sell personal information or share it for cross-context behavioral advertising.

PartyWelcome automatically removes directly uploaded guest photos and videos, host-update images, and stored album-link records 30 days after the scheduled event end. If no end time was entered, we use eight hours after the start time. Before removal, the host or a guest who has replied may buy 30, 90, or 365 more days. An extension postpones automatic removal; it does not change the host’s visibility, upload, or approval settings. There is no subscription or automatic renewal.

The invitation cover image is not part of that 30-day media cleanup. It remains with the event until the host replaces it or asks PartyWelcome to delete the event, or PartyWelcome removes it for a legal, security, or service reason. Deleting an album link from PartyWelcome does not delete anything held by the photo app or another provider.

A host can delete their own event. If guests have replied, the event must be cancelled first, because cancelling is what tells them. If nothing has been added to it, the event, its guest list and its cover image are removed straight away and cannot be recovered. If guests added photos or videos, the host can close the invitation and keep those contributions available until the stated removal date, or choose to delete the event and everything in it immediately. Immediate deletion permanently removes the event, replies, stored media, shared costs, receipts and guest access, including contributions from other people. Completed PartyWelcome purchases for the event are not refunded. Deleting an event also deletes PartyWelcome’s own records of purchases made for it, except a note that a refunded payment was refunded; our payment processor keeps its own record of each payment. Only the event owner can delete an event; a co-host cannot.

A date poll’s host can delete it from the poll’s own page, which removes its dates, every household’s answers and its link preview images; a poll is also removed 90 days after it was made. A split made without an event has no automatic deletion date. Whoever started it can delete it at any time, which permanently removes its names, costs, receipts, payments, ways to be paid and history; any member can download its spreadsheet first to keep a copy.

When a guest buys an extension, PartyWelcome privately tells the host the guest’s RSVP name and the time added. Other event, RSVP, email-delivery, text-delivery, and product-feedback records do not currently have an automatic deletion date. We keep them while needed to operate and improve PartyWelcome or until the affected person requests deletion. Payment and refund records for an event remain with it while it exists. Opt-out, fraud-prevention, security, and legal records may be kept longer when needed.

A guest can remove their own reply from the invitation, without emailing anyone. That removes the reply, the private note, the public comment, bring-list sign-ups and any album link they shared. Photos and videos they uploaded go with it unless they choose to leave those on the wall; a photo left behind keeps no record of who added it, so that choice cannot be reversed. A recorded text opt-out is kept, because clearing it would resume messages the guest stopped. Payment records for the event are kept while the event exists. If the guest took part in shared costs, the costs, receipts, payments and history they were part of stay in the group under “A former guest” so everyone else’s balances stay correct; their name, ways to be paid and payment code are removed.

Shared costs, receipts, recorded payments and the group’s history are not part of the 30-day media cleanup. A cost can be deleted by the person who added it or the host, which removes its receipts; a receipt by whoever uploaded it, the cost’s author or the host; and a recorded payment by whoever recorded it or the host. The history keeps a line for each change and is removed with the event. Any member can download a spreadsheet file of every cost and split in the group and their own payments; it does not include receipts.

A host or guest may request access to, correction of, or deletion of their information by emailing privacy@partywelcome.com. Include the public event link when it helps us find the record, but never send the private host link. Some records may remain when the law permits or requires it.

PartyWelcome is a general-audience service. A person under 13 must not submit personal information or upload a photo or video. A parent or guardian should create the event or reply for the household. If you believe a child under 13 submitted personal information, contact us so we can review and remove it.

You can get a copy of what we hold for your email address or mobile number, or delete it. You do not need an account.

Choose Your data at the foot of any page. Use an email from an invitation, reply, open poll, split or contact list. A US or Canadian mobile number on an invitation or contact list works too, unless it replied STOP. We send a private link to that email or number. The link works for 30 minutes. If you cannot get a link, write to us.

Your copy downloads at once. If a list is very long, the copy is cut short and says how to ask for the rest. Deletion starts when you confirm. Many events can take a few minutes. A payment still open on an event must finish first. If you write to privacy@partywelcome.com instead, we reply within 30 days.

Deleting removes your replies, notes, messages, photos and videos, guestbook messages, invitations, poll answers, and your place on any host’s guest or contact list. If you host, your events, date polls and splits go too. A poll already past its end goes in our regular cleanup. Guests of an upcoming event who get its emails receive a short note that you cancelled it.

A few records stay, only where needed. If you shared costs, your share stays as “A former guest” so everyone’s totals stay right. If your number replied STOP or cannot take texts, we keep it without your name, so it is not texted again. If an email to you bounced, you marked one as spam, or you stopped an event’s invitation emails, we keep a scrambled copy of your address so that event never emails you again. A purchase you made for someone else’s event stays without your name, and our payment processor keeps its own record. Feedback you sent us stays without your email. A scrambled copy of your address keeps hosts’ contact lists from adding you back, though a host can still invite you.

Our backups are replaced within 30 days, and our hosting provider keeps short records of visits. Our email and text providers keep their own delivery records for a time. Ask us for the list of providers we use.

Hosts can change event visibility and moderation settings through the private host link. Guests can remove their own reply and everything they added with it (except shared-costs records, which stay under “A former guest”), decline event-update email, turn off the shared-costs summary, download shared costs, and reply STOP or HELP to a text. You can get a copy of your data or delete it through Your data. Depending on where you live, you may have rights to know, correct, delete, or receive a copy of personal information and to appeal a denied request. PartyWelcome will not treat you differently for making a privacy request.

Email privacy@partywelcome.com from the relevant address and include the public party link when it helps identify the record. Never include a private host key or payment card number.

PartyWelcome limits access to host controls with private keys and uses service providers with security safeguards. No online service can promise perfect security. Information may be processed in the United States or another place where a service provider operates.

PartyWelcome is operated from 8 The Green, Suite B, Dover, Delaware 19901.

We may update this policy when the product or law changes. The effective date at the top identifies the current version. Material changes will be presented in the service when appropriate.

Questions and privacy requests may be sent to privacy@partywelcome.com.

Email a privacy request