Box AI Sample Clauses

Box AI i. Customer is solely responsible for the production and retention of outputs using Box AI in compliance with the Agreement, the then-current Box AI Acceptable Use Policy & Guiding Principles, and all applicable laws. All output generated by Box AI is done at the User’s direction and is stored in Content (a) at the User’s sole discretion and/or (b) as an outcome of a Customer workflow or API Call. Box AI outputs are not human generated or filtered by humans and cannot not be represented by user as human work product. Box is not responsible for the accuracy or biases of the output or Customer’s reliance on Box AI output. Box AI queries and outputs are Customer’s Confidential Information but are not Content. ii. A User direction to process a Box AI query qualifies as Customer consent for the modification, aggregation, deidentification or other Processing of Confidential Information for purposes of generating output. Notwithstanding the above, Box will not train Box AI using Customer queries or outputs without explicit consent.
View SourceView Similar (3)
Box AI i. Customer is solely responsible for the production and retention of outputs using Box AI in compliance with the Agreement, the then-current Box AI Acceptable Use Policy & Guiding Principles, and all applicable laws. All output generated by Box AI is created at the User’s direction and is stored in Content (a) at the User’s sole discretion and/or (b) as an outcome of a Customer workflow or API Call. Box AI outputs are not human generated or filtered by humans and cannot be represented by Customer as human work product. Box is not responsible for the accuracy or biases of the output or Customer’s reliance on Box AI output. Box AI queries and outputs are Customer’s Confidential Information but are not Content. ii. A User direction to process a Box AI query qualifies as Customer consent for the modification, aggregation, deidentification or other Processing of Confidential Information for purposes of generating output. Notwithstanding the above, Box will not train Box AI using Customer queries or outputs without explicit consent. iii. To the extent Users enter personal data or other sensitive information subject to regulatory oversight in Box AI queries, Customer and not Box has sole responsibility for providing any legally adequate privacy notices and obtaining any necessary consents for such Processing. iv. Box shall not be responsible for, and shall not have any obligation regarding, any use of Box AI which relies on queries that infringe on any proprietary right of a third party or any use of outputs in a manner which infringes on any proprietary right of a third party.
View Source

