# Digital Online Safety

**URL:** https://meta.discourse.org/t/digital-online-safety/219425
**Category:** Community Building
**Created:** [February 25, 2022, 11:13pm UTC](https://meta.discourse.org/t/digital-online-safety/219425 "2022-02-25T23:13:57Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![sarahann](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sarahann/32/96703_2.png) [@sarahann](https://meta.discourse.org/u/sarahann)
#### Post date: [February 25, 2022, 11:13pm UTC](https://meta.discourse.org/t/digital-online-safety/219425/1 "2022-02-25T23:13:57Z")

</div>

Curious about Discourse’s take on Digital Online Safety.

As platform owners, and allowing User Generated Content I do feel that there is an obligation to keep the web safe. Especially when it comes down to removing UGC content by law.

For instance, one example of Digital Online Safety with UGC is [Australia’s abhorrent violent material law](https://www.ag.gov.au/crime/abhorrent-violent-material#:~:text=The%20Act%20requires%20content%2C%20internet,hosted%20on%20their%20services.) where content that is abhorrent, inappropriate etc. is required by law to be taken off a platforms.

So I was just curious if this is up to each individual instance of Discourse to implement Digital Online Safety efforts? It just seems to me something that would make the web a better place and a safer place. Just looking to have an open discussion about it.

_User Generated Content_: images, photos, user-provided biographical information, in-game creations, live-streamed broadcasts, audio, video, GIFs, applications, comments, text, and location-based information

---

<div class="post-metadata">

### Author: ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [February 26, 2022, 10:23am UTC](https://meta.discourse.org/t/digital-online-safety/219425/2 "2022-02-26T10:23:17Z")

</div>

Since Discourse is used around the world and laws are different everywhere, I think that all Discourse(-the-software) can do is make sure that all the underlying technical mechanisms are in place, like:

- making an admin contact email address available
- giving tools to moderators and administrators to moderate, hide, and remove content
- giving tools to users to flag inappropriate or unlawful content
- giving tools to moderators and administrators to ban users and block address ranges

(And Discourse does that very well)

---

<div class="post-metadata">

### Author: ![osioke](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/osioke/32/238946_2.png) [@osioke](https://meta.discourse.org/u/osioke)
#### Post date: [February 28, 2022, 11:54am UTC](https://meta.discourse.org/t/digital-online-safety/219425/3 "2022-02-28T11:54:02Z")

</div>

Richard’s response here pretty much covers it all, I can add a bit here which is more or less repeating Richard’s reply using different words.

Discourse can be used in compliant ways with respect to the laws available, but the software itself isn’t compliant or non-compliant. If you host Discourse for users covered by Australis’s law or for instance GDPR, you’ll need to do so in a compliant way.

And as Richard pointed out, we’ve spent quite a bit of time making sure we provide you with all the necessary tools to be able to do it easily (user cancellation, user anonymization, etc).

For more information on this, please see our [Security brief | Discourse - Civilized Discussion](https://www.discourse.org/security) for general information and also [Privacy policy | Discourse - Civilized Discussion](https://www.discourse.org/privacy) for specific details.

---

<div class="post-metadata">

### Author: ![sarahann](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sarahann/32/96703_2.png) [@sarahann](https://meta.discourse.org/u/sarahann)
#### Post date: [February 28, 2022, 8:00pm UTC](https://meta.discourse.org/t/digital-online-safety/219425/4 "2022-02-28T20:00:27Z")

</div>

Thanks @RGJ and @osioke for your replies! Looks like it’s really up to how everyone uses Discourse. Maybe you don’t have Australian users and don’t need to worry or maybe you don’t host in the EU and have to be GDPR compliant.

Discourse is truly great at flagging and providing the tools moderators need, I 100% agree. 🙂 You two have answered my original question, thank you!

But I do have a follow up regarding:

> [@RGJ](#):
>
> giving tools to moderators and administrators to moderate, hide, and remove content

As a admin or mod I can delete a post or reply but it shows in the thread as “1 hidden reply” to admins and mods still. I was curious because in the case of unlawful content, removing the content from the server is also expected after some analytics are taken (like how many people may have seen it, how long it was up etc.). Curious if there were ways in the UI to remove the hidden content entirely from the server? Or is a programmatic solution using Discourse’s API the way to approach this?

---

<div class="post-metadata">

### Author: ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [February 28, 2022, 8:42pm UTC](https://meta.discourse.org/t/digital-online-safety/219425/5 "2022-02-28T20:42:46Z")

</div>

> [@Introducing permanently delete post functionality](https://meta.discourse.org/t/introducing-permanently-delete-post-functionality/207109):
>
> When a post is deleted in Discourse, we perform a soft-delete. This means that post is still present in the database in case an administrator wants to recover it later. A soft-delete is not sufficient when the deleted post contains sensitive information and must be pruned from the database completely. For those situations, we are introducing the ability to permanently delete a post. To use this feature, enable the can permanently delete setting. However, please be aware of the risks i…
