Managed Domains Sample Clauses

Managed Domains. Zoom permits Customers to reserve domains associated with their enterprise and to manage any accounts that are subscribed to Zoom using that domain (“Managed Domain Customer”). Customer may only associate to the Zoom Services domain(s) that they own or are legally entitled to associate for use with the Services. In the event that a Zoom account is created or exists on the reserved domain, but is not authorized by the Managed Domain Customer (the “Non-Managed Domain Account”), the person using or creating such Non-Managed Domain Account will be notified that the domain is reserved for the Managed Domain Customer and will be requested to change the domain associated with the Non-Managed Domain Account. If the person using or creating such Non-Managed Domain Account does not change the domain within the period specified, that person will be deemed to have consented to the Non-Managed Domain Account
Sample 1Sample 2See All (4)
AutoNDA by SimpleDocs
Managed Domains. The Managed Domains functionality is made available to certain Customers and is subject to the terms as further defined in Exhibit A.
Sample 1Sample 2Sample 3
Managed Domains. Zoom permits Customers to reserve domains associated with their enterprise and to manage any accounts that are subscribed to Zoom using that domain (“Managed Domain Customer”). Customer may only associate to the Zoom Services domain(s) that they own or are legally entitled to associate for use with the Services. In the event that a Zoom account is created or exists on the reserved domain, but is not authorized by the Managed Domain Customer (the “Non-Managed Domain Account”), the person using or creating such Non-Managed Domain Account will be notified that the domain is reserved for the Managed Domain Customer and will be requested to change the domain associated with the Non-Managed Domain Account. If the person using or creating such Non- Managed Domain Account does not change the domain within the period specified, that person will be deemed to have consented to the Non-Managed Domain Account being added to the Managed Domain Customer and to have further consented for all data associated with the Non-Managed Domain Account to be shared with the Managed Domain Customer. EXHIBIT “B” SCHEDULE OF DATA Category of Data Elements Check if used Application Technology Meta Data IP Addresses of users, Use of cookies etc. X Other application technology meta data Please specify: See Privacy Policy Application Use Statistics Meta data on user interaction with application X Assessment Standardized test scores Observation data Other assessment data Please specify: Attendance Student school (daily) attendance data Student class attendance data Communications Online communications that are captured (emails, blog entries) Conduct Conduct or behavioral data Demographics Date of Birth Place of Birth Gender Ethnicity or race Language information (native, preferred or primary language spoken primary language spoken by student) Other demographic information- Please specify: See Privacy Policy Enrollment Student school enrollment Student grade level Homeroom Guidance counselor Specific curriculum programs Year of graduation Other enrollment information- Please specify: See Privacy Policy Parent/Guardian Contact Information Address Email Phone Parent/Guardian ID Parent ID number (created to link parents to students) Parent/Guardian Name First and/or Last Schedule Student scheduled courses Teacher names X Special Indicator English language learner information Low income status Medical alerts /health data Student disability information Specialized education services (IEP or 504)...
Sample 1

Related to Managed Domains

  • NON-NETWORK PROVIDER is a provider that has not entered into a contract with us or any other Blue Cross and Blue Shield plan. For pediatric dental care services, non-network provider is a dentist that has not entered into a contract with us or does not participate in the Dental Coast to Coast Network. For pediatric vision hardware services, a non-network provider is a provider that has not entered into a contract with EyeMed, our vision care service manager.

  • Third Party Proprietary Data The Disclosing Party's Third Party Proprietary Data, if any, will be identified in a separate technical document.

  • Confidential System Information HHSC prohibits the unauthorized disclosure of Other Confidential Information. Grantee and all Grantee Agents will not disclose or use any Other Confidential Information in any manner except as is necessary for the Project or the proper discharge of obligations and securing of rights under the Contract. Grantee will have a system in effect to protect Other Confidential Information. Any disclosure or transfer of Other Confidential Information by Xxxxxxx, including information requested to do so by HHSC, will be in accordance with the Contract. If Grantee receives a request for Other Confidential Information, Xxxxxxx will immediately notify HHSC of the request, and will make reasonable efforts to protect the Other Confidential Information from disclosure until further instructed by the HHSC. Grantee will notify HHSC promptly of any unauthorized possession, use, knowledge, or attempt thereof, of any Other Confidential Information by any person or entity that may become known to Grantee. Grantee will furnish to HHSC all known details of the unauthorized possession, use, or knowledge, or attempt thereof, and use reasonable efforts to assist HHSC in investigating or preventing the reoccurrence of any unauthorized possession, use, or knowledge, or attempt thereof, of Other Confidential Information. HHSC will have the right to recover from Grantee all damages and liabilities caused by or arising from Grantee or Grantee Agents’ failure to protect HHSC’s Confidential Information as required by this section. IN COORDINATION WITH THE INDEMNITY PROVISIONS CONTAINED IN THE UTC, Xxxxxxx WILL INDEMNIFY AND HOLD HARMLESS HHSC FROM ALL DAMAGES, COSTS, LIABILITIES, AND EXPENSES (INCLUDING WITHOUT LIMITATION REASONABLE ATTORNEYS’ FEES AND COSTS) CAUSED BY OR ARISING FROM Grantee OR Grantee AGENTS FAILURE TO PROTECT OTHER CONFIDENTIAL INFORMATION. Grantee WILL FULFILL THIS PROVISION WITH COUNSEL APPROVED BY HHSC.

  • Domain Name Data 1.5.1 Query format: whois EXAMPLE.TLD

  • Privacy Shield To the extent that MailChimp processes any Customer Data protected by EU Data Protection Law under the Agreement and/or that originates from the EEA, in a country that has not been designated by the European Commission or Swiss Federal Data Protection Authority (as applicable) as providing an adequate level of protection for Personal Data, the parties acknowledge that MailChimp shall be deemed to provide adequate protection (within the meaning of EU Data Protection Law) for any such Customer Data by virtue of having self-certified its compliance with Privacy Shield. MailChimp agrees to protect such Personal Data in accordance with the requirements of the Privacy Shield Principles. If MailChimp is unable to comply with this requirement, MailChimp shall inform Customer.

  • Links to Third Party Websites In your use of the Service and/or the Company’s website, you may encounter various types of links that enable you to visit websites operated or owned by third parties (“Third Party Site”). These links are provided to you as a convenience and are not under the control or ownership of the Company. The inclusion of any link to a Third Party Site is not (i) an endorsement by the Company of the Third Party Site, (ii) an acknowledgement of any affiliation with its operators or owners, or (iii) a warranty of any type regarding any information or offer on the Third Party Site. Your use of any Third Party Site is governed by the various legal agreements and policies posted at that website.

  • Searchable Whois Notwithstanding anything else in this Agreement, Registry Operator must offer a searchable Whois service compliant with the requirements described in Section 1.10 of Specification 4 of this Agreement. Registry Operator must make available the services only to authenticated users after they logged in by supplying proper credentials (i.e., user name and password). Registry Operator must issue such credentials exclusively to eligible users and institutions that supply sufficient proof of their legitimate interest in this feature (e.g., law enforcement agencies).

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • Provider Network The Panel of health service Providers with which the Contractor contracts for the provision of covered services to Members and Out-of-network Providers administering services to Members.

  • Health Information System i. As required by 42 CFR 438.242(a), the MCP shall maintain a health information system that collects, analyzes, integrates, and reports data. The system shall provide information on areas including, but not limited to, utilization, grievances and appeals, and MCP membership terminations for other than loss of Medicaid eligibility.

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