@@ -89,3 +89,40 @@ the Jupyter Team is not aware either of who installs Jupyter.
89
89
many companies that provide Jupyter support; We cannot unfortunately give you
90
90
names out of fairness.
91
91
92
+ ## Data retention and Personal informations
93
+
94
+ This section is similar to the vendor assessment above but is more targeted at
95
+ institutions which are planning to use Jupyter. In particular you may have been
96
+ redirected here if you are from a k-12 institution planning to use Jupyter.
97
+
98
+ ### Jupyter Notebook, JupyterLab, JupyterHub and Similar
99
+
100
+ The Jupyter team does not provide Jupyter as a service, thus we usually are not
101
+ the right group to contact if you have questions on how your (or your users')
102
+ data and personal information are stored and used.
103
+
104
+ - If you use or plan on using a service provider for Jupyter; they are your
105
+ vendor, and can answer those questions.
106
+
107
+ - If you self-host or plan on self hosting Jupyter, then it is likely to your
108
+ IT team to decide and enforce policies as all the data is controlled by your
109
+ IT team.
110
+
111
+ - If each user deploy on their own machine, then it's up to how each user uses
112
+ Jupyter and the method they used to install Jupyter.
113
+
114
+ ### Jupyter.org/try
115
+
116
+ The usage of any instances of https://jupyter.org/try is meant only for evaluation of
117
+ Jupyter and not long term usage. Theses instances are ephemeral and do not
118
+ persist any data, or only store data in users' browsers which can be deleted by
119
+ clearing the browser's cache.
120
+
121
+
122
+ ### Forums and Chat
123
+
124
+ The Jupyter community self organised around multiple platforms, in particular
125
+ https://discourse.jupyter.org/ and https://jupyter.zulipchat.com/ . Having an
126
+ account on any of those platforms is neither required not encouraged to use the
127
+ Jupyter Software, and data collection on those platforms are governed by their
128
+ respective platforms.
0 commit comments