Registration and Use of Your Account Sample Clauses

Registration and Use of Your Account 
AutoNDA by SimpleDocs

Related to Registration and Use of Your Account

  • Registration Data Upon placing an order for Pilot Voice, and at subsequent times as requested by Pilot, Customer agrees to provide Pilot with its (i) true, accurate, current, and complete business name, (ii) physical addresses where Voice Service will be used, (iii) 911 registered address for each applicable endpoint, (iv) a designated Account Administrator, and (v) user email addresses, phone numbers, and any other requested data which may be necessary to administer its Voice Service account (the “Account”) (collectively, “Registration Data”). Customer represents and warrants that the information it provides is accurate, current, and complete, and agrees to promptly update any of the information if it changes. If Customer provides Registration Data that is false, inaccurate, not current, incomplete, fraudulent, or otherwise unlawful, Pilot has the right, in its sole discretion, to suspend or terminate the Voice Services and refuse any and all current or future use of all Voice Services by Customer, its business(es), affiliates and all users of its Account. Upon provision of all Registration Data and acceptance of Customer’s Service Order, Pilot may provide Customer’s designated Account Administrator and other Pilot Voice users with, as applicable, administrator or user web portal logins and other Account information. Customer is solely liable for any transactions or activities by it or any third- party that occurs on its Account. Customer shall immediately notify Pilot of any unauthorized use of its Account or if any other breach of security has occurred. In no event shall Pilot be liable for any unauthorized, third-party use of your Account.

  • REGISTRATION OF EZ2BID 3.1 E-bidders will log in into ESZAM AUCTIONEER SDN BHD secured website. E-bidders shall provide true, current and accurate information to register as a user.

  • Registration of Agreement The registration of License agreements should be done within 30 days of signing of agreement, the licensee/ lessee (registration fees, stamp duty etc to be fully borne by the licensee/lessee) and the duly registered documents to be submitted to Maha-Metro for records. Any amendment in the contract agreement, if required to be registered, shall also be registered within 30 days from the date of amendment and duly registered documents shall be submitted to Maha-Metro for record. In case the registration of the license/lease agreement /amendment is not done within the 30 days of signing of license/lease agreement/ amendment, it shall be treated as “Material Breach of Contract”. The Licensee will be given 30 days time to cure the defaults In case Licensee fail to remedify the default to the satisfaction of the Maha-Metro within the cure period, Maha-Metro may terminate the License agreement after expiry of cure period duly forfeiting the security deposit/ any other amount paid by Licensee.

  • Publication of Registration Data Registry Operator shall provide public access to registration data in accordance with Specification 4 attached hereto (“Specification 4”).

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

  • 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 (a) No later than the Filing Date, the Company shall file with the Commission the Initial Registration Statement relating to the resale by the Holders of all (or such other number as the Commission will permit) of the Registrable Securities. If Form S-3 is not available for the registration of the resale of Registrable Securities hereunder, the Company shall (i) register the resale of the Registrable Securities on another appropriate form and (ii) undertake to register the Registrable Securities on Form S-3 as soon as such form is available; provided that the Company shall maintain the effectiveness of the Registration Statement then in effect until such time as a Registration Statement on Form S-3 covering the Registrable Securities has been declared effective by the Commission. Subject to the terms of this Agreement, the Company shall use its best efforts to cause a Registration Statement filed under this Agreement (including, without limitation, under Section 3(c)) to be declared effective under the Securities Act within forty-five (45) days after the filing thereof, but in any event no later than the applicable Effectiveness Date, and shall use its best efforts to keep such Registration Statement continuously effective under the Securities Act until all Registrable Securities covered by such Registration Statement (i) have been sold, thereunder or pursuant to Rule 144, or (ii) may be sold without volume or manner-of-sale restrictions pursuant to Rule 144 and without the requirement for the Company to be in compliance with the current public information requirement under Rule 144, as determined by the counsel to the Company pursuant to a written opinion letter to such effect, addressed and acceptable to the Transfer Agent and the affected Holder (the “Effectiveness Period”). The Company shall telephonically request effectiveness of a Registration Statement as of 5:00 p.m. Eastern Time on a Trading Day. The Company shall immediately notify the Holder via facsimile or by e-mail of the effectiveness of a Registration Statement on the same Trading Day that the Company telephonically confirms effectiveness with the Commission, which shall be the date requested for effectiveness of such Registration Statement. The Company shall, by 9:30 a.m. Eastern Time on the Trading Day after the effective date of such Registration Statement, file a final Prospectus with the Commission as required by Rule 424. Failure to so notify the Holders within one (1) Trading Day of such notification of effectiveness or failure to file a final Prospectus as foresaid shall be deemed an Event under Section 2(g).

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

  • 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 of Contractors Contractor and all subcontractors must comply with the requirements of labor code section 1771.1(a), pertaining to registration of contractors pursuant to section 1725.5. Registration and all related requirements of those sections must be maintained throughout the performance of the Contract.

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