<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Student Data Privacy &amp; Security Archives - EduSchool</title>
	<atom:link href="https://eduschool.io/category/student-data-privacy-security/feed/" rel="self" type="application/rss+xml" />
	<link>https://eduschool.io/category/student-data-privacy-security/</link>
	<description>One School Platform That Does It All</description>
	<lastBuildDate>Wed, 04 Nov 2026 17:44:13 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.5</generator>

<image>
	<url>https://eduschool.io/wp-content/uploads/2025/09/site-icon-3-75x75.png</url>
	<title>Student Data Privacy &amp; Security Archives - EduSchool</title>
	<link>https://eduschool.io/category/student-data-privacy-security/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>What to Request From an SIS Vendor Before Sharing Student Data</title>
		<link>https://eduschool.io/sis-vendor-student-data-review-checklist/</link>
					<comments>https://eduschool.io/sis-vendor-student-data-review-checklist/#respond</comments>
		
		<dc:creator><![CDATA[EduSchool]]></dc:creator>
		<pubDate>Wed, 04 Nov 2026 17:44:13 +0000</pubDate>
				<category><![CDATA[Student Data Privacy & Security]]></category>
		<guid isPermaLink="false">https://eduschool.io/?p=206</guid>

					<description><![CDATA[<p>Use this SIS vendor review checklist to request privacy terms, security documentation, provider details, incident procedures, and data-return arrangements.</p>
<p>The post <a href="https://eduschool.io/sis-vendor-student-data-review-checklist/">What to Request From an SIS Vendor Before Sharing Student Data</a> appeared first on <a href="https://eduschool.io">EduSchool</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h2>What should a school request before giving an SIS vendor student information?</h2>
<p>Request the proposed contract and data privacy agreement, a description of the information involved, security and access documentation, details of other providers handling the data, incident-response arrangements, and data-return and deletion terms. Have your IT, privacy, procurement, and legal reviewers resolve essential questions before transferring identifiable records.</p>
<p>This checklist is for IT directors coordinating a student information system (SIS) review. It is a practical document-request framework, not legal advice, a complete compliance checklist, or evidence that any particular vendor meets your requirements.</p>
<h2>1. Define the proposed use before requesting records</h2>
<p>Write down the task the vendor would perform, the people who would use the service, and the information needed for that task. Include implementation, support, integrations, and any pilot in the scope of your questions.</p>
<p>Ask for a field-level description of required and optional information. Use fictional records for demonstrations where possible. Have your reviewers decide what information may be transferred, for what purpose, and under what conditions.</p>
<h2>2. Ask for the actual contract and privacy terms</h2>
<p>Request the proposed agreement, data privacy agreement or addendum, referenced policies, and any terms incorporated by link. Record their dates and ask how changes are communicated and accepted.</p>
<p>The U.S. Department of Education provides a model terms-of-service resource for evaluating how online educational services collect, use, and transmit information. Use it as supporting guidance alongside your school&#x27;s review process. <a href="https://studentprivacy.ed.gov/resources/protecting-student-privacy-while-using-online-educational-services-model-terms-service">Source: U.S. Department of Education, Model Terms of Service</a>.</p>
<p>If your school plans to rely on FERPA&#x27;s school-official exception, ask your legal or privacy team to assess the arrangement. The Department&#x27;s guidance describes conditions for outside providers, including institutional purpose, school control over the use and maintenance of education records, restrictions on use and redisclosure, and the school&#x27;s annual-notice criteria. A vendor&#x27;s marketing statement does not establish that your proposed arrangement meets those conditions. <a href="https://studentprivacy.ed.gov/faq/who-school-official-under-ferpa">Source: U.S. Department of Education, School-Official Guidance</a>.</p>
<h2>3. Request evidence about access and security</h2>
<p>Ask for documentation explaining authentication options, role permissions, privileged access, activity records, backup practices, and recovery procedures. Ask how vendor personnel obtain access for support and how that access ends.</p>
<p>Where an assessment or certification is offered, have your IT reviewer check its date, scope, exclusions, and relevance to the service you would actually use. Request a demonstration using fictional data for permissions that are essential to your school.</p>
<p>Keep evidence and open questions separate. Do not mark a requirement complete merely because a feature appears on a roadmap.</p>
<h2>4. Identify every organization handling the information</h2>
<p>Request a list of other providers that would store, process, or access the proposed school information. Ask what each organization does, where it handles the information, and how changes to the list are communicated.</p>
<p>Ask explicitly whether the proposed service uses school information for advertising, model training, product development, or another purpose beyond the contracted school task. Request written answers and the terms governing those uses. Do not assume an answer from a general privacy statement.</p>
<h2>5. Clarify incident handling and the end of the relationship</h2>
<p>Request the incident-response contact, escalation path, contractual notification terms, and description of the information the school would receive during an investigation. Ask your reviewers to compare those terms with the requirements applicable to your school.</p>
<p>Also request export formats, return procedures, deletion timing, treatment of backups, and any fees or exceptions. Ask how the vendor confirms completion and what happens to information held by its other providers.</p>
<p>For a New York school or charter school, ask your privacy and legal reviewers to identify the state-specific provisions, contract documents, and notices that apply to your proposed arrangement. This general checklist does not determine those obligations.</p>
<h2>Use a vendor document-request tracker</h2>
<p>Assign one reviewer and one next action to each open item. Record document versions and the date of each answer.</p>
<table>
<thead>
<tr>
<th>Review area</th>
<th>Request</th>
<th>What your team should resolve</th>
</tr>
</thead>
<tbody>
<tr>
<td>Purpose and data</td>
<td>Use description and required fields</td>
<td>What is necessary and permitted for the proposed task</td>
</tr>
<tr>
<td>Contract</td>
<td>Agreement, privacy addendum, and linked terms</td>
<td>Responsibilities, restrictions, and applicable requirements</td>
</tr>
<tr>
<td>Access and security</td>
<td>Technical documentation and relevant assessments</td>
<td>Evidence for essential controls and remaining gaps</td>
</tr>
<tr>
<td>Other providers</td>
<td>Provider list and responsibilities</td>
<td>Who handles information and under which terms</td>
</tr>
<tr>
<td>Secondary uses</td>
<td>Written use restrictions and answers</td>
<td>Whether proposed uses are acceptable to the school</td>
</tr>
<tr>
<td>Incidents</td>
<td>Response contacts and contractual terms</td>
<td>Escalation, communication, and school responsibilities</td>
</tr>
<tr>
<td>Exit</td>
<td>Export, return, retention, and deletion terms</td>
<td>How information is recovered and the relationship ends</td>
</tr>
</tbody>
</table>
<h2>Make a review decision before a data transfer</h2>
<p>Use clear statuses such as received, under review, clarification needed, and approved by the responsible reviewer. Identify the specific scope of any approval rather than treating a limited pilot review as approval for every use.</p>
<p>If an essential document is missing, assign an owner and resolve it before the planned transfer. Keep the decision record with the reviewed versions. Revisit the review when the proposed data, service, or use changes.</p>
<p>For the broader selection process, use our <a href="https://eduschool.io/choosing-student-information-system/">15 questions for choosing a student information system</a> alongside this document tracker.</p>
<h2>Bring your review requirements to EduSchool</h2>
<p>Apply the same document requests to EduSchool. Bring your proposed use, required information, and open questions to a walkthrough, and ask what documentation is available for your team&#x27;s review. Any unanswered requirement should remain open until supported by evidence.</p>
<p><a href="https://eduschool.io/eduschool-walkthrough/">Explore an EduSchool walkthrough</a>.</p>
<p>The post <a href="https://eduschool.io/sis-vendor-student-data-review-checklist/">What to Request From an SIS Vendor Before Sharing Student Data</a> appeared first on <a href="https://eduschool.io">EduSchool</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://eduschool.io/sis-vendor-student-data-review-checklist/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
