User Registration System Sample Clauses

User Registration System. During the term of this Agreement, AvantGo agrees ------------------------- to host and maintain a web-based user registration facility ("User Registration System") to record and deliver user registration information to Microsoft. The user registration information shall consist of information regarding End Users who wish to register that they are owners of a Windows CE Device. AvantGo may, as part of the registration process, allow such (i) End User data for all End User registrations made during the applicable month in the form identical to AvantGo's standard registration application subject to AvantGo's published privacy policy, provided such End User has authorized the use of such information; (ii) a demographic and usage pattern summary profiling End Users to the extent that AvantGo creates such summaries; and (iii) the total and monthly number of number of Windows CE registrations completed through the User Registration System. In consideration of AvantGo's hosting and collection of such data and provision of the monthly Report, Microsoft shall pay [******]($[******]) for each Acknowledged New Registration. An "Acknowledged New Registration" shall not include any End User of Windows CE already known to Microsoft and shall be identified by Microsoft by comparing the registrations listed in the Report with registrations of Windows CE End Users collected independently by, or on behalf of, Microsoft. Within thirty (30) days of receipt of each Report, Microsoft shall report to AvantGo the number of Acknowledged New Registrations. AvantGo shall invoice Microsoft quarterly for the number of Acknowledged New Registrations. Microsoft shall pay AvantGo within thirty (30) days from receipt of such invoice. Demographic and usage pattern summary information regarding the Windows CE End Users shall not be shared with developers of operating system platforms except as aggregated with data for other operating systems platforms.
AutoNDA by SimpleDocs
User Registration System. Section 4.4 of the Agreement shall be deleted in its entirety and replaced with the following:
User Registration System. The System may have functionality to allow registration of Commuter/user of Nagpur Metro by email, mobile number and allows to linkup the Metro Card if available at the time of Registration with the User/Commuter. The System may also allow to buy the Metro Card and accordingly complete the KYC inside the System.

Related to User Registration System

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

  • DTC DIRECT REGISTRATION SYSTEM AND PROFILE MODIFICATION SYSTEM (a) Notwithstanding the provisions of Section 2.04, the parties acknowledge that the Direct Registration System (“DRS”) and Profile Modification System (“Profile”) shall apply to uncertificated American Depositary Shares upon acceptance thereof to DRS by DTC. DRS is the system administered by DTC pursuant to which the Depositary may register the ownership of uncertificated American Depositary Shares, which ownership shall be evidenced by periodic statements issued by the Depositary to the Owners entitled thereto. Profile is a required feature of DRS which allows a DTC participant, claiming to act on behalf of an Owner of American Depositary Shares, to direct the Depositary to register a transfer of those American Depositary Shares to DTC or its nominee and to deliver those American Depositary Shares to the DTC account of that DTC participant without receipt by the Depositary of prior authorization from the Owner to register such transfer. (b) In connection with and in accordance with the arrangements and procedures relating to DRS/Profile, the parties understand that the Depositary will not verify, determine or otherwise ascertain that the DTC participant which is claiming to be acting on behalf of an Owner in requesting a registration of transfer and delivery as described in subsection (a) has the actual authority to act on behalf of the Owner (notwithstanding any requirements under the Uniform Commercial Code). For the avoidance of doubt, the provisions of Sections 5.03 and 5.08 shall apply to the matters arising from the use of the DRS. The parties agree that the Depositary’s reliance on and compliance with instructions received by the Depositary through the DRS/Profile System and in accordance with this Deposit Agreement shall not constitute negligence or bad faith on the part of the Depositary.

  • Voter Registration When designated by the Secretary of State, the Contractor agrees to become a voter registration agency as defined by 17 V.S.A. §2103 (41), and to comply with the requirements of state and federal law pertaining to such agencies.

  • Vendor Registration In order to complete any transaction between a Customer and the Contractor, the Contractor must be registered in MyFloridaMarketPlace.

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

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

  • Registration and Listing 15 Section 3.3

  • SEC Registration The Parties mutually agree to use commercially reasonable efforts to maintain effective registration statements with the Securities and Exchange Commission with respect to the long-term incentive awards to the extent any such registration statement is required by applicable Law.

  • Effectiveness of Registration No Shares shall be offered by either you or the Fund under any of the provisions of this Agreement and no orders for the purchase or sale of such Shares under this Agreement shall be accepted by the Fund if and so long as the effectiveness of the registration statement then in effect or any necessary amendments thereto shall be suspended under any of the provisions of the 1933 Act, or if and so long as a current prospectus as required by Section 5(b) (2) of the 1933 Act is not on file with the SEC; provided, however, that nothing contained in this paragraph 5 shall in any way restrict or have any application to or bearing upon the Fund's obligation to repurchase its Shares from any shareholder in accordance with the provisions of the Fund's prospectus, statement of additional information or charter documents, as amended from time to time.

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