MontanaStudents could ask state officials to delete school data
The proposal would let students and parents request deletion of school data and direct state officials to plan for privacy and send yearly notices.
What it does
Students or parents could ask state officials to delete a student's records from the statewide school data system. Officials could keep records needed for specified funding, contract, or legal duties.
State education officials would work with a K-12 task force on data security plans and publish privacy procedures. Students and parents would receive yearly notice of their privacy rights.
A state data board would have to adopt a policy against agencies and school districts using any part of a student's Social Security number as a unique ID.
Argument forStudents and parents could request deletion and receive a free copy, which may help them see and manage the school data held about a student.
Argument againstSome students might not get their data deleted if officials cannot verify a request or must keep records for funding, contracts, or legal demands.
More detail
Students or parents could ask the superintendent of public instruction to delete a student's data from the statewide K-12 system. A student could request deletion of their own data. A parent or legal guardian could request it for a minor. The office would need to verify the student and the request; it could decline if it cannot verify them. Officials would not have to delete data needed to meet state or federal funding laws, fulfill a contract involving another state agency or a third-party vendor, or comply with a court order, subpoena, or other lawful process. Officials would have 45 days after receiving a verified request to delete the data and provide a free copy. They could extend the deadline once by 45 days, or by 90 days after considering the number and complexity of requests, and would have to explain the delay.
The superintendent of public instruction would work with the K-12 data task force on student data security plans, privacy procedures, and notices. These duties concern student privacy and the statewide K-12 data system. The superintendent would consult the task force on required and proposed data in the statewide system, including the reason for proposed data collection. The security plan would cover privacy standards, audits, breach response, and rules for keeping or disposing of data. Officials would publish privacy procedures and notices. The bill sets July 1, 2025, as its proposed effective date. The privacy notice would be sent annually.
The education and workforce data governing board would have to adopt policies barring agencies and school districts from using any part of a student's Social Security number as a unique identifier. The policy would cover the contributing state agencies and school districts named in the text. The restriction would apply to using a Social Security number to identify a student; the text does not bar other uses of the number. The bill sets July 1, 2025, as its proposed effective date.
Where do you stand?
Choose your position
Tell your reps
Take a position to see your representatives and ways to contact them.
Where it stands
- Introduced
- Died
Looking ahead
No hearings or votes scheduled.
History
- 2025
- May 23(H) Died in CommitteeDied
- Apr 28(H) Motion
- Vote recorded Take from APH to Third Reading Tuesday 29th - Gillette. Result: fail.Lower
- Apr 10(H) Tabled in Committee - (H) AppropriationsMinor
- Vote recorded to_table. Result: pass.Lower
- Apr 10(H) Hearing Canceled - (H) Appropriations
- Apr 10(H) Hearing Canceled - (H) Appropriations
- Apr 8(H) Hearing - (H) Appropriations
- Vote recorded Do Concur. Result: pass.Lower
- Apr 8(H) Rereferred to Committee - (H) AppropriationsMinor
- Apr 8(H) 2nd ReadingMinor
- Apr 8(H) Scheduled for 2nd ReadingMinor
- Apr 1(H) Committee Report - (H) Education
- Apr 1(S) Revised Fiscal Note Requested
- Mar 31(H) Committee Executive Action - (H) Education
- Vote recorded be_concurred_in_as_amended. Result: pass.Lower
- Mar 31(H) Hearing - (H) Education
- Mar 27(H) Hearing Canceled - (H) Education
- Mar 21(H) Hearing - (H) Education
- Mar 21(H) 1st Reading
- Mar 19(S) Revised Fiscal Note Printed
- Mar 18(S) Fiscal Note Unsigned
- Mar 17(S) Revised Fiscal Note ReceivedMinor
- Mar 10(S) Revised Fiscal Note Requested
- Mar 5(H) Referred to Committee - (H) EducationMinor
- Mar 4(S) Transmitted to House
- Vote recorded Do Pass. Result: pass.Upper
- Mar 4(S) 3rd Reading
- Mar 4(S) Scheduled for 3rd ReadingMinor
- Mar 3(S) Committee Report - (S) Finance and Claims
- Vote recorded do_pass. Result: pass.Upper
- Mar 3(S) Committee Executive Action - (S) Finance and Claims
- Feb 27(S) Hearing - (S) Finance and Claims
- Feb 26(S) Fiscal Note Unsigned
- Feb 26(S) Fiscal Note ReceivedMinor
- Feb 19(S) Rereferred to Committee - (S) Finance and ClaimsMinor
- Feb 18(S) 2nd ReadingMinor
- Vote recorded Do Pass. Result: pass.Upper
- Feb 18(S) Scheduled for 2nd ReadingMinor
- Feb 18(S) Fiscal Note Requested
- Feb 14(S) Committee Report - (S) Education and Cultural Resources
- Feb 14(S) Committee Executive Action - (S) Education and Cultural Resources
- Feb 13
- Vote recorded do_pass_as_amended. Result: pass.Upper
- Jan 17(S) Hearing - (S) Education and Cultural Resources
- Jan 15(S) Referred to Committee - (S) Education and Cultural ResourcesMinor
- Jan 10(S) 1st Reading
- Jan 9(S) Introduced
- Jan 9(LC) Draft Delivered to Requester
- Jan 8(LC) Draft Ready for Delivery
- Jan 5(LC) Draft in Assembly
- Jan 5(LC) Draft in Final Drafter Review
- Jan 5(LC) Draft in Input/Proofing
- Jan 1(LC) Draft in Edit
- 2024
- Dec 30(LC) Draft in Legal Review
- Sep 23(LC) Drafter AssignedIntroduced
EducationAI & Privacy