How to get leaked content taken down from SimpCity threads, and the files they link to, step by step.
SimpCity is a forum. Threads collect leaked content about a creator, but the files themselves usually live on separate file hosts. Removing a SimpCity leak properly means dealing with both: the thread, and every file host it links to.
Estimated time: 30 minutes
Find every SimpCity thread containing your content and copy the thread link (and post links where you can). Then open the posts and note every file-host link they point to: those need their own notices.
Include each infringing link on its own line, a link to your original profile (OnlyFans, Fansly, Patreon) as proof the work is yours, a statement that you believe in good faith the use isn't authorised, a statement under penalty of perjury that the notice is accurate and you're the owner or their authorised agent, and a signature. Filing through an agent keeps your legal name off the notice.
Use the site's designated copyright contact, listed on its DMCA or terms page. Keep a copy of what you sent and the date.
Look up who hosts the site. If it sits behind Cloudflare (a WHOIS lookup will show Cloudflare), file through Cloudflare's web abuse form, not email: Cloudflare doesn't remove content on sites it only proxies, but it passes your notice to the real host and tells you who that host is. Then send the same notice directly to the host's abuse team.
File a copyright removal request with Google for each link. Even while the page is still up, de-indexing stops it appearing when people search your name. See our guide to removing leaked content from Google.
Re-uploads under new links are common. Check back regularly and file again for anything new, or use a service that monitors and re-files for you.
SimpCity is a forum. It rarely stores the files itself: threads usually embed or link to files on hosts such as Bunkr, GoFile or Pixeldrain. Removing the thread alone leaves the files online, and removing the files alone leaves a thread full of dead links that can be refreshed.
The forum has changed domain before. Use the thread links as they appear today, and re-check them if the domain changes.
The thread link and the specific post links or post numbers containing your content (several threads can go in one notice), plus your original profile link and the standard DMCA statements. Then file separate notices with each file host the thread links to.
The file hosts are usually the faster lever: once the files are gone, the thread has nothing to show. Request Google de-indexing for the thread links as well, since forum threads rank for creator names.
Privly scans for your content by username, image matching and fingerprinting, so you don't have to search SimpCity yourself.
Notices go out from Privly, a registered DMCA designated agent with the US Copyright Office, so your legal name stays off them.
If SimpCity doesn't act, we escalate to the hosting provider and request Google de-indexing, and we check the links again until they're gone.
It does act on some notices, especially complete ones with exact links and proof of ownership. When it doesn't, escalating to the hosting provider and removing the links from Google are the next steps.
It varies. Some notices are actioned within days; others need escalation and take longer. Removing the links from Google search can happen even while you wait on the site.
A notice has to be signed by the owner or someone authorised to act for them. If you file through an authorised agent such as Privly, the agent signs and your legal name stays off the notice.
That's common on sites like SimpCity. Each new link needs its own notice. Ongoing monitoring catches re-uploads and re-files without you having to search again.