System Use (a) An electronic site access system may be used on site, subject to the requirements of this statement. (b) The system operates via: (i) a facial recognition device; and (ii) an electronic gate. (c) The system will be installed at the access and egress point/s of the site and will only be utilised to identify presence on site. (d) The purpose for which the electronic site access system will be implemented is to ensure: (i) avoiding unauthorised access to site; (ii) confirmation and co-ordination of effort in emergency situations; and (iii) confirmation that all entrants to site have received a site specific induction; (e) The only personal data collected by the system is a site entrant’s: (i) image; (ii) first & last name; (iii) mobile phone number; (iv) email address; and (v) employer’s name. (the Collected Data) (f) The Collected Data will only be held or used for the purposes specified above, unless otherwise by consent or required by law. (g) The Employer will not use the electronic site access control system to verify who was on a site at a particular time for the purpose of: (i) evaluating whether a variation claim regarding labour costs made by a subcontractor can be substantiated; (ii) taking disciplinary action against an Employee, or assisting a subcontractor to take disciplinary action against its own employees, regarding their start and finish times; or (iii) otherwise generally tracking a worker’s movements whilst on the site.
System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.
Wireless Operator Data In addition to Section 20 (Information Authorization) of the General Terms, you acknowledge that we or Zelle® may use information on file with your wireless operator to further verify your identity and to protect against or prevent actual or potential fraud or unauthorized use of the Service. By using the Zelle® Payment Service, you authorize your wireless operator (AT&T, Sprint, T-Mobile, US Cellular, Verizon, or any other branded wireless operator) to disclose your mobile number, name, address, email, network status, customer type, customer role, billing type, mobile device identifiers (IMSI and IMEI) and other subscriber status and device details, if available, to us or our Service Providers solely to allow verification of your identity and to compare information you have provided to us or to Zelle® with your wireless operator account profile information for the duration of our business relationship. See Zelle®’s Privacy Policy at ▇▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/privacy-policy for how it treats your data. Please review our Privacy Policy in order to better understand our commitment to maintaining your privacy, as well as our use and disclosure of your information.
Customer Content As part of the Services provided under this Agreement, Customer Data will be stored and processed in the data center region specified in the applicable Ordering Document. Axway shall not access Customer Content except in response to support or technical issues where Customer provides Axway with prior Customer’s written authorization required to access such Customer Content. Axway is not responsible for unauthorized access, alteration, theft or destruction of Customer Content arising from Customer’s own or its authorized users’ actions or omissions in contravention of the Documentation. Customer’s ability to recover any lost data resulting from Axway’s misconduct is limited to restoration by Axway from the most recent back-up.
Software Development Software designs, prototypes, and all documentation for the final designs developed under this agreement must be made fully transferable upon direction of NSF. NSF may make the software design, prototype, and documentation for the final design available to competitors for review during any anticipated re-competition of the project.
