Access by Beta Testers; XXXX; End Users; Compliance Sample Clauses

Access by Beta Testers; XXXX; End Users; Compliance. Developer shall provide to Crashlytics the contact information of any user of Developer’s application(s) whom Developer intends to invite to become a Beta Tester. Developer is solely responsible for determining which users will receive an invitation to become a Beta Tester, and for ensuring the accuracy of any user contact information provided to Crashlytics. Developer may provide Beta Testers with its own XXXX for a Beta Application that will be accessed by Beta Testers (“Developer XXXX”); provided that the Developer XXXX provides terms and conditions consistent with this Agreement and, with respect to Crashlytics, no less protective than those terms and conditions set forth in the standard XXXX provided in Appendix A (“Standard XXXX”). If Developer does not provide a separate Developer XXXX to Beta Testers in connection with Developer’s Beta Application, then Developer acknowledges and agrees that such Beta Testers, by accessing the Beta Application through the Services, will be made subject to the terms and conditions of the Standard XXXX between Developer and such Beta Testers.. Developer acknowledges and agrees that Crashlytics provides the Standard XXXX by way of convenience only, and does not represent or warrant that the Standard XXXX will be enforceable under, or in compliance with, all applicable laws, rules, regulations, or otherwise. Developer acknowledges and agrees that the XXXX applicable to Developer’s Beta Application shall be between Developer and any Beta Tester, and Crashlytics shall not be responsible for, and shall not have any liability whatsoever for, such XXXX, any application tested by a Beta Tester, or for any breach by Developer or any Beta Tester of the terms and conditions of such XXXX. The Services allow the Developer to collect information relating to performance of Developer’s applications, including, without limitation, device state information, unique device identifiers, information relating to the physical location of a device, and information about how the application was used. Developer may turn on features of the Services to allow collection of other information via the Services, including some personally identifiable information (e.g., a user’s email address), which allows Developers to communicate with users about the engagement with and functionality of their applications and to invite them to become Beta Testers. Developer represents and warrants that Developer is collecting information via the Services solely to ...
AutoNDA by SimpleDocs

Related to Access by Beta Testers; XXXX; End Users; Compliance

  • Additional Requirements from Authorized Users An Authorized User may have distinct requirements that must be met by all individuals employed by or working for the Authorized User. The Contractor’s Staff Members will be expected to comply with these requirements as a condition of the placement.

  • Access to Network Interface Device (NID 2.4.3.1. Due to the wide variety of NIDs utilized by BellSouth (based on subscriber size and environmental considerations), Mpower may access the on-premises wiring by any of the following means: BellSouth shall allow Mpower to connect its loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premise. Mpower agrees to install compatible protectors and test jacks and to maintain the protection system and equipment and to indemnify BellSouth pursuant to Section 8 of the General Terms and Conditions of this Agreement.

  • Selection of Subcontractors, Procurement of Materials and Leasing of Equipment The contractor shall not discriminate on the grounds of race, color, religion, sex, national origin, age or disability in the selection and retention of subcontractors, including procurement of materials and leases of equipment. The contractor shall take all necessary and reasonable steps to ensure nondiscrimination in the administration of this contract.

  • Minimum Site Requirements for TIPS Sales (when applicable to TIPS Sale). Cleanup: When performing work on site at a TIPS Member’s property, Vendor shall clean up and remove all debris and rubbish resulting from their work as required or directed by the TIPS Member or as agreed by the parties. Upon completion of work, the premises shall be left in good repair and an orderly, neat, clean and unobstructed condition. Preparation: Vendor shall not begin a project for which a TIPS Member has not prepared the site, unless Vendor does the preparation work at no cost, or until TIPS Member includes the cost of site preparation in the TIPS Sale Site preparation includes, but is not limited to: moving furniture, installing wiring for networks or power, and similar pre‐installation requirements. Registered Sex Offender Restrictions: For work to be performed at schools, Vendor agrees that no employee of Vendor or a subcontractor who has been adjudicated to be a registered sex offender will perform work at any time when students are, or reasonably expected to be, present unless otherwise agreed by the TIPS Member. Vendor agrees that a violation of this condition shall be considered a material breach and may result in the cancellation of the TIPS Sale at the TIPS Member’s discretion. Vendor must identify any additional costs associated with compliance of this term. If no costs are specified, compliance with this term will be provided at no additional charge. Safety Measures: Vendor shall take all reasonable precautions for the safety of employees on the worksite, and shall erect and properly maintain all necessary safeguards for protection of workers and the public. Vendor shall post warning signs against all hazards created by the operation and work in progress. Proper precautions shall be taken pursuant to state law and standard practices to protect workers, general public and existing structures from injury or damage. Smoking: Persons working under Agreement shall adhere to the TIPS Member’s or local smoking statutes, codes, ordinances, and policies.

  • System Upgrade Facilities and System Deliverability Upgrades Connecting Transmission Owner shall design, procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Appendix A hereto. The responsibility of the Developer for costs related to System Upgrade Facilities and System Deliverability Upgrades shall be determined in accordance with the provisions of Attachment S to the NYISO OATT.

  • Technical Standards Applicable to a Wind Generating Plant i. Low Voltage Ride-Through (LVRT) Capability A wind generating plant shall be able to remain online during voltage disturbances up to the time periods and associated voltage levels set forth in the standard below. The LVRT standard provides for a transition period standard and a post-transition period standard.

  • Loop Testing/Trouble Reporting 2.1.6.1 Think 12 will be responsible for testing and isolating troubles on the Loops. Think 12 must test and isolate trouble to the BellSouth portion of a designed/non- designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Think 12 will be required to provide the results of the Think 12 test which indicate a problem on the BellSouth provided Loop.

  • Minimum Customer Support Requirements for TIPS Sales Vendor shall provide timely and commercially reasonable support for TIPS Sales or as agreed to in the applicable Supplemental Agreement.

  • Access to Work Locations Reasonable access to employee work locations shall be granted officers of the Association and their officially designated representatives for the purpose of processing grievances or contacting members of the Association concerning business within the scope of representation. Such officers or representatives shall not enter any work location without the consent of the City Manager. Access shall be restricted so as not to interfere with the normal operations of the department or with established safety or security requirements. Solicitation of membership and activities concerned with the internal management of the Association, such as collecting dues, holding membership meetings, campaigning for office, conducting elections and distributing literature, shall not be conducted during working hours.

  • Technical Requirements for SCPs/Databases 10.5.3.1 BellSouth shall provide physical access to SCPs through the SS7 network and protocols with TCAP as the application layer protocol.

Time is Money Join Law Insider Premium to draft better contracts faster.