# Externe inhoud, PII en hotlinking

**URL:** <https://meta.discourse.org/t/remote-content-pii-and-hotlinking/168646>\
**Category:** Product Support\
**Created:** [29 oktober 2020 om 15:37 UTC](https://meta.discourse.org/t/remote-content-pii-and-hotlinking/168646 "2020-10-29T15:37:48Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![yosignals](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/yosignals/32/198521_2.png) [@yosignals](https://meta.discourse.org/u/yosignals)\
**Post date:** [29 oktober 2020 om 15:37 UTC](https://meta.discourse.org/t/remote-content-pii-and-hotlinking/168646/1 "2020-10-29T15:37:48Z")

</div>

Hey all, I love the platform, I’m looking for some guidance around controlling remote content locations,

Such as I want to forbid untrusted resources from loading, in an example I could use a jpg this one " ![](https://global.discourse-cdn.com/meta/original/3X/b/8/b80b11203d97fe01c5597ca3be70406ea48f5709.gif) " isn’t actually a jpg but all viewers will surrender their IP address and less important, their user agent.

I’d like to only allow uploads of content that is to be rendered, with the exception of some domains such as YouTube or common online storage platforms

Is that at all with the current version of Discourse ? - I’ll be using the forum for internet forensics and it will be perfect for purpose if there is a way to remediate this PII leak on like this and in profile content locations

Thanks!

I used canary tokens to ‘fake’ the jpeg [http://canarytokens.com/](http://canarytokens.com/) and wrapped it in the markdown for an image

---

_[View the full topic](https://meta.discourse.org/t/remote-content-pii-and-hotlinking/168646)._
