Data Held Sample Clauses

The 'Data Held' clause defines the types of data that a party collects, stores, or processes under the agreement. It typically outlines the categories of information involved, such as personal data, business records, or technical logs, and may specify the purposes for which this data is retained. By clearly identifying what data is held and under what circumstances, this clause ensures transparency and helps both parties understand their responsibilities regarding data management and compliance with relevant data protection laws.
Data Held. The following is a list of the types of data relating to you that will be held by Company and may be deemed “personal data”: (a) data about you, including your name, nickname, office address, office telephone, mobile telephone, pager and facsimile number, office email address, email mailing list memberships, direct reports, country of citizenship (necessary for access controls on export-controlled information), Company Directory Initiative (“CDI”) ID (a database identifier assigned by Company), whether you are a prior Company employee, whether Supplier has performed a satisfactory background check on you, and whether you have signed certain agreements and acknowledgements that may apply to your assignment, such as this Personal Data Consent Form, Assignment Limitation Acknowledgement, Company Integrity Acknowledgement, Network Access Agreement, End User License Agreement, and Secrecy and Invention Agreement; and (b) data about your Company assignment, including the name of the assignment, your job title on the assignment, your function (work skill) on the assignment, your role within that function, your assignment location, your contract type (i.e., fixed price, time & materials, etc.), your hourly billing rate, your normal billing hours per week, your assignment start date, assignment target end date and assignment actual end date, the payment method for your services, Purchase Order (“PO”) number, Request for Proposal (“RFP”) number, Funding Cost Center Code, and Cost Tracking Type used for the assignment, and whether a Purchase Service Agreement was signed; and (c) data about projects you work on while in the assignment, including Contingent Worker’s Project ID number, the project name, project description, the name of the Company IT Organization leading the project, the Company business unit supported by the project, the Company function supported by the project, the primary technology used on the project, and the Company-assigned category of the project (such as Make, Buy or Sell, and RTS or Program); and (d) data about your employer (Company’s Supplier), such as Supplier’s name, the Supplier’s primary contact person’s name, telephone number and email address, the percentage of Company ownership in Supplier, whether Supplier is a Minority/Women Owned Enterprise (yes/no), whether Supplier has signed a Master Services Agreement (“MSA”) with Company (yes/no, MSA Effective Date, MSA end date); and (e) data about your Company Assignment Leader, such as his...
View SourceView Similar (7)

Related to Data Held

  • Data Use Each party may use Connected Account Data in accordance with this Agreement and the consent (if any) each obtains from each Connected Account. This consent includes, as to Stripe, consent it receives via the Connected Account Agreement.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • Investment; Access to Data The undersigned has carefully reviewed and understands the risks of, and other considerations relating to, a purchase of the Common Stock and an investment in the Company. The undersigned has been furnished materials relating to the Company, the private placement of the Common Stock or anything else that it has requested and has been afforded the opportunity to ask questions and receive answers concerning the terms and conditions of the offering and obtain any additional information which the Company possesses or can acquire without unreasonable effort or expense. Representatives of the Company have answered all inquiries that the undersigned has made of them concerning the Company, or any other matters relating to the formation and operation of the Company and the offering and sale of the Common Stock. The undersigned has not been furnished any offering literature other than the materials that the Company may have provided at the request of the undersigned; and the undersigned has relied only on such information furnished or made available to the undersigned by the Company as described in this Section. The undersigned is acquiring the Shares for investment for the undersigned's own account, not as a nominee or agent and not with the view to, or for resale in connection with, any distribution thereof. The undersigned acknowledges that the Company is a start-up company with no current operations, assets or operating history, which may possibly cause a loss of Purchaser’s entire investment in the Company.

  • Access to Data Operator shall make Data in the possession of the Operator available to the LEA within five (5) business days of a request by the LEA.

  • Data Segregation a. DSHS Data must be segregated or otherwise distinguishable from non-DSHS data. This is to ensure that when no longer needed by the Contractor, all DSHS Data can be identified for return or destruction. It also aids in determining whether DSHS Data has or may have been compromised in the event of a security breach. As such, one or more of the following methods will be used for data segregation. (1) DSHS Data will be kept on media (e.g. hard disk, optical disc, tape, etc.) which will contain no non-DSHS Data. And/or, (2) DSHS Data will be stored in a logical container on electronic media, such as a partition or folder dedicated to DSHS Data. And/or, (3) DSHS Data will be stored in a database which will contain no non-DSHS data. And/or, (4) DSHS Data will be stored within a database and will be distinguishable from non-DSHS data by the value of a specific field or fields within database records. (5) When stored as physical paper documents, DSHS Data will be physically segregated from non- DSHS data in a drawer, folder, or other container. b. When it is not feasible or practical to segregate DSHS Data from non-DSHS data, then both the DSHS Data and the non-DSHS data with which it is commingled must be protected as described in this exhibit.