You can show the birthday guest's photo on your dining room TVs, with a countdown to the toast, using the same screen that already runs the daily playlist. Under Brazil's LGPD data protection law, the person who consents is the birthday guest — or a parent or legal guardian if it is a child — in writing or by another means that demonstrates their will, and only for that party. Without that consent, run the tribute without a photo: a generic birthday video, a countdown and the first name announced by the team deliver the same moment without exposing anyone.
Why birthdays are worth so much to a restaurant
A birthday is the booking every restaurant wants: a big table, a high check, and guests who have never been there and might come back on their own. Search for how to attract birthday parties and you will find a free dessert above X guests, Instagram photos and online booking. All valid — and all of it happens before or after the visit. What nobody covers is what happens during, in the dining room, the minute the cake leaves the kitchen.
That is where the screen comes in, and the effect is more direct than it looks. On the Café & Tech episode about steakhouses, the conversation was precisely about what the guest does when the tribute shows up:
"Whoever asked for the photo, what do you think they'll do when the singing starts? … the camera comes out … they'll film the screen in your room and then film the toast right after … and tag the restaurant, with everyone watching."
That is the commercial point of the tribute: it produces the content guests publish on their own, with your brand in the frame. No ad buys that. All the restaurant has to do is give the phone a reason to come up — without embarrassing the person being celebrated.
If you already use the screen for other things in the dining room, the day-to-day content logic is in digital menu boards for restaurants; this article is only about the birthday moment.
Three tribute formats for the screen
From the simplest to the most personal — and, not by chance, from the one that exposes nobody to the one that requires consent.
1. The generic birthday video on every screen
A single asset, no photo and no name, that plays on all screens when the team goes out to sing. You build it once and use it all year. As described in the episode: "you have a little birthday video on all the TVs together." It processes nobody's personal data, so it needs no consent — and it already turns a loose round of singing into a moment for the whole room.
2. The countdown synced with the kitchen
This is the most underrated format, and the one that most improves the operation. A 30- or 60-second asset with the countdown running on screen, triggered the moment the team leaves with the cake. On the restaurants episode, the mechanics were explained like this:
"you can set 60 seconds, one minute, which is the time the team needs to leave the kitchen and get there … or 30 seconds … the countdown runs, and by the time it hits zero the team is already at the table, ready to sing."
The side effect is operational: the whole room knows a toast is coming, the team arrives together, and the moment no longer depends on someone shouting "here we go". The countdown also exposes nobody — it is the part of the tribute you can standardize for every table, including the guest's first name when the table is fine with it.
Whoever triggers it does so from a phone, without leaving the table: running the playlist from your phone is covered in manage your indoor TV from your phone.
3. The birthday guest's photo turned into a video
The most personal format, and the only one that processes personal data. The photo becomes a short video asset with the birthday message and enters the playlist at the agreed moment — "the birthday video with the person's photo shows up on all the TVs." Generating that asset from a still, with music and motion, is what we covered in indoor TV with artificial intelligence, where the generated video runs from 20 seconds to a minute. The technical part is the easy part. The question that decides whether the asset can air is a different one: who consented to that photo?
Consent: who signs, what it says, how long it lasts
On the episode, the suggested path for the photo was the one most common in day-to-day operations: the family sends the image and signs a note.
"If the family is up for it, you can ask the family to give you a photo of the birthday guest, make the video, write happy birthday … and turn that photo into a video."
"they sign a little note saying that relative so-and-so provided the photo and is authorizing it, and then you publish."
This is where this article corrects the episode. That note proves where the photo came from, not that the person shown agreed to appear. If the birthday guest is an adult, a relative cannot consent on their behalf:
- the LGPD (Law 13.709/2018) defines personal data as "information related to an identified or identifiable natural person" (art. 5, I) — a photo and a name on screen are exactly that;
- art. 7, I allows processing "upon the provision of consent by the data subject";
- art. 8 says that consent is given "in writing or by another means that demonstrates the data subject's will", and § 2 is the one that matters most to a restaurant: "The burden of proof that consent was obtained in accordance with this Law lies with the controller." The restaurant is the one that has to prove it;
- art. 14, § 1 opens the exception for children: "The processing of children's personal data shall be carried out with specific and highlighted consent given by at least one parent or by the legal guardian." Here a relative does consent — as long as they are a parent or legal guardian.
Add to that art. 20 of the Brazilian Civil Code: unless authorized, the publication, exhibition or use of a person's image "may be prohibited at their request, without prejudice to any applicable damages … if it is intended for commercial purposes." A restaurant dining room is a commercial setting.
The three cases, side by side
| Situation | Who consents | What the law asks for |
|---|---|---|
| Adult birthday guest | The birthday guest (the data subject) | Consent from the data subject (art. 7, I), in writing or by another means that demonstrates their will (art. 8), for a determined purpose (art. 8, § 4). Proof is on the restaurant (art. 8, § 2). |
| Child birthday guest | A parent or legal guardian | Specific and highlighted consent (art. 14, § 1). Generic does not work: it has to state which photo, on which screens, on which day. |
| A past party photo used as social proof | Every recognizable person in the photo (or the guardian, if a child is in it) | It is a different purpose, so it needs its own consent (art. 8, § 4, which voids generic authorizations). Art. 20 of the Civil Code applies the same way to commercial use. |
Recording the yes without bureaucratizing the dining room
The law does not require signed paper — it requires the restaurant to be able to demonstrate the person's will. Three ways that survive a real service:
- In the booking form or the booking WhatsApp: a plain field — "Do you authorize showing your photo on the dining room TVs during the birthday toast? Yes / No" — answered by the birthday guest, not by whoever booked.
- On arrival: the host shows the finished asset to the birthday guest and asks. That is the scenario the episode itself points to, when the host remembers that "the birthday guest is the one who knows whether they'll like it, whether they're the reserved type."
- In writing, on a card or release: if you prefer to formalize it, art. 8, § 1 requires that, inside a contract, the authorization sit in a clause highlighted from the others.
Whatever the means, the wording has to state the concrete purpose. A sample sentence, for your lawyer to review:
"I authorize [restaurant name] to display the photo I have sent on the dining room TVs of the [address] location, only on [MM/DD/YYYY], during the birthday tribute. This authorization does not cover social media or any other date, and I may withdraw it at any time."
That covers the three things the LGPD asks for: a determined purpose (art. 8, § 4), a time frame, and the withdrawal at any time set out in art. 8, § 5.
The surprise without a photo
The most common objection from owners is an honest one: asking first ruins the surprise. Not always — and when it does, there is a way out.
In most birthday bookings the guest already knows there will be a celebration; what they do not know is the format of the tribute. In those cases, asking on arrival gives nothing away: "we do a tribute on the screen — are you up for appearing?" preserves the moment and settles the consent.
When the surprise is real — the whole table arranged it without the guest knowing — the tribute airs without a photo:
- a generic birthday video on every screen;
- a 30- or 60-second countdown;
- the first name only, announced by the team at the table — not displayed on screen as an identifier next to an image.
And if the guest likes the idea after the singing, the photo can go in with their yes, right there. The episode suggests exactly that as a variation: the birthday guest sending their own video or photo and scheduling it with the restaurant. Then the consent comes from the person it should have come from all along.
There is a practical reason on top of the legal one: some people hate being put on display. The host of the episode said as much about birthday singing in restaurants — "I'd rather keep it low-key." A tribute that embarrasses the guest does not become an Instagram story; it becomes a complaint at the table.
The birthday package on the screen
There is a sale restaurants lose in silence: almost nobody asks, mid-dinner, whether the house reserves an area for birthdays. From the episode:
"birthday booking policies — people often say, 'book a birthday, but what do I actually get?' … Hardly anyone is going to ask that while they're right in the middle of the experience."
Whoever is in your restaurant today celebrating someone else's birthday is exactly who might book their own party two months from now. The screen asset that solves it is simple and informative: the party size from which you reserve an area, what is included, whether cake is part of it, whether there is a dedicated server, how far in advance and through which channel to book. The numbers and conditions belong to each restaurant — this article suggests no price, no guest minimum and no freebie.
One variation the episode suggests is showing photos of past birthdays and company parties as social proof. It works, but it falls under the third row of the table above: every recognizable person in those photos must have consented to that use. If you do not have that on record, the safe alternative is to photograph the setup — the decorated table, the reserved area, the cake — with no identifiable people in frame.
If the idea is to reuse those assets on your own social channels, turning screen content into posts is covered in indoor TV video for social media — with the same caveat: a post is a different purpose and needs fresh consent.
After the party: pull it and delete it
This is the step almost every restaurant forgets, and the cheapest one to get right. Consent was given for that display, on that date. So, at closing:
- Pull the asset from the playlist. A birthday asset left running is guaranteed embarrassment the following week.
- Delete the file — the photo and the generated video, including from the WhatsApp thread it arrived in.
- Do not recycle it into a post. Reposting on the restaurant's Instagram is a new purpose: if you want it, ask again, stating where it will appear.
- Honor withdrawal. If the guest changes their mind, art. 8, § 5 guarantees they can take it back at any time, through a free and simple procedure.
One extra caution when a child is involved: publishing is one thing, boosting is another. Monetized or boosted content that habitually exploits the image of a child or adolescent carries specific obligations for platforms under the rules in force in Brazil since 2026 — showing the tribute on your own dining room TV is not that case, but turning it into recurring paid media featuring a child's image is ground to clear with your lawyer first.
Starting with the screen already in your dining room
None of this requires new hardware. The digital signage system runs on the smart TV already hanging in your dining room, and the tribute is just one more asset in the daily playlist. The minimum path:
- Build the two fixed assets: the generic birthday video and the countdown, in a 30- and a 60-second version. They last all year and depend on nobody's consent.
- Agree the trigger with the kitchen: who flags it, who fires it, how many seconds ahead. Without that, the countdown hits zero while the team is still at the door.
- Decide where the yes is recorded: booking form, WhatsApp or a card on arrival. Pick one and standardize it — the proof is on the restaurant.
- Keep the booking policy asset running on busy nights, so whoever is celebrating today books their own party tomorrow.
- Close the loop at the end of the night: asset out of the playlist, file deleted.
| Plan | Who it is for | Price |
|---|---|---|
| Start | One screen: the main dining room | see current pricing |
| Pro | Dining room, private party area, entrance and kids area | see current pricing |
| Extra display point | Each additional screen | see current pricing |
Prices change. Always check the current plan table on jmvindoor.com before signing up.
The trial is free for 30 days, with one display point and no credit card — enough time to build the fixed assets, test the countdown on two or three tables and fine-tune the trigger with the kitchen.
Put your restaurant's birthday moment on the screen
Start the free 30-day trial and build the countdown before the next weekend. This article covers one part of a 1h05 episode: watch the full Café & Tech episode on indoor TV for steakhouses and, as a second reference, the episode on indoor TV for restaurants, the source of the countdown format. Both are in Portuguese.
Questions about the product? Talk to us through the contact form or on WhatsApp at +55 (11) 4063-8923. For how we handle your data on this site, see our Privacy Policy.