|
| 1 | +# **IPFS Companion Privacy Policy** |
| 2 | + |
| 3 | +<em>First Posted: 2019-02-15<br/> |
| 4 | +Last Update: 2019-02-20</em> ([change history](https://github.com/ipfs-shipyard/ipfs-companion/commits/master/docs/privacy-policy.md)) |
| 5 | + |
| 6 | +The IPFS Companion browser extension is owned by Protocol Labs Inc. and created |
| 7 | +by the IPFS Project. We know you care about how your personal data is used and |
| 8 | +we take your privacy seriously. That is why, at the moment, we don’t track or |
| 9 | +collect any of your Personal Data, nor do we sell it to anyone else or use it |
| 10 | +for advertising. If that changes, we'll let you know by updating this policy. By |
| 11 | +using IPFS Companion, you are accepting and agreeing to this Privacy Policy. |
| 12 | + |
| 13 | +**What Does This Privacy Policy Cover?** |
| 14 | + |
| 15 | +This Privacy Policy explains that we don’t gather, track, nor permanently store |
| 16 | +any of your Personal Data. It also covers Additional Privacy Protocols related |
| 17 | +to the way the IPFS Companion extension allows people to add and retrieve data |
| 18 | +to and from the IPFS Network (which is a peer-to-peer network). This Privacy |
| 19 | +Policy doesn’t apply to projects run by other organizations outside IPFS and |
| 20 | +Protocol Labs, even if we promote the use of those projects or happen to |
| 21 | +contribute to them. |
| 22 | + |
| 23 | +**What Information Do We Collect?** |
| 24 | + |
| 25 | +None. We don’t collect your Personal Data, period. |
| 26 | + |
| 27 | +**Explicitly Shared Data Will Be Publicly Available over IPFS** |
| 28 | + |
| 29 | +We do not collect, rent, store or sell your Personal Data to anyone. However |
| 30 | +because IPFS Companion is a web extension that provides access to the real-time, |
| 31 | +peer-to-peer IPFS Network (which is a public platform for which anyone may join |
| 32 | +and participate) the data that you add or upload to the IPFS Network using IPFS |
| 33 | +Companion is then publicly available and accessible to everyone participating in |
| 34 | +IPFS Network. |
| 35 | + |
| 36 | +**Additional Privacy Protocols** |
| 37 | + |
| 38 | +If you add files to the IPFS Network using the IPFS Companion extension, they |
| 39 | +will be stored on your local IPFS Network node. Those files are also then cached |
| 40 | +by anyone who retrieves those files from the IPFS network and co-hosted on that |
| 41 | +user’s local IPFS Network node. Generally, cached files will eventually expire, |
| 42 | +but it’s possible for a user with whom you have shared access to such files (by |
| 43 | +sharing the relevant Content Identifier or CID) to pin that data, which means |
| 44 | +the cached files then will not expire and will remain stored on such user’s |
| 45 | +local IPFS Network node. |
| 46 | + |
| 47 | +All content shared with the IPFS Network is public by default. This means your |
| 48 | +files and data that you’ve added will be accessible to everyone who knows the |
| 49 | +CID or queries the data on the IPFS Network. If you want to share certain |
| 50 | +materials or data privately, you must encrypt such data before adding it to the |
| 51 | +IPFS Network. |
| 52 | + |
| 53 | +If you are using embedded JS IPFS node it will connect to bootstrap servers |
| 54 | +hosted by Protocol Labs and some of your Personal Information, such as public |
| 55 | +key and IP address of your IPFS node will be stored on the IPFS network publicly |
| 56 | +as well to facilitate p2p exchanges. |
| 57 | + |
| 58 | +If you are using “window.ipfs”, “Linkify IPFS Addresses” or “Catch Unhandled |
| 59 | +IPFS Protocols” experiments, websites will be able to detect you are running |
| 60 | +IPFS Companion. This behavior can be changed on Preferences screen by disabling |
| 61 | +mentioned experiments. |
| 62 | + |
| 63 | +**Will We Ever Change This Privacy Policy?** |
| 64 | + |
| 65 | +We’re constantly trying to improve IPFS Companion, so we may need to change this |
| 66 | +Privacy Policy sometimes. When we do, we will update the date at the top of this |
| 67 | +Privacy Policy and will also post an update |
| 68 | +[here](https://ipfs-shipyard.github.io/ipfs-companion/docs/privacy-policy). We |
| 69 | +encourage you to periodically review this Privacy Policy to stay informed, which |
| 70 | +is ultimately your responsibility. If you use IPFS Companion after any changes |
| 71 | +to the Privacy Policy have been posted, that means you agree to all of those |
| 72 | +changes. |
| 73 | + |
| 74 | +**What If I Have Questions About This Policy?** |
| 75 | + |
| 76 | +If you have any questions or concerns regarding our privacy policies, please |
| 77 | +send us a message at <[email protected]>. |
0 commit comments