Where should I send a private watch-party link — group chat, DM, or social?

Group thread for friend circles you text weekly. Individual DMs for anyone outside that circle. Avoid pasting it into a public social post or a Twitter/Instagram story — those audiences are too leaky. iMessage and WhatsApp are fine because the link only goes to the addresses you typed in.

What is RSVP-gated address reveal?

The street address only unlocks for a guest after they RSVP yes. The shareable link lands them on a page that shows match, time, what to bring, and a 'tap to RSVP' button. The address appears on the confirmation screen and in the day-of reminder. Pitch Party handles this automatically — the host doesn't have to manually send the address.

What if a guest asks to bring a plus-one?

Tell them to ask first, then add the plus-one through the RSVP system so the headcount stays accurate. Never just say 'sure forward the link' — a forwarded raw link is what burns address privacy. On Pitch Party, the original RSVP can add a +1 from inside the event so the plus-one's name is on the list before they walk up.

Should I use an expiring link or an evergreen one?

Expiring for matches more than 2 weeks out — set it to expire at kickoff so a screenshot from someone's camera roll doesn't haunt the next match. Evergreen is fine for the friend-circle weekly thread where everyone already has the link. The 80/20 default is: expire it at kickoff.

A guest sent the link to someone I don't know. What do I do?

First, don't panic — the RSVP gate hasn't fired yet, so the stranger only has the event preview, not your door. Second, message the original guest and ask who they shared it with. Third, if the stranger isn't acceptable, rotate the link from the event settings. The old URL stops working instantly; everyone who already RSVP'd keeps their reminder and their address access. New people have to come through the new link.

Hosting guides · Anywhere

How to share a private event link without leaking your address

How to share a private watch-party link without leaking your address — channel, message, RSVP-gated reveal, plus-ones, and link rotation when it forwards to a stranger.

Create your private event May 12, 2026 · Pitch Party editors

You’ve decided to host. Living room, four to twelve people, a match that means something. The next step is the part most first-time hosts get wrong — how to actually share the invite. Drop the wrong link in the wrong thread and you’ve put your home address into a Google Maps preview that’s now sitting in five group chats you don’t know about.

This is the mechanics post. Where to share. What to write. How to keep your address gated behind an RSVP. What to do when the link travels further than you meant.

TL;DR. Send via iMessage, WhatsApp, or DM — not public social. Don’t paste your street address into the message. Use a link that hides the address until the guest RSVPs. Set the link to expire at kickoff. If a guest wants a +1, route it through the RSVP, not by forwarding the raw link.

RSVP-gated address reveal in 60 seconds Spin up your private event — friends RSVP, then they get the door → Create your private event

The channel matters as much as the message. Three real options for a private watch party, in order of how often they’re the right call.

Group thread (iMessage, WhatsApp, Signal). This is the default for friend circles, the same six to twelve people who already plan dinners together. Paste the invite link with a one-line note. Everyone sees it once, RSVPs trickle in over a day or two, you don’t have to chase. The privacy logic works because the thread is already a closed set. You typed every number in there yourself.

Individual DMs. For anyone outside the regular thread. The new neighbor, the work friend who’s been meaning to come over, the cousin in town for the weekend. One DM per guest, same one-line note, same link. Slower than blasting a thread, but it signals to the recipient that they were thought of specifically — which is the kind of guest you want. A DM also keeps the share log clean: you know exactly who got the link.

Social DMs (Instagram, X). Useful when you don’t have someone’s phone number but you do follow each other. Treat it like an individual DM, one-line note plus link, done. One caveat. Instagram aggressively previews links, and the preview will pull whatever your event’s open-graph image is set to. That’s fine for a Pitch Party event because the preview is the match card. It’s not fine if you’ve pasted a raw Google Maps URL, because then your front door shows up as the preview image. Use the platform’s event link, not the address.

Where not to share. Twitter/X posts, public Instagram stories, Facebook walls, LinkedIn, your personal site. Public social is for public watch parties. Private events stay in private channels. The whole point of a private link is that you control the distribution.

The middle case is the Discord server or Slack workspace. Closer to a group thread than to public social, but if you’ve got 400 members and you don’t know half of them, treat it as public and either skip it or post a different event meant for the wider crowd. The “did I personally invite each person in this channel” test is the right test.

The message is short. Three things, in this order.

The match and kickoff time in the recipient’s time zone. “USA vs Paraguay, Friday June 12, 6 p.m. PT (9 p.m. ET).”
The doors-and-vibe one-liner. “Doors at 5, low-key, kids welcome, bring a six-pack if you can.”
The link. That’s it. Not the address. Not the parking notes. Not the menu.

Why so short. Because everything else lives behind the link. The RSVP page has the address, the parking, the what-to-bring breakdown, the dietary notes. If you put the full address in the iMessage, three things happen. One, it bypasses your RSVP gate entirely. The recipient now has the door whether they RSVP or not. Two, the address gets included in any forwarded screenshot. Three, the iMessage link preview now shows your front yard. Keep the address off the share message, full stop.

