Uses of Data Sample Clauses

Uses of Data. Whilst the DPA has defined these three classes of data, some categories within these classifications will have different levels of risk associated with them and WDP has therefore, defined sub-categories of the classes based on intended use and the risk associated with those sub-categories.
Sample 1Sample 2
AutoNDA by SimpleDocs
Uses of Data. Recipient shall share Provider’s aggregated De-identified Data with other SIM PCMH participants for purposes including population health analysis, quality improvement, and utilization measures.
Sample 1Sample 2
Uses of Data. (a) TCS certifies that it will use the Services (including the Models) only in connection with one of the following needs with respect to a consumer: (i) for use as necessary to effect, administer or enforce a transaction requested or authorized by the consumer; (ii) to protect against or prevent actual or potential fraud, unauthorized transactions, claims or other liabilities; (iii) for required institutional risk control; (iv) for resolving consumer disputes or inquiries; (v) due to holding a legal or beneficial interest relating to the consumer; (vi) for use by persons acting with the consumer's consent in a fiduciary or representative capacity on behalf of the consumer; (vii) for use in complying with federal, state or local laws, rules and other applicable legal requirements; or (viii) for use and to the extent specifically permitted or required under other provisions of law and in accordance with the Right to Financial Privacy Act of 1978, to law enforcement agencies (including a Federal functional regulator, the Secretary of Treasury, a State insurance authority or the Federal Trade Commission), self-regulatory organizations or for an investigation on a matter related to public safety. TCS further certifies that its use of RiskWise products will be limited, on a product-by-product basis, to that purpose (or purposes) set forth next to such product on Exhibit A of the Strategic Modeling Agreement. TCS will comply with all applicable laws in connection with its use of the RiskWise information services. (b) RiskWise does not intend for a Model or other Services generated under this Agreement to constitute a "consumer report" as defined in the Fair Credit Reporting Act, 15 U.S.C. ss. 1681 et. seq. ("FCRA"). TCS is specifically prohibited from using RiskWise's Models or other Services, in whole or part, as a factor in establishing any consumer's eligibility for credit, insurance, employment purposes, or any other permissible purpose of consumer reports as defined by the FCRA. It is expressly forbidden for TCS to take "adverse action" as defined by the FCRA on any customer request using information supplied by RiskWise pursuant to this Agreement. TCS represents and warrants to RiskWise that any "adverse action" taken with respect to a consumer request will be based solely on information received from sources other than RiskWise. Furthermore, TCS warrants that it will not identify RiskWise in any declination communication with the consumer as having provid...
Sample 1
Uses of Data. (a) The Client is specifically prohibited from using RiskWise's scores or other data services, in whole or part, as a factor in establishing any consumer's eligibility for credit, insurance, employment purposes, or any other permissible purpose of consumer reports as defined by the FCRA. It is permissible for the Client to use the information to verify prospective customer information, to determine whether to authorize purchases or to request additional information from the prospective customer via telephone, mail or e-mail communication, to confirm or verify the information provided on the prospective customer's order or application. It is expressly forbidden for Client to take "adverse action" as defined by the FCRA on any customer request using information supplied by RiskWise pursuant to this Agreement. (b) Client represents and warrants that its use and/or disclosure of the RiskWise scores or other data services shall be in accordance with Individual Reference Service Industry Principles (developed by the Individual Reference Services Group ("IRSG")), as such principles currently exist and as they may be modified in the future. Specifically, Client shall ensure that RiskWise scores or other data services are accessed and utilized by Client in a secure and controlled manner, including, but not limited to, data security and limiting data access to personnel that have a legitimate business reason to see such information. In addition, Client agrees that it will limit its use of the RiskWise scores or other data services to fraud prevention and detection, data verification, debtor location and general risk management services.
Sample 1
Uses of Data. Coordinate housing services for families and individuals experiencing homelessness or facing a housing crisis in the Northwest MN region,
Sample 1
Uses of Data. DFSS reserves the right to use data related to Delegate Agency performance, including but not limited to data submitted by the Delegate Agency, for the following:
Sample 1
Uses of Data. While both Departments may separately assess and match data in different ways and conduct a variety of assessments involving the lead screening data and the Medicaid data, both Departments shall: - Discuss preliminary results with the Work Group, with representatives from both departments in attendance; - Present findings of preliminary matches to the Work Group for feedback, clarification, and reanalysis if needed; - Ensure findings are reviewed and agreed to by the Work Group and other appropriate representatives from both departments to assure that the findings are scientifically sound and the limitations and potential biases are clearly delineated for the purpose of which the findings will be utilized, as well as to assure that confidentiality of medical information has been appropriately maintained; - Develop a joint dissemination plan and select formal and semi-formal channels to publish reports, updates, or other products of the collaboration and data analysis; - Ensure that information is tailored to meet the specific goal and audience; - Prominently credit the other agency for providing part of the necessary data in all publicly distributed uses of data covered by this agreement. Nothing here prohibits the regular data analysis and reporting activities of the two departments, which do not utilize data generated from the other department. Neither agency shall publish or present data or results based on data from the other agency without written consent of the other agency, via the Workgroup.
Sample 1
AutoNDA by SimpleDocs
Uses of Data. Whilst the Data Protection Act has defined these three classes of data, some categories within these classifications will have different levels of risk associated with them and Amplitude has therefore, defined sub-categories of the classes based on intended use and the risk associated with those sub-categories.
Sample 1
Uses of Data. A service of quality
Sample 1

