Data Issues Sample Clauses

The Data Issues clause defines how parties will address problems related to the quality, accuracy, or availability of data exchanged or used under the agreement. Typically, it outlines procedures for identifying, reporting, and resolving data discrepancies, such as requiring prompt notification if incorrect or incomplete data is discovered, and may specify responsibilities for correcting errors or compensating for data-related losses. This clause ensures that both parties have a clear process for managing data problems, thereby minimizing disruptions and allocating responsibility for data integrity.
Data Issues. 8.1. Tenderers are asked to address how they will manage data security and research ethics. 8.2. If primary qualitative research is required, the Agency requires a fully documented anonymised dataset, which it can use for its own analysis and research purposes. Tenderers must set out what documentation they would provide to accompany the dataset. 8.3. The dataset will require encrypted identifiers for each record, with a separate file to link these to names and contact details – which would be held securely by the Agency. Tenderers must set out what documentation they would provide to accompany the dataset. 8.4. As the Food Standards Agency is the data controller, it may wish to use the data for further research at a future date. Re-contact questions and supporting documentation must be phrased in such a way that participants are giving consent for the Agency or its selected agent to re-contact them. The contact data will only be used for research purposes and would only be handled by SSRU and IT Security staff.
View Source
Data Issues. Customer/End-User will have sole responsibility for the accuracy, quality, integrity, legality, reliability and appropriateness of all data, information, or material that Customer/End-User submits to the Dash Onboard during Customer/End-User’s access or use of the System. Except as permitted in this Agreement, ▇▇▇▇▇ will not edit, delete, or disclose the contents of Customer/End-User Data unless authorized by Customer/End-User or unless ▇▇▇▇▇ is required to do so by law or in the good faith belief that such action is necessary to: (i) conform with applicable laws or comply with legal process served on ▇▇▇▇▇; (ii) protect and defend the rights or property of ▇▇▇▇▇; or (iii) enforce this Agreement. ▇▇▇▇▇ may provide insight data or statistical data in aggregate form to third parties, but such information will not include identifying information. ▇▇▇▇▇ may access Customer/End-User data to respond to service or technical problems with the Dash Onboard or Platform. Customer will be responsible for any deletion, correction, destruction, damage, loss, or failure to store any Customer/End-User data in the Dash Onboard. ▇▇▇▇▇ reserves the right to establish a maximum amount of memory or other computer storage and a maximum amount of Customer/ End-User Data that may store, post, or transmit on or through the Dash Onboard or Platform. Customer/End-User may not upload advertisements or transmit unsolicited information, materials, spam, or data.
View Source
Data Issues. Where the Helpdesk determine that an issue raised by a User is related to the integrity of Customer data within the Solution where the integrity of that data has been compromised by the Solution itself as opposed to the actions or inactions of the Customer or Users then the Helpdesk will deal with that issue within this Agreement as either Software defect or Professional Services defect under clause 8 or clause 23 respectively.
View Source
Data Issues. Lead Generation and Co-Branded Sweepstakes Services may ----------- result in the development and/or collection of an HTML prospecting survey (the "Survey"); consumer data gathered from individuals responding to the Survey (the "Survey Data"); and for multiple question lead generation programs, such individuals' name, postal address, Survey Data and scoring analysis of the Survey Data (collectively, the "Respondent Data").
View Source
Data Issues 
View Source

Related to Data Issues

  • Open Issues (a) Notwithstanding any provision of the Registry Agreement to the contrary (including Sections 7.6 and 7.7 thereof), Registry Operator agrees that the following requirements, procedures and provisions of the Registry Agreement (including the documents incorporated by reference therein) may be modified and amended by ICANN after the date hereof, without the consent of Registry Operator: i. Specification 6 – Registry Interoperability and Continuity Specifications; ii. Trademark Clearinghouse Requirements (§ 1 of Specification 7 of the Registry Agreement); iii. Trademark Post-­‐Delegation Dispute Resolution Procedure (§ 2.a of Specification 7 of the Registry Agreement);

  • 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.

  • Data Integrity Policies and procedures to ensure the confidentiality, integrity, and availability of Customer Data or Professional Services Data and protect it from disclosure, improper alteration, or destruction.

  • Customer Relations A. Actively promote DCP Holding Company in all Marketing, Sales, Public Relations, and Community activity. B. Strategize that the DCP Holding Company product is placed effectively before the public with emphasis on “Agent/Broker” C. Continually monitor the success, quality and effectiveness of DCP Holding Company marketing

  • Data Exchange Except where prohibited by law or regulation, MCP and MHP must share the minimum necessary data and information to facilitate referrals and coordinate care under this MOU. The Parties must have policies and procedures for supporting the timely and frequent exchange of Member information and data, including behavioral health and physical health data; for ensuring the confidentiality of exchanged information and data; and, if necessary, for obtaining Member consent, when required. The minimum necessary information and data elements to be shared as agreed upon by the Parties, are set forth in Exhibit C of this MOU. To the extent permitted under applicable law, the Parties must share, at a minimum, Member demographic information, behavioral and physical health information, diagnoses, assessments, medications prescribed, laboratory results, referrals/discharges to/from inpatient or crisis services and known changes in condition that may adversely impact the Member’s health and/or welfare. The Parties must annually review and, if appropriate, update Exhibit C of this MOU to facilitate sharing of information and data. MHP and MCP must 4 CalAIM Data Sharing Authorization Guidance VERSION 2.0 June 2023 available at: ▇▇▇▇▇://▇▇▇.▇▇▇▇.▇▇.▇▇▇/Documents/MCQMD/CalAIM-Data-Sharing-Authorization- Guidance-Version-2- Draft-Public-Comment.pdf. establish policies and procedures to implement the following with regard to information sharing: i. A process for timely exchanging information about Members eligible for ECM, regardless of whether the Specialty Mental Health provider is serving as an ECM provider; ii. A process for MHP to send regular, frequent batches of referrals to ECM and Community Supports to MCP in as close to real time as possible; iii. A process for MHP to send admission, discharge, and transfer data to MCP when Members are admitted to, discharged from, or transferred from facilities contracted by MHP (e.g., psychiatric inpatient hospitals, psychiatric health facilities, residential mental health facilities), and for MCP to receive this data. This process may incorporate notification requirements as described in Section 8(a)(v)(3); iv. A process to implement mechanisms to alert the other Party of behavioral health crises (e.g., MHP alerts MCP of Members’ uses of mobile health, psych inpatient, and crisis stabilization and MCP alerts MHP of Members’ visits to emergency departments and hospitals); and v. A process for MCP to send admission, discharge, and transfer data to MHP when Members are admitted to, discharged from, or transferred from facilities contracted by MCP (e.g., emergency department, inpatient hospitals, nursing facilities), and for MHP to receive this data. This process may incorporate notification requirements as described in Section 8(a)(v)(3).