Below is the letter from Parent Coalition for Student Privacy, Parents Across America, Network for Public Education, FairTest and many state and local parent groups to the Education Commissioners in the PARCC and SBAC states, asking if they use machine scoring of their Common Core exams. Please send your own letter to your State Education Chief if you are in one of these states. More information about the lack of evidence for machine scoring is in this issue brief here and the Washington Post Answer Sheet here.
UPDATE: In response to our (or reporter) queries, PARCC finally posted their study from March 2014 on automated scoring here. The SBAC automated scoring study is here. Both are problematic in different ways. Our analysis featuring Les Perelman’s comments was published in the WaPost AnswerSheet (see above).
Subsequently the CO Commissioner Rich Crandall responded to a parent activist, Cheri Kiesecker, that the state would be using computer scoring on 2/3 of the PARCC writing samples this year — as the standard PARCC/Pearson contract prescribes. On May 19, the Jack Smith, interim Commissioner of the Maryland Dept of Education responded that they too would be using machine scoring for 2/3 on PARCC written responses. Check out Les Perelman’s response to his claims here.
Rhode Island Commissioner Ken Wagner mentioned this issue at a board meeting, and confirmed they would be using machine scoring for most of the state’s PARCC written responses, while falsely saying that this was standard practice for SAT and GRE exams as well — although each of these exams is scored at least once and sometimes twice by human beings. (see video here).
Angela Chamness, Illinois Director of Assessments, ambiguously responded to a parent’s specific queries about what percent of the writing samples were scored by machine this way: “Like the majority of PARCC states, Illinois PARCC writing assessments are evaluated using automated and non-automated scoring approaches.” We can only surmise that Illinois is using the standard PARCC method of scoring 2/3 of the exams by machine, as in Rhode Island and Colorado, though she refused to make that clear.
After six weeks, none of these states have responded to our letter or other parent queries as far as I know: CA, CT, DE, DC, HI, ID, LA, MI, MT, NH, NJ, NM, ND, SD, VT, WA, WV.
If you are a parent from one of these states: please continue to send in your questions, especially #1-#3 below. The email addresses of your State Commissioners are posted here. And please let us know if you get a response by emailing us at [email protected]
thanks Leonie
April 5, 2016
To the Education Commissioners in the PARCC and SBAC states:
As parents and advocates, we have many outstanding concerns about the administration and scoring of the PARCC and SBAC Common Core exams this spring. There are several unresolved questions the answers to which have not been publicly revealed. The original PARCC contract called for two thirds of the students to have their ELA exams, including written responses, entirely scored by computers this spring, with only 10 percent of them re-checked by humans.
Similarly, according to the SBAC contract, 100 percent of students’ written responses would be scored by computers, with only half re-checked by a human being.
This is despite the fact that many experts have cited the inability of computers to assess the creativity and critical thought that the Common Core standards were supposed to demand and these exams to assess, no less distinguish nonsense from coherent narrative and reasoning. In each case, however, states had the option of having the exams entirely hand-scored for an additional charge.
So we demand that you answer the following questions:
What percentage of the ELA exams in our state are being scored by machines this year, and how many of these exams will then be re-scored by a human being?
What happens if the machine score varies significantly from the score given by the human being?
Will parents have the opportunity to learn whether their children’s ELA exam was scored by a human being or a machine?
Will you provide the “proof of concept” or efficacy studies promised months ago by Pearson in the case of PARCC, and AIR in the case of SBAC, and cited in the contracts as attesting to the validity and reliability of the machine-scoring method being used?
Will you provide any independent research that provides evidence of the reliability of this method, and preferably studies published in peer-reviewed journals?
We look forward to your prompt reply,
Leonie Haimson and Rachael Stickland, Co-Chairs, Parent Coalition for Student Privacy
Julie Woestehoff, Executive Director, Parents Across America and Wyoming parent advocate
Carol Burris, Executive Director, Network for Public Education
Monty Neill, Executive Director, FairTest
Save Our Schools New Jersey
Parents Across Rhode Island
Lee P. Barrios, M.Ed., NBCT, Louisiana Friends of Public Education
Cheri Kiesecker, CO parent, privacy advocate and blogger, Missouri Education Watchdog
Cassie Creswell, More Than A Score, Chicago IL
Dawn Collins, board member, East Baton Rouge (LA) school board
Stephanie Zimmerman, Idahoans For Local Education
Wendy Katten, Raise Your Hand for Illinois Public Education
Michelle Fine, Lynn Fedele, C. McGoey , R. Tuma & E.Halberstadt , Montclair Cares About Schools [NJ]
Arthur Freitas and Kayla Kirkpatrick, M.Ed., Colorado parents
Sheila Resseger, retired teacher from the RI School for the Deaf
On Tuesday, March 22, 2016, Parent Coalition for Student Privacy co-chair Rachael Stickland was invited to testify before the U.S. House Education & the Workforce Committee at a hearing entitled “Strengthening Education Research and Privacy Protections to Better Serve Students.”
The Committee’s media advisory can be viewed here along with the press release here. Rachael’s full testimony can be found here (and below).
Webcast of the hearing can be viewed here:
For articles about the hearing, please visit the following:
Testimony of Rachael Stickland, Co-Founder, Co-Chair
Parent Coalition for Student Privacy
Before the United States House of Representatives
House Committee on Education and the Workforce
Hearing on Strengthening Education Research and Privacy Protections to Better Serve Students
March 22, 2016
Good morning Chairman Kline, Ranking Member Scott and distinguished members of the Committee. I would like to thank you for the opportunity to testify today on behalf of parents concerned about strengthening privacy protections to better serve students.
My name is Rachael Stickland. I am a parent of two public school children in Colorado, and I am co-founder and co-chair of the Parent Coalition for Student Privacy which represents a wide coalition of parents from across the nation, from Florida to Washington, California to New York, including Democrats, Republicans and Independents, public school parents and homeschoolers, professionals and stay-at-home mothers. We receive no funding from special interests, and are united in our effort to protect all children and their privacy. We came together in July 2014 after working together as individuals and groups to defeat the widely criticized inBloom project.[1]
The controversy surrounding this corporation that was designed to collect the personal information from students in nine states and districts sparked a new awareness among parents nationwide about how widely their children’s personal data was already being disclosed to third parties beyond the schoolhouse doors, and how few protections existed against its misuse. Though inBloom is now gone, parents continue to seek answers to exactly what information pertaining to their children is being collected, who has access to the information and for what purpose, and when that information will be destroyed.
I would like to focus my testimony today on the need to strengthen federal educational law to meet the challenges of our modern educational ecosystem and to address the current threats to student privacy. Specifically, I will place an emphasis on personal student information collected by schools and school districts that are then disclosed to state education departments and maintained in Statewide Longitudinal Data Systems or SLDS.
Currently, schools collect much more information on students than most parents realize. While some was required by No Child Left Behind and individual state mandates, much of the data now collected appears to transcend legal requirements. Beyond standard transcript-type data like student names, addresses, courses taken, grades earned and days absent, schools also collect hundreds of pieces of information like disabilities and interventions, medical information from 504 plans, disciplinary incident reports, scores on standardized exams, school readiness scores and recommendations for grade retention. Additionally, schools or commercial vendors used by schools collect highly personal information from students as they use online education tools such as Google Apps for Education or Khan Academy.
Once this information is collected at the local level, much of it is pushed up to the state to be maintained in the state unit record system called the SLDS or the P-20W (preschool through workforce). These unit record systems have been funded partly through federal grants awarded in five rounds of funding from 2005-2012. Forty seven of fifty states as well as the District of Columbia, Puerto Rico, and the Virgin Islands have received at least one SLDS grant.[2] These systems are intended to match students and teachers for the purpose of teacher evaluation, and to promote interoperability across multiple state agencies, as well as across state lines via multi-state consortia.
Rather than simply collecting standard administrative data, these SLDS systems have the capability to maintain upwards of 400 data elements on each individual child. According to the Colorado State Department of Education, our SLDS project is designed to link information from the education department to five other state agencies, including the Colorado Department of Higher Education (CDHE), Colorado Department of Labor and Employment (CDLE), Colorado Department of Corrections (CDOC), Colorado Department of Public Safety (CDPS) and the Colorado Department of Human Services (CDHS). [3] The individually identifiable life-information that is so neatly organized in these systems effectively become life-long dossiers and, if or when compromised, could give away the entire life history of every student in a state.
Interagency linkages like Colorado’s SLDS and even interstate linkages [4] would not have been permissible prior to the unilateral regulatory changes to the federal student privacy law known as FERPA by the Department of Education in 2011. [5] The parents we represent strongly urge Congress to strengthen FERPA and restore the robust protections it originally contained that prohibited the expansion of the SLDS program.
SLDS’s purported purpose is to help states, districts, schools, educators, and other stakeholders make data-informed decisions to improve student learning and outcomes; as well as to facilitate research to increase student achievement and close achievement gaps. Parents don’t disagree with the premise that data can and should be used for purposes to help advance their children’s education. However, parents are concerned about SLDS because of the lack of compelling governmental interest which would justify this level of tracking that serves as an open invitation to mission creep. The availability of a dataset as rich as SLDS quickly turns it into the go-to data mart for authorized or unauthorized use by other institutions, organizations, and state agencies.
For example, earlier this year a California organization filed a lawsuit alleging that the state is failing to ensure districts provide services to all children who need them. The federal judge ruled in favor of the plaintiff and ordered the release of records for 10 million California students dating back to 2008 maintained in the state SLDS known as CALPADS.[6] Highly sensitive information on every child in the state’s education system were to be made available to the plaintiff’s legal team including student “names, addresses, disciplinary records, grades, test scores, and even details such as pregnancy, addiction and criminal history.”[7] Since the initial ruling in February, thousands of parents including the California PTA vehemently protested this unprecedented release. Because of the backlash, the judge has since modified her order allowing the plaintiff’s legal team to access and query the CALPADS data system rather than receive a full copy of the system. It’s worth noting that this disclosure of student information is authorized under current federal law, and as a result of the controversy the judge has since suggested modernizing FERPA.[8]
Another example of the unintended yet currently allowable use of SLDS was the attempt by the New York State Education Department, without public input or comment, to declare that all data in the SLDS should be placed into the state archives for a hundred years or more with no clear restrictions on access. After parent advocates discovered this decision in an obscure memo and protested, the state is now reconsidering this decision, but such a reckless policy without strong citizen oversight should never be allowed.[9] Should children of uniformed parents be any less protected?
Examples of authorized uses of SLDSs such as the California and New York cases are threat enough in their own right, but the high probability of breach or abuse should give advocates of maximal data collection in SLDS considerable pause. There are currently no specific security protections required for the collection and storage of this data unlike those required in HIPPA, for example, even though education records maintained by the SLDS often contain equally sensitive health information.
As Congress weighs competing interests in the student privacy debate, parents in our coalition urge you to always first think of the individual child. Allowing or incentivizing the government to track autonomous individuals through most of their lives in the name of research has speculative benefits at best and can instead lead to profiling, stereotyping and discrimination that can hinder a child’s potential for growth and success. We agree with both the testimony provided by National PTA[10] and Microsoft[11] to the House Subcommittee on Early Childhood, Elementary and Secondary Education in February 2015 that an individual owns his or her own data. Parents believe this to mean the right to decide with whom it will be shared and under what conditions.
Recommendations
Should Congress continue supporting the development and expansion of SLDS through federal grants, and as you contemplate student privacy as a legislative matter, please consider our coalition’s recommendations for the SLDS program as well as the use of personal student information by schools and districts:
Increased transparency: At minimum, SLDS unit record systems must be subject to the Privacy Act of 1974’s code of fair information practices that governs the collection, maintenance, use, and dissemination of information about individuals that is maintained in systems of records by federal agencies.[12] Optimally, parents must be told what student information is collected and by whom, how it is to be used and when it is to be destroyed, and to be notified in advance of any disclosure of personal student information to any persons, companies or organizations outside of the school or district.
In addition to increased transparency, parents also advocate for state Institutional Review Boards or IRBs to vet all uses of personal data, to question whether de-identified, anonymized or aggregated data could not be used in its stead, and to ensure that there are strict security standards and requirements for data destruction. We also urge that citizen oversight of the SLDS be required.
There should be no commercial uses of personal student information; or use for any marketing purposes should be banned.
Security protections: At minimum, there must be encryption of ALL personal data at motion and at rest, required training for all individuals with access to personal student data, audit logs, and security audits by an independent auditor.
Increased parent/student rights: Re-disclosures by vendors or any other third parties to additional individuals, sub-contractors, or organizations should be prohibited without parental notification and consent. Parents must be allowed to see any data collected directly from their child by a school or a vendor given access through the school, delete the data if it is in error or is nonessential to the child’s transcript, and opt out of further collection, unless that data is part of their child’s educational records at school. Any data-mining for purpose of creating student profiles, even for educational purposes, must be done with full parental knowledge. Parental consent must be required for disclosure for highly sensitive information such as their child’s disabilities, health and disciplinary information. We also urge that HIPPA be used as a model which requires individual notice and consent before personal health information can be used in research, with few exceptions.
Enforcement: Any federal student privacy law should specify fines if the school, district or third party violates the law, their contracts and/or privacy policies; with parents able to seek redress on behalf of their children as well.
Thank you again for the opportunity to participate in this hearing and for your consideration of my testimony.
[1]See Benjamin Herold, inBloom to shut down amid growing privacy concerns, Education Week, Apr. 21, 2014 http://blogs.edweek.org/edweek/DigitalEducation/2014/04/inbloom_to_shut_down_amid_growing_data_privacy_concerns.html
[2] See U.S. Department of Education, Institute of Education Sciences, National Center for Education Statistics Statewide Longitudinal Data Systems Grant Program http://nces.ed.gov/programs/slds/stateinfo.asp
[3]See Colorado Department of Education’s Statewide Longitudinal Data System “RISE” project https://www.cde.state.co.us/rise/connect
[4]See Western Interstate Commission for Higher Education report Beyond Borders: Understanding the Development and Mobility of Human Capital in an Age of Data-Driven Accountability http://www.wiche.edu/info/longitudinalDataExchange/publications/MLDE_BeyondBorders.pdf
[5]See U.S. Department of Education Family Education Rights and Privacy Act, Final Rule Dec. 2, 2011 https://www.gpo.gov/fdsys/pkg/FR-2011-12-02/pdf/2011-30683.pdf
[6]See Elizabeth Weise, Calif. judge allows data release on 10M students, USA Today, Feb. 17, 2016 http://www.usatoday.com/story/tech/news/2016/02/16/morgan-hill-kimberly-mueller-california-public-schools-information-disabled-release-10-million/80472900/
[7]See Sharon Noguchi, Judge backtracks on release of California student records, San Jose Mercury News, Mar. 4, 2016 http://www.mercurynews.com/bay-area-news/ci_29590794/judge-pulls-back-from-calif-student-records-release?source=infinite-up
[9] New York Archives, Records Disposition Request rec-3, dated 12/20/13
[10]See Ms. Shannon Servier, National PTA, testimony before the U.S. House of Representatives Subcommittee on Early Childhood, Elementary and Secondary Education, Feb. 12, 2015 http://edworkforce.house.gov/uploadedfiles/sevier_testimony_final.pdf
[11]See Ms. Allyson Knox, Microsoft, testimony before the U.S. House of Representatives Subcommittee on Early Childhood, Elementary and Secondary Education, Feb. 12, 2015 http://edworkforce.house.gov/uploadedfiles/knox_testimony_final.pdf
[12] The Privacy Act of 1974, 5 U.S.C. § 552a, establishes a code of fair information practices that governs the collection, maintenance, use, and dissemination of information about individuals that is maintained in systems of records by federal agencies. The Privacy Act of 1974 requires each federal agency that maintains a system of records shall publish in the Federal Register upon establishment or revision a notice of the existence and character of the system of records, which notice shall include:
(A) the name and location of the system;
(B) the categories of individuals on whom records are maintained in the system;
(C) the categories of records maintained in the system;
(D) each routine use of the records contained in the system, including the categories of users and the purpose of such use;
(E) the policies and practices of the agency regarding storage, retrievability, access controls, retention, and disposal of the records;
(F) the title and business address of the agency official who is responsible for the system of records;
(G) the agency procedures whereby an individual can be notified at his request if the system of records contains a record pertaining to him;
(H) the agency procedures whereby an individual can be notified at his request how he can gain access to any record pertaining to him contained in the system of records, and how he can contest its content; and;
(I) the categories of sources of records in the system.
The U.S. Department of Education intends to create a new student database to house the personally identifiable information of 12,000 students, 500 teachers and 104 principals from 104 unidentified schools in 12 school districts across the country.
The information collected on students will include vast amounts of sensitive data including, but not limited to, standardized test scores, race/ethnicity, individual education plan status, and discipline records in order to facilitate “a rigorous study of the effectiveness of providing data-driven instruction professional development to teachers and principals.” The Department of Education is accepting public comments about its data-collection plans until February 18, 2016. There was an article about this plan in the Washington Post Answer Sheet last month, before the comment period was extended.
Please send in your comments and join the Parent Coalition for Student Privacy in telling the Department of Education that the federal government should never collect personally identifiable student information for any reason and that it should cease plans to develop this database at once. However, if the Department is intent on moving forward with this study, we believe it should be obligated to:
explain why aggregate information can’t be used instead of personally identifiable information;
specifically define the personally identifiable elements that will be collected and why each data element is needed;
notify parents of student who are involved in the study, or at least reveal which districts are participating, and report the names of any other third parties to whom the personally identifiable information will be disclosed;
demand that districts obtain informed consent from parents whose children are participating in the study;
demonstrate “significant improvement” in the four key areas identified as a result of a recent Congressional hearing on cybersecurity, or at least report what security protections will be used to safeguard the data;
disclose specifically when the data will be deleted or destroyed;
explain why the federal government has a need to collect or maintain any personally identifiable data when districts could provide it directly to the researchers for their analysis.
Feel free to simply copy our recommendations, add/subtract, or write your own, and submit themhere by Thursday, February 18th.
To view our full comments to the U.S. Department of Education, please visit here; and see the official notice here.
Thank you for your continued support to protect student privacy! —
Comments of the Parent Coalition for Student Privacy to the Institute of Education Sciences, U.S. Department of Education
Privacy Act of 1974; System of Records—“Impact Evaluation of Data-Driven Instruction
Professional Development for Teachers” (#18-13-39)
[FR Doc. 2015-30526]
February 13, 2016
In response to the Institute of Education Sciences of the Department of Education’s published notice, dated December, 2, 2015, to create a new system of records for the “Impact Evaluation of Data-Driven Instruction Professional Development for Teachers” (#18-13-39) (“Study”), the Parent Coalition for Student Privacy (“PCSP”) respectfully submits the following comments objecting to the Department of Education’s (“Department”) proposed collection, use and disclosure of students’ personally identifiable information for purposes of this Study.
According to the System of Records Notice (“SORN”), the Study will facilitate the collection of “personally identifying information on approximately 12,000 students, 500 teachers, and 104 principals from 104 schools in 12 school districts…”
The SORN further states that records “[f]or students… will include, but will not necessarily be limited to, standardized math and English/Language Arts test scores, age, sex, race/ethnicity, grade, eligibility for free/reduced-price lunches, English Learner status, individualized education plan status, school enrollment dates, attendance records, and discipline records.”
We oppose the federal government collecting this highly sensitive personally identifying information from students, on the following grounds:
1. We agree with the Electronic Privacy Information Center that the Department could likely achieve its research goals by using aggregate data instead of students’ personally identifiable information.
This would also reduce the risk that the personal data of students might be misused or breached by the federal government or the private contractors to whom the agency proposes to share the data. If the Department or its contractors cannot achieve their goals by collecting and analyzing aggregate data, they should be obligated to explain why. The goal of data minimization is a requirement of the Fair Information Practice Principles as delineated by the National Institute of Standards and Technology (“NIST”).
2. The Department should be obligated to define specifically which student personally identifiable information (PII) it plans to collect and why.
The Department’s vague declaration that the student information it will collect “will include, but will not necessarily be limited to…” lacks the precision necessary to meet the Department’s own transparency guidance for local education agencies. According to the document entitled “Transparency Best Practices for Schools and Districts,” the Department’s Privacy Technical Assistance Center (“PTAC”) advises that schools and districts communicate the following information to parents:
What information are you collecting about students? • Develop and publish a data inventory listing the information that you collect from or about your students. A best practice is to provide this information at the data element level. Why are you collecting this information? • Explain why you collect student information (e.g., for state or federal reporting, to provide educational services, to improve instruction, to administer cafeteria services, etc.). A best practice is to provide this information at the data element level.
Just as the PTAC advises local education agencies to develop and publish an inventory at the data element level, the federal government should be obligated to maintain at least the same level of transparency as it recommends that schools and districts display. Transparency is also one of the key Fair Information Practice Principles.
3. Notify the parents of children involved in this Study that their student’s personally identifiable information will be collected and disclosed to researchers.
While FERPA no longer requires parental notification and consent of student participation in a federal study, audit or evaluation since the regulations were re-written in 2011, best practices for transparency developed by the PTAC for local education agencies urge them to answer the following questions and communicate the answers to parents:
Do you share any personal information with third parties? If so, with whom, and for what purpose(s)?
The Department should adopt this practice for the unit record system developed for purposes of this Study. This is yet another Fair Information Practice Principle as articulated by NIST: “Organizations should be transparent and notify individuals regarding collection, use, dissemination, and maintenance of personally identifiable information.”
4. The Department should obtain informed consent from parents before children participate in the Study.
Approximately 50 million students are currently educated in the U.S. Of those 50 million, 12,000 children will be taking part in the Study, representing 0.024% of the entire student population. Obtaining consent from parents of this relatively small sampling of families would not be overly burdensome. The Department or participating districts should ask parents for their permission to participate before the Study begins, in accordance with the following Fair Information Practice Principle: “Organizations should involve the individual in the process of using PII and, to the extent practicable, seek individual consent for the collection, use, dissemination, and maintenance of PII.”
5. Improve the Department’s data security protocols before developing yet another unit record system.
Troubling findings from the U.S. Department of Education: Information Security Review Hearing (“Hearing”) by the Full House Committee on Oversight and Government Reform on November 17, 2015, include:
1. The Department maintains 184 information systems. • 120 are managed by outside contractors • 29 are valued by the Office of Management and Budget (OMB) as “high asset” 2. The Department scored NEGATIVE 14% on the OMB CyberSprint for total users using strong authentication 3. The Department received an “F” on the FITARA scorecard 4. The IG penetrated DoEd systems completely undetected by both the CIO or contractor 5. The Department needs significant improvement in four key security areas: • Continuous monitoring • Configuration management • Incident response and reporting • Remote access management
Until the Department markedly improves its information security practices for the data systems it currently maintains it should not be in the business of creating additional unit record systems. Security is yet another principle of Fair Information Practices that the federal government should be obligated to respect: “Organizations should protect PII (in all media) through appropriate security safeguards against risks such as loss, unauthorized access or use, destruction, modification, or unintended or inappropriate disclosure.” At the very least, the Department should be obligated to reveal what security protections will be used to safeguard this data, as in this PTAC recommendation: “Explain your institutions information technology (IT) security and data protection policies.”
5. Reveal when the data will be deleted or destroyed. Another Fair Information Practice Principle refers to data deletion: any organization, including the Department should “only retain PII for as long as is necessary to fulfill the specified purpose(s)” for which it has been collected. Yet nowhere in the SORN does the Department disclose exactly when the data will be deleted. To the contrary, according to the General Records Schedule 4.1 referred to in the SORN, an unsatisfactorily vague statement is made that the personal information collected for this Study will be “Destroy[ed] when no longer needed.”
6. Explain why the Department must collect any personally identifiable data for the purpose of a study that other researchers are conducting.
Finally, we are unable to discern why the Department needs to acquire this information at all. If a study of Data-Driven Instruction Professional Development by contractors must involve the analysis of personally identifiable student information, why cannot these researchers obtain the data directly from participating districts, without the data being collected or maintained by the federal government?
Conclusion
For the preceding reasons, the Department should cease development of the “Impact Evaluation of Data-Driven Instruction Professional Development for Teachers” unit record system. The PCPS feels strongly that the Department should never collect personally identifiable student information for any reason.
However, if the Department is intent on moving forward with this study, it should be obligated to: (1) explain why aggregate information would not be sufficient for the purposes of the Study; (2) specifically define the personally identifiable data elements that will be collected and why each data element is needed; (3) notify parents of students who are involved in the Study, or at least reveal which districts are participating, and report the names of any other third parties to whom the personally identifiable information will be disclosed; (4) demand that districts obtain informed consent from parents whose children are participating in the Study; (5) demonstrate “significant improvement” in the four key security areas identified as a result of the Hearing, or at least report what security protections will be used to safeguard the data (6) disclose specifically when the data will be deleted; and (7) explain why the federal government has a need to collect or maintain any personally identifiable data when districts could provide it directly to the researchers for their analysis.
The PCSP awaits the Department’s responses to each of these questions and/or recommendations.
Respectfully submitted,
Rachael Stickland
Co-Chair
Leonie Haimson
Co-Chair
Parent Coalition for Student Privacy
124 Waverly Place
New York, New York 10011 [email protected]
Click here for a downloadable version of the comments with references.
We know you care about student privacy but are you aware this Thursday is Data Privacy Day? Data Privacy Day is an annual international effort held every January 28th to increase awareness and empower people to protect their personal information.
The Parent Coalition for Student Privacy will be celebrating Data Privacy Day this year by holding a Twitter chat on January 28th from 9:00-10:00 PM EST. We will be asking parents and teachers to weigh in on what questions they would like answered and resources they need to protect and advocate for student privacy in their own school communities. We will use feedback from the Twitter chat to help us design a student privacy toolkit which we will release in partnership with the Campaign for a Commercial-Free Childhood this fall when kids go back-to-school. Stay tuned!
Please join us this Thursday, January 28th from 9:00-10:00 PM EST on Twitter at @parents4privacy and @commercialfree and use the hashtag #StudentPrivacy.
