De-Identified Data Set. The data set comprised of De-Identified Data derived from the Pre-processed Claims Data, to be used by VHI to create the De-Identified Reports. The De- Identified Data Set shall not include any Actual Reimbursement Amounts.
De-Identified Data Set Sample Clauses
Related to De-Identified Data Set
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: (1) assisting the LEA or other governmental agencies in conducting research and other studies; and (2) research and development of the Provider's educational sites, services, or applications, and to demonstrate the effectiveness of the Services; and (3) for adaptive learning purpose and for customized student learning. Provider's use of De-Identified Data shall survive termination of this DPA or any request by XXX to return or destroy Student Data. Except for Subprocessors, Xxxxxxxx agrees not to transfer de- identified Student Data to any party unless (a) that party agrees in writing not to attempt re-identification, and (b) prior written notice has been given to the LEA who has provided prior written consent for such transfer. Prior to publishing any document that names the LEA explicitly or indirectly, the Provider shall obtain the LEA’s written approval of the manner in which de-identified data is presented.
Data Subjects The categories of Data Subjects who we may collect Personal Data about may include the following where they are a natural person: the Customer, the directors and ultimate beneficial owner(s) of the Customer, your customers, employees and contractors, payers and payees. You may share with Airwallex some or all of the following types of Personal Data regarding Data Subjects: • full name; • email address; • phone number and other contact information; • date of birth; • nationality; • public information about the data subject; • other relevant verification or due diligence documentation as required under these terms; and • any other data that is necessary or relevant to carry out the Agreed Purposes.
If Identified If the HSP is Identified it will: (a) work towards applying the principles of Active Offer in the provision of services; (b) provide services to the public in French in accordance with its existing French language services capacity; (c) develop, and provide to the Funder upon request from time to time, a plan to become Designated by the date agreed to by the HSP and the Funder; (d) continuously work towards improving its capacity to provide services in French and toward becoming Designated within the time frame agreed to by the parties; (e) provide a report to the Funder that outlines progress in its capacity to provide services in French and toward becoming Designated; (f) annually, provide a report to the Funder that outlines how it addresses the needs of its local Francophone community; and (g) collect and submit to the Funder, as requested by the Funder from time to time, French language services data.
Categories of Data Subjects Any individual accessing and/or using the Services through the Customer's account ("Users"); and any individual: (i) whose email address is included in the Customer's Distribution List; (ii) whose information is stored on or collected via the Services, or (iii) to whom Users send emails or otherwise engage or communicate with via the Services (collectively, "Subscribers").
Data Segregation a. DSHS Data must be segregated or otherwise distinguishable from non-DSHS data. This is to ensure that when no longer needed by the Contractor, all DSHS Data can be identified for return or destruction. It also aids in determining whether DSHS Data has or may have been compromised in the event of a security breach. As such, one or more of the following methods will be used for data segregation. (1) DSHS Data will be kept on media (e.g. hard disk, optical disc, tape, etc.) which will contain no non-DSHS Data. And/or, (2) DSHS Data will be stored in a logical container on electronic media, such as a partition or folder dedicated to DSHS Data. And/or, (3) DSHS Data will be stored in a database which will contain no non-DSHS data. And/or, (4) DSHS Data will be stored within a database and will be distinguishable from non-DSHS data by the value of a specific field or fields within database records. (5) When stored as physical paper documents, DSHS Data will be physically segregated from non- DSHS data in a drawer, folder, or other container. b. When it is not feasible or practical to segregate DSHS Data from non-DSHS data, then both the DSHS Data and the non-DSHS data with which it is commingled must be protected as described in this exhibit.
Categories of Data Subject 2.1. When using this Service, the groups of individual’s data by category • Your end users using the service that you deliver • The personal data about your employees and contractors that bookinglab collects as a Customer of ours to complete account administration and set up
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. 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.
Covered Data All instances of "Student Data" should be replaced with "LEA Data". The protections provided within this DPA extend to all data provided to or collected by the Provider.
Customer Identification Program Notice To help the U.S. government fight the funding of terrorism and money laundering activities, U.S. Federal law requires each financial institution to obtain, verify, and record certain information that identifies each person who initially opens an account with that financial institution on or after October 1, 2003. Certain of PNC’s affiliates are financial institutions, and PNC may, as a matter of policy, request (or may have already requested) the Fund’s name, address and taxpayer identification number or other government-issued identification number, and, if such party is a natural person, that party’s date of birth. PNC may also ask (and may have already asked) for additional identifying information, and PNC may take steps (and may have already taken steps) to verify the authenticity and accuracy of these data elements.
Separate Identity The Seller acknowledges that the Collateral Agent, the Administrative Agent, the Lenders and the other Secured Parties are entering into the transactions contemplated by this Agreement and the Credit and Security Agreement in reliance upon the Buyer’s identity as a legal entity that is separate from the Seller and each other Affiliate of the Seller. Accordingly, from and after the date of execution and delivery of this Agreement, the Seller will take all reasonable steps, including all steps that the Buyer, the Collateral Agent or the Administrative Agent may from time to time reasonably request, to maintain the Buyer’s identity as a legal entity that is separate from the Seller and each other Affiliate of the Seller and to make it manifest to third parties that the Buyer is an entity with assets and liabilities distinct from those of the Seller and each other Affiliate thereof and not just a division of the Seller or any such other Affiliate. Without limiting the generality of the foregoing and in addition to the other covenants set forth herein, the Seller agrees that: (i) the Seller will take all other actions necessary on its part to ensure that the Buyer is at all times in compliance with Section 5.05 of the Credit and Security Agreement; (ii) the Seller shall maintain corporate records and books of account separate from those of the Buyer; (iii) the annual financial statements of the Seller shall disclose the effects of the Seller’s transactions in accordance with GAAP and the annual financial statements of the Seller shall note that the assets of the Buyer, including the Transferred Assets, are not available to pay creditors of the Seller or any other Affiliate of the Seller; (iv) the resolutions, agreements and other instruments underlying the transactions described in this Agreement shall be continuously maintained by the Seller as official records; (v) the Seller shall maintain an arm’s–length relationship with the Buyer and will not hold itself out as being liable for the debts of the Buyer; (vi) the Seller shall keep its assets and its liabilities wholly separate from those of the Buyer; and (vii) the Seller will avoid the appearance, and promptly correct any known misperception of any of the Seller’s creditors, that the assets of the Buyer are available to pay the obligations and debts of the Seller.