One sentence that does work in the share message. “Address unlocks after you RSVP.” Sets the expectation, doesn’t feel weird, signals that the link is more than a flyer.

RSVP-gated address reveal — how it actually works

This is the core mechanic. RSVPify’s privacy guidance puts it plainly. Invite-only events should match RSVPs by name and email, hide event details behind a gate, and prevent invitees from editing preset names so invites stay non-transferable (RSVPify). Hejmo, an invite-only platform built on tokenized URLs, takes the same approach further. Every household gets a unique tokenized link, and if a link leaks, only that one household’s link is compromised while everyone else’s URL keeps working (Hejmo).

The pattern, applied to a watch party. The share link lands the guest on an event page that shows the match, the kickoff time, what to bring, and a tap-to-RSVP button. The street address is not on that page. After the guest RSVPs yes, the confirmation screen reveals the address, drops it into the day-of reminder, and (if you’ve turned it on) opens it directly in their maps app at the right time.

The host benefit is real. You don’t have to text the address to nine people the morning of. You don’t have to remember who told you they were coming over coffee. The address travels with the RSVP, automatically, only to people who said yes.

Pitch Party handles this by default. Once a guest RSVPs through your private link, the address appears in their confirmation and in the 24-hour and 1-hour reminders. Until then, the page they see is just match-card and door-time. Pull the link back, rotate it, or close RSVPs and the address access goes with it.

Screening guests — when to actually require approval

Default for a friend-circle invite is auto-approve. You already know everyone, you don’t want to add manual friction, the link goes in the thread.

The case where you flip on manual approval is a public match that you’re hosting “semi-privately.” Big knockout-round game, a small apartment, friends-of-friends you’d like to meet but not 40 of them. Pitch Party’s manual-approve toggle lets RSVPs queue up; you tap yes or no inside the event. The address only reveals on approval. It’s the same gate, just with a human review step instead of an automatic one.

Two practical reasons to use it. One, the match has stakes and you’ve got more interest than seats. Two, you’ve published the event in a context (a Discord, a Slack, a community thread) where you don’t fully control who has the link. Approval flips the default from “anyone with the link gets the door” to “anyone with the link can ask for the door, and you decide.”

What’s not worth bothering with is manually approving your closest six friends. That’s friction for no security benefit. Approval is for the in-between guests, not the inner circle.

RSVP gate + address reveal, built in Create the event, share the link, let the gate do the work → Spin up your private event

The plus-one problem

The most common way a private link gets out is plus-ones. A friend RSVPs, then asks if they can bring their roommate. You say yes. They forward the raw link. The roommate now has the address, except the roommate didn’t actually RSVP, so they’re not on your headcount. You ordered food for ten and twelve people walked in.

Etiquette on plus-ones is pretty settled. If the invitation doesn’t say plus-one, the guest doesn’t get to assume one, and the polite move is to ask the host directly (Inside Weddings). For a casual watch party that almost always means yes, sure, bring your roommate. The mechanics of how that yes happens is where it matters.

The right flow. Your friend RSVPs, sees a +1 toggle, types the roommate’s first name, taps add. The roommate’s name now shows on the headcount. The address is shared in your friend’s confirmation. The roommate doesn’t get a separate link forwarded to them, doesn’t independently RSVP, doesn’t show up anonymous. You can see at a glance that “Jake +1 (Mara)” is on the list.

If you’re managing this in a group thread without a structured RSVP, you can still do it. The rule you enforce. “If you’re bringing someone, text me their name in advance.” Not “forward the link.” The name goes on a list, the address travels through the existing guest. The raw link doesn’t multiply.

Expiring vs evergreen links — the 80/20 default

Two link models, depending on the cadence of your hosting.

Expiring links. Set the URL to die at kickoff. New people can’t RSVP after that, the page returns a “this event has ended” message, the address stops being accessible to anyone who hadn’t already RSVP’d. This is the right default for one-off matches and especially for any match more than two weeks out. The further out you publish, the more chance a link gets screenshotted, forwarded, or sat in someone’s camera roll until next month, by which point you don’t want it surfacing.

Evergreen links. The link works until you turn it off. Useful for the recurring case. Every Sunday morning EPL pub-and-house rotation, every Champions League midweek. The same eight friends, the same routine, no need to redistribute the URL every match. Pair it with a fixed group thread; the rest takes care of itself.

The 80/20 default is to expire at kickoff. Set it once when you create the event and forget it. The link can’t outlive the party that way.

If you don’t want a hard expiry, the next-best move is a rotatable link, same URL, but the host can regenerate it on demand. Hejmo’s pattern is the same one Pitch Party uses. Generate a new link in one tap, the old URL stops working instantly, everyone who already RSVP’d keeps their access (Hejmo). That’s the right tool when something feels off but you don’t want to scrub the whole event.

