De-Identified Data Provider agrees not to attempt to re-identify de-identified Student Data. De-Identified Data may be used by the Provider for those purposes allowed under FERPA and the following purposes: (1) assisting the LEA or other governmental agencies in conducting research and other studies; and (2) research and development of the Provider's educational sites, services, or applications, and to demonstrate the effectiveness of the Services; and (3) for adaptive learning purpose and for customized student learning. Provider's use of De-Identified Data shall survive termination of this DPA or any request by XXX to return or destroy Student Data. Except for Subprocessors, Xxxxxxxx agrees not to transfer de- identified Student Data to any party unless (a) that party agrees in writing not to attempt re-identification, and (b) prior written notice has been given to the LEA who has provided prior written consent for such transfer. Prior to publishing any document that names the LEA explicitly or indirectly, the Provider shall obtain the LEA’s written approval of the manner in which de-identified data is presented.
Use of websites (a) The Borrower may satisfy its obligation to deliver any public information to the Lenders by posting this information onto an electronic website designated by the Borrower and the Administrative Agent (the “Designated Website”) by notifying the Administrative Agent (i) of the address of the website together with any relevant password specifications and (ii) that such information has been posted on the website; provided, that in any event the Borrower shall supply the Administrative Agent with one copy in paper form of any information which is posted onto the website. (b) The Administrative Agent shall supply each Lender with the address of and any relevant password specifications for the Designated Website following designation of that website by the Borrower and the Administrative Agent. (c) The Borrower shall promptly upon becoming aware of its occurrence notify the Administrative Agent if: (i) the Designated Website cannot be accessed due to technical failure; (ii) the password specifications for the Designated Website change; (iii) any new information which is required to be provided under this Agreement is posted onto the Designated Website; (iv) any existing information which has been provided under this Agreement and posted onto the Designated Website is amended; or (v) the Borrower becomes aware that the Designated Website or any information posted onto the Designated Website is or has been infected by any electronic virus or similar software. If the Borrower notifies the Administrative Agent under Section 5.3(c)(i) or Section 5.3(c)(v) above, all information to be provided by the Borrower under this Agreement after the date of that notice shall be supplied in paper form unless and until the Administrative Agent is satisfied that the circumstances giving rise to the notification are no longer continuing.
Personally Identifiable Information By submitting any of your personally identifiable information, such as your name, address, email address, phone number or fax number, to us, you consent to our privacy policy located at xxx.xxxxxxxx.xxx/xxxxx.
Personally Identifiable Information (PII); Security a. If Grantee or any of its subcontractors may or will create, receive, store or transmit PII under the terms of this Agreement, Grantee must provide for the security of such PII, in a form acceptable to Florida Housing, without limitation, non-disclosure, use of appropriate technology, security practices, computer access security, data access security, data storage encryption, data transmission encryption, security inspections and audits. Grantee shall take full responsibility for the security of all data in its possession or in the possession of its subcontractors and shall hold Florida Housing harmless for any damages or liabilities resulting from the unauthorized disclosure of loss thereof. b. If Grantee or any of its subcontractors may or will create, receive, store or transmit PII under the terms of this Agreement, Grantee shall provide Florida Housing with insurance information for stand-alone cyber liability coverage, including the limits available and retention levels. If Grantee does not carry stand-alone cyber liability coverage, Grantee agrees to indemnify costs related to notification, legal fees, judgments, settlements, forensic experts, public relations efforts, and loss of any business income related to this Agreement. c. Grantee agrees to maintain written policies and procedures for PII and/or data classification. This plan must include disciplinary processes for employees that violate these guidelines. d. Grantee agrees at all times to maintain reasonable network security that, at a minimum, includes a network firewall. e. Grantee agrees to protect and maintain the security of data with protection security measures that include maintaining secure environments that are patched and up to date with all appropriate security updates as designated by a relevant authority (e.g. Microsoft notifications, Common Vulnerabilities and Exposures (CVE) database, etc.) Grantee agrees that PII shall be appropriately destroyed based on the format stored upon the expiration of any applicable retention schedules. f. Grantee agrees that any and all transmission or exchange of system application data with Florida Housing and/or any other parties shall take place via secure Advanced Encryption Standards (AES), e.g. HTTPS, FTPS, SFTP or equivalent means. All data stored as a part of backup and recovery processes shall be encrypted, using AES. g. If Grantee reasonably suspects that a cybersecurity event or breach of security has occurred, they must notify Florida Housing’s Contract Administrator within 48 hours. h. In the event of a breach of PII or other sensitive data, Grantee must abide by provisions set forth in Section 501.171, Fla. Stat. Additionally, Grantee must immediately notify Florida Housing in writing of the breach and any actions taken in response to such a breach. As the information becomes available the statement must include, at a minimum, the date(s) and number of records affected by unauthorized access, distribution, use, modification or disclosure of PII; Grantee’s corrective action plan; and the timelines associated with the corrective action plan.
Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-‐to-‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.
Use of De-identified information De-identified information may be used by the Contractor for the purposes of development, research, and improvement of educational sites, services, or applications, as any other member of the public or party would be able to use de-identified data pursuant to 34 CFR 99.31(b). Contractor agrees not to attempt to re-identify de-identified Student Data.
Line Information Database LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, MyLineToo must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.
Use of Software Any software that is available on the Services ("Software") is the copyrighted work of Red Hat and/or its licensors. Copying or reproducing the Software to any other server or location for further reproduction or redistribution is strictly prohibited, unless such reproduction or redistribution is permitted by a license agreement accompanying such Software. You may not create derivative works of the Software, or attempt to decompile or reverse-engineer the Software unless otherwise permitted by law. Use of the Software is subject to the license terms of any license agreement that may accompany or is provided with the Software. You may not download any Software until you have read and accepted the terms of the accompanying software license. WITHOUT LIMITING THE FOREGOING, THE SOFTWARE IS WARRANTED, IF AT ALL, ONLY ACCORDING TO THE TERMS OF THE SEPARATE LICENSE AGREEMENT ACCOMPANYING THE SOFTWARE. EXCEPT AS WARRANTED IN SUCH LICENSE AGREEMENT, RED HAT, ITS PARENT, SUBSIDIARY, AND AFFILIATE COMPANIES, AND ITS LICENSORS DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THE SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT, TO THE MAXIMUM EXTENT PERMITTED BY LAW.
Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit C. 9.2 BellSouth will provide LIDB Storage upon written request to <<customer_name>>’s Account Manager stating a requested activation date.
Use of the Card 4.1. The Cardholder shall use the Card and operate the Account in a satisfactory manner. The decision as to whether the Card is being so used or the Account is being so operated rests with the Bank and shall be conclusive and binding on the Account Holder/s and on the Cardholder. 4.2. The Bank will bear no responsibility for the refusal of any merchant or establishment to accept the Card for any reason whatsoever. 4.3. Cash withdrawals that are recorded by the ATM, and payments effected by the Cardholder with his Card, shall be debited to his Bank Account. 4.4. Before using his Card, the Cardholder shall ensure that there are sufficient funds on his Account to cover the payment of the Card transactions. Furthermore, the Cardholder will not operate the Account in such a way to exceed the available balance of the Account. 4.5. The fraudulent, incorrect or illegal use of the Card by any person whomsoever shall not relieve the Cardholder of his liabilities to the Bank in respect thereof. 4.6. The Bank shall not be responsible to the Cardholder for any goods or services supplied to the Cardholder by merchants, or to any person to whom the said goods and services have been supplied. Disputes arising from the supply of such goods and services shall be settled directly with the merchants without the Bank being constituted party thereto. The Cardholder shall consequently not be relieved of his obligations to the Bank under the relevant Card transactions. 4.7. The Cardholder shall ensure the correctness of the amounts borne on, and contained in, the envelopes referred to in clause 1.3 of Part III above. The contents of the envelopes shall be checked and certified by two officers of the Bank. The amounts so certified shall be credited to the Account whose number is borne on the envelopes and shall be final and conclusive and not liable to be called in question by the Cardholder or the Account Holder. 4.8. Transactions for POS and ATM withdrawals are subject to the respective daily limits as determined by the Bank from time to time.
