{"id":286846,"date":"2017-03-29T22:15:22","date_gmt":"2017-03-30T03:15:22","guid":{"rendered":"http:\/\/itblog.lcisd.net\/?p=286846"},"modified":"2017-03-29T22:15:22","modified_gmt":"2017-03-30T03:15:22","slug":"privacy-by-practice-not-just-by-policy-a-system-administrator-advocating-for-student-privacy","status":"publish","type":"post","link":"https:\/\/itblog.lcisd.net\/?p=286846","title":{"rendered":"Privacy By Practice, Not Just By Policy: A System Administrator Advocating for Student Privacy"},"content":{"rendered":"

March 28, 2017 | By Gennie Gebhart<\/a><\/p>\n

\"\"<\/p>\n

When Matt L. started to raise the alarm about educational technology in his school district, he knew it would ruffle some feathers.<\/h5>\n

As a system administrator (or sysadmin), Matt has had a front-row seat to the increasing use of technology in his rural, public school district. At first, the district only issued Chromebooks to students in guest \u201ckiosk\u201d mode for test-taking. Over time, though, each of the district\u2019s 10,000 students got individual access to school-issued devices, from iPads for younger students who cannot yet type to Chromebooks and G-Suite for Education logins for students as young as third grade.<\/p>\n

Matt and his sysadmin colleagues are at the center of deploying, configuring, and maintaining Google devices and software for the entire district. This gives Matt opportunities to identify privacy problems with ed tech implementation, and to propose solutions.<\/p>\n

\u201cAll our eggs in one basket\u201d<\/h3>\n

\u201cI don\u2019t want to say that Google or Chromebooks or any of this stuff is inherently bad,\u201d Matt said. \u201cGetting these tools into the hands of kids is hard to argue with. That\u2019s why I got into technology.\u201d<\/p>\n

As the district has continued to expand its technology use, however, Matt has started to have concerns about consolidating students\u2019 educational and personal information in one company. \u201cWe\u2019re putting all our eggs in one basket that we\u2019re not in control of,\u201d he said. \u201cWe don\u2019t know where this student data is going.\u201d<\/p>\n

On top of his privacy concerns<\/a>, Matt observed students learning about only certain softwares without broader awareness of their technology choices. Having grown up experimenting with Linux and other open softwares, he was dismayed to see students being steered toward only Google services and away from other options.<\/p>\n

\u201cThe beauty of technology is that it is so vast and deep, with so many choices. But we\u2019re funnelling people into one situation, which is not our job,\u201d he said. \u201cWe should be teaching concepts of computing, not specific software. We should be giving parents and kids a choice.\u201d<\/p>\n

Privacy by policy<\/h3>\n

After frustrating initial conversations with colleagues, it became clear to Matt that student privacy advocacy in his district could \u201cget touchy pretty quick.\u201d Even higher-up colleagues who might have been in a position to make district-level changes were hard to effectively approach.<\/p>\n

\u201cThey like Chrome because it\u2019s easy to use and they don\u2019t have to worry much about the mechanics behind it,\u201d he said. \u201cSo, I was constantly ridiculed when I brought up concerns about privacy.\u201d<\/p>\n

Colleagues also pointed out the cost-effectiveness of free Google services in response to Matt\u2019s concerns. But Matt was not convinced.<\/p>\n

\u201cNobody’s asking why it’s free<\/a>,” Matt said. \u201cI thought it was common sense that, generally, if you’re not paying for the app, you’re the product.\u201d<\/p>\n

After repeated requests to talk more about student privacy issues, Matt\u2019s boss and members of administration pointed him to the district\u2019s as well as Google\u2019s privacy policies. But this approach of ensuring \u201cprivacy by policy\u201d did not lessen Matt\u2019s concerns.<\/p>\n

\u201cWe have privacy policies for our website, and for our student academic records, but not so much for students\u2019 information in regards to what Google is collecting,\u201d he said. \u201cWe can\u2019t guarantee what Google is or is not doing with this information. It\u2019s all pretty vague, and it\u2019s not the kind of thing you want to be vague about.\u201d<\/p>\n

One of the biggest problems with such \u201cprivacy by policy\u201d is that it relies on all staff members being up-to-date on complex, sometimes vague policies, and having the time and resources to comply with them consistently. Matt observed that many in his district\u2014including his colleagues in system administration\u2014see student privacy as a long-term issue rather than an active, ongoing project.<\/p>\n

\u201cStuff like student privacy gets back-burnered,\u201d Matt said. \u201cIt\u2019s hard to look down the road at long-term projects when teachers\u2019 day-to-day is consuming all of our department\u2019s time and energy.\u201d<\/p>\n

Privacy by practice<\/h3>\n

Unsatisfied by the \u201cprivacy by policy\u201d that his district usually practices, Matt is investigating how he can implement \u201cprivacy by practice\u201d\u2014that is, prioritizing student privacy with active safeguards to augment and ensure existing policy, like technical settings<\/a> and opt-out options<\/a>.<\/p>\n

His first step has been to \u201ccrank down the lid\u201d on privacy settings<\/a> so that students use Google products as anonymously as possible by default, without associating their online profiles with identifying information. Ideally, technical controls like these will make it harder for teachers or third-party companies to collect student data, making privacy the default in students\u2019 and teachers\u2019 work.<\/p>\n

He is also advocating for an opt-out policy. EFF helped Matt locate relevant examples of opt-out policies from other school districts to get conversations started. However, this advocacy process has brought up more questions than answers. Coworkers were concerned that giving students the option to opt out of Chromebooks and\/or Google services will create more work for teachers and administrators, and it has been hard to build consensus around what classroom alternatives would be available when students choose to opt out.<\/p>\n

Continuing to advocate<\/h3>\n

Matt\u2019s conversations with colleagues have moved forward in fits and starts, and are constantly changing as the district\u2019s technology situation changes. For example, a system-wide update gave Matt an opportunity to propose concurrent changes in ed tech implementation. But, soon after, discussions about abandoning local storage and migrating completely to Google Drive ran counter to Matt\u2019s efforts to locally control student data and ensure their privacy.<\/p>\n

In the meantime, Matt is thinking about stepping up student digital literacy education with more student-staff interactions on the topic. He has also brought up his concerns at professional conferences to learn from sysadmin in different schools and districts. Matt remains persistent and committed to advocating for more secure, more private student systems.<\/p>\n

\u201cIt\u2019s a really hard problem, but we need to come up with an answer,\u201d Matt said.<\/p>\n","protected":false},"excerpt":{"rendered":"

March 28, 2017 | By Gennie Gebhart When Matt L. started to raise the alarm about educational technology in his school district, he knew it would ruffle some feathers. As a system administrator (or sysadmin), Matt has had a front-row<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[20,6],"tags":[],"class_list":["post-286846","post","type-post","status-publish","format-standard","hentry","category-cloud","category-security"],"_links":{"self":[{"href":"https:\/\/itblog.lcisd.net\/index.php?rest_route=\/wp\/v2\/posts\/286846","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/itblog.lcisd.net\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/itblog.lcisd.net\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/itblog.lcisd.net\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/itblog.lcisd.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=286846"}],"version-history":[{"count":3,"href":"https:\/\/itblog.lcisd.net\/index.php?rest_route=\/wp\/v2\/posts\/286846\/revisions"}],"predecessor-version":[{"id":286849,"href":"https:\/\/itblog.lcisd.net\/index.php?rest_route=\/wp\/v2\/posts\/286846\/revisions\/286849"}],"wp:attachment":[{"href":"https:\/\/itblog.lcisd.net\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=286846"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/itblog.lcisd.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=286846"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/itblog.lcisd.net\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=286846"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}