End User Requests Sample Clauses

The 'End User Requests' clause defines the procedures and conditions under which end users may submit requests related to the product or service, such as support inquiries, feature enhancements, or data access. Typically, this clause outlines the acceptable channels for submitting requests, any required information, and the expected response times or limitations. Its core function is to establish a clear and efficient process for handling end user communications, ensuring that requests are managed consistently and expectations are set for both parties.
End User Requests. In the event that Apple receives any requests from End Users for a copy of their Personal Data in connection with the Service, Apple will either reasonably (i) enable You to manage such requests directly, such as through available tools in the Web Portal, or (ii) cooperate with You to handle such requests to the extent such requests involve Personal Data that Apple has access to. If You choose to allow Apple to provide a copy of an End User’s Personal Data in its privacy portal at ▇▇▇▇▇▇▇.▇▇▇▇▇.▇▇▇ through the Web Portal, You hereby instruct Apple, upon the End User’s request, to process and fulfil such End User’s request to access their data as available on ▇▇▇▇▇▇▇.▇▇▇▇▇.▇▇▇ on Your behalf.
View SourceView Similar (9)
End User Requests. IBM will not independently respond to requests from Client's End Users without Client's prior written consent, except where required by applicable law.
View SourceView Similar (3)
End User Requests. During the Term, if Google receives any request from an End User for records relating to that End User’s personal data included in the Customer Data, Google will advise such End User to submit its request to Customer. Customer will be responsible for responding to any such request using the functionality of the Services.
View SourceView Similar (3)
End User Requests. If any End User requests Komo to provide them with information relating to Processing of their Personal Information, or to make changes to their Personal Information, then Komo will promptly notify the Customer of the request, unless otherwise required by applicable law. The Customer may make changes to User data using the features and functionality of the Komo Platform. Komo will not make changes to User data except as agreed in writing with the Customer.
View SourceView Similar (3)
End User Requests. Microsoft will not independently respond to requests from Customer’s End Users without Customer’s prior written consent, except where required by applicable law.
View SourceView Similar (2)
End User Requests. Client will, at its own expense, respond to questions and complaints from End Users or third parties. Client will use commercially reasonable efforts to resolve support issues before escalating them to PredPol. Should Client need to escalate the issue to PredPol, contact will be made in accordance with Notices, Section 14.B.
View Source
End User Requests. We will, to the extent legally permitted, promptly notify you if an End User seeks to exercise its data subject access and related rights under applicable law through us instead of you, and we will reasonably cooperate with you to fulfill your obligations provided that you are responsible for any reasonable costs arising therefrom.
View Source
End User Requests. CLIENT will, at its own expense, respond to questions and complaints from End Users or third parties. CLIENT will use commercially reasonable efforts to resolve support issues before escalating them to PREDPOL. Should CLIENT need to escalate the issue to PREDPOL, contact will be made in accordance with Notices, Section 14.B.
View Source
End User Requests. If any End User requests Mercero to provide them with information relating to Processing of their Personal Data, or to make changes to their Personal Data, then Mercero will promptly notify Customer of the request, unless otherwise required by applicable law. Customer may make changes to User data using the features and functionality of the Mercero Platform. Mercero will not make changes to User data except as agreed
View Source

Related to End User Requests

  • Transfer Requests The Partnership agrees to use its Reasonable Best Efforts to promptly process, and to cause the Exchange Agent to promptly process, all sale or other transfer requests relating to the Contributor Units that are exempt from the registration requirements of the Securities Act.

  • Stop Payment Order Request Any owner may request a stop payment order on any check or draft drawn on the owner’s account. To be binding, the order must be in writing, dated and signed, and must accurately describe the check or draft, including the exact account number, the check or draft number, and the exact amount of the check or draft. This exact information is necessary for the Credit Union’s computer to identify the check or draft. If we receive incorrect or incomplete information, we will not be responsible for failing to stop payment on the check or draft. In addition, we must receive sufficient advance notice of the stop payment order to allow us a reasonable opportunity to act on it. If we recredit your account after paying a check or draft over a valid and timely stop payment order, you agree to sign a statement describing the dispute with the payee, to assign to us all of your rights against the payee or other holders of the check or draft, and to assist us in any legal action.

  • Data Subject Requests To the extent legally permitted, Okta shall promptly notify Customer if Okta receives a request from a Data Subject to exercise the Data Subject's right of access, right to rectification, restriction of Processing, erasure (“right to be forgotten”), data portability, object to the Processing, or its right not to be subject to an automated individual decision making (“Data Subject Request”). Factoring into account the nature of the Processing, Okta shall assist Customer by appropriate organizational and technical measures, insofar as this is possible, for the fulfilment of Customer’s obligation to respond to a Data Subject Request under Data Protection Laws and Regulations. In addition, to the extent Customer, in its use of the Service, does not have the ability to address a Data Subject Request, Okta shall, upon Customer’s request, provide commercially- reasonable efforts to assist Customer in responding to such Data Subject Request, to the extent that Okta is legally authorized to do so, and the response to such Data Subject Request is required under Data Protection Laws and Regulations. To the extent legally permitted, Customer shall be responsible for any costs arising from Okta’s provision of such assistance.

  • Government End Users The Apple Software and related documentation are “Commercial Items”, as that term is defined at 48 C.F.R. §2.101, consisting of “Commercial Computer Software” and “Commercial Computer Software Documentation”, as such terms are used in 48 C.F.R. §12.212 or 48

  • Customer Requirements Customer will be required to maintain complex passwords for their User accounts where applicable. For any such passwords LightEdge will provide a secure URL that any User can access to change passwords. All User passwords are set to a ninety (90) day password expiration schedule by default. LightEdge is not responsible for unexpected use of Services whether by ex-employees, compromised User passwords or any other misuse of Customer accounts. Customer shall be responsible for all costs incurred by such unexpected use of Service. Customer shall be fully responsible for providing to LightEdge at Customer’s own expense and in a timely manner the following: - All security for its Services and systems used or accessible in connection with Service; - Cooperative testing of all Customer-provided hardware, software, and Services for compatibility with Service; - Designating an Authorized Contact(s) to be the point of contact to interface with LightEdge Technical Support; - All cabling necessary to support Service; and - Physical and remote management access to any and all Servers onto which Service is installed.