32.97 Feels Like 28.08
Clouds
Sunrise 7:16 am
Sunset 7:48 pm
  • 3065 - Acceptable Use Policy for Internet and Network Access

    1. Introduction

    1.1      Computer use is a valuable and necessary component of the educational system. School use must be in support of education and research and consistent with educational objectives. In addition, varying work responsibilities result in access to information sources such as software, programs, the Internet, district network, etc. Access is a privilege, not a right and entails responsibility. Technology protection measures are in place and used for all Internet access. Monitoring of Internet usage for minors and adults is policy for the District.

    1.2      Although employees and students may have access to these information sources, their use must be authorized. Access and authorization to information and equipment carry a corresponding responsibility to their appropriate use. District equipment and access is intended to be used for educational and professional or career development activities.

    1.3    Outside of school, families can give the same guidance of Internet use as they exercise with information sources such as television, telephones, radio, movies, and other possibly offensive media.

    1.4    All users and users’ families are hereby notified that some material accessible via the Internet or which may be sent or received through Internet email accounts may contain items that are illegal, defamatory, inaccurate, or potentially offensive to some people. In addition, it is possible to purchase certain goods and services via the Internet, which could result in unwanted financial obligations for which a student's parent or guardian would be liable.

    1.5    The District’s Acceptable Use Policy is to prevent unauthorized access and other unlawful activities by users online, prevent unauthorized disclosure of or access to sensitive information, and to comply with the Children’s Internet Protection Act (“CIPA”).  As used in this policy, “user” includes anyone using the computers, Internet, email, chat rooms and other forms of direct electronic communications or equipment provided by the District (the “network”) or of accounts established by or under the direction of the District.  Only current students and employees are authorized to use the network or District accounts.

    1.6    All users, including students, teachers, administrators, and educational organizations are covered by this policy and are expected to be familiar with its provisions.

    2. Acceptable Uses of the Computer Network or the Internet


    2.1    The resources available are for educational purposes. Personal files will be subject to the same rules as educational files and become the property of the school district.

    2.2    Schools must verify each year that students using the computer network and Internet access for that school year have a signed page acknowledging this policy.

    2.3    Students who are under 18 must have their parents or guardians sign this page and schools must keep it on file. Once signed that permission/acknowledgement page remains in effect until revoked by the parent, or the student loses the privilege of using the District’s network due to violation of this policy or is no longer a Sevier School District student.  Employees and other users are required to follow this policy.  Even without signature, all users must follow this policy and report any misuse of the network or Internet or school accounts to a teacher, supervisor or other appropriate District personnel.  Access is provided for education and District business.  Users should take all reasonable precautions against receiving or downloading messages, images, or other data not appropriate for school use. Staff may use the Internet for incidental personal use during duty-free time.  

    2.4    By using the network or District accounts, users have agreed to this policy.  If a user is uncertain about whether a particular use is acceptable or appropriate, he or she should consult a teacher, supervisor or other appropriate District personnel.     

    3.    Unacceptable Use

    3.1    Students shall not reveal on the Internet personal information about themselves or other persons. For example, students should not reveal their name, home address, telephone number, or display photographs of themselves or others; Students should not meet in person anyone they have met only on the Internet;
    3.2 District resources or accounts shall not be used for:
    3.2.1 gaining unauthorized access to computer or telecommunications networks
    3.2.2 attempting to gain unauthorized access to the network
    3.2.3 intercepting communications intended for other persons
    3.2.4 interfering with the operations of technology resources, including placing a computer virus on any computer system
    3.2.5 accessing or sharing sexually explicit, obscene, potentially damaging, dangerous, disruptive, or otherwise inappropriate materials false or defamatory information, personal or generalized attacks or harassment or libelous material concerning a person or group of people
    3.2.6 logging in through another person’s account or attempting to access another user’s password
    3.2.7 accessing or modifying another person’s files when such access or modification has not been authorized by that person
    3.2.8 sending defamatory messages, furthering any illegal act, including infringing on any intellectual property rights
    3.2.9 downloading, uploading, or distributing any files, software, or other material in violation of federal copyright laws
    3.2.10 plagiarizing written work of others
    3.2.11 creating, sending, or storing messages or other data that are considered offensive, contain sexually explicit material, or otherwise offensively address the age, race, ethnicity, gender, sexual orientation, religious or political beliefs, national origin, or disability of a person or a group of people
    3.2.12 creating, sending, or storing threatening messages pertaining to dangerous devices such as weaponry or explosive devices
    3.2.13 violating any state or federal law or municipal ordinance, such as:  Accessing or transmitting pornography of any kind, obscene depictions, harmful materials, materials that encourage others to violate the law, confidential information or copyrighted materials
    3.2.14 engaging in criminal activities that can be punished under law
    3.2.15 selling or purchasing illegal items or substances
    3.2.16 obtaining and/or using anonymous email sites; spamming; spreading viruses
    3.2.17 causing harm to others or damage to their property
    3.2.18 posting personal contact information for themselves or others
    3.2.19 deleting, copying, modifying, or forging other users' names, emails, files, or data (except for authorized use of shared files); disguising one's identity, impersonating other users, or sending anonymous email
    3.2.20 damaging computer equipment, files, data or the network in any way, including intentionally accessing, transmitting or downloading computer viruses or other harmful files or programs, or disrupting any computer system performance
    3.2.21 using any District computer to pursue “hacking,” internal or external to the District, or attempting to access information protected by privacy laws
    3.2.22 accessing, transmitting or downloading large files, including "chain letters" or any type of "pyramid schemes"
    3.2.23 engaging in uses that jeopardize access or lead to unauthorized access into others’ accounts or other computer networks
    3.2.24 using another’s account password(s) or identifier(s)
    3.2.25 interfering with other users' ability to access their account(s)
    3.2.26 disclosing anyone’s password to others or allowing them to use another’s account(s)
    3.2.27 using the network or Internet or District account for Commercial purposes
    3.2.28 using the Internet for personal financial gain, personal advertising, promotion    
    3.2.29 conducting for-profit business activities and/or engaging in non-government related fundraising or public relations activities such as solicitation for religious purposes or lobbying for personal political purposes using the Internet to bully, intimidate, harass and/or mislead any person.
    3.3    These are examples of inappropriate activity on the District web site, but the District reserves the right to take immediate action regarding activities:
    3.3.1 that create security and/or safety issues for the District, students, employees, schools, network or computer resources
    3.3.2 that expend District resources on content the District in its sole discretion determines lacks legitimate educational content/purpose
    3.3.3 that are determined by District as inappropriate     

    4.    User Responsibilities:


    4.1    It is the responsibility of any person using Sevier School District resources to read, understand, and follow these guidelines. In addition, users are expected to exercise reasonable judgment in interpreting these guidelines and in making decisions about the appropriate use of Sevier School District resources. Any person with questions regarding the application or meaning of these guidelines should seek clarification from his or her Sevier School District administrator, as appropriate. Use of Sevier School District resources shall constitute acceptance of the terms of these guidelines.

    4.2    Users shall not go beyond their authorized access to the District network or other computer equipment or software including the files or accounts of others.  Users shall not disrupt or attempt to damage or disrupt any computer system, system performance, or data.  Users shall not use District resources to engage in illegal acts.     

    5.    Administrator Responsibilities:


    5.1    The administrator is responsible for making certain that the educators and students in the district or organization understand and abide by the Acceptable Use Policy as stated in this document.  If a Sevier School District administrator has reason to believe that a user (educator or student) is misusing the system, the administrator has the right to access to the user’s account in order to review the use of Sevier School District tools by the user.  It is also the responsibility of the administrator to report any misuse of the system to Sevier School District.       

    6.    Educator Responsibilities:


    6.1    Employees who supervise students with access to computer equipment shall be familiar with the Sevier School District Acceptable Use Agreement and enforce its provisions.

    6.2    It is the responsibility of educators who are using Sevier School District tools with students to teach students about safe and responsible use of the Internet.  Educators are responsible for monitoring students’ use of these resources, and to intervene if students are using them inappropriately. Educators should make sure that students understand and abide by the Acceptable Use Agreement policy as stated in this document. If an educator has reason to believe that a student is misusing the system, he or she has the right to access the student’s account in order to review the use of Sevier School District tools by the student.  It is also the responsibility of the teacher to report any misuse of the system to his/her administrator or directly to Sevier School District.  

    6.3    Employees are responsible for the security of their computer equipment, files and passwords. Employees shall promptly notify the District of security problems. Employees with access to student records may not use, release, or share these records except as authorized by Federal and State law.     

    7.    Student Responsibilities:

    7.1    It is the responsibility of students to learn about safe and responsible use of the Internet.  They are responsible to use these resources appropriately. Students using school resources must abide by the Acceptable Use Agreement as stated in this document.  If a student is misusing resources, the district has the right to discontinue his/her use. Parents and students are advised that some material accessible via the Internet may contain items that are illegal, defamatory, inaccurate, or potentially offensive to some people. The District cannot guarantee that filtering software will in all instances successfully block access to inappropriate materials.  When the Internet is accessed using a District account from locations other than school, such access does not go through the filtering software used by the District’s network. Parents and students are therefore encouraged to take appropriate steps to limit access to inappropriate materials (such as home filtering software, parental monitoring, or other means).  The District’s filtering software is not able to check or limit email communication using an Internet-based email account and will not prevent inappropriate communications from being sent with such accounts.     

      8.    No Expectation of Privacy


    8.1    Employees have no expectation of privacy in files, disks, documents, e-mail, websites, etc; which have been created in, entered in, stored in, downloaded from, or used on District equipment, nor in District Internet accounts.

    8.2    The District reserves the right to monitor users' online activities and to access, review, copy, and store or delete any electronic communication or files and disclose them to others as it deems necessary.

    8.3    Users shall have no expectation of privacy regarding their use of District property, network and/or Internet access or files, including email and Web site access.

    8.4    District resources are the property of the District and are to be used in conformance with these guidelines. Sevier School District retains the right to inspect any district computer, Virtual Hard Drive (VHD), Internet account, District provided cell phone, and the files they contain. Sevier School District also has the right to give permission to the teachers, the school administrators, and the parents of any student to review the use of resources and tools used by a student for any reason.

    8.5    Users are advised that messages in discussion forums, including deleted messages, can be archived and can be retrieved. In addition, an Internet firewall automatically checks all data moving between the local area network and the Internet and logs the sending and receiving destinations.

    8.6    Use of technology resources constitutes consent for the Sevier School District staff to monitor and/or inspect any files that users create, any messages they post or receive, and any websites they access.     

    9.    Passwords

    9.1     Each user shall be required to use and maintain personal passwords.  Users should never share their passwords with anyone.  The user must take precautions to maintain the secrecy of their passwords so that other users will not be able to utilize that password for any purpose.  If a user suspects that someone has discovered the user's password, the user should change the password immediately.  Users are responsible for all activity under their accounts.

      

    10.    Violations


    10.1    Failure to observe these guidelines may subject users to termination of their accounts. The use of Internet is a privilege, not a right, and inappropriate use may result in a cancellation of those privileges. The district will notify school or organization administrators of any inappropriate activities by the users.  It will also advise law enforcement agencies of illegal activities and will cooperate fully with local, state, and/or federal officials in any investigation related to illegal activities.

    10.2    The District may deny, revoke, or suspend specific user access. Misuse may also lead to further disciplinary and/or legal action for both students and employees, including suspension, expulsion, dismissal from District employment, or criminal prosecution by government authorities.

    10.3    The District will attempt to tailor any student disciplinary action to the specific issues related to each violation and assist the student in gaining the self-discipline necessary to behave appropriately.     

    11.    Due Process


    11.1    In the event there is an allegation that a user has violated this agreement, the user will receive notice of the alleged violation and an opportunity to present an explanation.

    11.2    Disciplinary actions, in harmony with Corrective Discipline procedures, will be tailored to meet the specific concerns related to the violation. Deliberate violations of this agreement (e.g. malicious acts or omissions; searching for, viewing or otherwise visiting pornographic or sexually explicit sites) may be cause for immediate termination of employment.     

    12.    Disclaimers


    12.1    Sevier School District makes no warranties of any kind, either expressed or implied, for computer services and resources. The district is not responsible for any damages incurred, including, but not limited to: loss of data resulting from delays or interruption of service, loss of data, or damage to personal property; for the accuracy, nature, or quality of information stored or gathered; for unauthorized financial obligations incurred through provided access. Any statement, accessible on the computer network or the Internet, is understood to be the author's individual point of view and not that of the District, its affiliates, or employees.


    12.2    Further, even though the district may use technical or manual means to limit student access, these limits do not provide a foolproof means for enforcing the provisions of this policy. All provisions of this agreement are subordinate to local, state and federal statutes.                                  

    Approved     04/08/96

    Revised        09/10/02

    Revised        01/16/13

    Revised        08/09/17

    Revised        02//08/23

             
             
             
             
             
             
             
             
             
             
             
             
             
                    

  • 6015 Information Technology Security

    1. Sevier School District supports secure network systems, including security for all personally identifiable information that is stored on paper or stored digitally on Sevier School District-maintained computers and networks. This policy supports efforts to mitigate threats that may cause harm to the District’s, students, or employees of Sevier School District.
    1. The District will ensure reasonable efforts will be made to maintain network security. Data loss can be caused by human error, hardware malfunction, natural disaster, security breach, etc., and may not be preventable.
    1. All persons who are granted access to the Sevier School District network and other technology resources are expected to be careful and aware of suspicious communications and unauthorized use of devices on the network. When an employee or other user becomes aware of suspicious activity, he/she is to immediately contact the network administrator with the relevant information.
    1. This policy also covers third party vendors/contractors that contain or have access to the District’s critically sensitive data. All third party entities will be required to sign the Restriction on Use of Confidential Information Agreement before accessing our systems or receiving information.
    1. It is the policy of Sevier School District to fully conform with all federal and state privacy and data governance laws. Including the Family Educational Rights and privacy Act, 20 S. Code § 1232g; 34 CFR Part 99 (hereinafter (FERPA”), the Government Records and Management Act U.C.A §62G-2 (hereafter “GRAMA”), U.C.A. §53A-1-1401 et se. and Utah Administrative Code R277-487.
    1. The Sevier School District Director of technology will maintain procedures to support this policy. Professional development for staff regarding the importance of network security and best practices is to be included in the procedures. The procedures associated with this policy are consistent with guidelines provided by cyber security professionals worldwide and in accordance with the Utah Education Network. The board supports the development, implementation and ongoing improvements for a robust security system of hardware and software that is designed to protect data, users, and electronic assets.

    Approved:    08/09/17

  • 6025 - Data Governance Plan

    DATA GOVERNANCE PLAN                                                            6025

     

    1. PURPOSE

    Data governance is an organizational approach to data and information management that is formalized as a set of policies and procedures that encompass the full life cycle of data; from acquisition, to use, to disposal. The Sevier School District (SSD) takes seriously its moral and legal responsibility to protect student privacy and ensure data security. Utah’s Student Data Protection Act (SDPA), U.C.A §53A-1-1401 requires that SSD adopt a Data Governance Plan. SSD supports the continual updating, improvement, and implementation of this policy as further guidance and procedures are made available by the Utah State Board of Education (USBE). SSD will work to meet implementation deadlines outlined by USBE as resources become available.

    1. SCOPE AND APPLICABILITY

    2.1      This policy is applicable to all employees, temporary employees, and contractors of the SSD. The policy must be used to assess agreements made to disclose data to third-parties. This policy is designed to ensure only authorized disclosure of confidential information. The following 8 subsections provide data governance policies and processes for SSD:

    2.1.1   Data Advisory Groups

    2.1.2   Non-Disclosure Assurances for Employees

    2.1.3   Data Security and Privacy Training for Employees

    2.1.4   Data Disclosure

    2.1.5   Data Breach

    2.1.6   Record Retention and Expungement

    2.1.7   Data Quality

    2.1.8   Transparency

    2.2      Furthermore, the SSD Information Technology Security Policy works in conjunction with this Policy, which:

    2.2.1   Designates SSD as the steward for all confidential information maintained within SSD.

    2.2.2   Designates Data Stewards access for all confidential information.

    2.2.3   Requires Data Stewards to maintain a record of all confidential information that they are responsible for.

    2.2.4   Requires Data Stewards to manage confidential information according to this policy and all other applicable policies, standards and plans.

    2.2.5   Complies with all legal, regulatory, and contractual obligations regarding privacy of SSD data. Where such requirements exceed the specific stipulation of this policy, the legal, regulatory, or contractual obligation shall take precedence.

    2.2.6   Provides the authority to design, implement, and maintain privacy procedures meeting SSD standards concerning the privacy of data in motion, at rest and processed by related information systems.

    2.2.7   Ensures that all SSD board members, employees, contractors, and volunteers comply with the policy and undergo annual privacy training.

    2.2.8   Provides policies and process for

    2.2.8.1            Systems administration,

    2.2.8.2            Network security,

    2.2.8.3            Application security,

    2.2.8.4            Endpoint, server, and device Security

    2.2.8.5            Identity, authentication, and access management,

    2.2.8.6            Data protection and cryptography

    2.2.8.7            Monitoring, vulnerability, and patch management

    2.2.8.8            High availability, disaster recovery, and physical protection

    2.2.8.9            Incident Responses

    2.2.8.10         Acquisition and asset management, and

    2.2.8.11         Policy, audit, e-discovery, and training.

    1. DATA ADVISORY GROUPS

    3.1.    Structure

    SSD has a three-tiered data governance structure to ensure that data is protected at all levels of Utah’s educational system (LEA Student Data Manager, IT Systems Security Manager, and Educators).

    3.2      Group Membership

    Membership in the groups require board approval. Group membership is for two years. If individual members exit the group prior to fulfilling their two-year appointment, the board may authorize SSD Superintendent or designee to appoint a replacement member.

    3.3      Individual and Group Responsibilities

    The following tables outlines individual SSD staff and advisory group responsibilities.

    3.3.1   Table 1. Individual SSD Staff responsibilities

     

    Role Responsibilities

    Chief Privacy Officer

     

    1.    Authorize and manage the sharing, outside of the education entity, of personally identifiable student date from a cumulative record for the education entity.

    2.    Act as the primary local point of contact for the state student data officer.

    3.    A student data manager may share personally identifiable student data that are:

    a.     of a student with the student and the student’s parent

    b.    required by state or federal law

    c.     in an aggregate form with appropriate data redaction techniques applied

    d.    for a school official

    e.    for an authorized caseworker or other representative of the Department of Human Services or the Juvenile Court.

    f.      in a response to a subpoena issued by a court

    g.    directory information

    4.     A student data manager may not share personally identifiable student data for the purpose of external research or evaluation.

    5.     Create and maintain a list of all LEA staff that have access to personally identifiable student data.

    6.     Ensure annual LEA level training on data privacy to all staff members, including volunteers. Document all staff names, roles and training dates, times, locations, and agendas.

     

    Role Responsibilities

    IT Systems Security Manager

     

    1. Acts as the primary point of contact for SSD student data security administration in assisting the board to administer this part;

    2. Ensures compliance with security systems laws throughout the SSD education system, including:

    a.     providing training and support to applicable SSD employees; and

    b.    producing resource materials;

    3.  Investigates complaints of alleged violations of systems breaches;

    4.  Provides an annual report to the board on SSD systems security needs.

     

     Role Responsibilities

    Educators

     

    Fully support Data and Security Managers and comply with this policy and Policy #6015, Information Technology Security and stay current on training.

    1. EMPLOYEE NON-DISCLOSURE ASSURANCES

    Employee non-disclosure assurances are intended to minimize the risk of human error and misuse of information.

    4.1      Scope

    All SSD employees with access to student educational data or confidential educator records must sign and obey the SSD Employee Non-Disclosure Agreement (See Appendix A), which describes the permissible uses of SSD technology and information.

    4.2      Non-Compliance

    Non-compliance with the agreements shall result in consequences up to and including removal of access to SSD network; if this access is required for employment, employees may be subject to dismissal.

    4.3      Non-Disclosure Assurances

    All student data utilized by SSD is protected as defined by the Family Educational Rights and Privacy Act (FERPA) and Utah statute. This policy outlines the way SSD staff is to utilize data and protect personally identifiable and confidential information. A signed agreement form is required from all SSD staff to verify agreement to adhere to/abide by these practices and will be maintained by SSD. All SSD employees with access to student educational data or confidential educator records (including contract or temporary) will:

    4.3.1   Complete a Security and Privacy Fundamentals Training.

    4.3.2   Complete a Security and Privacy Training for Researchers and Evaluators, if your position is a research analyst or if requested by the Technology Director.

    4.3.3   Consult with SSD principals/administrators in their role as internal data owners when creating or disseminating reports containing data.

    4.3.4   Use password-protected SSD-authorized computers when accessing any student-level or staff-level records.

    4.3.5   NOT share individual passwords for personal computers or data systems with anyone.

    4.3.6   Log out of any data system/portal and close the browser after each use.

    4.3.7   Store sensitive data on appropriate-secured location. Unsecured access and flash drives, DVD, CD-ROM or other removable media, or personally-owned computers or devices are not deemed appropriate for storage of sensitive, confidential or student data.

    4.3.8   Keep printed reports with personally identifiable information in a locked location while unattended and use the secure document destruction service provided at SSD when disposing of such records.

    4.3.9   NOT share personally identifying data during public presentations, webinars, etc. If users need to demonstrate child/staff level data, demo records should be used for such presentations.

    4.3.10 Redact any personally identifiable information when sharing sample reports with general audiences, in accordance with guidance provided by the student data manager, found in Appendix B (Protecting PII in Public Reporting).

    4.3.11 Take steps to avoid disclosure of personally identifiable information in reports, such as aggregating, data suppression, rounding, recoding, blurring, perturbation, etc.

    4.3.12 Delete files containing sensitive data after using them on computers or move them to secured servers or personal folders accessible only by authorized parties.

    4.3.13 NOT use email to send screenshots, text, or attachments that contain personally identifiable or other sensitive information. If users receive an email containing such information, they will delete the screenshots/text when forwarding or replying to these messages. If there is any doubt about the sensitivity of the data the Student Data Privacy Manager should be consulted.

    4.3.14 Use secure methods when sharing or transmitting sensitive data. The approved method is SSD Secure File Transfer Protocol (SFTP) website. Also, sharing within secured server folders is appropriate for SSD internal file transfer.

    4.3.15 NOT transmit child/staff-level data externally unless expressly authorized in writing by the data owner and then only transmit data via approved methods such as described in item ten.

    4.3.16 Limit use of individual data to the purposes, which have been authorized within the scope of job responsibilities.

    4.4      Data security and privacy training

    4.4.1   PURPOSE

    SSD will provide a range of training opportunities for all SSD staff, including employees, temporary employees with access to student educational data or confidential educator records in order to minimize the risk of human error and misuse of information.

    4.4.2   Scope

    All SSD employees with access to student educational data or confidential educator records

    4.4.3   Compliance

    New employees who do not comply may not be able to use SSD networks or technology.

    4.4.4   POLICY

    4.4.4.1            Within the first week of employment, all SSD employees and temporary employees with access, must sign and follow the SSD Employee Acceptable Use Policy, which describes the permissible uses of SSD technology and information.

    4.4.4.2            New employees who do not comply may not be able to use SSD networks or technology. Within the first week of employment, all SSD employees with access to student educational data or confidential educator records must also sign and obey the SSD Employee Non-Disclosure Agreement, which describes appropriate uses and the safeguarding of student and educator data.

    4.4.4.3            All current SSD employees are required to participate in an annual Security and Privacy Fundamentals Training Curriculum within 60 days of the adoption of this rule.

    4.4.4.4            SSD requires a targeted Security and Privacy Training for all employees and will determine the annual training topics for these targeted groups based on SSD training needs.

    4.4.4.5            Participation in the training, as well as a signed copy of the Employee Non-Disclosure Agreement, will be annually monitored and reported.

    1. DATA DISCLOSURE

    5.1      PURPOSE

    Providing data to persons and entities outside of the SSD increases transparency, promotes education in Utah, and increases knowledge about Utah public education. This policy establishes the guidelines for sharing data maintained by SSD. It is intended to be consistent with the disclosure provisions of the Federal Family Educational Rights and Privacy Act (FERPA), 20 U.S.C. 1232g, 34 CFR Part 99 and Utah’s Student Data Protection Act (SDPA), U.C.A §53A-1-1401.

    5.2      POLICY FOR DISCLOSURE OF PERSONALLY IDENTIFIABLE INFORMATION (PII)

    5.2.1   Student or Student’s Parent/Guardian Access

    Parents are advised that the records maintained by SSD are provided to SSD by the school district in which their student is/was enrolled, and access to their student’s record can be obtained from the student’s school district. In accordance with FERPA regulations 20 U.S.C. § 1232g (a)(1) (A) (B) (C) and (D), LEAs will provide parents with access to their child’s education records, or an eligible student access to his or her own education records (excluding information on other students, the financial records of parents, and confidential letters of recommendation if the student has waived the right to access), within 45 days of receiving an official request. SSD is not required to provide data that it does not maintain, nor is SSD required to create education records in response to an eligible student’s request.

    5.2.2   Third Party Vendor

    5.2.2.1            Third party vendors may have access to students’ personally identifiable information if the vendor is designated as a “school official” as defined in FERPA, 34 CFR §§ 99.31(a)(1) and 99.7(a)(3)(iii). A school official may include parties such as: professors, instructors, administrators, health staff, counselors, attorneys, clerical staff, trustees, members of committees and disciplinary boards, and a contractor, consultant, volunteer or other party to whom the school has outsourced institutional services or functions.

    5.2.2.2            All third-party vendors contracting with SSD must be compliant with Utah’s Student Data Protection Act (SDPA), U.C.A §53A-1-1401. Vendors determined not to be compliant may not be allowed to enter into future contracts with SSD without third-party verification that they are compliant with federal and state law, and board rule.

    5.2.3   Internal Partner Requests

    Internal partners to SSD include school officials who are determined to have a legitimate educational interest in the information.

    5.2.4   Governmental Agency Requests

    5.2.4.1            SSD may not disclose personally identifiable information of students to external persons or organizations to conduct research or evaluation that is not directly related to a state or federal program reporting requirement, audit, or evaluation. The requesting governmental agency must provide evidence the federal or state requirements to share data in order to satisfy FERPA disclosure exceptions to data without consent in the case of a federal or state

    5.2.4.1.1        reporting requirement

    5.2.4.1.2        audit

    5.2.4.1.3        evaluation

    5.2.4.2            The SSD Student Data Manager will ensure the proper data disclosure avoidance are included if necessary.

    5.3      Policy for External disclosure of Non-Personally Identifiable Information (PII)

    5.3.1   SCOPE

    External data requests from individuals or organizations that are not intending on conducting external research or are not fulfilling a state or federal reporting requirement, audit, or evaluation will not be allowed.

    5.4      Data Disclosure to a Requesting External Researcher or Evaluator

    5.4.1   Responsibility: The Student Data Manager will ensure the proper data are shared with external researcher or evaluator to comply with federal, state, and board rules.

    5.4.2   SSD may not disclose personally identifiable information of students to external persons or organizations to conduct research or evaluation that is not directly related to a state or federal program audit or evaluation. Data that do not disclose PII may be shared with an external researcher or evaluators for projects unrelated to federal or state requirements if:

    5.4.2.1            A SSD Director or Superintendent sponsors an external researcher or evaluator request.

    5.4.2.2            Student data are not PII, but are in an aggregate form and de-identified through disclosure avoidance techniques and other pertinent techniques as determined by the Student Data Manager.

    5.4.2.3            Researchers and evaluators supply the SSD a copy of any publication or presentation that uses SSD data 10 business days prior to any publication or presentation.

    5.5      Process: Research Proposal must be submitted using this form:http://www.schools.utah.gov/data/Data-Request/ResearcherProposal.aspx. Research proposals are sent directly to the Director, Superintendent or designee for review. If the request is approved, an MOA is drafted and reviewed by the Superintendent, and/or District Administration and sent to the Student Data Manager, appropriate Data Steward fulfills the request, de-identifies data as appropriate, and sends to another Data Steward for Quality Assurance (ensuring student data protection). If it passes QA, data are sent to the requester and saves the dataset in a secure folder managed by the Coordinator of Data and Statistics. If it does not pass QA, the data are sent back to the Data Steward for modification.

    1. DATA BREACH

    6.1      PURPOSE

    Establishing a plan for responding to a data breach, complete with clearly defined roles and responsibilities, will promote better response coordination and help educational organizations shorten their incident response time. Prompt response is essential for minimizing the risk of any further data loss and, therefore, plays an important role in mitigating any negative consequences of the breach, including potential harm to affected individuals.

    6.2      POLICY

    6.2.1   SSD shall follow industry best practices to protect information and data. In the event of a data breach or inadvertent disclosure of personally identifiable information, SSD staff shall follow industry best practices outlined in the SSD IT Security Procedures for responding to the breach. Further, SSD shall follow best practices for notifying affected parties, including students, in the case of an adult student, or parents or legal guardians, if the student is not an adult student.

    6.2.2   Concerns about security breaches must be reported immediately to the IT security manager who will collaborate with appropriate members of the SSD executive team to determine whether a security breach has occurred. If the SSD data breach response team determines that one or more employees or contracted partners have substantially failed to comply with SSD’s IT Security Policy/Procedure and relevant privacy policies, they will identify appropriate consequences, which may include termination of employment or a contract and further legal action. Concerns about security breaches that involve the IT Security Manager must be reported immediately to the Superintendent. SSD will periodically update, in keeping with best practices, and resources from USBE in preparing for and responding to a security breach.

    7. DATA RETENTION

    7.1 The District shall classify all student data which it collects under an approved records retention schedule. The District shall retain and dispose of all student data in accordance with an approved records retention schedule.
    7.2 If no existing retention schedule governs student disciplinary records collected by the District:
    7.2.1 The District may propose to the State Records Committee a retention schedule of up to one year if collection of the data is not required by federal or state law or Board rule; or
    7.2.2 The District may propose to the State Records Committee a retention schedule of up to three years if collection of the data is required by federal or state law or State Board rule, unless a longer retention period is prescribed by federal or state law or State Board rule.

    7.3 The District’s retention schedules shall take into account the District’s administrative need for the data.

    7.4 Unless the data requires permanent retention, the District’s retention schedules shall require destruction or expungement of student data after the administrative need for the data has passed.

    7.5 A parent or adult student may request that the District amend, expunge, or destroy any record not subject to an approved retention schedule and believed to be inaccurate, misleading, or in violation of the privacy rights of the student. The District shall process such a request following the same procedures outlined to amend a student education record under FERPA, as set out in Policy FE “Right to Amend Records.”

    8. SHARING STUDENT DATA
    The District may not share a student’s personally identifiable student data without written consent, except in conformance with the requirements of this policy and with the Family Educational Rights and Privacy Act (“FERPA”) and related provisions under 20 U.S.C. §§ 1232(g) and 1232(h).
    Utah Code § 53E-9-308 (2019)

    9. PERMITTED AND PROHIBITED SHARING OF STUDENT DATA BY STUDENT DATA MANAGER

    9.1 A student data manager may share the personally identifiable student data of a student with the student and the student’s parent. Otherwise, a student data manager may only share a student’s personally identifiable student data from a cumulative record in accordance with federal law or as follows. Such data may be shared with:

    9.1.1 A school official;
    9.1.2 An authorized caseworker, in accordance with this policy, or other representative of the Department of Human Services; or
    9.1.3 A person to whom the District has outsourced a service or function:
    9.1.3.1 To research the effectiveness of a program’s implementation; or
    9.1.3.2 that the District’s employees would typically perform.

    9.2 A student data manager may share a student’s personally identifiable student data from a cumulative record with a caseworker or representative of the Department of Human Services if:
    9.2.1 The Department of Human Services is:
    9.2.1.1 legally responsible for the care and protection of the student; or
    9.2.1.2 providing services to the student; and
    9.2.2 The student’s personally identifiable student data is not shared with a person who is not authorized:
    9.2.2.1 to address the student’s education needs; or
    9.2.2.2 by the Department of Human Services to receive the student’s personally identifiable student data; and
    9.2.3 The Department of Human Services maintains and protects the student’s personally identifiable student data.
    9.2.4 A student data manager may share a student’s personally identifiable student data to improve educational outcomes for the student where the student is:
    9.2.4.1 In the custody of or under the guardianship of, the Department of Human Services;
    9.2.4.2 Receiving services from the Division of Juvenile Justice Services;
    9.2.4.3 In the custody of the Division of Child and Family Services;
    9.2.4.4 Receiving services from the Division of Services for People with Disabilities; or
    9.2.4.5 Under the jurisdiction of the Utah Juvenile Court.

    9.3 A student data manager may share aggregate data.

    9.4. A student data manager may not share personally identifiable student data for the purpose of external research or evaluation except as follows: If a student data manager receives a request to share data for the purpose of external research or evaluation, the student data manager shall:
    9.4.1 Verify that the request meets the requirements of 34 C.F.R. § 99.31(a)(6);
    9.4.2 Submit the request to the District’s external research review process; and
    Fulfill the instructions that result from the review process.

    9.5 If the student data manager is informed that the State Board of Education intends to share student data collected by the District with the Utah Registry of Autism and Developmental Disabilities, the student data manager shall give notice to the parent of each student whose data is to be shared of the State Board’s intention to share the data. This notice shall be provided at least 30 days before the State Board is to share the data. If a parent requests that the State Board not share the data, the student data manager shall relay that request to the State Board.

    9.6 A student data manager may share personally identifiable student data in response to a subpoena issued by a court.

    9.7 In accordance with State Board of Education rule, a student data manager may share personally identifiable information that is directory information.
    Utah Code § 53E-9-308 (2019)

    10. QUALITY ASSURANCES AND TRANSPARENCY REQUIREMENTS

    10.1 PURPOSE
    Data quality is achieved when information is valid for the use to which it is applied, is consistent with other reported data and users of the data have confidence in and rely upon it. Good data quality does not solely exist with the data itself, but is also a function of appropriate data interpretation and use and the perceived quality of the data. Thus, true data quality involves not just those auditing, cleaning and reporting the data, but also data consumers. Data quality at is addressed in five areas:

    10.1.1 Data Governance Structure
    The SSD data governance policy is structured to encourage the effective and appropriate use of educational data. The SSD data governance structure centers on the idea that data is the responsibility of all SSD departments and that data driven decision-making is the goal of all data collection, storage, reporting and analysis. Data driven decision making guides what data is collected, reported and analyzed.

    10.1.2 Data Requirements and Definitions

    10.1.2.1 Clear and consistent data requirements and definitions are necessary for good data quality. On the data collection side, the SSD communicates data requirements and definitions to LEAs through the Data Clearinghouse Update Transaction documentations (see http://www.schools.utah.gov/vomputerservices/Data-Clearinghouse.aspx). The SSD also communicates with SSD IT staff regularly, at monthly Data Warehouse Group meetings and at biannual Data Conferences. Where possible, SSD program specialists are invited to these meetings and the same guidance is give to the appropriate program directors.

    10.1.2.2 On the data reporting side, the production and presentation layers provide standard data definitions and business rules. Data Stewards coordinate data releases through the Data Warehouse Group meetings. All data released includes relevant data definitions, business rules, and are date stamped. Further, Data and Statistics produces documentation, trainings and FAQs on key statistics and reports, such as AYP, graduation rate and class size.

    10.1.3 Data Collection
    10.1.3.1 Data elements should be collected only once—no duplicate data collections are permitted. Where possible, data is collected at the lowest level available (i.e. at the student/teacher level). Thus, there are no aggregate data collections if the aggregate data can be derived or calculated from the detailed data.
    10.1.3.2 For all new data collections, SSD provides to LEAs clear guidelines for data collection and the purpose of the data request. The SSD also notifies LEAs as soon as possible about future data collections. Time must be given to LEAs in order for them to begin gathering the data needed.

    10.1.4 Data Auditing
    Data and Statistics Data Analysts perform regular and ad hoc data auditing. They analyze data in the warehouse for anomalies, investigate the source of the anomalies, and work with IT and/or LEAs in explaining and/or correcting the anomalies. Data Analysts also work with School Finance to address findings from the Auditors.

    10.1.5 Quality Control Checklist
    Checklists have been proven to increase quality (See Appendix C).

    11. DATA TRANSPARENCY
    Annually, SSD will publically post:

    11.1 SSD data collections

    11.2 Metadata Dictionary as described in Utah’s Student Data Protection Act (SDPA), U.C.A §53A-1-1401

    12. APPENDIX
    Appendix A. SSD Employee Non-Disclosure Agreement
    As an employee of the Sevier School District I hereby affirm that: (Initial)
    ______ I have read the Employee Non-Disclosure Assurances attached to this agreement form and read and reviewed Data Governance Plan SSD policies. These assurances address general procedures, data use/sharing, and data security.
    ______ I will abide by the terms of the SSD policies and its subordinate process and procedures;
    ______ I grant permission for the manual and electronic collection and retention of security related information, including but not limited to photographic or videotape images, of your attempts to access the facility and/or workstations.

    Trainings
    ______ I have completed SSD Data Security and Privacy Fundamentals Training.
    ______ I will complete SSD Data Security and Privacy Fundamentals Training within 30 days.

    Using SSD Data and Reporting Systems
    ______ I will use a password-protected computer when accessing data and reporting systems, viewing child/staff records, and downloading reports.
    ______ I will not share or exchange individual passwords, for either personal computer(s) or SSD system user accounts, with SSD staff or participating program staff.
    ______I will log out of and close the browser after each use of SSD data and reporting systems.
    ______I will only access data in which I have received explicit written permissions from the data owner.
    ______I will not attempt to identify individuals, except as is required to fulfill job or volunteer duties, or to publicly release confidential data;

    Handling Sensitive Data
    ______ I will keep sensitive data on password-protected SSD -authorized computers.
    ______ I will keep any printed files containing personally identifiable information in a locked location while unattended.
    ______ I will not share child/staff-identifying data during public presentations, webinars, etc. I understand that dummy records should be used for such presentations.
    ______ I will delete files containing sensitive data after working with them from my desktop, or move them to a secured SSD server.
    Reporting & Data Sharing
    ______ I will not redisclose or share any confidential data analysis except to other authorized personnel without SSD express written consent.
    ______ I will not publically publish any data without the approval of the Superintendent.
    ______ I will take steps to avoid disclosure of personally identifiable information in SSD -level reports, such as aggregating, data suppression, rounding, recoding, blurring, perturbation, etc.
    ______ I will not use email to send screenshots, text, or attachments that contain personally identifiable or other sensitive information. If I receive an email containing such information, I will delete the screenshots/text when forwarding or replying to these messages.
    ______I will not transmit child/staff-level data externally unless explicitly authorized in writing.
    ______ I understand that when sharing child/staff-identifying data with authorized individuals, the only approved methods are phone calls or SSD Secure File Transfer Protocol (SFTP). Also, sharing within secured server folders is appropriate for SSD internal file transfer.
    ______ I will immediately report any data breaches, suspected data breaches, or any other suspicious activity related to data access to my supervisor and the SSD Information Security Officer. Moreover, I acknowledge my role as a public servant and steward of child/staff information, and affirm that I will handle personal information with care to prevent disclosure.
    Consequences for Non-Compliance
    ______ I understand that access to the SSD network and systems can be suspended based on any violation of this contract or risk of unauthorized disclosure of confidential information;
    ______I understand that failure to report violation of confidentiality by others is just as serious as my own violation and may subject me to personnel action, including termination.
    Termination of Employment
    _______I agree that upon the cessation of my employment from SSD I will not disclose or otherwise disseminate any confidential or personally identifiable information to anyone outside of SSD without the prior written permission of the Chief Information Officer of SSD.
    Print Name: ___________________________________
    Signed: ________________________________________
    Date: __________________

    Appendix B. Protecting PII in Public Reporting

    Data Gateway Statistical Reporting Method for Protecting PII
    Public education reports offer the challenge of meeting transparency requirements while also meeting legal requirements to protect each student’s personally identifiable information (PII). Recognizing this, the reporting requirements state that subgroup disaggregation of the data may not be published if the results would yield personally identifiable information about an individual student. While the data used by the SSD and local agencies(LEAs) is comprehensive, the data made available to the public is masked to avoid unintended disclosure of personally identifiable information at summary school, LEA, or state-level reports.

    This is done by applying the following statistical method for protecting PII.
    1. Underlying counts for groups or subgroups totals are not reported.

    2. If a reporting group has 1 or more subgroup(s) with 10 or fewer students.
    2.1 The results of the subgroup(s) with 10 or fewer students are recoded as “N<10”
    2.2. For remaining subgroups within the reporting group
    2.2.1 For subgroups with 300 or more students, apply the following suppression rules.
    2.2.1.1 Values of 99% to 100% are recoded to ≥99%
    2.2.1.2 Values of 0% to 1% are recoded to ≤1%

    3. For subgroups with 100 or more than but less than 300 students, apply the following suppression rules.
    3.1 Values of 98% to 100% are recoded to ≥98%
    3.2 Values of 0% to 2% are recoded to ≤2%

    4. For subgroups with 40 or more but less than 100 students, apply the following suppression rules.
    4.1 Values of 95% to 100% are recoded to ≥95%
    4.2 Values of 0% to 5% are recoded to ≤5%

    5. For subgroups with 20 or more but less than 40 students, apply the following suppression rules.
    5.1 Values of 90% to 100% are recoded to ≥90%
    5.2 Values of 0% to 10% are recoded to ≤10%
    5.3 Recode the percentage in all remaining categories in all groups into intervals as follows (11-19,20-29,…,80-89)

    6. For subgroups with 10 or more but less than 20 students, apply the following suppression rules.
    6.1 Values of 80% to 100% are recoded to ≥80%
    6.2 Values of 0% to 20% are recoded to ≤20%
    6.3 Recode the percentage in all remaining categories in all groups into intervals as follows (20-29,30-39,…,70-79)

    Appendix C. Quality Control Checklist

    1. Reliability (results are consistent)
    1.1 Same definitions were used for same or similar data previously reported or it is made very clear in answering the request how and why different definitions were used
    1.2 Results are consistent with other reported results or conflicting results are identified and an explanation provided in request as to why is different
    1.3 All data used to answer this particular request was consistently defined (i.e. if teacher data and student data are reported together, are from the same year/time period)
    1.4 Another SSD data steward could reproduce the results using the information provided in the metadata

    2. Validity (results measure what are supposed to measure, data addresses the request)
    2.1 Request was clarified
    2.2 Identified and included all data owners that would have a stake in the data used
    2.3 Data owners approve of data definitions and business rules used in the request
    2.4 All pertinent business rules were applied
    2.5 Data answers the intent of the request (intent ascertained from clarifying request)
    2.6 Data answers the purpose of the request (audience, use, etc.)
    2.7 Limits of the data are clearly stated
    2.8 Definitions of terms and business rules are outlined so that a typical person can understand what the data represents

    3. Presentation
    3.1 Is date-stamped
    3.2 Small n-sizes and other privacy issues are appropriately handled
    3.3 Wording, spelling and grammar are correct
    3.4 Data presentation is well organized and meets the needs of the requester
    3.5 Data is provided in a format appropriate to the request
    3.6 A typical person could not easily misinterpret the presentation of the data

     

    Approved : 08/09/17

    Revised: 02/19/20

  • Family Educational Rights and Privacy Act (FERPA) Notice for Directory Information

    Family Educational Rights and Privacy Act (FERPA)
    Notice for Directory Information

    [Note: Per 34 C.F.R. § 99.37(d), a school or school district may adopt a limited directory information policy. If a school or school district does so, the directory information notice to parents and eligible students must specify the parties who may receive directory information and/or the purposes for which directory information may be disclosed.]

    The Family Educational Rights and Privacy Act (FERPA), a Federal law, requires that Sevier School District, with certain exceptions, obtain your written consent prior to the disclosure of personally identifiable information from your child’s education records. However, Sevier School District may disclose appropriately designated “directory information” without written consent, unless you have advised the Sevier School District to the contrary in accordance with Sevier School District procedures. The primary purpose of directory information is to allow the Sevier School District to include information from your child’s education records in certain school publications. Examples include:

    • A playbill, showing your student’s role in a drama production;
    • The annual yearbook;
    • Honor roll or other recognition lists;
    • Graduation programs; and
    • Sports activity sheets, such as for wrestling, showing weight and height of team members.

    Directory information, which is information that is generally not considered harmful or an invasion of privacy if released, can also be disclosed to outside organizations without a parent’s prior written consent. The sharing of whole school or multiple student directory information must be approved by the Superintendent or his/her designee. Outside organizations include, but are not limited to, companies that manufacture class rings or publish yearbooks. In addition, two federal laws require local educational agencies (LEAs) receiving assistance under the Elementary and Secondary Education Act of 1965, as amended (ESEA) to provide military and higher education recruiters, upon request, with the following information – names, addresses and telephone listings – unless parents have advised the LEA that they do not want their student’s information disclosed without their prior written consent. [Note: These laws are Section 9528 of the ESEA (20 U.S.C. § 7908) and 10 U.S.C. § 503(c).]

    If you do not want Sevier School District to disclose any or all of the types of information designated below as directory information from your child’s education records without your prior written consent, you must notify the Sevier School District in writing by September 15 of the current school year. Sevier School District has designated the following information as directory information:


    • Student's name
    • Address
    • Telephone listing
    • Electronic mail address
    • Photograph
    • Date and place of birth
    • Major field of study
    • Dates of attendance
    • Grade level
    • Participation in officially recognized activities and sports
    • Weight and height of members of athletic teams
    • Degrees, honors, and awards received
    • The most recent educational agency or institution attended
    • Student ID number, user ID, or other unique personal identifier used to communicate in electronic systems but only if the identifier cannot be used to gain access to education records except when used in conjunction with one or more factors that authenticate the user’s identity, such as a PIN, password, or other factor known or possessed only by the authorized user
    • A student ID number or other unique personal identifier that is displayed on a student ID badge, but only if the identifier cannot be used to gain access to education records except when used in conjunction with one or more factors that authenticate the user's identity, such as a PIN, password, or other factor known or possessed only by the authorized user.

  • MetaData Dictionary - USBE

    The State of Utah has created a repository of shared information.  This can be found here:

    Metadata Dictionary

  • Mid-Utah Radio Interview Regarding the School Dismissal Announcement

    Please click the link below to listen:

    https://drive.google.com/file/d/12zEru6rv4LeDWrPRnqF9NTx-xt5wLwt7/view?usp=sharing

  • Mid-Utah Radio Interview with Superintendent Douglas and Central Utah Health Department

    Please click the following link to listen to the interview with Mid-Utah Radio, Superintendent Douglas and Central Utah Health Department regarding the COVID-19 (Coronavirus). One thing is certain, things will change including recommendations and guidelines from the task-force. We remind you to please be flexible with us as we adapt to recommendations and changes that are coming in hourly.

    http://midutahradio.com/news/local-news/sevier-school-district-and-central-utah-public-health-department-officials-discuss-the-coronavirus/  

  • Notification of Rights under FERPA for Elementary and Secondary Schools

    The Family Educational Rights and Privacy Act (FERPA) affords parents and students who are 18 years of age or older ("eligible students") certain rights with respect to the student's education records. These rights are:

    1. The right to inspect and review the student's education records within 45 days after the day the [Name of school (“School”)] receives a request for access.
    Parents or eligible students who wish to inspect their child’s or their education records should submit to the school principal [or appropriate school official] a written request that identifies the records they wish to inspect. The school official will make arrangements for access and notify the parent or eligible student of the time and place where the records may be inspected.

    2. The right to request the amendment of the student’s education records that the parent or eligible student believes are inaccurate, misleading, or otherwise in violation of the student’s privacy rights under FERPA.
    Parents or eligible students who wish to ask the [School] to amend their child’s or their education record should write the school principal [or appropriate school official], clearly identify the part of the record they want changed, and specify why it should be changed. If the school decides not to amend the record as requested by the parent or eligible student, the school will notify the parent or eligible student of the decision and of their right to a hearing regarding the request for amendment. Additional information regarding the hearing procedures will be provided to the parent or eligible student when notified of the right to a hearing.

    3. The right to provide written consent before the school discloses personally identifiable information (PII) from the student's education records, except to the extent that FERPA authorizes disclosure without con¬sent.

    One exception, which permits disclosure without consent, is disclosure to school officials with legitimate educational interests. The criteria for determining who constitutes a school official and what constitutes a legitimate educational interest must be set forth in the school’s or school district’s annual notification for FERPA rights. A school official typically includes a person employed by the school or school district as an ad¬ministrator, supervisor, instructor, or support staff member (including health or medical staff and law enforcement unit personnel) or a person serving on the school board. A school official also may include a volunteer, contractor, or consultant who, while not employed by the school, performs an institutional service or function for which the school would otherwise use its own employees and who is under the direct control of the school with respect to the use and maintenance of PII from education records, such as an attorney, audi¬tor, medical consultant, or therapist; a parent or student volunteering to serve on an official committee, such as a disciplinary or grievance committee; or a parent, student, or other volunteer assisting another school official in performing his or her tasks. A school official typically has a legitimate educational interest if the official needs to review an educa¬tion record in order to fulfill his or her professional responsibility.
    [Optional] Upon request, the school discloses education records without consent to officials of another school or school district in which a student seeks or intends to enroll, or is already enrolled if the disclosure is for purposes of the student’s enrollment or transfer. [NOTE: FERPA requires a school or school district to make a reasonable attempt to notify the parent or student of the records re¬quest unless it states in its annual notification that it intends to forward records on request or the disclosure is initiated by the parent or eligible student.]

    4. The right to file a complaint with the U.S. Department of Education concerning alleged failures by the [School] to comply with the requirements of FERPA. The name and address of the Office that administers FERPA are:
    Family Policy Compliance Office
    U.S. Department of Education
    400 Maryland Avenue, SW
    Washington, DC 20202
    [

    NOTE: In addition, a school may want to include its directory information public notice, as required by § 99.37 of the regulations, with its annual notification of rights under FERPA.]
    [Optional] See the list below of the disclosures that elementary and secondary schools may make without consent.

    FERPA permits the disclosure of PII from students’ education records, without consent of the parent or eligible student, if the disclosure meets certain conditions found in § 99.31 of the FERPA regulations. Except for disclosures to school officials, disclosures related to some judicial orders or lawfully issued subpoenas, disclosures of directory information, and disclosures to the parent or eligible student, § 99.32 of the FERPA regulations requires the school to record the disclosure. Parents and eligible students have a right to inspect and review the record of disclosures. A school may disclose PII from the education records of a student without obtaining prior written consent of the parents or the eligible student –


    • To other school officials, including teachers, within the educational agency or institution whom the school has determined to have legitimate educational interests. This includes contractors, consultants, volunteers, or other parties to whom the school has outsourced institutional services or functions, provided that the conditions listed in § 99.31(a)(1)(i)(B)(1) - (a)(1)(i)(B)(3) are met. (§ 99.31(a)(1))


    • To officials of another school, school system, or institution of postsecondary education where the student seeks or intends to enroll, or where the student is already enrolled if the disclosure is for purposes related to the student’s enrollment or transfer, subject to the requirements of § 99.34. (§ 99.31(a)(2))


    • To authorized representatives of the U. S. Comptroller General, the U. S. Attorney General, the U.S. Secretary of Education, or State and local educational authorities, such as the State educational agency (SEA) in the parent or eligible student’s State. Disclosures under this provision may be made, subject to the requirements of § 99.35, in connection with an audit or evaluation of Federal- or State-supported education programs, or for the enforcement of or compliance with Federal legal requirements that relate to those programs. These entities may make further disclosures of PII to outside entities that are designated by them as their authorized representatives to conduct any audit, evaluation, or enforcement or compliance activity on their behalf, if applicable requirements are met. (§§ 99.31(a)(3) and 99.35)
    • In connection with financial aid for which the student has applied or which the student has received, if the information is necessary for such purposes as to determine eligibility for the aid, determine the amount of the aid, determine the conditions of the aid, or enforce the terms and conditions of the aid. (§ 99.31(a)(4))


    • To State and local officials or authorities to whom information is specifically allowed to be reported or disclosed by a State statute that concerns the juvenile justice system and the system’s ability to effectively serve, prior to adjudication, the student whose records were released, subject to § 99.38. (§ 99.31(a)(5))


    • To organizations conducting studies for, or on behalf of, the school, in order to: (a) develop, validate, or administer predictive tests; (b) administer student aid programs; or (c) improve instruction, if applicable requirements are met. (§ 99.31(a)(6))
    • To accrediting organizations to carry out their accrediting functions. (§ 99.31(a)(7))
    • To parents of an eligible student if the student is a dependent for IRS tax purposes. (§ 99.31(a)(8))
    • To comply with a judicial order or lawfully issued subpoena if applicable requirements are met. (§ 99.31(a)(9))
    • To appropriate officials in connection with a health or safety emergency, subject to § 99.36. (§ 99.31(a)(10)
    • Information the school has designated as “directory information” if applicable requirements under § 99.37 are met. (§ 99.31(a)(11))
    • To an agency caseworker or other representative of a State or local child welfare agency or tribal organization who is authorized to access a student’s case plan when such agency or organization is legally responsible, in accordance with State or tribal law, for the care and protection of the student in foster care placement. (20 U.S.C. § 1232g(b)(1)(L))

    • To the Secretary of Agriculture or authorized representatives of the Food and Nutrition Service for purposes of conducting program monitoring, evaluations, and performance measurements of programs authorized under the Richard B. Russell National School Lunch Act or the Child Nutrition Act of 1966, under certain conditions. (20 U.S.C. § 1232g(b)(1)(K))

  • Radio Interview - CTE Health Sciences

    CTE Center Health Sciences teacher Paul Torgerson and several students share experiences about the capstone course and projects that are strengthening the Health Sciences Pathway.

  • Radio Interview - CTE Pathways

    CTE Directors discuss college and career readiness and collaborative efforts towards building successful pathways with local industries.

     

     

     

  • Radio Interview - Richfield Chamber Business of the Year

    On November 9th at the Annual Chamber of Commerce Banquet Sevier School District was selected as the Business of the Year!  Though we aren't a business as most are defined, there is no doubt we are in the Kid Business and that is the most important business of all. "This award goes out to the many teachers, administrators, faculty members, and support staff. Their dedication to our students is inspiring, it is wonderful to see them honored with this!" Superintendent Douglas. 

     

     

     

  • Radio Interview - Superintendent Douglas & Principal Krahenbuhl

    Superintendent Cade Douglas and Salina Elementary School Principal Kole Krahenbuhl discuss a range of topics starting with concerns about Critical Race Theory and the "woke" movement. They then move into senior graduation, Utah Rural Schools Association Conference, the COVID-induced academic gap and the proactive approach Sevier School District is taking to make up for lost ground by offering summer school programs.

  • Radio Interview - Superintendent Douglas & Principal Nielson

    The interview is with Superintendent Douglas and SSMS Principal Michelle Nielson. The interview includes an update on the SSMS construction project, Back to School information, and an update on the COVID-19 protocols and letter that was sent to parents. 

     

     

  • Radio Interview - Superintendent Douglas and Principal Jill Porter

    Please listen to the following interview with Superintendent Douglas and Jill Porter regarding the Importance of School Attendance, South Sevier Middle School Construction Update, Intervention Support for Students, and Graduation.

  • Radio Interview - Superintendent Douglas COVID update

    Superintendent Douglas gives an update on current COVID cases as well as student wellness and strategies for adults to connect and reconnect with students. 

     

     

  • Radio Interview - Superintendent Douglas CRHS Mark Stewart 10/13/21

    Superintendent Douglas and Cedar Ridge High School Lead Teacher/Admin Mark Stewart discuss concerns with absenteeism, principals appreciation month, and Cedar Ridge High School

     

     

  • Radio Interview - Superintendent Douglas, Brent Gubler 1-12-22

    Superintendent Douglas and Principal Bent Gubler discuss Sevier School Board members receiving the state Master Boards Award, board member precincts, and school board member governance roles. They also discuss the many exciting opportunities available to high school students through the Sevier CTE Center and other exciting happenings at Richfield High School. 

     

     

  • Radio Interview - Superintendent Douglas, Chad Johnson 1-11-23

    Elementary Principal Chad Johnson and Superintendent Douglas discuss happenings at Pahvant Elementary and throughout the District including an introduction of the Dignity Index.

    1/11/2023

     

     

  • Radio Interview - Superintendent Douglas, Rod Hinck 3-15-23

    Principal Rod Hinck, Superintendent Douglas, and a student guest discuss happenings at North Sevier Middle School. The Superintendent also gives a District update including an exciting discussion on unified sports.

  • Radio Interview - Superintendent Douglas, Ted Chappell 11-09-22

    Interview with Superintendent Douglas and Red Hills Middle School Principal Ted Chappell 11-09-2022

    Discuss RHMS and Think Right Paret Night

     

     

Page 1 of 2