No Sensitive Information; Security Sample Clauses

No Sensitive Information; Security. User acknowledges and agrees that HDG is not responsible for any sensitive information related to the use of the Solution, including but not limited to protected health information under HIPAA, credit card numbers, financial account numbers, or other similarly-sensitive personal information, and that User assumes all risk arising from the use of any such sensitive information with the Solution, including the risk of any inadvertent disclosure or unauthorized access thereto. User additionally acknowledges and agrees that User is solely responsible for maintaining the security of all usernames, passwords, and electronic devices used to access the Solution.
Sample 1
AutoNDA by SimpleDocs

Related to No Sensitive Information; Security

  • Sensitive Information Buyer will inform Licensor if Personal Data falls into any special categories of personal data as defined in Article 9(1) of Regulation (EU) 2016/679.

  • Contractor Sensitive Information 17.1 The Authority must:

  • COMMERCIALLY SENSITIVE INFORMATION 1. The Authority acknowledges that the Contractor has requested that the following information be treated as Commercially Sensitive Information; Document Page Number Section Condition or Paragraph Number Explanation of harm which may result from disclosure and time period applicable to sensitivity.

  • Handling Sensitive Personal Information and Breach Notification A. As part of its contract with HHSC Contractor may receive or create sensitive personal information, as section 521.002 of the Business and Commerce Code defines that phrase. Contractor must use appropriate safeguards to protect this sensitive personal information. These safeguards must include maintaining the sensitive personal information in a form that is unusable, unreadable, or indecipherable to unauthorized persons. Contractor may consult the “Guidance to Render Unsecured Protected Health Information Unusable, Unreadable, or Indecipherable to Unauthorized Individuals” issued by the U.S. Department of Health and Human Services to determine ways to meet this standard.

  • Information Security IET information security management practices, policies and regulatory compliance requirements are aimed at assuring the confidentiality, integrity and availability of Customer information. The UC Xxxxx Cyber-safety Policy, UC Xxxxx Security Standards Policy (PPM Section 310-22), is adopted by the campus and IET to define the responsibilities and key practices for assuring the security of UC Xxxxx computing systems and electronic data.

  • Personal Information security breach Supplier/Service Provider’s Obligations

  • NOXIOUS WEEDS DISCLOSURE Buyers of property in the State of Montana should be aware that some properties contain noxious weeds. The laws of the State of Montana require owners of property within this state to control, and to the extent possible, eradicate noxious weeds. For information concerning noxious weeds and your obligations as an owner of property, contact either your local County extension agent or Weed Control Board.

  • Use of De-identified information De-identified information may be used by the Contractor for the purposes of development, research, and improvement of educational sites, services, or applications, as any other member of the public or party would be able to use de-identified data pursuant to 34 CFR 99.31(b). Contractor agrees not to attempt to re-identify de-identified Student Data.

  • Negative Information Notice We may report information about your loan, share or deposit accounts to credit bureaus. Late payments, missed payments, or other defaults on your accounts may be reflected in your credit report.

  • Confidential Information Defined For the purposes of this ARR Agreement, “Confidential Information” means nonpublic proprietary information of a Party (the “Disclosing Party”) that is disclosed to another Party (each such Party, a “Receiving Party”), including but not limited to: (i) business or technical processes, formulae, source codes, object code, product designs, sales, cost and other unpublished financial information, customer information, product and business plans, projections, marketing data or strategies, trade secrets, intellectual property rights, know-how, expertise, methods and procedures for operation, information about employees, customer names, business or technical proposals, and any other information which is or should reasonably be understood to be confidential or proprietary to the Disclosing Party; and (ii) PII (as defined in Section 7.03 of this ARR Agreement). The foregoing definition of Confidential Information applies to: (i) all such information, whether tangible or intangible and regardless of the medium in which it is stored or presented; and (ii) all copies of such information, as well as all memoranda, notes, summaries, analyses, computer records, and other materials prepared by the Receiving Party or any of its employees, agents, advisors, directors, officers, and subcontractors (collectively “Representatives”) that contain or reflect the Confidential Information.

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