REGISTRATION DATABASE Sample Clauses

REGISTRATION DATABASE. Xxxxxxxxx.xxx intends to maintain a Registration Database. [*] Trimark acknowledges that xxxxxxxxx.xxx does not make any representations or warranties regarding the reliability or accuracy of the Registration Database for these purposes. Trimark shall treat the Registration Database as xxxxxxxxx.xxx's Confidential Information, and Trimark shall not have the right to sell or license the contents of the Registration Database or any portion thereof to any third parties, or to make any other use thereof, without xxxxxxxxx.xxx's express, written consent.
AutoNDA by SimpleDocs
REGISTRATION DATABASE. Vendor agrees to provide access to its database of customers who purchase or subscribe to its products and/or services as a result of the bundle with USR products hereunder. The information to be made available to USR shall include the customers' names, addresses, phone numbers, fax numbers, email addresses, and any other customer data gathered during the Vendor's registration process. USR or its authorized representative may, at USR's expense and upon reasonable notice, obtain this information in a mutually agreed upon format on a quarterly basis. All information obtained by USR or its authorized representative shall be deemed Confidential Information and used solely for the purpose of USR's marketing and research programs.
REGISTRATION DATABASE. Client acknowledges that Provider will maintain a database of registered COR for Kindergarten users. Information contained in such database shall be treated as Confidential Information of the HighScope, Inc., and the Provider, as that term is defined herein.
REGISTRATION DATABASE. To the extent that the AG Parties are legally able to do so, it shall give Mindscape reasonable access to its database of customer names which has been accumulated from software registration of the CreataCard series of products.

