# KYC data on IPFS

**URL:** <https://discuss.ipfs.tech/t/kyc-data-on-ipfs/552>\
**Category:** Help\
**Created:** [May 31, 2017, 12:13pm UTC](https://discuss.ipfs.tech/t/kyc-data-on-ipfs/552 "2017-05-31T12:13:53Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jl1](https://avatars.discourse-cdn.com/v4/letter/j/90db22/32.png) [@jl1](https://discuss.ipfs.tech/u/jl1)\
**Post date:** [May 31, 2017, 12:13pm UTC](https://discuss.ipfs.tech/t/kyc-data-on-ipfs/552/1 "2017-05-31T12:13:53Z")

</div>

Hello,  
can anyone provide expert advice on moving huge KYC data on IPFS?  
Thanks in advance

---

<div class="post-metadata">

**Author:** ![flyingzumwalt](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/flyingzumwalt/32/12_2.png) [@flyingzumwalt](https://discuss.ipfs.tech/u/flyingzumwalt)\
**Post date:** [May 31, 2017, 4:48pm UTC](https://discuss.ipfs.tech/t/kyc-data-on-ipfs/552/2 "2017-05-31T16:48:41Z")

</div>

@jl1 the first things to address:

1. What use cases are motivating you to put the data on IPFS?
2. Is this public, open-access data that can be written onto IPFS in un-encrypted form, or is it private/sensitive data that would have to be encrypted before writing it to IPFS?
3. Do you need to coordinate independent parties to pin the data on their nodes, or will you primarily pin the data on machines that you run?

---

<div class="post-metadata">

**Author:** ![cybertriton](https://avatars.discourse-cdn.com/v4/letter/c/c2a13f/32.png) [@cybertriton](https://discuss.ipfs.tech/u/cybertriton)\
**Post date:** [December 13, 2017, 7:25am UTC](https://discuss.ipfs.tech/t/kyc-data-on-ipfs/552/3 "2017-12-13T07:25:46Z")

</div>

Good questions and good answer.