Related to Box AI

  • Consent to Emails and Automated Text Messages By participating as a Zelle User, you represent that you are the owner of the email address, mobile phone number, and/or other alias you enroll, or that you have the delegated legal authority to act on behalf of the owner of such email address, mobile phone number and/or other alias to send or receive money as described in this Agreement. You consent to the receipt of emails or text messages from us, from Zelle, from other Users that are sending you money or requesting money from you, and from other Network Banks or their agents regarding the Zelle Service or related transfers between Network Banks and you. You agree that we, Zelle, or either of our agents may use automatic telephone dialing systems in connection with text messages sent to any mobile phone number you enroll. You further acknowledge and agree: ▪ You are responsible for any fees or other charges that your wireless carrier may charge for any related data, text or other message services, including without limitation for short message service. Please check your mobile service agreement for details or applicable fees. ▪ You will immediately notify us if any email address or mobile phone number you have enrolled is (i) surrendered by you, or (ii) changed by you. ▪ In the case of any messages that you may send through either us or Zelle or that we may send or Zelle may send on your behalf to an email address or mobile phone number, you represent that you have obtained the consent of the recipient of such emails or automated text messages to send such emails or text messages to the recipient. You understand and agree that any emails or text messages that we send or that ▇▇▇▇▇ sends on your behalf may include your name. ▪ Your wireless carrier is not liable for any delay or failure to deliver any message sent to or from us or Zelle, including messages that you may send through us or through Zelle or that we may send or Zelle may send on your behalf. ▪ To cancel text messaging from us, text STOP to 20736. For help or information regarding text messaging, text HELP to 20736 or contact our customer service at ▇.▇▇▇.▇▇▇.▇▇▇▇ or ▇.▇▇▇.▇▇▇.▇▇▇▇. You expressly consent to receipt of a text message to confirm your “STOP” request. ▪ Our Zelle notifications are supported by many carriers, such as AT&T, Verizon Wireless, T- Mobile, and Sprint. Check with your individual carrier to confirm availability. ▪ We or Zelle may use information on file with your wireless operator to further verify your identity and to protect against or prevent actual or potential fraud or unauthorized use of the Zelle Service. By using the Zelle Service, you authorize your wireless operator (AT&T, Sprint, T-Mobile, US Cellular, Verizon, or any other branded wireless operator) to disclose your mobile number, name, address, email, network status, customer type, customer role, billing type, mobile device identifiers (IMSI and IMEI) and other subscriber status and device details, if available, to our third party service provider solely to allow verification of your identity and to compare information you have provided to us or to Zelle with your wireless operator account profile information for the duration of our business relationship. See ▇▇▇▇▇’▇ Privacy Policy [▇▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/privacy-policy] for how it treats your data. Please review our Privacy Policy for more information.

  • 240104 Vendor Agreement (Part If responding to Part 1, the Vendor Agreement must be downloaded from the “Attachments” section of the IonWave eBid System, reviewed, Vendor Name placed in the line provided at the top, and uploaded to this location. If Vendor has proposed deviations to the Vendor Agreement (Part 1), Vendor may assert so in the Attribute Questions and those shall be addressed during evaluation.

  • Joint Funded Project with the Ohio Department of Transportation In the event that the Recipient does not have contracting authority over project engineering, construction, or right-of-way, the Recipient and the OPWC hereby assign certain responsibilities to the Ohio Department of Transportation, an authorized representative of the State of Ohio. Notwithstanding Sections 4, 6(a), 6(b), 6(c), and 7 of the Project Agreement, Recipient hereby acknowledges that upon notification by the Ohio Department of Transportation, all payments for eligible project costs will be disbursed by the Grantor directly to the Ohio Department of Transportation. A Memorandum of Funds issued by the Ohio Department of Transportation shall be used to certify the estimated project costs. Upon receipt of a Memorandum of Funds from the Ohio Department of Transportation, the OPWC shall transfer funds directly to the Ohio Department of Transportation via an Intra- State Transfer Voucher. The amount or amounts transferred shall be determined by applying the Participation Percentages defined in Appendix D to those eligible project costs within the Memorandum of Funds. In the event that the Project Scope is for right-of-way only, notwithstanding Appendix D, the OPWC shall pay for 100% of the right-of-way costs not to exceed the total financial assistance provided in Appendix C.

  • Cloud Computing State Risk and Authorization Management Program (TX-RAMP In accordance with Senate Bill 475, Acts 2021, 87th Leg., R.S., pursuant to Texas Government Code, Section 2054.0593, Contractor acknowledges and agrees that, if providing cloud computing services for System Agency, Contractor must comply with the requirements of the state risk and authorization management program and that System Agency may not enter or renew a contract with Contractor to purchase cloud computing services for the agency that are subject to the state risk and authorization management program unless Contractor demonstrates compliance with program requirements. If providing cloud computing services for System Agency that are subject to the state risk and authorization management program, Contractor certifies it will maintain program compliance and certification throughout the term of the Contract.

  • END USER AGREEMENTS (“EUA GAC acknowledges that the END USER may choose to enter into an End User Agreement (“EUA) with the Contractor through this Agreement, and that the term of the EUA may exceed the term of the current H-GAC Agreement. H-GAC’s acknowledgement is not an endorsement or approval of the End User Agreement’s terms and conditions. Contractor agrees not to offer, agree to or accept from the END USER, any terms or conditions that conflict with those in Contractor’s Agreement with H-GAC. Contractor affirms that termination of its Agreement with H-GAC for any reason shall not result in the termination of any underlying EUA, which shall in each instance, continue pursuant to the EUA’s stated terms and duration. Pursuant to the terms of this Agreement, termination of this Agreement will disallow the Contractor from entering into any new EUA with END USERS. Applicable H-GAC order processing charges will be due and payable to H-GAC