Related to REGISTRATION DATABASE

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

  • 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, etc Each Pledgor agrees that, upon the occurrence and during the continuance of an Event of Default hereunder, if for any reason the Collateral Agent desires to sell any of the Pledged Securities of the Borrower at a public sale, it will, at any time and from time to time, upon the written request of the Collateral Agent, use its best efforts to take or to cause the issuer of such Pledged Securities to take such action and prepare, distribute and/or file such documents, as are required or advisable in the reasonable opinion of counsel for the Collateral Agent to permit the public sale of such Pledged Securities. Each Pledgor further agrees to indemnify, defend and hold harmless the Collateral Agent, each other Secured Party, any underwriter and their respective officers, directors, affiliates and controlling persons from and against all loss, liability, expenses, costs of counsel (including, without limitation, reasonable fees and expenses to the Collateral Agent of legal counsel), and claims (including the costs of investigation) that they may incur insofar as such loss, liability, expense or claim arises out of or is based upon any alleged untrue statement of a material fact contained in any prospectus (or any amendment or supplement thereto) or in any notification or offering circular, or arises out of or is based upon any alleged omission to state a material fact required to be stated therein or necessary to make the statements in any thereof not misleading, except insofar as the same may have been caused by any untrue statement or omission based upon information furnished in writing to such Pledgor or the issuer of such Pledged Securities by the Collateral Agent or any other Secured Party expressly for use therein. Each Pledgor further agrees, upon such written request referred to above, to use its best efforts to qualify, file or register, or cause the issuer of such Pledged Securities to qualify, file or register, any of the Pledged Securities under the Blue Sky or other securities laws of such states as may be requested by the Collateral Agent and keep effective, or cause to be kept effective, all such qualifications, filings or registrations. Each Pledgor will bear all costs and expenses of carrying out its obligations under this Section 12. Each Pledgor acknowledges that there is no adequate remedy at law for failure by it to comply with the provisions of this Section 12 and that such failure would not be adequately compensable in damages, and therefore agrees that its agreements contained in this Section 12 may be specifically enforced.

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

  • USER REGISTRATION You may be required to register with the Site. You agree to keep your password confidential and will be responsible for all use of your account and password. We reserve the right to remove, reclaim, or change a username you select if we determine, in our sole discretion, that such username is inappropriate, obscene, or otherwise objectionable.

  • Registration Process In connection with the registration of the Registrable Securities pursuant to Section 5.2.1, the Company shall: (a) Prepare and file with the SEC the Registration Statement and such amendments (including post effective amendments) to the Registration Statement and supplements to the prospectus included therein (a “Prospectus”) as the Company may deem necessary or appropriate and take all lawful action such that the Registration Statement and any amendment thereto does not, when it becomes effective, contain an untrue statement of a material fact or omit to state a material fact required to be stated therein or necessary to make the statements therein, not misleading and that the Prospectus forming part of the Registration Statement, and any amendment or supplement thereto, does not at any time during the period commencing on the effective date of the Registration Statement and ending on the date on which all of the Registrable Securities may be sold to the public without registration under the Securities Act in reliance on Rule 144 (the “Registration Period”) include an untrue statement of a material fact or omit to state a material fact required to be stated therein or necessary to make the statements therein, in light of the circumstances under which they were made, not misleading; (b) Comply with the provisions of the Securities Act with respect to the Registrable Securities covered by the Registration Statement until the earlier of (i) such time as all of such Registrable Securities have been disposed of in accordance with the intended methods of disposition by each Purchaser as set forth in the Prospectus forming part of the Registration Statement or (ii) the date on which the Registration Statement is withdrawn; (c) Furnish to each Purchaser and its legal counsel identified to the Company (i) promptly after the same is prepared and publicly distributed, filed with the SEC, or received by the Company, one copy of the Registration Statement, each Prospectus, and each amendment or supplement thereto, and (ii) such number of copies of the Prospectus and all amendments and supplements thereto and such other documents, as the Purchaser may reasonably request in order to facilitate the disposition of the Registrable Securities; (d) Register or qualify the Registrable Securities covered by the Registration Statement under such securities or “blue sky” laws of such jurisdictions as the Purchasers reasonably request, (ii) prepare and file in such jurisdictions such amendments (including post effective amendments) and supplements to such registrations and qualifications as may be necessary to maintain the effectiveness thereof at all times during the Registration Period, (iii) take all such other lawful actions as may be necessary to maintain such registrations and qualifications in effect at all times during the Registration Period, and (iv) take all such other lawful actions reasonably necessary or advisable to qualify the Registrable Securities for sale in such jurisdictions; provided, however, that the Company shall not be required in connection therewith or as a condition thereto to (A) qualify to do business in any jurisdiction where it would not otherwise be required to qualify, (B) subject itself to general taxation in any such jurisdiction or (C) file a general consent to service of process in any such jurisdiction; (e) As promptly as practicable after becoming aware of such event, notify each Purchaser of the occurrence of any event, as a result of which the Prospectus included in the Registration Statement, as then in effect, includes an untrue statement of a material fact or omits to state a material fact required to be stated therein or necessary to make the statements therein, in light of the circumstances under which they were made, not misleading, and promptly prepare an amendment to the Registration Statement and supplement to the Prospectus to correct such untrue statement or omission, and deliver a number of copies of such supplement and amendment to each Purchaser as such Purchaser may reasonably request; (f) As promptly as practicable after becoming aware of such event, notify each Purchaser (or, in the event of an underwritten offering, the managing underwriters) of the issuance by the SEC of any stop order or other suspension of the effectiveness of the Registration Statement and take all lawful action to effect the withdrawal, rescission or removal of such stop order or other suspension; (g) Take all such other lawful actions reasonably necessary to expedite and facilitate the disposition by the Purchaser of its Registrable Securities in accordance with the intended methods therefor provided in the Prospectus which are customary under the circumstances; (h) In the event of an underwritten offering, promptly include or incorporate in a Prospectus supplement or post-effective amendment to the Registration Statement such information as the underwriters reasonably agree should be included therein and to which the Company does not reasonably object and make all required filings of such Prospectus supplement or post-effective amendment as soon as practicable after it is notified of the matters to be included or incorporated in such Prospectus supplement or post-effective amendment; (i) In connection with any underwritten offering, deliver such documents and certificates as may be reasonably required by the underwriters; and (j) Cooperate with the Purchasers to facilitate the timely preparation and delivery of certificates representing Registrable Securities to be sold pursuant to the Registration Statement, which certificates shall, if required under the terms of this Agreement, be free of all restrictive legends, and to enable such Registrable Securities to be in such denominations and registered in such names as any Purchaser may request and maintain a transfer agent for the Common Stock.

  • 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. 1.1. The format of responses shall follow a semi-­‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database. 1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value. 1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together. 1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.

  • NERC Registration The NTO shall register or enter into agreement with a NERC registered entity for all required NERC functions applicable to the NTO, that may include, without limitation, those functions designated by NERC to be: “Transmission Owner” and “Transmission Planner” and “Transmission Operator.” The Parties agree to negotiate in good faith the compliance obligations for the NERC functions applicable to, and to be performed by, each Party with respect to the NTO’s facilities. Notwithstanding the foregoing, the ISO shall register for the “Transmission Operator” function for all NTO Transmission Facilities under ISO Operational Control identified in Appendix A-1 of this Agreement.

  • 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. 3.2 For individual bidder(s): The E-bidder’s need to key in their personal information (correspondence address & telephone contact number) accurately for online registration and upload the bidder’s NRIC (both sides) to ESZAM AUCTIONEER SDN BHD website.

  • Registration The terms “register,” “registered,” and “registration” refer to a registration effected by preparing and filing a registration statement in compliance with the Securities Act, and the declaration or ordering of effectiveness of such registration statement.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!