Compatibility of Routine Use Sample Clauses

Compatibility of Routine Use. In accordance with the Privacy Act (5 U.S.C. 552(a) and (b)(3)), and our disclosure regulations (20 CFR Part 401), we are proposing to establish a new routine use to support the ACA. We can disclose information when the disclosure is required by law (20 CFR 401.120). 40544 Federal Register / Vol. 78, No. 129 / Friday, July 5, 2013 / Notices • Section 1411(c) of the ACA requires SSA to determine whether the name, date of birth, SSN and attestation of citizenship of individuals applying for IAPs under the ACA are consistent with information in SSA’s records. • Section 205(r)(3) of the Social Security Act (Act) permits SSA to disclose, on a reimbursable basis, death information to a Federal or State agency that administers a Federally-funded benefit other than pursuant to the Act to ensure proper payment of such benefit. Section 7213 of the Intelligence Reform and Terrorism Prevention Act of 2004 provides SSA authority to add a death indicator to verification routines that the agency deems appropriate. • Sections 202(x)(3)(B)(iv) and 1611(e)(1)(I)(iii) of the Act permit SSA to disclose, on a reimbursable basis, prisoner information to an agency administering a Federal or Federally- funded cash, food, or medical assistance program for eligibility and other administrative purposes under such program. We can also disclose information when the purpose is compatible with the purpose for which we collected the information and is supported by a published routine use (20 CFR 401.150). The Privacy Act allows us to disclose information maintained in a system of records without consent of the record subject to another party if such disclosure is pursuant to a routine use published in the system of records. 5 U.S.C. 552a(b)(3). A ‘‘routine use’’ must be compatible with the purpose for which SSA collected the information (5
AutoNDA by SimpleDocs

Related to Compatibility of Routine Use

  • Compatibility 1. Any unresolved issue arising from a mutual agreement procedure case otherwise within the scope of the arbitration process provided for in this Article and Articles 25A to 25G shall not be submitted to arbitration if the issue falls within the scope of a case with respect to which an arbitration panel or similar body has previously been set up in accordance with a bilateral or multilateral convention that provides for mandatory binding arbitration of unresolved issues arising from a mutual agreement procedure case.

  • Technical Feasibility of String While ICANN has encouraged and will continue to encourage universal acceptance of all top-­‐level domain strings across the Internet, certain top-­‐level domain strings may encounter difficulty in acceptance by ISPs and webhosters and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.

  • Software Use Case Red Hat Enterprise Virtualization Supported on physical hardware solely to support virtual quests. Red Hat Enterprise Virtualization is designed to run and manage virtual instances and does not support user-space applications. Red Hat Enterprise Virtualization may be used as a virtual desktop infrastructure solution, however, the Subscription does not come with any software or support for the desktop operating system. You must purchase the operating system for each instance of a desktop or server separately.

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

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

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

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

  • Availability of Licensed Materials Upon the Effective Date of this Agreement, Licensor will make the Licensed Materials available to the Licensee, the Participating Institutions and Authorized Users.

  • Connectivity User is solely responsible for providing and maintaining all necessary electronic communications with Exchange, including, wiring, computer hardware, software, communication line access, and networking devices.

  • Evaluation Software If the Software is an evaluation version or is provided to You for evaluation purposes, then, unless otherwise approved in writing by an authorized representative of Licensor, Your license to use the Software is limited solely for internal evaluation purposes in non-production use and in accordance with the terms of the evaluation offering under which You received the Software, and expires 90 days from installation (or such other period as may be indicated within the Software). Upon expiration of the evaluation period, You must discontinue use of the Software, return to an original state any actions performed by the Software, and delete the Software entirely from Your system and You may not download the Software again unless approved in writing by an authorized representative of Licensor. The Software may contain an automatic disabling mechanism that prevents its use after a certain period of time. RESTRICTIONS

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