Need Tech Support? Go to: oes.incidentiq.com
Discuss with your divisional Tech Coordinator
How does the tool meet teachers teaching and learning goals?
What does the tool offer that other/existing tools do not?
Who will use the tool?
What social interactions happen between accounts? Public/ Private?
Discuss with your divisional Tech Coordinator
Consult the tool's Terms of Service and Privacy Policy
Student accounts: Are student accounts required? Who creates accounts? Can OES use Google sign-in? Who manages these student accounts (resets passwords, etc.)
Minimum age requirement? Parental permission required?
What is the cost of licensing for the tool?
What platforms is the tool used on (mobile, desktop, etc.)?
What other tools does this tool integrate with ?
Consult the tool's Terms of Service and Privacy Policy
Submit the tool for formal review by Tech Team
Data Privacy: Service should not sell user information, should be COPPA, etc. compliant (not collect data under 13), should share user data only as needed, should not target advertise
Data Security: Service should take reasonable security precautions to protect user data
Content Ownership: Users should own and maintain copyright on content. Users should be able to export data out
Is user data public or private? Can it be deleted upon request?
What type of support/ integrity is provided by the vendor?
Here's how to proceed when considering a new tool for use:
Familiarize yourself with the considerations here around tool safety and the tool you are considering.
Set an appointment to discuss the tool with your Ed Tech Coordinator.
If the tool meets the initial requirements of appropriateness, safety, and privacy:
IT and Ed Tech Coordinators will then investigate the tool and report back with an assessment.
If approved, necessary structures around use and support will be set up with requesting teacher and all users
Updated 7/9/24: Formatting and content update -- baylorm@oes.edu