Storing the Chromebook Sample Clauses

Storing the Chromebook. ● Avoid using the Chromebooks in areas where damage or theft is likely. ● NEVER leave the Chromebook in unsupervised areas. Unsupervised areas include, but are not limited to the outdoor spaces, benches, playgrounds, tracks, fields, buses, locker rooms, gyms, restrooms, hallways, and in vehicles. Secure your Chromebook in your locker before going to an unsecured area. ● When students are not using the Chromebooks, they should be stored in their secured lockers. Nothing should be placed on top of the Chromebook in the locker. Students are expected to take their Chromebooks home every night. ● Chromebooks should not be stored in a vehicle at home. If a Chromebook is placed in a vehicle temporarily, it must not be visible from the outside. Theft from cars is not covered by any insurance and will be the responsibility of the parent to pay the district for a replacement unit. ● Unsupervised Chromebooks will be confiscated by staff and could result in disciplinary action. The District does not accept responsibility for the loss of any data deleted due to re-imaging Chromebooks (make sure everything is saved in your google drive).
AutoNDA by SimpleDocs

Related to Storing the Chromebook

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • The Web Services E-Verify Employer Agent agrees to, consistent with applicable laws, regulations, and policies, commit sufficient personnel and resources to meet the requirements of this MOU.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

  • Reliance on Third Party Service Providers Each Party may allow Reporting Financial Institutions to use third party service providers to fulfill the obligations imposed on such Reporting Financial Institutions by a Party, as contemplated in this Agreement, but these obligations shall remain the responsibility of the Reporting Financial Institutions.

  • Monitoring and Management Information C10.1 The Contractor shall comply with the monitoring arrangements set out in the Monitoring Schedule including, but not limited to, providing such data and information as the Contractor may be required to produce under the Contract.

  • Joint Network Implementation and Grooming Process Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia:

  • Procedures for Providing NP Through Full NXX Code Migration Where a Party has activated an entire NXX for a single Customer, or activated at least eighty percent (80%) of an NXX for a single Customer, with the remaining numbers in that NXX either reserved for future use by that Customer or otherwise unused, if such Customer chooses to receive Telephone Exchange Service from the other Party, the first Party shall cooperate with the second Party to have the entire NXX reassigned in the LERG (and associated industry databases, routing tables, etc.) to an End Office operated by the second Party. Such transfer will be accomplished with appropriate coordination between the Parties and subject to appropriate industry lead times for movements of NXXs from one switch to another. Neither Party shall charge the other in connection with this coordinated transfer.

  • Authorized User Overview and Mini-Bid Process Project Based IT Consulting Services Contracts enable Authorized Users to use a competitive Mini-bid Process to acquire Services on an as-needed basis, for qualified IT Projects. Project Based IT Consulting Services may include, but will not be limited to projects requiring: analysis, data classification, design, development, testing, quality assurance, security and associated training for Information Technology based applications. See section 1.3 Out of Scope Work for a listing of projects expressly excluded from the scope of this Contract. An Authorized User Agreement for Project Based IT Consulting Services will be governed first by the terms and conditions specified in the OGS Centralized Contract and second by terms and conditions added to the Authorized User Statement of Work. Additional terms and conditions shall not conflict with or modify the terms and conditions of the OGS Centralized Contract. NYS Executive Agencies must adhere to all internal processes and approvals including, as required, approval from NYS Office of Information Technology Services. Other Authorized Users must adhere to their own internal processes and approvals. In accordance with Appendix B, section 28, Modification of Contract Terms, an Authorized User may add additional required terms and conditions to this Mini-Bid and resultant Authorized User Agreement only if such terms and conditions (1) are more favorable to the Authorized User and (2) do not conflict with or supersede the OGS Centralized Contract terms and conditions. Examples of additional terms and conditions include: • Expedited delivery timeframe; • Additional incentives, such as discount for expedited payment/Procurement Card use; and • Any additional requirements imposed by the funding source or Federal law.

  • For the Contractor Name: Xxxxxxx XxXxxxxxxx Phone: 000-000-0000 Email: xxxxxxx.xxxxxxxxxx@xxxxxxx.xxx

Time is Money Join Law Insider Premium to draft better contracts faster.