Screenshot blocking: Difference between revisions
Added citation and removed ownership violation apologia. |
m wanted: cookies |
||
| (4 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{ToneWarning}}{{Incomplete|Issue 1=Makes specific claims without citations}} | {{ToneWarning}}{{Incomplete|Issue 1=Makes specific claims without citations}} | ||
'''Screenshot blocking''' prevents the owner of a computing device from capturing screenshots and screen recordings. Some operating systems such as Android OS and iOS let app makers block the device owners from capturing screenshots and screen recordings of certain content. This may be done to prevent copyrighted content from being copied, such as Netflix blocking screenshots of the app<ref name=netflix-vdocipher>{{Cite web |last=Sharma |first=Vishal |date=2026-01-14 |title=Netflix DRM: How & Why of Encrypted Video Security (2025)? |url=https://www.vdocipher.com/blog/2022/05/netflix-drm/ |access-date=2026-02-21 |website=vdocipher |archive-url=http://web.archive.org/web/20251015170902/https://www.vdocipher.com/blog/2022/05/netflix-drm/ |archive-date=15 Oct 2025}}</ref>. However, some instances of screenshot blocking may be seen as excessive and unnecessary in some cases, thus violating ownership of consumers by unreasonably limiting what they are allowed to do with their devices. | '''Screenshot blocking''' prevents the owner of a computing device from capturing screenshots and screen recordings. Some operating systems such as Android OS and iOS let app makers block the device owners from capturing screenshots and screen recordings of certain content. This may be done to prevent copyrighted content from being copied, such as Netflix blocking screenshots of the app<ref name="netflix-vdocipher">{{Cite web |last=Sharma |first=Vishal |date=2026-01-14 |title=Netflix DRM: How & Why of Encrypted Video Security (2025)? |url=https://www.vdocipher.com/blog/2022/05/netflix-drm/ |access-date=2026-02-21 |website=vdocipher |archive-url=http://web.archive.org/web/20251015170902/https://www.vdocipher.com/blog/2022/05/netflix-drm/ |archive-date=15 Oct 2025}}</ref>. However, some instances of screenshot blocking may be seen as excessive and unnecessary in some cases, thus violating ownership of consumers by unreasonably limiting what they are allowed to do with their devices. | ||
==How it works== | ==How it works== | ||
Blocking screenshots is typically an in-app technology, not something that automatically applies across all apps or devices. Here's how it works, depending on the platform: | Blocking screenshots is typically an in-app technology, not something that automatically applies across all apps or devices. Here's how it works, depending on the platform: | ||
On Android, apps can block screenshots using a flag called: WindowManager.LayoutParams.FLAG_SECURE. When this flag is set on an activity, it prevents the content from being captured in screenshots, screen recordings, and even in the app switcher (recent apps view). This is often used by apps like, banking apps, streaming services (e.g., Netflix), and secure messaging apps.<ref>[https://developer.android.com/reference/android/view/WindowManager.LayoutParams WindowManager.LayoutParams | API reference | Android Developers]</ref><ref name=netflix-vdocipher /> | On Android, apps can block screenshots using a flag called: WindowManager.LayoutParams.FLAG_SECURE. When this flag is set on an activity, it prevents the content from being captured in screenshots, screen recordings, and even in the app switcher (recent apps view). This is often used by apps like, banking apps, streaming services (e.g., Netflix), and secure messaging apps.<ref>[https://developer.android.com/reference/android/view/WindowManager.LayoutParams WindowManager.LayoutParams | API reference | Android Developers]</ref><ref name="netflix-vdocipher" /> | ||
On iOS, iOS does not give developers an official flag like FLAG_SECURE, but they use workarounds, like displaying sensitive content in a UIView with custom rendering, then hiding or blurring it when the app detects screenshot events or apps going into background or app switcher{{Citation needed}}. | On iOS, iOS does not give developers an official flag like FLAG_SECURE, but they use workarounds, like displaying sensitive content in a UIView with custom rendering, then hiding or blurring it when the app detects screenshot events or apps going into background or app switcher{{Citation needed}}. | ||
| Line 12: | Line 12: | ||
==Why it happens== | ==Why it happens== | ||
Companies tend to | Companies tend to cite the following reasons for blocking screenshots: | ||
'''Protecting sensitive information''' | '''Protecting sensitive information''' | ||
| Line 36: | Line 36: | ||
===Overuse=== | ===Overuse=== | ||
Some apps implement screenshot blocking in situations where it is unnecessary. For example, since 2018, Chrome has blocked screenshots while in | Some apps implement screenshot blocking in situations where it is unnecessary. For example, since 2018, Chrome has blocked screenshots while in Incognito mode. It is unclear what this restriction is meant to protect against, given that Incognito browsing already functions by not saving history or [[Web cookie|cookies]]. | ||
There are | There are legitimate reasons to take a screenshot in Incognito mode. Developers may need to capture how a website looks to first-time visitors, or users might want to save information temporarily without adding it to their browsing history. In these cases, blocking screenshots serves no meaningful security purpose and only prevents the device owner from using their phone’s features as intended. | ||
=== Ineffective === | |||
Screens can be photographed from an external device. The quality of the image is likely to be lower, but it generally does not prevent someone from being able to reach alphanumerical information such as banking details and text-based messages.<!-- (Recently moved from: "It's a local file) Not sure this is a convincing argument. Just because someone can do something through one means, it doesn't follow that another means should be allowed. There is a counterargument to be made that making something more difficult acts as a deterrent, meaning fewer people would do it and it is therefore successful on that level. --> | |||
==Incidents== | ==Incidents== | ||
| Line 44: | Line 47: | ||
Earlier in 2025, the German cellular provider ALDI TALK blocked screenshots throughout its entire app.{{CitationNeeded}} The app displays information such as how much high-speed data a subscriber has remaining. Blocking screenshots of such basic information seems unnecessary, and applying the restriction across the entire app because some “private” content might appear in certain sections is excessive.<!-- I just tested this on the ALDI TALK app, and I was able to take a screenshots on multiple pages. There wasn't a single instance in which I was blocked from making a screenshot. I use Android, so unless this a feature exclusive to iOS, this ought to be deleted. Even if this was once true, it no longer is. --> | Earlier in 2025, the German cellular provider ALDI TALK blocked screenshots throughout its entire app.{{CitationNeeded}} The app displays information such as how much high-speed data a subscriber has remaining. Blocking screenshots of such basic information seems unnecessary, and applying the restriction across the entire app because some “private” content might appear in certain sections is excessive.<!-- I just tested this on the ALDI TALK app, and I was able to take a screenshots on multiple pages. There wasn't a single instance in which I was blocked from making a screenshot. I use Android, so unless this a feature exclusive to iOS, this ought to be deleted. Even if this was once true, it no longer is. --> | ||
=== | ===WhatsApp=== | ||
The developers of [[WhatsApp]] have threatened with blocking screenshots inside chats with "advanced chat privacy" enabled: | The developers of [[WhatsApp]] have threatened with blocking screenshots inside chats with "advanced chat privacy" enabled: | ||
<blockquote> | <blockquote> | ||
The company has stated that this is the first iteration of the feature, with plans to introduce even more robust protections in future updates, potentially including measures to block screenshots<ref>[https://archive.today/2025.07.07-200053/https://cybersecuritynews.com/whatsapp-advanced-chat-privacy-feature/ WhatsApp’s New Advanced Chat Privacy Feature to Protect Sensitive Conversations]</ref>. | The company has stated that this is the first iteration of the feature, with plans to introduce even more robust protections in future updates, potentially including measures to block screenshots<ref>[https://archive.today/2025.07.07-200053/https://cybersecuritynews.com/whatsapp-advanced-chat-privacy-feature/ WhatsApp’s New Advanced Chat Privacy Feature to Protect Sensitive Conversations]</ref>. | ||
</blockquote> | </blockquote>WhatsApp blocked screenshots of profile pictures in 2024, citing it as a measure to protect privacy.<ref>{{Cite web |date=25 Feb 2026 |title=About profile photo screenshot blocking |url=https://faq.whatsapp.com/1799783917198636 |access-date=25 Feb 2026 |website=WhatsApp Help Center}}</ref> However, once a profile picture has been uploaded to WhatApp, it is no longer a private image. | ||
==It's a local file== | ==It's a local file== | ||
When you take a screenshot, the screenshot is stored locally inside the encrypted internal storage of your smartphone, protected | When you take a screenshot, the screenshot is stored locally inside the encrypted internal storage of your smartphone, protected by a user's lockscreen credentials. As a local file, it remains fully under the user's control.<!-- I question whether this is a convincing argument against screenshot blocking. If a screenshot is under a user's control, they could choose to disseminate the screenshot at anytime. When screenshot blocking is defended by citing the privacy of others, e.g., WhatsApp, a third-party gaining full control over the image is the basis of their argument. --> | ||
==External displays== | ==External displays== | ||