• Board Policies/Administrative Regulations/District Procedures: 

     
     
     
     

     
    Student Privacy: 
    DUSD APP Agreements Student privacy laws mitigate the need to have clarity on what APP's we can allow in classrooms.  Instructional Software must follow district guidelines in concert with LCAP and agreed Board adopted curriculum. Please complete and submit to your Principal or Department Lead the Instructional Software Approval Form.  New push towards privacy with F3/CETPA/counties/schools Any online software, extension, or add-on used on Chromebooks by students must adhere to the CA student privacy agreement in order to be considered for use.  Use the *Dublin CSPA form with the educational technology company and once signed, send to Mari Terhune
     
    Please read our **Google related Dublin Unified Google FAQ. & here's more information Google Education Apps, in AB 1584 Compliance, Data Privacy Guidebook, , Created by F3, CETPA and CCSESA  “Ask Before You App”  6-minute video for professional development, Created by F3, CETPA and CommonSense Education.  Great tools for new hire orientation, and trainings/staff meetings with Administrators, Teachers, Coaches and adjunct staff. Google provides this template for parents for YouTube, Maps, and Blogger. Google+ is turned off for all students in Dublin. 
     
     
     
     
     

    image source: https://dpi.wi.gov/

     
    Research/Resources: 
     
     
     
     
     * CSDPA and Exhibit E to enable all CA LEAs piggyback off this privacy agreement. The CSDPA is signed once with any district and uploaded to the CA Student Privacy Alliance (CSPA) site.  Then any other Subscribing LEA can download the Exhibit E and cosign.  When the Subscriber LEA uploads their Exhibit E, the system knows to tie any new Exhibit Es to the original CSDPA signed, so there is a record of both the original agreement and the subscriber agreement tied to every LEA signing an Exhibit E

    The executed Exhibit E serves as the written agreement between the provider and the LEA in order to meet the Ed Code 49073.1 (AB 1584) requirement for a written contract.  This has been vetted by several law firms, PTAC, Kathleen Stiles, Chief Privacy Officer DOE, and the CA Attorney General’s office, so no further language should be needed.

     

    ** What are G Suite for Education core services?  The G Suite for Education (formerly called Google Apps for Education) core services are the heart of Google’s educational offering to schools. The core services are Gmail (including Inbox by Gmail), Calendar, Classroom, Contacts, Drive, Docs, Forms, Groups, Sheets, Sites, Slides, Talk/Hangouts and Vault. These services are provided under the G Suite agreement.

    Schools can use G Suite core services in compliance with COPPA and FERPA. G Suite core services contain no advertising and do not use information in those services for advertising purposes.

    More than 50 million students, teachers and administrators in almost every country in the world rely on G Suite to learn and work together. We are committed to protecting the privacy and security of all our users, including students.

    Please note that there are additional services outside of the G Suite core services that G Suite users can access. These services are not governed by the Student Privacy Pledge or the G Suite agreement, so we may use information in these services in ways we would not for G Suite core services. For example, additional services may serve ads, and Google may use information in these additional services to improve them. For G Suite users in primary/secondary (K-12) schools, Google does not use any user personal information (or any information associated with a Google Account) to target ads. Please review the G Suite Privacy NoticeGoogle Terms of Service and Google Privacy Policy. Learn more about the differences between core services and additional services below.