Routine Use Publication Sample Clauses

Routine Use Publication. Agencies must publish routine uses pursuant to Subsection (b)(3) of the Privacy Act for those systems of records from which they intend to disclose information for purposes of a computer match. BOP and VA have determined that their systems of records contain appropriate routine use disclosure authority which is compatible with the purpose for which the information was collected, and which indicates that disclosures can be made for computer matching. BOP's specific routine use provision is referenced in Attachment Ill. VBA's routine use provision is Routine Use number 35 in 58VA21/22/28. VHA will also match SSNs received from BOP with SSNs in VA’s SOR entitled “Enrollment and Eligibility Records-VA” (147VA10NF1) published on July 13, 2016 (81 FR 45597), once this SOR is amended, to include a routine use to allow for this match.
Sample 1
AutoNDA by SimpleDocs
Routine Use Publication. Agencies must publish routine uses pursuant to Subsection (b)(3) of the Privacy Act for those systems of records from which they intend to disclose information for purposes of a computer match. BOP and VA have determined that their systems of records contain appropriate routine use disclosure authority which is compatible with the purpose for which the information was collected, and which indicates that disclosures can be made for computer matching. These routine uses are described above in Article V. B, D & E.
Sample 1

Related to Routine Use Publication

  • Root-­‐zone Information Publication ICANN’s publication of root-­‐zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.

  • zone Information Publication ICANN’s publication of root-zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.

  • Programming Processor is not responsible for programming or reprogramming of fuel dispensers.

  • Web Site Information on registration for and use of the E-Verify program can be obtained via the Internet at the Department of Homeland Security Web site: xxxx://xxx.xxx.xxx/E-Verify.

  • Non-Publication The parties mutually agree not to disclose publicly the terms of this Agreement except to the extent that disclosure is mandated by applicable law or regulation or to their respective advisors (e.g., attorneys, accountants).

  • Authoritative Root Database To the extent that ICANN is authorized to set policy with regard to an authoritative root server system (the “Authoritative Root Server System”), ICANN shall use commercially reasonable efforts to (a) ensure that the authoritative root will point to the top-­‐level domain nameservers designated by Registry Operator for the TLD, (b) maintain a stable, secure, and authoritative publicly available database of relevant information about the TLD, in accordance with ICANN publicly available policies and procedures, and (c) coordinate the Authoritative Root Server System so that it is operated and maintained in a stable and secure manner; provided, that ICANN shall not be in breach of this Agreement and ICANN shall have no liability in the event that any third party (including any governmental entity or internet service provider) blocks or restricts access to the TLD in any jurisdiction.

  • Directory Publication Nothing in this Agreement shall require Verizon to publish a directory where it would not otherwise do so.

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

  • Contract Database Metadata Elements Title: Great Neck Union Free School District and Great Neck Paraprofessionals Association (2011) Employer Name: Great Neck Union Free School District Union: Great Neck Paraprofessionals Association Local: Effective Date: 07/01/2011 Expiration Date: 06/30/2015 PERB ID Number: 5132 Unit Size: Number of Pages: 28 For additional research information and assistance, please visit the Research page of the Catherwood website - xxxx://xxx.xxx.xxxxxxx.xxx/library/research/ For additional information on the ILR School - xxxx://xxx.xxx.xxxxxxx.xxx/ ARTICLE# TITLE PAGE# Preamble 2 Article 1 Association Rights 2 Article 2 Board-Administration-Association Relationship and Procedures 4 Article 3 Exchange of Proposals 6 Article 4 Professionals Duties and Responsibilities of Paraprofessionals 7 Article 5 Work Assignments 8 Article 6 Annual Appointment 10 Article 7 Selection and Promotion 10 Article 8 Evaluations and Standards 11 Article 9 Procedures for Termination of Employment 11 Article 10 Conferences 12 Article 11 Human Resource File 12 Article 12 Professional Growth 13 Article 13 Sick Leave 14 Article 14 Personal Leave 16 Article 15 Other Leaves 17 Article 16 Grievance Procedures 18 Article 17 Legal Assistance 19 Article 18 Conformity to Law 19 Article 19 Health Insurance 20 Article 20 Retirement Plan 20 Article 21 Salary Schedule 21 Article 22 Seniority Policy 23 Article 23 Compensation for Financial Loss 24 Article 24 Duration of Agreement 25 Appendix A Determination of Negotiating Unit 25 Appendix B Payroll Deduction Authorization 26 Appendix C Bus Aides 26 Appendix D Salary Schedules 27

  • Mobile Application If Red Hat offers products and services through applications available on your wireless or other mobile Device (such as a mobile phone) (the "Mobile Application Services"), these Mobile Application Services are governed by the applicable additional terms governing such Mobile Application Service. Red Hat does not charge for these Mobile Application Services unless otherwise provided in the applicable additional terms. However, your wireless carrier's standard messaging rates and other messaging, data and other rates and charges will apply to certain Mobile Application Services. You should check with your carrier to find out what plans your carrier offers and how much the plans cost. In addition, the use or availability of certain Mobile Application Services may be prohibited or restricted by your wireless carrier, and not all Mobile Application Services may work with all wireless carriers or Devices. Therefore, you should check with your wireless carrier to find out if the Mobile Application Services are available for your wireless Device, and what restrictions, if any, may be applicable to your use of such Mobile Application Services.

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