Data Takedown Sample Clauses

Data Takedown. By making any Data publicly available in the manner aforementioned, You expressly agree that GiaSpace will have the right to block access to or remove such Data made available by You, if GiaSpace receives complaints, inquiries or notices concerning any illegality or infringement of rights in such Data. You expressly consent to having GiaSpace determine questions of illegality or infringement of rights in such Data.
AutoNDA by SimpleDocs

Related to Data Takedown

  • Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-­‐to-­‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.

  • Service Registration Certain of our Services require you to register to use them. In such case, you agree that a l information you provide is truthful, current and complete. If there is any change to your registration information, you agree to provide us with updated information immediately. To the extent any of the Services are password protected, you agree to keep such password confidential and not to share it with any third party. You also agree that you wil not access any Services for which a password is required by using any third party’s password. If you discover any use of your password other than by you, you agree to immediately notify us. If you become aware of unauthorized account access, you similarly agree to immediately notify us. At the end of any use of a password protected Service, you agree to exit and logout out of your user session. Under no circumstances sha l we be responsible for any loss or damage that may result if you fail to comply with these requirements.

  • Unbundled Voice Loop – SL2 (UVL-SL2 Loops may be 2-wire or 4-wire circuits, shall have remote access test points, and will be designed with a DLR provided to NewPhone. SL2 circuits can be provisioned with loop start, ground start or reverse battery signaling. OC is provided as a standard feature on XX0 Xxxxx. The OC feature will allow NewPhone to coordinate the installation of the Loop with the disconnect of an existing customer’s service and/or number portability service. In these cases, BellSouth will perform the order conversion with standard order coordination at its discretion during normal work hours.

  • Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.

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

  • Registration Process In connection with the registration of the Registrable Securities pursuant to Section 4.1, the Company shall:

  • School-Initiated Closure Should the School choose to voluntarily surrender this Contract before the end of the Contract term, it may do so in consultation with the Commission at the close of any school year and upon written notice to the Commission given at least ninety (90) days before the end of the school year.

  • Registration for E - Bidders 4.1. Parties who are interested to participate in public auction as (“E-Bidders”) may do so by logging on to the Auctioneer’s website and register as a user.

  • PRICING for Markup of Non-Prepriced Items in RS Means Unit Price Book What is your proposed Markup Percentage on materials not found in the RS Means Price Book? If any materials being utilized for a project cannot be found in the RS Means Price Book, this question is what is the markup percentage on those materials? When answering this question please insert the number that represents your percentage of proposed markup. Example: if you are proposing a 30 percent markup, please insert the number "30". Remember that this is a ceiling markup. You may markup a lesser percentage to the TIPS Member customer when pricing the project, but not a greater percentage. EXAMPLE: You need special materials that are not in the RS Means Unit Price Book for a project. You would buy the materials and mark them up to the TIPS Member customer by the percentage you propose in this question. If the materials cost you, the contractor, $100 and you proposed a markup on this question for the material of 30 percent, then you would charge the TIPS Member customer $130 for the materials.

  • EPP query-­‐command RTT Refers to the RTT of the sequence of packets that includes the sending of a query command plus the reception of the EPP response for only one EPP query command. It does not include packets needed for the start or close of either the EPP or the TCP session. EPP query commands are those described in section 2.9.2 of EPP RFC 5730. If the RTT is 5-­‐times or more the corresponding SLR, the RTT will be considered undefined.

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