Personal Data That You Provide Through Registration Sample Clauses

Personal Data That You Provide Through Registration. We may collect Personal Data from you when you register with the Site and create an account, including your e-mail address and device identification number. We do not collect any credit card or other financial account information, driver’s license numbers and/or social security numbers.
AutoNDA by SimpleDocs

Related to Personal Data That You Provide Through Registration

  • Company to Provide Copy of the Prospectus in Form That May be Downloaded from the Internet If requested by the Representatives, the Company shall cause to be prepared and delivered, at its expense, within one business day from the effective date of this Agreement, to the Representatives an “electronic Prospectus” to be used by the Underwriters in connection with the offering and sale of the Offered Shares. As used herein, the term “electronic Prospectus” means a form of Time of Sale Prospectus, and any amendment or supplement thereto, that meets each of the following conditions: (i) it shall be encoded in an electronic format, satisfactory to the Representatives, that may be transmitted electronically by the Representatives and the other Underwriters to offerees and purchasers of the Offered Shares; (ii) it shall disclose the same information as the paper Time of Sale Prospectus, except to the extent that graphic and image material cannot be disseminated electronically, in which case such graphic and image material shall be replaced in the electronic Prospectus with a fair and accurate narrative description or tabular representation of such material, as appropriate; and (iii) it shall be in or convertible into a paper format or an electronic format, satisfactory to the Representatives, that will allow investors to store and have continuously ready access to the Time of Sale Prospectus at any future time, without charge to investors (other than any fee charged for subscription to the Internet as a whole and for on-line time). The Company hereby confirms that it has included or will include in the Prospectus filed pursuant to XXXXX or otherwise with the Commission and in the Registration Statement at the time it was declared effective an undertaking that, upon receipt of a request by an investor or his or her representative, the Company shall transmit or cause to be transmitted promptly, without charge, a paper copy of the Time of Sale Prospectus.

  • Authorization to Release and Transfer Necessary Personal Information The Grantee hereby explicitly and unambiguously consents to the collection, use and transfer, in electronic or other form, of the Grantee’s personal data by and among, as applicable, the Company and its Subsidiaries for the exclusive purpose of implementing, administering and managing the Grantee’s participation in the Plan. The Grantee understands that the Company may hold certain personal information about the Grantee, including, but not limited to, the Grantee’s name, home address and telephone number, date of birth, social security number (or any other social or national identification number), salary, nationality, job title, number of Award Units and/or shares of Common Stock held and the details of all Award Units or any other entitlement to shares of Common Stock awarded, cancelled, vested, unvested or outstanding for the purpose of implementing, administering and managing the Grantee’s participation in the Plan (the “Data”). The Grantee understands that the Data may be transferred to the Company or to any third parties assisting in the implementation, administration and management of the Plan, that these recipients may be located in the Grantee’s country or elsewhere, and that any recipient’s country (e.g., the United States) may have different data privacy laws and protections than the Grantee’s country. The Grantee understands that he or she may request a list with the names and addresses of any potential recipients of the Data by contacting his or her local human resources representative or the Company’s stock plan administrator. The Grantee authorizes the recipients to receive, possess, use, retain and transfer the Data, in electronic or other form, for the sole purpose of implementing, administering and managing the Grantee’s participation in the Plan, including any requisite transfer of such Data to a broker or other third party assisting with the administration of Award Units under the Plan or with whom shares of Common Stock acquired pursuant to the vesting of the Award Units or cash from the sale of such shares may be deposited. Furthermore, the Grantee acknowledges and understands that the transfer of the Data to the Company or to any third parties is necessary for the Grantee’s participation in the Plan. The Grantee understands that the Grantee may, at any time, view the Data, request additional information about the storage and processing of the Data, require any necessary amendments to the Data or refuse or withdraw the consents herein by contacting the Grantee’s local human resources representative or the Company’s stock plan administrator in writing. The Grantee further acknowledges that withdrawal of consent may affect his or her ability to vest in or realize benefits from the Award Units, and the Grantee’s ability to participate in the Plan. For more information on the consequences of refusal to consent or withdrawal of consent, the Grantee understands that he or she may contact his or her local human resources representative or the Company’s stock plan administrator.

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

  • Effect of Failure to File and Obtain and Maintain Effectiveness of any Registration Statement If (i) a Registration Statement covering the resale of all of the Registrable Securities required to be covered thereby (disregarding any reduction pursuant to Section 2(f)) and required to be filed by the Company pursuant to this Agreement is (A) not filed with the SEC on or before the Filing Deadline for such Registration Statement (a “Filing Failure”) (it being understood that if the Company files a Registration Statement without affording each Investor and Legal Counsel the opportunity to review and comment on the same as required by Section 3(c) hereof, the Company shall be deemed to not have satisfied this clause (i)(A) and such event shall be deemed to be a Filing Failure) or (B) not declared effective by the SEC on or before the Effectiveness Deadline for such Registration Statement (an “Effectiveness Failure”) (it being understood that if on the Business Day immediately following the Effective Date for such Registration Statement the Company shall not have filed a “final” prospectus for such Registration Statement with the SEC under Rule 424(b) in accordance with Section 3(b) (whether or not such a prospectus is technically required by such rule), the Company shall be deemed to not have satisfied this clause (i)(B) and such event shall be deemed to be an Effectiveness Failure), (ii) other than during an Allowable Grace Period (as defined below), on any day after the Effective Date of a Registration Statement sales of all of the Registrable Securities required to be included on such Registration Statement (disregarding any reduction pursuant to Section 2(f)) cannot be made pursuant to such Registration Statement (including, without limitation, because of a failure to keep such Registration Statement effective, a failure to disclose such information as is necessary for sales to be made pursuant to such Registration Statement, a suspension or delisting of (or a failure to timely list) the shares of Common Stock on the Principal Market (as defined in the Securities Purchase Agreement) or any other limitations imposed by the Principal Market, or a failure to register a sufficient number of shares of Common Stock or by reason of a stop order) or the prospectus contained therein is not available for use for any reason (a “Maintenance Failure”), or (iii) if a Registration Statement is not effective for any reason or the prospectus contained therein is not available for use for any reason, and either (x) the Company fails for any reason to satisfy the requirements of Rule 144(c)(1), including, without limitation, the failure to satisfy the current public information requirement under Rule 144(c) or (y) the Company has ever been an issuer described in Rule 144(i)(1)(i) or becomes such an issuer in the future, and the Company shall fail to satisfy any condition set forth in Rule 144(i)(2) (a “Current Public Information Failure”) as a result of which any of the Investors are unable to sell Registrable Securities without restriction under Rule 144 (including, without limitation, volume restrictions), then, as partial relief for the damages to any holder by reason of any such delay in, or reduction of, its ability to sell the underlying shares of Common Stock (which remedy shall not be exclusive of any other remedies available at law or in equity, including, without limitation, specific performance), the Company shall pay to each holder of Registrable Securities relating to such Registration Statement an amount in cash equal to two percent (2%) of such Investor’s original principal amount stated in such Investor’s Note on the Closing Date (1) on the date of such Filing Failure, Effectiveness Failure, Maintenance Failure or Current Public Information Failure, as applicable, and (2) on every thirty (30) day anniversary of (I) a Filing Failure until such Filing Failure is cured; (II) an Effectiveness Failure until such Effectiveness Failure is cured; (III) a Maintenance Failure until such Maintenance Failure is cured; and (IV) a Current Public Information Failure until the earlier of (i) the date such Current Public Information Failure is cured and (ii) such time that such public information is no longer required pursuant to Rule 144 (in each case, pro rated for periods totaling less than thirty (30) days). The payments to which a holder of Registrable Securities shall be entitled pursuant to this Section 2(e) are referred to herein as “Registration Delay Payments.” Following the initial Registration Delay Payment for any particular event or failure (which shall be paid on the date of such event or failure, as set forth above), without limiting the foregoing, if an event or failure giving rise to the Registration Delay Payments is cured prior to any thirty (30) day anniversary of such event or failure, then such Registration Delay Payment shall be made on the third (3rd) Business Day after such cure. In the event the Company fails to make Registration Delay Payments in a timely manner in accordance with the foregoing, such Registration Delay Payments shall bear interest at the rate of two percent (2%) per month (prorated for partial months) until paid in full. Notwithstanding the foregoing, no Registration Delay Payments shall be owed to an Investor (other than with respect to a Maintenance Failure resulting from a suspension or delisting of (or a failure to timely list) the shares of Common Stock on the Principal Market) with respect to any period during which all of such Investor’s Registrable Securities may be sold by such Investor without restriction under Rule 144 (including, without limitation, volume restrictions) and without the need for current public information required by Rule 144(c)(1) (or Rule 144(i)(2), if applicable).

  • Registration Information Customer shall be responsible for the accuracy and legality of all account, Agent, and registration information (including without limitation Customer’s legal name and payment information, Customer/Agent contact information, and any personal data included therein) (“Registration Information”) and the means of its acquisition.

  • Handling Sensitive Personal Information and Breach Notification A. As part of its contract with HHSC Contractor may receive or create sensitive personal information, as section 521.002 of the Business and Commerce Code defines that phrase. Contractor must use appropriate safeguards to protect this sensitive personal information. These safeguards must include maintaining the sensitive personal information in a form that is unusable, unreadable, or indecipherable to unauthorized persons. Contractor may consult the “Guidance to Render Unsecured Protected Health Information Unusable, Unreadable, or Indecipherable to Unauthorized Individuals” issued by the U.S. Department of Health and Human Services to determine ways to meet this standard. B. Contractor must notify HHSC of any confirmed or suspected unauthorized acquisition, access, use or disclosure of sensitive personal information related to this Contract, including any breach of system security, as section 521.053 of the Business and Commerce Code defines that phrase. Contractor must submit a written report to HHSC as soon as possible but no later than 10 business days after discovering the unauthorized acquisition, access, use or disclosure. The written report must identify everyone whose sensitive personal information has been or is reasonably believed to have been compromised. C. Contractor must either disclose the unauthorized acquisition, access, use or disclosure to everyone whose sensitive personal information has been or is reasonably believed to have been compromised or pay the expenses associated with HHSC doing the disclosure if: 1. Contractor experiences a breach of system security involving information owned by HHSC for which disclosure or notification is required under section 521.053 of the Business and Commerce Code; or 2. Contractor experiences a breach of unsecured protected health information, as 45 C.F.R. §164.402 defines that phrase, and HHSC becomes responsible for doing the notification required by 45 C.F.R. §164.404. HHSC may, at its discretion, waive Contractor's payment of expenses associated with HHSC doing the disclosure.

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

  • Dissemination of Research Findings and Acknowledgement of Controlled-Access Datasets Subject to the NIH GDS Policy

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

  • Abuse and Neglect of Children and Vulnerable Adults: Abuse Registry Party agrees not to employ any individual, to use any volunteer or other service provider, or to otherwise provide reimbursement to any individual who in the performance of services connected with this agreement provides care, custody, treatment, transportation, or supervision to children or to vulnerable adults if there has been a substantiation of abuse or neglect or exploitation involving that individual. Party is responsible for confirming as to each individual having such contact with children or vulnerable adults the non-existence of a substantiated allegation of abuse, neglect or exploitation by verifying that fact though (a) as to vulnerable adults, the Adult Abuse Registry maintained by the Department of Disabilities, Aging and Independent Living and (b) as to children, the Central Child Protection Registry (unless the Party holds a valid child care license or registration from the Division of Child Development, Department for Children and Families). See 33 V.S.A. §4919(a)(3) and 33 V.S.A. §6911(c)(3).

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