# How to make an image orphaned so that it gets removed?

**URL:** <https://meta.discourse.org/t/how-to-make-an-image-orphaned-so-that-it-gets-removed/79231>\
**Category:** Product Support\
**Created:** [January 29, 2018, 12:52am UTC](https://meta.discourse.org/t/how-to-make-an-image-orphaned-so-that-it-gets-removed/79231 "2018-01-29T00:52:45Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![WorldIsMine](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/worldismine/32/455660_2.png) [@WorldIsMine](https://meta.discourse.org/u/WorldIsMine)\
**Post date:** [February 21, 2019, 6:53am UTC](https://meta.discourse.org/t/how-to-make-an-image-orphaned-so-that-it-gets-removed/79231/13 "2019-02-21T06:53:46Z")

</div>

> [@sam](#):
>
> I object to the GDPR concern

I am in a situation where I can’t ignore it. On my instance, our users constantly exchange sensitive data via PM’s such as IDs and documents. They were under the impression that once deleted, they’re gone. I gave them that impression via our rules and terms, as I was mislead by the options within Discourse that state that deleted uploads are removed after X days. It turns out, they’re not. And now this all sits in our database, which will be a disaster if we ever get breached.

Would “hard nuking” as you’ve said would be something that could be implemented via a plugin? It’s not about nuking the post itself, just the attachments/uploads.

---

_[View the full topic](https://meta.discourse.org/t/how-to-make-an-image-orphaned-so-that-it-gets-removed/79231)._