Consent in Connected TV Apps: Choices on the Big Screen
Connected TV apps sit in an awkward spot. They run on shared screens in living rooms, they lean heavily on advertising and viewing analytics, and their interfaces make detailed privacy choices hard to present. Many apps solve the difficulty by not presenting a choice at all, or by burying it three menus deep after the analytics have already started.
This guide covers what a workable TV consent flow looks like: when it appears, how granular it can realistically be on a remote control, how receipts should be stored for a household device, and how to handle the shared screen problem when several people watch under one profile.
Show the choice before measurement starts
The same rule that governs mobile applies on TV, only more so, because viewing data is unusually revealing. A viewing history can show health interests, political leanings, and household routines. No analytics, attribution, or ad personalisation SDK should initialise before the viewer answers. The free, ad supported tier argument does not change this. If the business model needs measurement, ask first and make the ad experience work for people who say no, with contextual ads instead of behavioural ones. Test on a fresh install and watch the network traffic before the choice is made.
Design for the remote, not a mouse
A TV consent screen has to work with five buttons. Long scrolling notices and dense category lists fail in practice, and a flow people cannot complete is not a real choice. Use a short first screen with accept and reject given equal weight, then a second screen for anyone who wants categories, written in plain words like viewing measurement and personalised ads. Keep focus order predictable, make the selected option visually obvious from across the room, and never let a timeout or a screensaver dismiss the prompt into an assumed yes.
Receipts for a shared device
Store the TV receipt the way you would any other: timestamp, notice version, categories chosen, and the app and SDK list versions in force. The complication is identity. The receipt belongs to the device or profile that answered, not to a named person, and your records should say so. When a new profile is created, ask again for that profile instead of inheriting the household choice silently. When the app updates in a way that changes data collection, surface the change on next launch rather than waiting for someone to find a settings menu.
Give viewers a way back in
Consent on TV fails most often after the first run, because changing your mind requires hunting through settings menus designed for other purposes. Put privacy choices in the main settings list with a clear label, show the current state when the screen opens, and apply a change immediately, including stopping SDKs that were running. If a viewer withdraws, that withdrawal should propagate to the same server side stores your web and mobile choices use, so a household is not opted in on one screen and opted out on another without knowing it.
Related reading
These earlier guides cover connected questions in more depth: Consent Audit Trails: Exporting Records a Regulator Can Actually Read, Consent Renewal Prompts: When to Re-Ask and When to Leave People Alone, and Consent for Embedded Checkout and Payment Iframes.
Frequently asked questions
Do TV apps need consent for viewing analytics?
In most privacy frameworks yes, because viewing analytics are not needed to play the video the viewer asked for. Analytics that measure what was watched, for how long, and on which profile are a separate purpose and need their own basis.
Can one household member consent for everyone?
Practically, the person holding the remote makes the choice for that profile. That is why per profile prompts and an easy settings path matter, so other viewers are not permanently bound by a choice they never saw.
What about kids profiles on TV apps?
Kids profiles should default to no behavioural advertising and no third party measurement beyond what safety and playback require. Do not carry an adult profile choice into a kids profile.
How often should a TV app re-ask?
Re-ask when processing changes materially or when a new profile is created. A fixed schedule alone is less useful than change driven prompts, which give viewers a real reason to look.