Electronic Surveillance in Support of Law Enforcement Sample Clauses

Electronic Surveillance in Support of Law Enforcement. The parties acknowledge that Service Provider and UTOPIA from time to time may be required to provide a Law Enforcement Agency (LEA) with the capability to conduct electronic surveillances on the Subscribers. Where UTOPIA is providing the underlying network facilities for on-net local voice calls between Service Provider’s customers on UTOPIA’s Network, UTOPIA agrees to provide Service Provider access to any necessary elements of its Network required to comply with federal, state and local electronic surveillance requirements; provided, however, that the implementation and provision of any such electronic surveillance with respect to the Subscribers shall be Service Provider’s sole responsibility and implemented by Service Provider’s employees or agents, unless otherwise required by law or to fulfill Service Provider’s compliance with such law. The Parties further agree no later than ninety (90) days after the Effective Date to document a method and procedure that fully sets forth the roles, responsibilities, methods, and procedures of the Parties for handling security and electronic surveillance issues related to the Subscribers. Service Provider shall be responsible for filing any and all reports with all applicable governmental agencies related to compliance with the provisions of this Section 8.5. On those occasions when Service Provider receives a court order that requires the assistance of UTOPIA to capture or monitor on-net activity, and recognizing the non-disclosure obligations that may be contained therein, Service Provider shall advise the issuing authority that UTOPIA’s assistance is required and the issuing authority shall direct and serve the court order upon UTOPIA. If either UTOPIA or Service Provider receives an initial inquiry from the LEA, prior to the issuance of a court order, which will require the assistance of the other party to capture or monitor on-net activity, that Party shall request the LEA to name and serve both UTOPIA and Service Provider.
Sample 1
AutoNDA by SimpleDocs
Electronic Surveillance in Support of Law Enforcement. The parties acknowledge that Service Provider and Network Owner from time to time may be required to provide a Law Enforcement Agency (“LEA”) with the capability to conduct electronic surveillances on the Subscribers. Where Network Owner is providing the underlying network facilities for on-net local voice calls between Service Provider’s customers on Network, Network Owner agrees to provide Service Provider access to any necessary elements of its Network required to comply with federal, state and local electronic surveillance requirements; provided, however, that the implementation and provision of any such electronic surveillance with respect to the Subscribers shall be Service Provider’s sole responsibility and implemented by Service Provider’s employees or agents, unless otherwise required by law or to fulfill Service Provider’s compliance with such law. Service Provider shall be responsible for filing any and all reports with all applicable governmental agencies related to compliance with the provisions of this Section 8.e. If Service Provider receives a court order that requires the assistance of Network Owner or Network Operator to capture or monitor on-net activity, Service Provider shall advise the LEA that Network Owner’s assistance is required so the LEA may direct and serve the court order upon Network Owner. If either Network Owner or Service Provider receives an initial inquiry from the LEA, prior to the issuance of a court order, which will require the assistance of the other party to capture or monitor on-net activity, that party shall request the LEA to name and serve both Network Owner and Service Provider.
Sample 1

