Statistical, Demographic or Market-Related Data All statistical, demographic or market-related data included in the Registration Statement, the Disclosure Package or the Prospectus are based on or derived from sources that the Company believes to be reliable and accurate and all such data included in the Registration Statement, the Disclosure Package or the Prospectus accurately reflects the materials upon which it is based or from which it was derived.
De-Identified Data Provider agrees not to attempt to re-identify de-identified Student Data. De-Identified Data may be used by the Provider for those purposes allowed under FERPA and the following purposes:
Statistical or Market-Related Data Any statistical, industry-related and market-related data included or incorporated by reference in the Time of Sale Disclosure Package, are based on or derived from sources that the Company reasonably and in good faith believes to be reliable and accurate, and such data agree with the sources from which they are derived.
Statistical and Marketing-Related Data All statistical or market-related data included or incorporated by reference in the Registration Statement, the Time of Sale Disclosure Package or the Final Prospectus, or included in the Marketing Materials, are based on or derived from sources that the Company reasonably believes to be reliable and accurate, and the Company has obtained the written consent to the use of such data from such sources, to the extent required.
Statistical and Market-Related Data Any statistical and market-related data included in the Registration Statement, the General Disclosure Package or the Prospectus are based on or derived from sources that the Company believes, after reasonable inquiry, to be reliable and accurate and, to the extent required, the Company has obtained the written consent to the use of such data from such sources.
Aggregated Data Anonymous, aggregate information, comprising financial account balances, other financial account data, or other available data that is collected through your use of the Services, may be used by us and our service providers to conduct certain analytical research, performance tracking and benchmarking. Our service providers may publish summary or aggregate results relating to metrics comprised of research data, from time to time, and distribute or license such anonymous, aggregated research data for any purpose, including but not limited to, helping to improve products and services and assisting in troubleshooting and technical support. Your personally identifiable information will not be shared with or sold to third parties.
Contractor Certification regarding Boycotting Israel Pursuant to Chapter 2270, Texas Government Code, Contractor certifies Contractor (1) does not currently boycott Israel; and (2) will not boycott Israel during the Term of this Agreement. Contractor acknowledges this Agreement may be terminated and payment withheld if this certification is inaccurate.
Disclosure Updates Promptly and in no event later than 5 Business Days after obtaining knowledge thereof, notify Agent if any written information, exhibit, or report furnished to the Lender Group contained, at the time it was furnished, any untrue statement of a material fact or omitted to state any material fact necessary to make the statements contained therein not misleading in light of the circumstances in which made. The foregoing to the contrary notwithstanding, any notification pursuant to the foregoing provision will not cure or remedy the effect of the prior untrue statement of a material fact or omission of any material fact nor shall any such notification have the effect of amending or modifying this Agreement or any of the Schedules hereto.
Authoritative Root Database To the extent that ICANN is authorized to set policy with regard to an authoritative root server system (the “Authoritative Root Server System”), ICANN shall use commercially reasonable efforts to (a) ensure that the authoritative root will point to the top-‐level domain nameservers designated by Registry Operator for the TLD, (b) maintain a stable, secure, and authoritative publicly available database of relevant information about the TLD, in accordance with ICANN publicly available policies and procedures, and (c) coordinate the Authoritative Root Server System so that it is operated and maintained in a stable and secure manner; provided, that ICANN shall not be in breach of this Agreement and ICANN shall have no liability in the event that any third party (including any governmental entity or internet service provider) blocks or restricts access to the TLD in any jurisdiction.
Data Security and Unauthorized Data Release The Requester and Approved Users, including the Requester’s IT Director, acknowledge NIH’s expectation that they have reviewed and agree to manage the requested controlled-access dataset(s) and any Data Derivatives of controlled-access datasets according to NIH’s expectations set forth in the current NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy and the Requester’s IT security requirements and policies. The Requester, including the Requester’s IT Director, agree that the Requester’s IT security requirements and policies are sufficient to protect the confidentiality and integrity of the NIH controlled-access data entrusted to the Requester. If approved by NIH to use cloud computing for the proposed research project, as outlined in the Research and Cloud Computing Use Statements of the Data Access Request, the Requester acknowledges that the IT Director has reviewed and understands the cloud computing guidelines in the NIH Security Best Practices for Controlled-Access Data Subject to the NIH GDS Policy. The Requester and PI agree to notify the appropriate DAC(s) of any unauthorized data sharing, breaches of data security, or inadvertent data releases that may compromise data confidentiality within 24 hours of when the incident is identified. As permitted by law, notifications should include any known information regarding the incident and a general description of the activities or process in place to define and remediate the situation fully. Within 3 business days of the DAC notification, the Requester agrees to submit to the DAC(s) a detailed written report including the date and nature of the event, actions taken or to be taken to remediate the issue(s), and plans or processes developed to prevent further problems, including specific information on timelines anticipated for action. The Requester agrees to provide documentation verifying that the remediation plans have been implemented. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. All notifications and written reports of data security incidents and policy compliance violations should be sent to the DAC(s) indicated in the Addendum to this Agreement. NIH, or another entity designated by NIH may, as permitted by law, also investigate any data security incident or policy violation. Approved Users and their associates agree to support such investigations and provide information, within the limits of applicable local, state, tribal, and federal laws and regulations. In addition, Requester and Approved Users agree to work with the NIH to assure that plans and procedures that are developed to address identified problems are mutually acceptable and consistent with applicable law.
