Device identifiers Sample Clauses

Device identifiers. When you access the Service by or through a mobile device (including but not limited to smart-phones or tablets), we may access, collect, monitor and/or remotely store one or more “device identifiers,” such as a universally unique identifier (“UUID”). Device identifiers are small data files or similar data structures stored on or associated with your mobile device, which uniquely identify your mobile device. A device identifier may be data stored in connection with the device hardware, data stored in connection with the device’s operating system or other software, or data sent to the device by the Service. A device identifier may convey information to us about how you browse and use the Service. A device identifier may remain persistently on your device, to help you log in faster and enhance your navigation through the Service. Some features of the Service may not function properly if use or availability of device identifiers is impaired or disabled.
AutoNDA by SimpleDocs
Device identifiers. When a user accesses the SERVICE by or through a mobile device, SERVICE PROVIDER may access, collect, monitor, and/or remotely store one or more device identifiers. SERVICE PROVIDER may use device identifiers to improve the SERVICE. The device identifier may provide SERVICE PROVIDER with information about how you use the SERVICE but it does not collect or share personally identifying information. However, a device identifier may be used in conjunction with personally

Related to Device identifiers

  • Indirect Identifiers Any information that, either alone or in aggregate, would allow a reasonable person to be able to identify a student to a reasonable certainty Information in the Student’s Educational Record Information in the Student’s Email

  • Non-Identification Approved Users agree not to use the requested datasets, either alone or in concert with any other information, to identify or contact individual participants from whom data and/or samples were collected. Approved Users also agree not to generate information (e.g., facial images or comparable representations) that could allow the identities of research participants to be readily ascertained. These provisions do not apply to research investigators operating with specific IRB approval, pursuant to 45 CFR 46, to contact individuals within datasets or to obtain and use identifying information under an 2 The project anniversary date can be found in “My Projects” after logging in to the dbGaP authorized-access portal. IRB-approved research protocol. All investigators including any Approved User conducting “human subjects research” within the scope of 45 CFR 46 must comply with the requirements contained therein.

  • Customer Identification Unless Elastic has first obtained Customer's prior written consent, Elastic shall not identify Customer as a user of the Products, on its website, through a press release issued by Elastic and in other promotional materials.

  • Customer Identification Program Notice To help the U.S. government fight the funding of terrorism and money laundering activities, U.S. Federal law requires each financial institution to obtain, verify, and record certain information that identifies each person who initially opens an account with that financial institution on or after October 1, 2003. Certain of PNC’s affiliates are financial institutions, and PNC may, as a matter of policy, request (or may have already requested) the Fund’s name, address and taxpayer identification number or other government-issued identification number, and, if such party is a natural person, that party’s date of birth. PNC may also ask (and may have already asked) for additional identifying information, and PNC may take steps (and may have already taken steps) to verify the authenticity and accuracy of these data elements.

  • Customer Identification Program (A) To assist the Fund in complying with requirements regarding a customer identification program in accordance with applicable regulations promulgated by U.S. Department of Treasury under Section 326 of the USA PATRIOT Act ("CIP Regulations"), BNYM will do the following: (i) Implement procedures which require that prior to establishing a new account in the Fund BNYM obtain the name, date of birth (for natural persons only), address and government-issued identification number (collectively, the "Data Elements") for the "Customer" (defined for purposes of this Agreement as provided in 31 CFR 1024.100(c)) associated with the new account. (ii) Use collected Data Elements to attempt to reasonably verify the identity of each new Customer promptly before or after each corresponding new account is opened. Methods of verification may consist of non-documentary methods (for which BNYM may use unaffiliated information vendors to assist with such verifications) and documentary methods (as permitted by 31 CFR 1024.220), and may include procedures under which BNYM personnel perform enhanced due diligence to verify the identities of Customers the identities of whom were not successfully verified through the first- level (which will typically be reliance on results obtained from an information vendor) verification process(es). (iii) Record the Data Elements and maintain records relating to verification of new Customers consistent with 31 CFR 1024.220(a)(3). (iv) Regularly report to the Fund about measures taken under (i)-(iii) above. (v) If BNYM provides services by which prospective Customers may subscribe for shares in the Fund via the Internet or telephone, BNYM will work with the Fund to notify prospective Customers, consistent with 31 CFR 1024.220(a)(5), about the program conducted by the Fund in accordance with the CIP Regulations. (B) To assist the Fund in complying with the Customer Due Diligence Requirements for Financial Institutions promulgated by FinCEN (31 CFR § 1020.230) pursuant to the Bank Secrecy Act ("CDD Rule"), BNYM will maintain and implement written procedures that are reasonably designed to: (i) Obtain information of a nature and in a manner permitted or required by the CCD Rule in order to identify each natural person who is a "beneficial owner" (as that term is defined in the CDD Rule) of a legal entity at the time that such legal entity seeks to open an account as a shareholder of the Fund, unless that legal entity is excluded from the CDD Rule or an exemption provided for in the CDD Rule applies; and (ii) Verify the identity of each beneficial owner so identified according to risk based procedures to the extent reasonable and practicable, in accordance with the minimum requirements of the CDD Rule. (C) Nothing in Section (3) shall be construed to require BNYM to perform any course of conduct that is not required for Fund compliance with the CIP Regulations or CDD Rule, including by way of illustration not limitation the collection of Data Elements or verification of identity for individuals opening Fund accounts through financial intermediaries which use the facilities of the NSCC. (D) BNYM agrees to permit inspections relating to the CIP services provided hereunder by U.S. Federal departments or regulatory' agencies with appropriate jurisdiction and to make available to examiners from such departments or regulatory agencies such information and records relating to the CIP services provided hereunder as such examiners shall reasonably request.

  • Domain Name Data 1.5.1 Query format: whois EXAMPLE.TLD 1.5.2 Response format:

  • If Identified If the HSP is Identified it will: (a) work towards applying the principles of Active Offer in the provision of services; (b) provide services to the public in French in accordance with its existing French language services capacity; (c) develop, and provide to the Funder upon request from time to time, a plan to become Designated by the date agreed to by the HSP and the Funder; (d) continuously work towards improving its capacity to provide services in French and toward becoming Designated within the time frame agreed to by the parties; (e) provide a report to the Funder that outlines progress in its capacity to provide services in French and toward becoming Designated; (f) annually, provide a report to the Funder that outlines how it addresses the needs of its local Francophone community; and (g) collect and submit to the Funder, as requested by the Funder from time to time, French language services data.

  • Partnership Formation and Identification 6 2.1 Formation............................................................................................ 6 2.2 Name, Office and Registered Agent.................................................................... 6 2.3 Partners............................................................................................. 6 2.4

  • Product Information EPIZYME recognizes that by reason of, inter alia, EISAI’s status as an exclusive licensee in the EISAI Territory under this Agreement, EISAI has an interest in EPIZYME’s retention in confidence of certain information of EPIZYME. Accordingly, until the end of all Royalty Term(s) in the EISAI Territory, EPIZYME shall keep confidential, and not publish or otherwise disclose, and not use for any purpose other than to fulfill EPIZYME’s obligations, or exercise EPIZYME’s rights, hereunder any EPIZYME Know-How Controlled by EPIZYME or EPIZYME Collaboration Know-How, in each case that are primarily applicable to EZH2 or EZH2 Compounds (the “Product Information”), except to the extent (a) the Product Information is in the public domain through no fault of EPIZYME, (b) such disclosure or use is expressly permitted under Section 9.3, or (c) such disclosure or use is otherwise expressly permitted by the terms and conditions of this Agreement. For purposes of Section 9.3, each Party shall be deemed to be both the Disclosing Party and the Receiving Party with respect to Product Information. For clarification, the disclosure by EPIZYME to EISAI of Product Information shall not cause such Product Information to cease to be subject to the provisions of this Section 9.2 with respect to the use and disclosure of such Confidential Information by EPIZYME. In the event this Agreement is terminated pursuant to Article 12, this Section 9.2 shall have no continuing force or effect, but the Product Information, to the extent disclosed by EPIZYME to EISAI hereunder, shall continue to be Confidential Information of EPIZYME, subject to the terms of Sections 9.1 and 9.3 for purposes of the surviving provisions of this Agreement. Each Party shall be responsible for compliance by its Affiliates, and its and its Affiliates’ respective officers, directors, employees and agents, with the provisions of Section 9.1 and this Section 9.2.

  • Vendor Identity and Contact Information It is Vendor’s sole responsibility to ensure that all identifying vendor information (name, EIN, d/b/a’s, etc.) and contact information is updated and current at all times within the TIPS eBid System and the TIPS Vendor Portal. It is Vendor’s sole responsibility to confirm that all e-correspondence issued from xxxx-xxx.xxx, xxxxxxx.xxx, and xxxxxxxxxxxxxxxx.xxx to Vendor’s contacts are received and are not blocked by firewall or other technology security. Failure to permit receipt of correspondence from these domains and failure to keep vendor identity and contact information current at all times during the life of the contract may cause loss of TIPS Sales, accumulating TIPS fees, missed rebid opportunities, lapse of TIPS Contract(s), and unnecessary collection or legal actions against Vendor. It is no defense to any of the foregoing or any breach of this Agreement that Vendor was not receiving TIPS’ electronic communications issued by TIPS to Vendor’s listed contacts.

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