Question 1

Does StopNCII work retroactively on Bluesky for content posted before the partnership?

Accepted Answer

Yes, partially. Hash registration scans existing content against the database. Posts matching a registered hash get flagged for removal in subsequent scan cycles. For immediate removal of pre-partnership posts, parallel filing through Bluesky's formal moderation channel is faster.

Question 2

What happens to Bluesky content on independent personal data servers?

Accepted Answer

Bluesky's decentralized architecture means content can live on independent PDS infrastructure. Removal from the main Bluesky app does not automatically propagate to independent servers. For content republished there, additional takedown notices to the PDS operator are required, which IntimaShield handles as part of the case.

Question 3

How long does Bluesky take to respond to authorized-agent NCII notices?

Accepted Answer

Bluesky transitioned in 2025 to responding to moderation reports directly within the app. Authorized-agent filings via the formal moderation channel typically process within 24-72 hours, faster than civilian in-app reports because the agent-filed format includes structured legal framing.

Question 4

Does F2F refund subscribers who paid for unauthorized content of me?

Accepted Answer

F2F's policy supports refunds for content confirmed as unauthorized, but the refund process is separate from the takedown process. Our priority is content removal and account enforcement. Refund coordination is something you can request directly from F2F support after the takedown lands.

Question 5

How does the StopNCII partnership work for F2F creator accounts using my old content?

Accepted Answer

Hash registration blocks any upload attempt of registered content, regardless of which account is uploading. If a fraudulent creator account tries to upload your hashed content, F2F's upload-layer scan flags it before the post goes live.

Question 6

What if my content is on F2F and also on leak sites?

Accepted Answer

Most retired creator content surfaces in both places simultaneously. IntimaShield handles F2F via the StopNCII + agent-filing chain, and handles leak sites via the full infrastructure escalation (Cloudflare abuse, hosting provider, registrar, payment processors). Both are part of the same case.

Question 7

Does the StopNCII partnership apply to all FetLife content or just photos?

Accepted Answer

StopNCII hash technology works on still images. Videos are not currently covered by the standard hash partnership. For video content on FetLife, the path is direct authorized-agent reporting to report@fetlife.com.

Question 8

What if my content was posted with consent originally but I withdraw consent now?

Accepted Answer

Consent withdrawal is recognized under FetLife's policies, but the path is different from non-consensual reporting from the start. Withdrawal requests require account-holder context, while non-consensual reports go through caretaking. IntimaShield's intake walks through which path fits your situation.

Question 9

How does FetLife handle takedown requests for accounts owned by ex-partners?

Accepted Answer

FetLife's caretaking team handles the moderation action regardless of the relationship between the reporter and the account holder. We do not contact the ex-partner or anyone else in your social context as part of the takedown. The action happens through FetLife's internal process.