Related to Electronic Surveillance in Support of Law Enforcement

  • ELECTRONIC SUBMISSIONS Concessionaire must have the capacity to send and receive electronic submissions and communications as a pre-condition and continuing requirement of this Agreement. For purposes of this Agreement, “Electronic Submissions” shall only include the transmission of documents by email. Concessionaire shall comply with the following terms and conditions: A. Concessionaire shall electronically submit all reports, including, but not limited to, Monthly Reports and Annual Reports as described in Paragraphs 12 and 13, by email to: XxxxxxxxXxxxxx@xxx.xx.xxx. Failure on the part of Concessionaire to submit reports electronically shall be a material breach of this Agreement, subject to Suspension of Operations and/or Termination in accordance with the terms and conditions set forth in Paragraphs 9 and 10. B. Concessionaire shall maintain and monitor on a daily basis an active email address, designated for this Agreement and report any change to the email address during any Term of this Agreement. Failure on the part of Concessionaire to maintain and monitor the active email address, designated for this Agreement, shall be a material breach of this Agreement, subject to Suspension of Operations and/or Termination in accordance with the terms and conditions set forth in Paragraphs 9 and 10.

  • PROHIBITION ON CERTAIN TELECOMMUNICATIONS AND VIDEO SURVEILLANCE SERVICES OR EQUIPMENT To the extent applicable, Supplier certifies that during the term of this Contract it will comply with applicable requirements of 2 C.F.R. § 200.216.

  • Electronic Monitoring All observations shall be conducted openly. Mechanical or electronic devices shall not be used to listen to or record the procedures of any class without the prior knowledge and consent of the teacher.

  • ELECTRONIC SUBMITTALS Contractor shall obtain a license for the State to utilize Submittal Exchange for the purposes of this project. The State and its representatives will have full control of the use of Submittal Exchange by authorized users of the State.

  • Electronic Visit Verification ("EVV A. To ensure: 1. the EVV system is used to verify the provision of services governed under 40 TAC, Chapter 68 or its successor; 2. only authorized people access the Contractor's EVV account; 3. all data elements required by HHSC or HHSC's designee are uploaded or entered and maintained in the EVV system completely, accurately, and prior to submitting the claim; 4. that each time services governed by 40 TAC Chapter 68 or its successor are delivered to an individual, the Contractor's staff uses an HHSC-approved EVV system; and 5. service delivery documentation is immediately available for review by HHSC when requested. B. Equipment provided to Contractor by HHSC, HHSC’s designee, or an HHSC-approved EVV vendor, must be returned in good condition when the equipment is no longer needed under this Contract. In the context of this agreement, “good condition” means Contractor must not place any marks or identifying information on the equipment and may not alter information on the equipment including logos and serial numbers. If the equipment is lost, stolen, marked, altered or damaged by Contractor, Contractor may be required to pay the replacement cost for each piece of equipment that is lost, stolen, marked or damaged. Replacement costs for lost, stolen, marked or damaged equipment may be assessed periodically. If Contractor recovers previously lost or stolen equipment for which Contractor paid the replacement cost in the prior 12 months, Contractor may return the equipment and be reimbursed for the replacement costs within 12 months of the date HHSC, HHSC’s designee or an HHSC-approved EVV vendor (as applicable) received payment in full from the Contractor. This is provided the equipment is returned in good condition as specified above. C. HHSC may perform EVV compliance oversight reviews to determine if Contractor has complied with EVV compliance requirements as outlined in 40 TAC Chapter 68 or its successor, EVV Policy posted on the HHSC EVV website or EVV Policy Handbook. D. If the Contractor determines an electronic record in the EVV system needs to be adjusted at any time, the Contractor will make the adjustment in the EVV system using the most appropriate EVV reason code number(s), EVV reason code description(s) and enter any required free text when completing visit maintenance in the EVV system, if applicable. E. Contractor must begin using an HHSC-approved EVV system prior to submitting an EVV relevant claim. F. All claims for services required to use EVV (EVV claims) must match to an accepted EVV visit transaction in the EVV Aggregator (the state’s centralized EVV database) prior to reimbursement of an EVV claim. Without a matching accepted EVV visit transaction, the claim will be denied. G. Contractor must submit all EVV related claims through the Texas Medicaid Claims Administrator, or as otherwise described in the EVV Policy posted on the HHSC EVV website or in the EVV Policy Handbook. H. Contractor must complete all required EVV training as outlined in the EVV Policy posted on the HHSC EVV website or EVV Policy Handbook: • Prior to using either an EVV vendor system or an EVV proprietary system and • Yearly thereafter. I. Contractor and, if applicable, the Contractor’s appointed EVV system administrator, must complete, sign and date the EVV Onboarding Form as outlined in 40 TAC Chapter 68 or its successor, EVV Policy posted on the HHSC website or EVV Policy Handbook.

  • Rights Protection Mechanisms and Abuse Mitigation ­‐ Registry Operator commits to implementing and performing the following protections for the TLD: i. In order to help registrars and registrants identify inaccurate data in the Whois database, Registry Operator will audit Whois data for accuracy on a statistically significant basis (this commitment will be considered satisfied by virtue of and for so long as ICANN conducts such audits). ii. Work with registrars and registrants to remediate inaccurate Whois data to help ensure a more accurate Whois database. Registry Operator reserves the right to cancel a domain name registration on the basis of inaccurate data, if necessary. iii. Establish and maintain a Domains Protected Marks List (DPML), a trademark protection service that allows rights holders to reserve registration of exact match trademark terms and terms that contain their trademarks across all gTLDs administered by Registry Operator under certain terms and conditions. iv. At no cost to trademark holders, establish and maintain a Claims Plus service, which is a notice protection mechanism that begins at the end of ICANN’s mandated Trademark Claims period. v. Bind registrants to terms of use that define and prohibit illegal or abusive activity. vi. Limit the use of proxy and privacy registration services in cases of malfeasance. vii. Consistent with the terms of this Registry Agreement, reserve the right to exclude from distribution any registrars with a history of non-­‐compliance with the terms of the Registrar Accreditation Agreement. viii. Registry Operator will be properly resourced to perform these protections.

  • Incident Event and Communications Management a. Incident Management/Notification of Breach - DST shall develop, implement and maintain an incident response plan that specifies actions to be taken when DST or one of its subcontractors suspects or detects that a party has gained material unauthorized access to Fund Data or systems or applications containing any Fund Data (the “Response Plan”). Such Response Plan shall include the following: i. Escalation Procedures - An escalation procedure that includes notification to senior managers and appropriate reporting to regulatory and law enforcement agencies. This procedure shall provide for reporting of incidents that compromise the confidentiality of Fund Data (including backed up data) to Fund via telephone or email (and provide a confirmatory notice in writing as soon as practicable); provided that the foregoing notice obligation is excused for such period of time as DST is prohibited by law, rule, regulation or other governmental authority from notifying Fund. ii. Incident Reporting - DST will use commercially reasonable efforts to promptly furnish to Fund information that DST has regarding the general circumstances and extent of such unauthorized access to the Fund Data.

  • Availability of Verizon Telecommunications Services 3.1 Verizon will provide a Verizon Telecommunications Service to Z-Tel for resale pursuant to this Attachment where and to the same extent, but only where and to the same extent, that such Verizon Telecommunications Service is provided to Verizon’s Customers. 3.2 Except as otherwise required by Applicable Law, subject to Section 3.1, Verizon shall have the right to add, modify, grandfather, discontinue or withdraw, Verizon Telecommunications Services at any time, without the consent of Z-Tel. 3.3 To the extent required by Applicable Law, the Verizon Telecommunications Services to be provided to Z-Tel for resale pursuant to this Attachment will include a Verizon Telecommunications Service customer-specific contract service arrangement (“CSA”) (such as a customer specific pricing arrangement or individual case based pricing arrangement) that Verizon is providing to a Verizon Customer at the time the CSA is requested by Z-Tel.

  • Electronic Check Transactions You authorize us to honor any electronic check conversion transaction and re-presented check fee debit transactions you authorize ("Electronic Check Transactions"). You agree that your authorization for an electronic check transaction occurs when you initiate such a transaction after receiving any notice regarding the merchant's right to process the transaction, including any written sign provided by the merchant at the time of your transaction. All terms governing electronic funds transfer services will apply to electronic check transactions, except the $50 and $500 limits of liability for unauthorized transactions in Section 9. You remain responsible for notifying us of any unauthorized electronic check transaction shown on your statement.

  • Foreign-Owned Companies in Connection with Critical Infrastructure If Texas Government Code, Section 2274.0102(a)(1) (relating to prohibition on contracts with certain foreign-owned companies in connection with critical infrastructure) is applicable to this Contract, pursuant to Government Code Section 2274.0102, Contractor certifies that neither it nor its parent company, nor any affiliate of Contractor or its parent company, is: (1) majority owned or controlled by citizens or governmental entities of China, Iran, North Korea, Russia, or any other country designated by the Governor under Government Code Section 2274.0103, or (2) headquartered in any of those countries.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!