Related to Uses of Data

  • Use of Data (a) In connection with the provision of the services and the discharge of its other obligations under this Agreement, State Street (which term for purposes of this Section XXIX includes each of its parent company, branches and affiliates (''Affiliates")) may collect and store information regarding a Trust and share such information with its Affiliates, agents and service providers in order and to the extent reasonably necessary (i) to carry out the provision of services contemplated under this Agreement and other agreements between the Trusts and State Street or any of its Affiliates and (ii) to carry out management of its businesses, including, but not limited to, financial and operational management and reporting, risk management, legal and regulatory compliance and client service management.

  • Use of Data by User Registry Operator will permit user to use the zone file for lawful purposes; provided that (a) user takes all reasonable steps to protect against unauthorized access to and use and disclosure of the data and (b) under no circumstances will Registry Operator be required or permitted to allow user to use the data to, (i) allow, enable, or otherwise support the transmission by email, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than user’s own existing customers, or (ii) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator or any ICANN-­‐accredited registrar.

  • Loss of Data In the event of loss of any State data or records where such loss is due to the intentional act, omission, or negligence of the Contractor or any of its subcontractors or agents, the Contractor shall be responsible for recreating such lost data in the manner and on the schedule set by the Contract Manager. The Contractor shall ensure that all data is backed up and is recoverable by the Contractor.

  • Rights of Data Subjects 5.1 You control access to Your Services environment that holds Personal Information about Your end users, and Your end users should direct any requests related to their rights under Applicable Data Protection Law to You. 5.2 To the extent such access is not available to You, Oracle will provide assistance with requests from individuals to access, delete or erase, restrict, rectify, receive and transmit, block access to or object to processing related to Personal Information held in Your Services environment on Oracle systems, insofar as reasonably and technically possible. 5.3 If Oracle directly receives any requests or inquiries from Your end users that have identified You as the Controller, it will promptly pass on such requests to You without responding to the end user.

  • Categories of Data Data relating to individuals provided to Google via the Services, by (or at the direction of) Customer or End Users. Data subjects include the individuals about whom data is provided to Google via the Services by (or at the direction of) Customer or End Users.

  • Protection of Data The Contractor agrees to store Data on one or more of the following media and protect the Data as described: a. Hard disk drives. For Data stored on local workstation hard disks, access to the Data will be restricted to Authorized User(s) by requiring logon to the local workstation using a Unique User ID and Hardened Password or other authentication mechanisms which provide equal or greater security, such as biometrics or smart cards. b. Network server disks. For Data stored on hard disks mounted on network servers and made available through shared folders, access to the Data will be restricted to Authorized Users through the use of access control lists which will grant access only after the Authorized User has authenticated to the network using a Unique User ID and Hardened Password or other authentication mechanisms which provide equal or greater security, such as biometrics or smart cards. Data on disks mounted to such servers must be located in an area which is accessible only to authorized personnel, with access controlled through use of a key, card key, combination lock, or comparable mechanism. For DSHS Confidential Information stored on these disks, deleting unneeded Data is sufficient as long as the disks remain in a Secure Area and otherwise meet the requirements listed in the above paragraph. Destruction of the Data, as outlined below in Section 8 Data Disposition, may be deferred until the disks are retired, replaced, or otherwise taken out of the Secure Area. c. Optical discs (CDs or DVDs) in local workstation optical disc drives. Data provided by DSHS on optical discs which will be used in local workstation optical disc drives and which will not be transported out of a Secure Area. When not in use for the contracted purpose, such discs must be Stored in a Secure Area. Workstations which access DSHS Data on optical discs must be located in an area which is accessible only to authorized personnel, with access controlled through use of a key, card key, combination lock, or comparable mechanism. d. Optical discs (CDs or DVDs) in drives or jukeboxes attached to servers. Data provided by DSHS on optical discs which will be attached to network servers and which will not be transported out of a Secure Area. Access to Data on these discs will be restricted to Authorized Users through the use of access control lists which will grant access only after the Authorized User has authenticated to the network using a Unique User ID and Hardened Password or other authentication mechanisms which provide equal or greater security, such as biometrics or smart cards. Data on discs attached to such servers must be located in an area which is accessible only to authorized personnel, with access controlled through use of a key, card key, combination lock, or comparable mechanism.

  • Source of Data A description of (1) the process used to identify claims in the Population, and (2) the specific documentation relied upon by the IRO when performing the Quarterly Claims Review (e.g., medical records, physician orders, certificates of medical necessity, requisition forms, local medical review policies (including title and policy number), CMS program memoranda (including title and issuance number), Medicare contractor manual or bulletins (including issue and date), other policies, regulations, or directives).‌‌‌

  • Retention of Data With regard to business transactions covered by this Agreement, Licensee must retain any records for a period of ten years starting on 1th of January of the year following the year during which the data were transmitted or otherwise transferred, or for the minimum period prescribed by applicable law, whichever is longer. In addition, Licensee must maintain current, complete and accurate reports on all of SAP’s Confidential Information in its possession or in the possession of its representatives.

  • Marking of Data Pursuant to Paragraph A above, any Data delivered under this Agreement shall be marked with the following legend: Use, duplication, or disclosure is subject to the restrictions as stated in Agreement HR0011-XX-9-XXXX between the Government and the Performer.

  • Identification of Data a. All Background, Third Party Proprietary and Controlled Government Data provided by Disclosing Party shall be identified in the Annex under which it will be provided. b. NASA software and related Data provided to Partner shall be identified in the Annex under which it will be used. Notwithstanding H.4., Software and related Data will be provided to Partner under a separate Software Usage Agreement (SUA). Partner shall use and protect the related Data in accordance with this Article. Unless the SUA authorizes retention, or Partner enters into a license under 37 C.F.R. Part 404, the related Data shall be disposed of as instructed by NASA.

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