# Legal responsibility **URL:** \ **Category:** FAQ\ **Tags:** illegal-content, storagenode\ **Created:** [September 3, 2019, 9:37pm UTC](https://forum.storj.io/t/legal-responsibility/1433 "2019-09-03T21:37:17Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![JanPhilB1](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/janphilb1/32/68_2.png) [@JanPhilB1](https://forum.storj.io/u/JanPhilB1)\ **Post date:** [September 3, 2019, 9:37pm UTC](https://forum.storj.io/t/legal-responsibility/1433/1 "2019-09-03T21:37:17Z")
So if illegal data is stored on my node who is responsible for that? ---
**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\ **Post date:** [September 3, 2019, 10:00pm UTC](https://forum.storj.io/t/legal-responsibility/1433/2 "2019-09-03T22:00:52Z")
Hello @JanPhilB1, Welcome the forum! The customer. You can’t decrypt the content even if you figure out, where is other encrypted pieces on the network and how they should be combined before decryption. We do not condone the use of illegal content on our platform, but the nature of the platform with its end-to-end encryption prevents us from having any control on what is stored or shared by users. We believe decentralized technologies will have a lasting, positive effect on society. However, such technologies can only flourish in the long-term if they work within and evolve with a society’s legal and ethical norms. ---
**Author:** ![xopok](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/xopok/32/66_2.png) [@xopok](https://forum.storj.io/u/xopok)\ **Post date:** [September 4, 2019, 8:08am UTC](https://forum.storj.io/t/legal-responsibility/1433/3 "2019-09-04T08:08:38Z")
I’ve found an interesting piece a few weeks ago. [https://www.researchgate.net/publication/331474925\_Frameup\_An\_incriminatory\_attack\_on\_Storj\_A\_peer\_to\_peer\_blockchain\_enabled\_distributed\_storage\_system](https://www.researchgate.net/publication/331474925_Frameup_An_incriminatory_attack_on_Storj_A_peer_to_peer_blockchain_enabled_distributed_storage_system) ---
**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\ **Post date:** [September 4, 2019, 8:16am UTC](https://forum.storj.io/t/legal-responsibility/1433/4 "2019-09-04T08:16:06Z")
This article describes an attack on deprecated v2, no more new customers there. I’d like to see the similar investigation for v3 ---
**Author:** ![super3](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/super3/32/133_2.png) [@super3](https://forum.storj.io/u/super3)\ **Post date:** [September 4, 2019, 2:12pm UTC](https://forum.storj.io/t/legal-responsibility/1433/5 "2019-09-04T14:12:51Z")
@xopok Thanks for posting that paper. Really cool that people are doing research in that area. As @Alexey says this attack is valid for v2, but not for v3. Also from our developer @Egon “Currently the storage node has signed piece hashes for the data. Which means it has proof that the request to store the data came from somewhere else. For storage node to clear itself it needs to provide the piece hash and order limit and the satellite certificate (this can be used to verify the signatures).” ---
**Author:** ![jocelyn](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/jocelyn/32/31_2.png) [@jocelyn](https://forum.storj.io/u/jocelyn)\ **Post date:** [September 4, 2019, 3:54pm UTC](https://forum.storj.io/t/legal-responsibility/1433/6 "2019-09-04T15:54:25Z")
@xopok Thanks for the question. It shows that you think about multiple aspects of a situation. this is a question we’ve talked about in a past Town Hall. You can jump to [https://youtu.be/S5coCag7vR4?t=1883](https://youtu.be/S5coCag7vR4?t=1883) to hear more. Between that and the answer from Alexey, I hope that answers your curiosity. Thx! ---
**Author:** ![jtolio](https://storj.bcdn.literatehosting.com/letter_avatar/jtolio/32/5_5575768a8748004e209b776fc1b2916d.png) [@jtolio](https://forum.storj.io/u/jtolio)\ **Post date:** [February 26, 2021, 9:26pm UTC](https://forum.storj.io/t/legal-responsibility/1433/8 "2021-02-26T21:26:08Z")
In case folks From The Future find this thread, here’s another recent conversation: > [@Can an attacker store potentially incriminating data unencrypted on a node?](https://forum.storj.io/t/can-an-attacker-store-potentially-incriminating-data-unencrypted-on-a-node/11972/27): > > Hey friends! So a couple of things on “FrameUp” and the potential impact of illegal data stored on the network, in general. The FrameUp paper was written analyzing Storj v2. Storj v2 had a very different situation around replication and encryption than v3. Most of the issues FrameUp discusses are not possible with v3 - all data on storage nodes is stored encrypted and then Reed Solomon encoded. I think this problem is unlikely to be a big deal (especially with the v3 changes) and I’m with @m… Thank you for putting up with my old thread necromancy.