Desktop browsers · Research guidance. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
Check what the browser permits
Chrome documents an Allow in incognito choice for individual extensions. Mozilla similarly lets users allow certain extensions in private windows, and Apple documents private-browsing extension choices in Safari. A private window therefore should not be described as universally free of all installed extension activity without inspecting the actual configuration.
Consider a reproducible comparison
If a player works in an ordinary window and fails privately, record the exact task and extension state in both contexts. A permitted extension can be one difference, but so can session data and other privacy defaults. Do not assume that the private result isolates a single cause merely because the browser window has a different appearance.
Change one relevant variable
Use the publisher’s documented controls for a trusted extension only when that comparison is appropriate. Keep the original state and restore an intentional access or privacy tool afterward. Avoid uninstalling every extension or weakening unrelated site protections simultaneously; that would make an improvement harder to interpret.
Describe the limited result
A useful report names the browser, window type, relevant extension permission and the action that changed. If the result remains uncertain, say so. A private-session comparison can guide diagnosis, but it does not independently establish a service outage, a universal browser-compatibility claim or the status of the viewing account.
Questions, answered
Can some extensions run in private windows?
Yes. The publishers document explicit permissions.
Does a different private-session result identify one cause automatically?
No. Record the actual differences and compare deliberately.