Data Masking Sample Clauses

Data Masking. The End User hereby warrants that any and all Data provided by the End User to the Managed Service Provider shall be transmitted to the Managed Service Provider in Masked format. The End User hereby indemnifies the Managed Service Provider, its Affiliates and/or the Licensor, including their officers, employees, agents and subcontractors, from and against any and all claims, liabilities, losses, damages and costs arising from or relating to Data that is shared by the End User with the Managed Service Provider in a format other than Masked format.
AutoNDA by SimpleDocs
Data Masking. Where access to personal data is required for testing, development or analytical purposes, the provider employs data masking techniques to conceal and protect sensitive data.

Related to Data Masking

  • Data Management Contractor will not use State data, including production data, for testing or development purposes unless authorized in writing by the State Chief Information Security Officer or delegate. Contractor will implement and maintain procedures to physically and logically segregate State data, unless otherwise explicitly authorized by the State Chief Information Security Officer or delegate.

  • Data Mining 4.1. Provider agrees not to use GLO Data for unrelated commercial purposes, advertising or advertising-related services, or for any other purpose not explicitly authorized by the GLO in this Contract or any document related thereto. 4.2. Provider agrees to take all reasonably feasible physical, technical, administrative, and procedural measures to ensure that no unauthorized use of GLO Data occurs.

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

  • Manufacturer A firm that operates or maintains a factory or establishment that produces on the premises, the materials or supplies obtained by the Contractor. Regular Dealer - A firm that owns, operates, or maintains a store, warehouse, or other establishment in which the materials or supplies required for the performance of the contract are bought, kept in stock, and regularly sold to the public in the usual course of business. A regular dealer engages in, as its principal business and in its own name, the purchase and sale or lease of the products in question. A regular dealer in such bulk items as steel, cement, gravel, stone, and petroleum products need not keep such products in stock, if it owns and operates distribution equipment for the products. Brokers and packagers are not regarded as manufacturers or regular dealers within the meaning of this section. United States Department of Transportation (USDOT) - Federal agency responsible for issuing regulations (49 CFR Part 26) and official guidance for the DBE program.

  • Data Location 1.1. The CONTRACTOR shall not store or transfer non-public COUNTY data outside of the United States. This includes backup data and Disaster Recovery locations. The CONTRACTOR will permit its personnel and contractors to access COUNTY data remotely only as required to provide technical support. (Remote access to data from outside the continental United States is prohibited unless approved in advance and in writing by the County.) 1.2. The CONTRACTOR must notify the COUNTY in advance and in writing of any location changes to CONTRACTOR’s data center(s) that will process or store County data.

  • AT&T-12STATE acknowledges that CLEC may have an embedded base of one-way trunks ordered and installed prior to the Effective Date of this Agreement that were used for termination of CLEC’s Section 251(b)(5)/IntraLATA Toll Traffic to AT&T-12STATE (Embedded Base). To the extent that CLEC has such an Embedded Base, CLEC shall only augment trunk groups in the Embedded Base with the mutual agreement of the Parties. CLEC shall not order any new one-way trunk groups following the Effective Date of this Agreement. Moreover, the Parties agree that the Embedded Base will be converted to two-way trunk groups under the following circumstances: 4.2.1.1 With reasonable notification from AT&T-12STATE and upon AT&T-12STATE’s request, CLEC shall convert all of its Embedded Base to two-way trunks. 4.2.1.2 At any time an Embedded Base trunk group (either originating or terminating) requires augmentation, AT&T-12STATE can require the associated originating and terminating trunks to be converted to a single two-way trunk group prior to the augmentation. 4.2.1.3 When any network changes are to be performed on a project basis (i.e., central office conversions, tandem re-homes, etc.), upon request and reasonable notice by AT&T-12STATE, CLEC will convert all of its Embedded Base affected by the project within the intervals and due dates required by the project parameters. 4.2.1.4 In addition to the foregoing, CLEC may choose, at any time, to convert its Embedded Base to two-way trunk groups. 4.2.1.5 The Parties will coordinate any trunk group migration, trunk group prioritization and implementation schedule. AT&T-12STATE agrees to develop a cutover plan within thirty (30) days of notification to CLEC of the need to convert pursuant to Section 4.2.1.1 above and Section 4.2.1.3 above.

  • Supplier Diversity Seller shall comply with Xxxxx’s Supplier Diversity Program in accordance with Appendix V.

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