The grandmother who stayed in Chicago already asked for the files. Someone wants to drop the keep into a family chat like a trailer. I host the table. I hear this on destination weekends in Spain. Sharing the podcast keep with people who were not in the room is a private-first job — not a feed, not a login myth, and not a reason to treat two guests as a show for an aunt who never sat down.
A table often hears “send it to everyone who missed the flight.” The pattern looks like this: two people talked for the couple, a private door exists, and Monday wants a broadcast. A link is not a feed. Nobody named here.
- Treat the keep as private first.
- Treat a link as a door, not a feed.
- Send it to named people, not a census of absentees.
- Remember guests sat for two chairs, not an audience.
- Name what you will not post.
- Let grandparents watch the door that exists — no login myth.
- Send the share line with the keep.
What lands after the night lives in what the couple keeps after a wedding podcast. Extra odds live in questions. Enquiry language lives on the privacy policy. This page is only the share: people who were not in the room.
The keep is private first
A wedding podcast is two chairs and two broadcast mics at the party. Guests sit, talk, leave voices on video. Entertainment now. A keep after. Not a Spotify show. Barcelona is the original market. Coverage is Spain. The public keep is professionally recorded video and audio — a private link and files. That door is the default. Sharing is a second job, not a public premiere.
A table often hears the tidy line: “We hired this so the people at home can watch the night.” That is a kiosk wish. This furniture hired a conversation for the couple. Home can wait for a yes. Home is not the reason two cousins sat down.
The pattern looks like this. Someone wants unique entertainment and a family broadcast from the same two mics. Then a guest who told a kitchen story finds that story in a group chat. Nobody named here needed a living-room premiere. They needed a private keep first, and a short list later.
Recommendation: write private as the share default. “Files for us. Then we choose who watches.” If the line says everyone who RSVP’d no, rewrite it.
A link is not a feed
A private link is a door. It is not a channel. It is not a QR album with a progress bar. It is not a Monday trailer you paste under a photo of the cake. If you treat the door like a feed, you will hunt subscribers the night never hired.
The pattern looks like this. A planner forwards “the guestbook link” into a forty-person family chat because grandma asked once. A table often hears a roast that needed a pause, now playing next to holiday memes. Nobody named here missed a setting. The paste did.
Optional YouTube lives on the keep page if you already know friends may watch. That upload is a choice. It is not the default door, and it is not this page’s job to sell a channel.
Recommendation: send the door to a name. Do not paste it under a group photo. If the sentence says “drop the album,” you have the wrong object.
Who the couple actually sends it to
The couple choose the list. Not the vendor WhatsApp. Not “anyone who could not fly.” A useful list is short and named: a parent, a grandmother who asked, a sibling who held the house. A census of absentees is a feed with extra guilt.
A table often hears “send it to the whole no-list, they paid for the flight they did not take.” Money is not consent. The pattern looks like this. Twenty people get a door. Two guests hear that their kitchen story is now a family screening. Nobody named here needed a roll call of empty chairs. They needed three names written before Monday.
I do not send files to a planner’s group as entertainment. I also do not make a groomsman the librarian of other people’s faces. The couple keep the door. They hand it to people they can name out loud.
Recommendation: write three names, or write none. If the line says the no-list, or the vendor chat, cut it.
Guests did not sit for an audience
Sitting down is a yes to talk for the couple. It is not a yes to a living-room premiere for cousins who skipped the flight. Identifiable faces and voices are personal data under European rules. A hire is not a blanket right to publish every uncle. We will not write a courtroom answer here, and we will not write “100% certified.”
The pattern looks like this. Two friends tell the train story because the card asked for a scene. They laugh. They leave. A week later an aunt who was not in Spain watches them like a show. A table often hears that laugh because two people were talking, not performing for a grid. Nobody named here signed up for an audience. They sat in two chairs.
Awkward takes belong to the couple. A sideways night has its own page. This page only says: the people who were not in the room are still an audience. That yes is separate. Controller language for enquiry data lives on the privacy page, not in a blog speech.
Recommendation: write the audience rule before anyone sits. “Talks are for us. A later watch needs a later yes.” If the line assumes sitting equals sharing, split it.
What not to post
Do not drop a guest roast on Stories. Do not put a crying take on Reels because the line was perfect. Do not paste the private door into a family group as if it were a highlight. Do not treat Instagram as a gallery of your guests. Setup films of the furniture are a different object.
The pattern looks like this. Someone watches a take the next week and laughs until they cry. Then they want the same clip on a grid because an aunt said a perfect line. A table often hears that line because the room felt small. Nobody named here needed a public encore. They needed the file to stay a file.
You can see table language on Instagram — setup films, not a named wedding. Named faces only with permission. A public uncle is not an accident you “just upload.”
Recommendation: decide the social rule before the day. Private keep unless everyone in the clip later says yes. If the line says “just a Story,” delete Story.
What grandparents can watch without a login myth
Grandparents can watch if the couple send the door that exists. We do not invent a portal, an app, an email login, or a one-tap product on this page. Formats, edits and timing are confirmed when you book. A living-room replay is the couple sharing a private keep. It is not a broadcast, and it is not a password wall we pretend to sell.
| Who is watching | Share job | Do not treat it as |
|---|---|---|
| The couple | Private link and files | A feed |
| A named parent or grandparent | Send the same door, on purpose | A login we invent |
| A family group chat | Usually no | A trailer paste |
| Stories / Reels / a grid | No, unless a later yes | The default gallery |
| Optional public upload | Only if you already chose it | The keep page’s default door |
The pattern looks like this. Someone asks for “a simple login so Grandma does not get confused.” Then they invent a product. A table often hears a grandmother who can open a link a child sent. Nobody named here needed a portal. They needed one named send, and a person in the room who can sit with her if the player is new.
Recommendation: write “we send the door to Grandma.” If the line says portal, password wall, or an app, throw it away.
Send the share line with the keep
The worst time to invent a broadcast is the Monday after, when someone is already forwarding a door into a chat. Add four share lines to the same note as date and venue.
- Private first. Files for the couple. Then a short list.
- A link is a door, not a feed. No group-chat trailer.
- Named people only. Guests sat for two chairs, not an audience.
- No default post. Grandparents watch the door that exists — no login myth.
We do not publish a share SLA. We confirm what fits. Extra odds stay on the questions page. The keep object stays on its own page.
Recommendation: the same four lines with the couple, then the planner. Send the date through Check availability.
What to do next
Name the keep as private first. Do not treat a link as a feed. Write three names or write none. If the date is close, message WhatsApp. When the date and the share line sit in one place, Check availability.
Frequently asked questions
Is the podcast keep public for family who were not there?
No. The keep is private first. A private link and files are the default door. Sharing is a second job, not a premiere.
Can we paste the private link into a family group chat?
Treat a link as a door, not a feed. Send it to a name. A group-chat paste is a broadcast. That is usually the wrong object.
Who should the couple send the keep to?
Named people the couple can say out loud — a parent, a grandmother who asked. Not a census of absentees. Not the vendor chat.
Did guests agree to an audience when they sat down?
No. Sitting is a yes to talk for the couple. An audience is a separate yes. They sat for two chairs. They did not sit for a living-room show.
What should we not post from the podcast table?
Do not drop a roast on Stories, a crying take on Reels, or the private door into a family group as a trailer. Setup films are not your guests’ faces.
How do grandparents watch without a login?
Send the door that exists. We do not invent a portal or an app here. A living-room replay is a named send, not a password wall.
What should we send with the keep?
Four lines plus the house: private first; a link is not a feed; named people only; no default post. We confirm what fits. We do not publish a share SLA.