When a guest forwards the link to a stranger

This will happen. Plan for it.

The good news. If you’ve gated the address behind RSVP, the stranger doesn’t have your door. They have a preview page. The blast radius is small.

What to actually do, in order:

Message the original guest. Friendly, not accusatory. “Hey, I saw a new RSVP from someone I don’t know, did you share the link?” Most of the time the answer is “Oh yeah, that’s my coworker, totally chill.” Sometimes the answer is “I forwarded it to a thread.”
Decide if the new person is okay. If yes, approve and move on. If no, deny the RSVP. They don’t get the address, they don’t get the reminder.
Rotate the link if it landed somewhere wide. A forwarded message in a 50-person thread is a different problem from a forwarded text to one friend. The rotate-link move kills the URL that’s loose without affecting anyone who’s already on your guest list.

The mistake hosts make here is apologizing to the original guest. You don’t need to. The friction you’re creating is small, the privacy you’re protecting is your home, and any reasonable friend will be apologetic for not checking with you first. Stay friendly, stay direct, fix the link, move on.

The post-script details, because they trip people up.

iMessage. Tap the share button on the event page, pick the contact or thread. iMessage will auto-render a link preview using whatever open-graph image is set. For a Pitch Party event that’s a clean match card. If you don’t want the preview at all, you can long-press the preview after pasting and convert it to a text link (iPhone Life). For most cases the preview is fine; it signals “this is a real event, not a phishing link.”

WhatsApp. Same share-sheet flow. WhatsApp will fetch the preview the first time the link is pasted in a thread, so give it 2-3 seconds before sending, otherwise the message goes through as a bare URL. Bare URLs in WhatsApp groups get ignored.

SMS (non-iMessage). No rich preview. The message is just text + URL. This is where the one-line “address unlocks after you RSVP” matters most. Without a preview, the recipient is deciding whether to tap a bare link in a text. Context wins the tap.

Instagram DM. Tap share, pick the user. Instagram’s preview will render. Don’t share into Stories; that’s a public surface even on a private account, because anyone who follows you can screenshot. DM only.

The cross-platform rule. Preview the message yourself before sending. Pull it up on your own phone. If the preview shows your address, you’ve pasted the wrong link. If the preview shows the match card, you’re good.

What goes wrong — the four common failures

The patterns we see, in rough order of frequency.

Pasting the address into the share message “just in case.” Defeats the entire gate. Don’t.
Sharing in too wide a channel. Big group thread that includes coworkers and exes. Pick the smaller subset and DM them, or build a thread of just the people you actually want over.
Not rotating the link after a plus-one chain. One friend forwards to two friends who forward to a Discord. Two days later you’re getting RSVPs from strangers and the link is loose. Rotate it. Re-share to your original group through a short follow-up note.
Forgetting to expire the link. The match ends, the link stays live, someone tries to come over the following Saturday because they screenshotted it. Set the expiry up front.

Sources

Frequently asked

Quick answers

Where should I send a private watch-party link — group chat, DM, or social?: Group thread for friend circles you text weekly. Individual DMs for anyone outside that circle. Avoid pasting it into a public social post or a Twitter/Instagram story — those audiences are too leaky. iMessage and WhatsApp are fine because the link only goes to the addresses you typed in.
What is RSVP-gated address reveal?: The street address only unlocks for a guest after they RSVP yes. The shareable link lands them on a page that shows match, time, what to bring, and a 'tap to RSVP' button. The address appears on the confirmation screen and in the day-of reminder. Pitch Party handles this automatically — the host doesn't have to manually send the address.
What if a guest asks to bring a plus-one?: Tell them to ask first, then add the plus-one through the RSVP system so the headcount stays accurate. Never just say 'sure forward the link' — a forwarded raw link is what burns address privacy. On Pitch Party, the original RSVP can add a +1 from inside the event so the plus-one's name is on the list before they walk up.
Should I use an expiring link or an evergreen one?: Expiring for matches more than 2 weeks out — set it to expire at kickoff so a screenshot from someone's camera roll doesn't haunt the next match. Evergreen is fine for the friend-circle weekly thread where everyone already has the link. The 80/20 default is: expire it at kickoff.
A guest sent the link to someone I don't know. What do I do?: First, don't panic — the RSVP gate hasn't fired yet, so the stranger only has the event preview, not your door. Second, message the original guest and ask who they shared it with. Third, if the stranger isn't acceptable, rotate the link from the event settings. The old URL stops working instantly; everyone who already RSVP'd keeps their reminder and their address access. New people have to come through the new link.

Pitch Party · the app

Spin up your watch party.
Pitch Party handles the room.

Pick a venue, set kickoff, share the link. Pitch Party runs the RSVPs and reminders so the room fills the way you planned for it.

Create your private event Find a watch party

How to share a private event link without leaking your address

Where to share the link (and where not to)

What to write in the share message