Content Takedowns Sample Clauses

Content Takedowns. 7.1 Takedown on your behalf. You may remove your Content from future distribution via myPOS AppMarket at any time, but you must comply with this Agreement. Removing your Contents from future distribution via myPOS AppMarket does not (a) affect the license rights of users who have previously purchased or downloaded your Contents, (b) remove your Contents from Devices or from any part of myPOS AppMarket where previously purchased or downloaded applications are stored on behalf of users, or (c) change your obligation to deliver or support Content that have been previously purchased or downloaded by users. Notwithstanding the foregoing, in no case will we maintain on myPOS AppMarket any Content that you have removed from myPOS AppMarket and provided written notice to myPOS AppMarket that such removal was due to (i) an allegation of infringement, or actual infringement, of any copyright, trademark, trade secret, trade dress, patent or other intellectual property right of any person, (ii) an allegation of defamation or actual defamation, (iii) an allegation of violation, or actual violation, of any third party's right of publicity or privacy, or (iv) an allegation or determination that such Content does not comply with applicable law. If you remove a Content from myPOS AppMarket pursuant to clauses (i), (ii), (iii) or (iv) of this Section 7.1, and an end user purchased such Content within a year before the date of takedown, you may be requested by us to refund to the affected end user all amounts paid by such end user for such affected Content.
AutoNDA by SimpleDocs
Content Takedowns 

Related to Content Takedowns

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry.

  • Content and Services Neither Licensor nor the provider of the wireless network is the provider of any financial services available through or related to the Software, and neither Licensor nor the provider of the wireless network or any contractor of the provider of the financial services available through or related to the Software, is responsible for any of the materials, information, products or services made available to you via the Software.

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