{ "batch": "151-worry-leaks-and-content-theft", "articles": [ { "id": "learn_r151_worry_leaks_and_content_theft_leak_drm_drmx5_triple_watermark", "category": "Safety", "title": "[Unverified - being checked] DRM-X 5.0 (Haihaisoft DRM platform): Vendor-advertised watermark features for leak deterrence", "summary": "[Unverified - being checked] DRM-X 5.0 advertises 'triple watermark protection' (random static, diagonal dynamic, and full-screen randomly changing watermarks) intended to deter redistribution and trace the source of leaked content.", "body": "DRM-X 5.0 advertises 'triple watermark protection' (random static, diagonal dynamic, and full-screen randomly changing watermarks) intended to deter redistribution and trace the source of leaked content.\n\nWhat Haihaisoft Limited actually says:\n\n“To address content leakage and AI watermark removal risks, DRM-X 5.0 provides triple watermark protection, including random static watermarks, diagonal dynamic watermarks, and full-screen randomly changing watermarks.”\n\nNote: Vendor self-description of its own product features; the anti-recording and traceability effectiveness is not independently verified by this source. Watermarks can display user-related information (username, email, phone, user ID) during playback.", "source_type": "official", "source_link": "https://www.drm-x.com/en/products/drm-x-5.0/features", "last_verified": "2026-09-07", "reliability": "STRONG PRACTICE", "source_tier": "A", "source_publisher": "Haihaisoft Limited", "evidence_quote": "To address content leakage and AI watermark removal risks, DRM-X 5.0 provides triple watermark protection, including random static watermarks, diagonal dynamic watermarks, and full-screen randomly changing watermarks.", "volatility": "medium", "from_batch": "151-worry-leaks-and-content-theft", "subject": "DRM-X 5.0 (Haihaisoft DRM platform)", "topic": "Vendor-advertised watermark features for leak deterrence", "applies_to_country": "*", "applies_to_scope": "Vendor capability claim; applies to content protected on the DRM-X 5.0 platform via the ZJGet secure browser", "tags": { "lane": "any", "stage": "any", "region": [ "any" ], "platform": "any", "topic": [ "unclassified" ], "explicitness": "any" }, "verification": { "status": "unverified", "label": "Unverified - being checked", "reasons": [ "legal_fetch_over_cap" ], "checked_utc": "20261021-123916Z" } }, { "id": "learn_r151_worry_leaks_and_content_theft_leak_drm_drmx5_smart_prevent_recording", "category": "Safety", "title": "[Unverified - being checked] DRM-X 5.0 (Haihaisoft DRM platform): Vendor-advertised screen-recording prevention and its stated limits", "summary": "[Unverified - being checked] DRM-X 5.0 claims its 'Smart Prevent Screen Recording' technology blocks unauthorized screen capture to reduce screen-recording piracy risk, while its own FAQ cautions that no solution can guarantee prevention in all environments.", "body": "DRM-X 5.0 claims its 'Smart Prevent Screen Recording' technology blocks unauthorized screen capture to reduce screen-recording piracy risk, while its own FAQ cautions that no solution can guarantee prevention in all environments.\n\nWhat Haihaisoft Limited actually says:\n\n“DRM-X 5.0 deeply integrates Haihaisoft’s Smart Prevent Screen Recording technology to block unauthorized screen capture and reduce screen recording piracy risks.”\n\nNote: Vendor's own FAQ caveat (verified on the drm-x.com homepage, same vendor): 'DRM-X includes smart anti-screen-recording features and watermarking to reduce piracy risk. No solution can guarantee prevention in all environments, but DRM-X significantly increases protection for high-value content.'", "source_type": "official", "source_link": "https://www.drm-x.com/en/products/drm-x-5.0/features", "last_verified": "2026-09-07", "reliability": "STRONG PRACTICE", "source_tier": "A", "source_publisher": "Haihaisoft Limited", "evidence_quote": "DRM-X 5.0 deeply integrates Haihaisoft’s Smart Prevent Screen Recording technology to block unauthorized screen capture and reduce screen recording piracy risks.", "volatility": "medium", "from_batch": "151-worry-leaks-and-content-theft", "subject": "DRM-X 5.0 (Haihaisoft DRM platform)", "topic": "Vendor-advertised screen-recording prevention and its stated limits", "applies_to_country": "*", "applies_to_scope": "Vendor capability claim for content played in the ZJGet secure browser (Windows, macOS, Android, iOS)", "tags": { "lane": "any", "stage": "any", "region": [ "any" ], "platform": "any", "topic": [ "unclassified" ], "explicitness": "any" }, "verification": { "status": "unverified", "label": "Unverified - being checked", "reasons": [ "legal_fetch_over_cap" ], "checked_utc": "20261021-123916Z" } }, { "id": "learn_r151_worry_leaks_and_content_theft_leak_watermark_unified_forensic", "category": "Safety", "title": "[Unverified - being checked] Unified Streaming (USP Unified Origin): Purpose of forensic watermarks in video delivery", "summary": "[Unverified - being checked] Unified Streaming states digital watermarks enforce contractual compliance, provide proof of misuse, and link back to the source of a leak.", "body": "Unified Streaming states digital watermarks enforce contractual compliance, provide proof of misuse, and link back to the source of a leak.\n\nWhat Unified Streaming actually says:\n\n“Digital watermarks are used to enforce contractual compliance between a content owner and the intended recipient. It provides proof of misuse and a link back to the source of a leakage. It is one of the most powerful means to protect media content.”\n\nNote: Also states: 'Forensic watermarking provides an efficient deterrent against pirated copies of content. It is the means by which a unique identifying code is inserted into a media asset.'", "source_type": "official", "source_link": "https://docs.unified-streaming.com/documentation/drm/watermarking.html", "last_verified": "2026-09-07", "reliability": "STRONG PRACTICE", "source_tier": "A", "source_publisher": "Unified Streaming", "evidence_quote": "Digital watermarks are used to enforce contractual compliance between a content owner and the intended recipient. It provides proof of misuse and a link back to the source of a leakage. It is one of the most powerful means to protect media content.", "volatility": "low", "from_batch": "151-worry-leaks-and-content-theft", "subject": "Unified Streaming (USP Unified Origin)", "topic": "Purpose of forensic watermarks in video delivery", "applies_to_country": "*", "applies_to_scope": "General industry statement in vendor documentation; includes Irdeto TraceMark and Nagra NexGuard integrations", "tags": { "lane": "any", "stage": "any", "region": [ "any" ], "platform": "any", "topic": [ "unclassified" ], "explicitness": "any" }, "verification": { "status": "unverified", "label": "Unverified - being checked", "reasons": [ "legal_fetch_over_cap" ], "checked_utc": "20261021-123916Z" } }, { "id": "learn_r151_worry_leaks_and_content_theft_leak_screenshot_android_flag_secure", "category": "Safety", "title": "[Unverified - being checked] Android / Google Play: Screenshot-protection reality: FLAG_SECURE window flag", "summary": "[Unverified - being checked] On Android, the FLAG_SECURE display flag signals that app UI should not appear in screenshots or on non-secure displays, and Google Play requires apps distributed on Play to respect it.", "body": "On Android, the FLAG_SECURE display flag signals that app UI should not appear in screenshots or on non-secure displays, and Google Play requires apps distributed on Play to respect it.\n\nWhat Google (Play Console Help) actually says:\n\n“It is a display flag declared in an app’s code to indicate that its UI contains sensitive data intended to be limited to a secure surface while using the app, signaling to other apps and services that the data should not appear in screenshots or be viewed on non-secure displays.”\n\nNote: Related verified quote (same page): 'For security and privacy purposes, all apps distributed on Google Play are required to respect FLAG_SECURE — which entails not facilitating or creating workarounds to bypass the flag settings in other apps.' Negative side effect noted by Google: apps that rely on sharing screenshots/recordings lose that capability on flagged pages.", "source_type": "official", "source_link": "https://support.google.com/googleplay/android-developer/answer/14638385?hl=en", "last_verified": "2026-09-07", "reliability": "VERIFIED RULE", "source_tier": "A", "source_publisher": "Google (Play Console Help)", "evidence_quote": "It is a display flag declared in an app’s code to indicate that its UI contains sensitive data intended to be limited to a secure surface while using the app, signaling to other apps and services that the data should not appear in screenshots or be viewed on non-secure displays.", "volatility": "low", "from_batch": "151-worry-leaks-and-content-theft", "subject": "Android / Google Play", "topic": "Screenshot-protection reality: FLAG_SECURE window flag", "applies_to_country": "*", "applies_to_scope": "OS-level control; applies only to the app's own windows", "tags": { "lane": "any", "stage": "any", "region": [ "any" ], "platform": "any", "topic": [ "unclassified" ], "explicitness": "any" }, "verification": { "status": "unverified", "label": "Unverified - being checked", "reasons": [ "legal_fetch_over_cap" ], "checked_utc": "20261021-123916Z" } }, { "id": "learn_r151_worry_leaks_and_content_theft_leak_screenshot_ios_detection_only", "category": "Safety", "title": "[Unverified - being checked] Screenshot-protection reality: iOS provides a notification, not a blocking API", "summary": "[Unverified - being checked] Apple's documented screenshot-control mechanism is a notification that posts when a person takes a screenshot on the device; Apple's documentation describes no API that blocks the capture itself.", "body": "Apple's documented screenshot-control mechanism is a notification that posts when a person takes a screenshot on the device; Apple's documentation describes no API that blocks the capture itself.\n\nWhat Apple actually says:\n\n“A notification that posts when a person takes a screenshot on the device.”\n\nNote: Apple's own page description contains only this notification API for screenshots; the page documents no API that prevents screenshots from being taken. 'Reality' for iOS is post-capture detection/alerts, unlike Android's OS-level FLAG_SECURE block.", "source_type": "official", "source_link": "https://developer.apple.com/documentation/uikit/uiapplication/userdidtakescreenshotnotification", "last_verified": "2026-09-07", "reliability": "VERIFIED RULE", "source_tier": "A", "source_publisher": "Apple", "evidence_quote": "A notification that posts when a person takes a screenshot on the device.", "volatility": "low", "from_batch": "151-worry-leaks-and-content-theft", "subject": "Apple iOS (UIKit)", "topic": "Screenshot-protection reality: iOS provides a notification, not a blocking API", "applies_to_country": "*", "applies_to_scope": "iOS 7.0+ per Apple; applies to all iOS apps", "tags": { "lane": "any", "stage": "any", "region": [ "any" ], "platform": "any", "topic": [ "unclassified" ], "explicitness": "any" }, "verification": { "status": "unverified", "label": "Unverified - being checked", "reasons": [ "legal_fetch_over_cap" ], "checked_utc": "20261021-123916Z" } }, { "id": "learn_r151_worry_leaks_and_content_theft_leak_dmca_dmcacom_pricing", "category": "Safety", "title": "[Unverified - being checked] Prices for DMCA takedown services and when costs rise", "summary": "[Unverified - being checked] DMCA.com prices its DIY takedown toolkit at $10.00 per month and its full-service managed takedown at $199.00 per takedown, as a one-time prepaid fee; additional costs can occur for ISPs/OSPs that do not follow conventional DMCA policy or are located outside the USA.", "body": "DMCA.com prices its DIY takedown toolkit at $10.00 per month and its full-service managed takedown at $199.00 per takedown, as a one-time prepaid fee; additional costs can occur for ISPs/OSPs that do not follow conventional DMCA policy or are located outside the USA.\n\nWhat DMCA.com (Digital Millennium Copyright Act Services Ltd) actually says:\n\n“The Do-it-Yourself DMCA Takedown pricing starts at $10.00 per month. Followed by our popular professional Takedown service, which cost $199.00 per Takedown. Pricing is a one time prepaid service fee.”\n\nNote: Page footer (same page): 'DMCA.com has been protecting online content since 2006 as the internet's original copyright protection service.' The $199 full-service option is described as: 'We do all the work for you.' FAQ last modified 2023-06-02; prices are current as of check date.", "source_type": "official", "source_link": "https://www.dmca.com/FAQ/How-much-does-a-DMCA-Takedown-cost", "last_verified": "2026-09-07", "reliability": "STRONG PRACTICE", "source_tier": "A", "source_publisher": "DMCA.com (Digital Millennium Copyright Act Services Ltd)", "evidence_quote": "The Do-it-Yourself DMCA Takedown pricing starts at $10.00 per month. Followed by our popular professional Takedown service, which cost $199.00 per Takedown. Pricing is a one time prepaid service fee.", "volatility": "high", "from_batch": "151-worry-leaks-and-content-theft", "subject": "DMCA.com (Digital Millennium Copyright Act Services Ltd)", "topic": "Prices for DMCA takedown services and when costs rise", "applies_to_country": "*", "applies_to_scope": "DMCA.com is a Canadian company (Victoria, BC / New York), not a law firm", "tags": { "lane": "any", "stage": "any", "region": [ "us-ny" ], "platform": "any", "topic": [ "unclassified" ], "explicitness": "any" }, "verification": { "status": "failed", "label": "Unverified - being checked", "reasons": [ "legal_fetch_over_cap", "deferred_state_uncorroborated:us-ny" ], "checked_utc": "20261021-123916Z" } }, { "id": "learn_r151_worry_leaks_and_content_theft_leak_dmca_dmcacom_surcharge", "category": "Safety", "title": "[Unverified - being checked] Conditions that raise DMCA takedown cost", "summary": "[Unverified - being checked] DMCA.com states the base takedown price is a one-time prepaid fee but additional costs may occur for ISPs/OSPs outside the USA or that do not follow conventional DMCA policy.", "body": "DMCA.com states the base takedown price is a one-time prepaid fee but additional costs may occur for ISPs/OSPs outside the USA or that do not follow conventional DMCA policy.\n\nWhat DMCA.com (Digital Millennium Copyright Act Services Ltd) actually says:\n\n“Pricing is a one time prepaid service fee. Additional takedown costs may occur for ISP's / OSP's that do not follow conventional DMCA Takedown policy or have implemented their own standard or copyright infringement claim process.”\n\nNote: Trigger list on the same FAQ includes the OSP/ISP being located outside the USA, the OSP/ISP ignoring the takedown notice or requesting documentation, and UGC platforms giving their user special consideration to remove content.", "source_type": "official", "source_link": "https://www.dmca.com/FAQ/How-much-does-a-DMCA-Takedown-cost", "last_verified": "2026-09-07", "reliability": "STRONG PRACTICE", "source_tier": "A", "source_publisher": "DMCA.com (Digital Millennium Copyright Act Services Ltd)", "evidence_quote": "Pricing is a one time prepaid service fee. Additional takedown costs may occur for ISP's / OSP's that do not follow conventional DMCA Takedown policy or have implemented their own standard or copyright infringement claim process.", "volatility": "high", "from_batch": "151-worry-leaks-and-content-theft", "subject": "DMCA.com (Digital Millennium Copyright Act Services Ltd)", "topic": "Conditions that raise DMCA takedown cost", "applies_to_country": "*", "applies_to_scope": "Fee caveat published by the service provider on its own FAQ; kept as a distinct record because surcharge conditions are ", "tags": { "lane": "any", "stage": "any", "region": [ "any" ], "platform": "any", "topic": [ "unclassified" ], "explicitness": "any" }, "verification": { "status": "unverified", "label": "Unverified - being checked", "reasons": [ "legal_fetch_over_cap" ], "checked_utc": "20261021-123916Z" } }, { "id": "learn_r151_worry_leaks_and_content_theft_leak_ncii_google_policy_ban", "category": "Safety", "title": "[Unverified - being checked] Google: NCII removal policy scope including deepfakes", "summary": "[Unverified - being checked] Google's NCII policy covers creation or distribution of intimate or sexually explicit imagery and videos, including AI-generated 'deepfakes', without consent, and NCII content is banned across all Google services.", "body": "Google's NCII policy covers creation or distribution of intimate or sexually explicit imagery and videos, including AI-generated 'deepfakes', without consent, and NCII content is banned across all Google services.\n\nWhat Google (Google Account Help) actually says:\n\n“Google’s policy defines non-consensual intimate imagery (NCII) abuse as the creation or distribution of intimate or sexually explicit imagery and videos (including fake, AI-generated or synthetic imagery, often known as “deepfakes”) without the consent of the individual(s) who appears in the content. NCII content is banned across all Google services.”\n\nNote: Same page states Google cannot remove content it does not host on a Google product or service.", "source_type": "official", "source_link": "https://support.google.com/accounts/answer/17045517?hl=en", "last_verified": "2026-09-07", "reliability": "VERIFIED RULE", "source_tier": "A", "source_publisher": "Google (Google Account Help)", "evidence_quote": "Google’s policy defines non-consensual intimate imagery (NCII) abuse as the creation or distribution of intimate or sexually explicit imagery and videos (including fake, AI-generated or synthetic imagery, often known as “deepfakes”) without the consent of the individual(s) who appears in the content. NCII content is banned across all Google services.", "volatility": "medium", "from_batch": "151-worry-leaks-and-content-theft", "subject": "Google", "topic": "NCII removal policy scope including deepfakes", "applies_to_country": "worldwide", "applies_to_scope": "Google services such as Search, Drive, Photos; YouTube requires a separate form; under-18 content goes through a Google ", "tags": { "lane": "any", "stage": "any", "region": [ "any" ], "platform": "any", "topic": [ "unclassified" ], "explicitness": "any" }, "verification": { "status": "unverified", "label": "Unverified - being checked", "reasons": [ "legal_fetch_over_cap" ], "checked_utc": "20261021-123916Z" } }, { "id": "learn_r151_worry_leaks_and_content_theft_leak_ncii_google_review_48h", "category": "Safety", "title": "[Unverified - being checked] Google: NCII removal request review timeframe", "summary": "[Unverified - being checked] Google states it aims to review a submitted NCII removal request within 48 hours and informs the requester by email; removal is not guaranteed for every report.", "body": "Google states it aims to review a submitted NCII removal request within 48 hours and informs the requester by email; removal is not guaranteed for every report.\n\nWhat Google (Google Account Help) actually says:\n\n“Once you submit your request, we aim to review it within 48 hours. When our review is complete, we’ll inform you via email.”\n\nNote: Google notes it cannot guarantee it will catch every copy, and that content owners are notified (without information about the reporter) and may appeal.", "source_type": "official", "source_link": "https://support.google.com/accounts/answer/17045517?hl=en", "last_verified": "2026-09-07", "reliability": "VERIFIED RULE", "source_tier": "A", "source_publisher": "Google (Google Account Help)", "evidence_quote": "Once you submit your request, we aim to review it within 48 hours. When our review is complete, we’ll inform you via email.", "volatility": "medium", "from_batch": "151-worry-leaks-and-content-theft", "subject": "Google", "topic": "NCII removal request review timeframe", "applies_to_country": "worldwide", "applies_to_scope": "Stated aim, not a legal guarantee", "tags": { "lane": "any", "stage": "any", "region": [ "any" ], "platform": "any", "topic": [ "unclassified" ], "explicitness": "any" }, "verification": { "status": "unverified", "label": "Unverified - being checked", "reasons": [ "legal_fetch_over_cap" ], "checked_utc": "20261021-123916Z" } }, { "id": "learn_r151_worry_leaks_and_content_theft_leak_ncii_google_search_commercial_exclusion", "category": "Safety", "title": "[Unverified - being checked] Eligibility requirement for NCII removal from Google Search results", "summary": "[Unverified - being checked] Google will only consider removing intimate images from Google Search if the requester is not currently being paid to commercialize the content online or elsewhere.", "body": "Google will only consider removing intimate images from Google Search if the requester is not currently being paid to commercialize the content online or elsewhere.\n\nWhat Google (Google Search Help) actually says:\n\n“You aren’t currently being paid to commercialize this content online or elsewhere.”\n\nNote: Other Google Search removal criteria (same page): the imagery shows the person nude, in a sexual act, or in an intimate state; and consent was not given and the imagery was made publicly available without consent. Non-qualifying requests may proceed under DMCA.", "source_type": "official", "source_link": "https://support.google.com/websearch/answer/13650142?hl=en", "last_verified": "2026-09-07", "reliability": "VERIFIED RULE", "source_tier": "A", "source_publisher": "Google (Google Search Help)", "evidence_quote": "You aren’t currently being paid to commercialize this content online or elsewhere.", "volatility": "medium", "from_batch": "151-worry-leaks-and-content-theft", "subject": "Google Search", "topic": "Eligibility requirement for NCII removal from Google Search results", "applies_to_country": "worldwide", "applies_to_scope": "Applies to Google Search removal requests", "tags": { "lane": "any", "stage": "any", "region": [ "any" ], "platform": "any", "topic": [ "unclassified" ], "explicitness": "any" }, "verification": { "status": "unverified", "label": "Unverified - being checked", "reasons": [ "legal_fetch_over_cap" ], "checked_utc": "20261021-123916Z" } }, { "id": "learn_r151_worry_leaks_and_content_theft_leak_ncii_youtube_take_it_down_form", "category": "Safety", "title": "[Unverified - being checked] Removal under the US TAKE IT DOWN Act via YouTube form", "summary": "[Unverified - being checked] YouTube offers users in the United States a review request under the TAKE IT DOWN Act via a dedicated form, in addition to its Community Guidelines and privacy reporting processes, and may subject legal removal requests to automated processing.", "body": "YouTube offers users in the United States a review request under the TAKE IT DOWN Act via a dedicated form, in addition to its Community Guidelines and privacy reporting processes, and may subject legal removal requests to automated processing.\n\nWhat Google (YouTube Help) actually says:\n\n“In addition to YouTube’s Community Guidelines and the privacy reporting process, users in the United States may request a review under the TAKE IT DOWN Act using this form.”\n\nNote: YouTube states requests are evaluated against its policies and TAKE IT DOWN Act requirements, and that 'the legal removal requests may be subject to automated processing.'", "source_type": "official", "source_link": "https://support.google.com/youtube/answer/17071740?hl=en", "last_verified": "2026-09-07", "reliability": "VERIFIED RULE", "source_tier": "A", "source_publisher": "Google (YouTube Help)", "evidence_quote": "In addition to YouTube’s Community Guidelines and the privacy reporting process, users in the United States may request a review under the TAKE IT DOWN Act using this form.", "volatility": "medium", "from_batch": "151-worry-leaks-and-content-theft", "subject": "YouTube", "topic": "Removal under the US TAKE IT DOWN Act via YouTube form", "applies_to_country": "US", "applies_to_scope": "Also available: Community Guidelines reporting and privacy complaint processes", "tags": { "lane": "any", "stage": "any", "region": [ "us" ], "platform": "any", "topic": [ "unclassified" ], "explicitness": "any" }, "verification": { "status": "unverified", "label": "Unverified - being checked", "reasons": [ "legal_fetch_over_cap" ], "checked_utc": "20261021-123916Z" } }, { "id": "learn_r151_worry_leaks_and_content_theft_leak_takeitdown_statute_48h", "category": "Safety", "title": "[Unverified - being checked] TAKE IT DOWN Act (S.146, Pub. L. 119-12): Statutory removal obligation on covered platforms", "summary": "[Unverified - being checked] The TAKE IT DOWN Act requires covered platforms (defined as public websites, online services, or applications that primarily provide a forum for user-generated content) to remove nonconsensual intimate visual depictions within 48 hours of notification, then make reasonable efforts to identify and remove known identical copies.", "body": "The TAKE IT DOWN Act requires covered platforms (defined as public websites, online services, or applications that primarily provide a forum for user-generated content) to remove nonconsensual intimate visual depictions within 48 hours of notification, then make reasonable efforts to identify and remove known identical copies.\n\nWhat Library of Congress (Congress.gov) actually says:\n\n“Covered platforms must remove such depictions within 48 hours of notification.”\n\nNote: Congress.gov bill summary states covered platforms 'must remove such depictions within 48 hours of notification.' The identical-copies clause is described in FTC's TIDA guidance (opened, same batch): 'TIDA requires covered platforms to make reasonable efforts to find and remove known identical copies of a reported photo or video.'", "source_type": "official", "source_link": "https://www.congress.gov/bill/119th-congress/senate-bill/146", "last_verified": "2026-09-07", "reliability": "VERIFIED RULE", "source_tier": "A", "source_publisher": "Library of Congress (Congress.gov)", "evidence_quote": "Covered platforms must remove such depictions within 48 hours of notification.", "volatility": "low", "from_batch": "151-worry-leaks-and-content-theft", "subject": "TAKE IT DOWN Act (S.146, Pub. L. 119-12)", "topic": "Statutory removal obligation on covered platforms", "applies_to_country": "US", "applies_to_scope": "Passed Congress April 28, 2025; signed into law May 19, 2025; notice-and-removal obligations effective May 19, 2026", "tags": { "lane": "any", "stage": "any", "region": [ "us" ], "platform": "any", "topic": [ "unclassified" ], "explicitness": "any" }, "verification": { "status": "unverified", "label": "Unverified - being checked", "reasons": [ "legal_fetch_over_cap" ], "checked_utc": "20261021-123916Z" } }, { "id": "learn_r151_worry_leaks_and_content_theft_leak_takeitdown_ftc_enforcement", "category": "Safety", "title": "[Unverified - being checked] FTC enforcement of the TAKE IT DOWN Act: Effective date and penalties for non-compliance", "summary": "[Unverified - being checked] The FTC enforces Section 3 of the TAKE IT DOWN Act effective May 19, 2026; covered platforms that violate the law may face civil penalties of $53,088 per violation.", "body": "The FTC enforces Section 3 of the TAKE IT DOWN Act effective May 19, 2026; covered platforms that violate the law may face civil penalties of $53,088 per violation.\n\nWhat U.S. Federal Trade Commission actually says:\n\n“TIDA requires covered platforms that receive a valid request to remove the content and known identical copies within 48 hours.”\n\nNote: Verified on the same FTC page: 'Platforms that violate the law may face FTC enforcement that could result in civil penalties of $53,088 per violation.' FTC also recommends hashing and sharing hashes with NCMEC's Take It Down (minors) and StopNCII.org (18+).", "source_type": "official", "source_link": "https://www.ftc.gov/business-guidance/resources/complying-take-it-down-act", "last_verified": "2026-09-07", "reliability": "VERIFIED RULE", "source_tier": "A", "source_publisher": "U.S. Federal Trade Commission", "evidence_quote": "TIDA requires covered platforms that receive a valid request to remove the content and known identical copies within 48 hours.", "volatility": "medium", "from_batch": "151-worry-leaks-and-content-theft", "subject": "FTC enforcement of the TAKE IT DOWN Act", "topic": "Effective date and penalties for non-compliance", "applies_to_country": "US", "applies_to_scope": "FTC compliance guidance for covered platforms (social media, messaging, image or video sharing, gaming)", "tags": { "lane": "any", "stage": "any", "region": [ "us" ], "platform": "any", "topic": [ "unclassified" ], "explicitness": "any" }, "verification": { "status": "unverified", "label": "Unverified - being checked", "reasons": [ "legal_fetch_over_cap" ], "checked_utc": "20261021-123916Z" } }, { "id": "learn_r151_worry_leaks_and_content_theft_leak_stopncii_tool_removal_rate", "category": "Safety", "title": "[Unverified - being checked] StopNCII.org (operated by the Revenge Porn Helpline / SWGfL): Free NCII hashing tool, self-reported removal statistics, and scope limitation", "summary": "[Unverified - being checked] StopNCII.org is a free tool that hashes intimate images on-device and shares only the hash with participating companies; its operator reports a removal rate over 90% and over 300,000 images removed, while noting the tool cannot remove images from the whole internet, only from participating platforms.", "body": "StopNCII.org is a free tool that hashes intimate images on-device and shares only the hash with participating companies; its operator reports a removal rate over 90% and over 300,000 images removed, while noting the tool cannot remove images from the whole internet, only from participating platforms.\n\nWhat StopNCII.org (Revenge Porn Helpline, part of SWGfL) actually says:\n\n“With an over 90% removal rate, RPH has successfully removed over 300,000 individual non-consensual intimate images from the internet.”\n\nNote: Statistics are self-reported by the operator on its homepage with no method, sample size, or date given; treat as operator-supplied figures. Verified on the how-it-works page (same batch record): 'Please note: StopNCII.org cannot remove images from the whole internet, only the participating platforms listed on our partners page.' The hash is also called a digital fingerprint; duplicate copies of the image all have the exact same hash.", "source_type": "official", "source_link": "https://stopncii.org/", "last_verified": "2026-09-07", "reliability": "STRONG PRACTICE", "source_tier": "A", "source_publisher": "StopNCII.org (Revenge Porn Helpline, part of SWGfL)", "evidence_quote": "With an over 90% removal rate, RPH has successfully removed over 300,000 individual non-consensual intimate images from the internet.", "volatility": "medium", "from_batch": "151-worry-leaks-and-content-theft", "subject": "StopNCII.org (operated by the Revenge Porn Helpline / SWGfL)", "topic": "Free NCII hashing tool, self-reported removal statistics, and scope limitation", "applies_to_country": "worldwide", "applies_to_scope": "Eligibility (per homepage): the requester is the person in the image; 18 or older at the time the image was taken; curre", "tags": { "lane": "any", "stage": "any", "region": [ "any" ], "platform": "any", "topic": [ "unclassified" ], "explicitness": "any" }, "verification": { "status": "unverified", "label": "Unverified - being checked", "reasons": [ "legal_fetch_over_cap" ], "checked_utc": "20261021-123916Z" } }, { "id": "learn_r151_worry_leaks_and_content_theft_leak_stopncii_microsoft_implementation", "category": "Safety", "title": "Microsoft / StopNCII.org partnership: What hashing-based NCII removal actually achieved at one partner", "summary": "Microsoft piloted the StopNCII hash database in Bing and took action on 268,899 images up to the end of August 2024.", "body": "Microsoft piloted the StopNCII hash database in Bing and took action on 268,899 images up to the end of August 2024.\n\nWhat Microsoft actually says:\n\n“We have been piloting use of the StopNCII database to prevent this content from being returned in image search results in Bing. We have taken action on 268,899 images up to the end of August.”\n\nNote: Verified on StopNCII's industry-partners page (opened, same batch): 'Microsoft uses validated StopNCII hashes in its Bing search engine and (as of May 2026) its hosted consumer services, including GroupMe, Teams Free, OneDrive, and Xbox.'", "source_type": "official", "source_link": "https://blogs.microsoft.com/on-the-issues/2024/09/05/an-update-on-our-approach-to-tackling-intimate-image-abuse/", "last_verified": "2026-09-07", "reliability": "STRONG PRACTICE", "source_tier": "A", "source_publisher": "Microsoft", "evidence_quote": "We have been piloting use of the StopNCII database to prevent this content from being returned in image search results in Bing. We have taken action on 268,899 images up to the end of August.", "volatility": "medium", "from_batch": "151-worry-leaks-and-content-theft", "subject": "Microsoft / StopNCII.org partnership", "topic": "What hashing-based NCII removal actually achieved at one partner", "applies_to_country": "worldwide", "applies_to_scope": "Figures from Microsoft's corporate blog dated Sep 5, 2024, by Chief Digital Safety Officer Courtney Gregoire", "tags": { "lane": "any", "stage": "any", "region": [ "any" ], "platform": "any", "topic": [ "unclassified" ], "explicitness": "any" } }, { "id": "learn_r151_worry_leaks_and_content_theft_leak_testimony_creators_takedown_limits", "category": "Safety", "title": "[Unverified - being checked] Counter-view: what takedowns do and do not achieve according to practitioner commentary", "summary": "[Unverified - being checked] A practitioner guide states that after paying for DMCA 'scrubbing' of an OnlyFans leak, creators typically still do not learn which subscriber's file leaked, and the same file can reappear under a new URL within days.", "body": "A practitioner guide states that after paying for DMCA 'scrubbing' of an OnlyFans leak, creators typically still do not learn which subscriber's file leaked, and the same file can reappear under a new URL within days.\n\nWhat CreatorSense (industry practitioner guide) actually says:\n\n“That’s why forum threads end the same way: pay for scrubbing, feel better for a week, still don’t know which account to deal with.”\n\nNote: Verified on the same page: 'Whack-a-mole. The same file reappears under a new URL within days.' and 'No subscriber identity. A successful takedown never answers “who paid for the file that started this?”' Also: 'Delisting works when the host or indexer cooperates.' Guide updated 11 Aug 2026; ~8 min read; labeled 'not legal advice.'", "source_type": "community", "source_link": "https://www.creatorsenseai.com/blog/dmca-takedown-onlyfans-leak.html", "last_verified": "2026-09-07", "reliability": "CREATOR STRATEGY", "source_tier": "C", "source_publisher": "CreatorSense (industry practitioner guide)", "evidence_quote": "That’s why forum threads end the same way: pay for scrubbing, feel better for a week, still don’t know which account to deal with.", "volatility": "medium", "from_batch": "151-worry-leaks-and-content-theft", "subject": "DMCA takedowns for OnlyFans leaks (practitioner testimony)", "topic": "Counter-view: what takedowns do and do not achieve according to practitioner commentary", "applies_to_country": "*", "applies_to_scope": "Practitioner commentary (CreatorSense blog) describing common forum-reported experiences; counter-view to claims that ta", "tags": { "lane": "any", "stage": "any", "region": [ "any" ], "platform": "any", "topic": [ "unclassified" ], "explicitness": "any" }, "verification": { "status": "unverified", "label": "Unverified - being checked", "reasons": [ "legal_fetch_over_cap" ], "checked_utc": "20261021-123916Z" } } ] }