Privacy Threshold Analysis (PTA)

U.S. DEPARTMENT OF

HOUSING AND URBAN DEVELOPMENT

PRIVACY THRESHOLD ANALYSIS (PTA)

Public/Private Partnerships

for the Mixed-Finance Development

of Public Housing Units

Office of Public Housing Investments, PI

Instruction & Template

November 19, 2018

PRIVACY THRESHOLD ANALYSIS (PTA)

The PTA is a compliance form developed by the Privacy Branch to identify the use of Personally Identifiable Information (PII) across the Department. The PTA is the first step in the PII verification process, which focuses on these areas of inquiry:

• Purpose for the information,

• Type of information,

• Sensitivity of the information,

• Use of the information,

• And the risk to the information.

Please use the attached form to determine whether a Privacy Impact Assessment (PIA) is required under the E-Government Act of 2002 or a System of Record Notice (SORN) is required under the Privacy Act of 1974, as amended.

Please complete this form and send it to your program Privacy Liaison Officer (PLO). If you have no program Privacy Liaison Officer, please send the PTA to the HUD Privacy Branch:

Marcus Smallwood, Acting, Chief Privacy Officer

Privacy Branch

U.S. Department of Housing and Urban Development

privacy@hud.gov

Upon receipt from your program PLO, the HUD Privacy Branch will review this form. If a PIA or SORN is required, the HUD Privacy Branch will send you a copy of the PIA and SORN templates to complete and return.

PRIVACY THRESHOLD ANALYSIS (PTA)

Summary Information

Project or Program Name:	Public/Private Partnerships for the Mixed-Finance Development of Public Housing Units
Program:
CSAM Name (if applicable):	NA	CSAM Number (if applicable):	NA
Type of Project or Program:		Project or program status:
Date first developed:	October 21, 1998	Pilot launch date:	NA
Date of last PTA update:	July 17, 2015	Pilot end date:	NA
ATO Status (if applicable)		ATO expiration date (if applicable):	N/A

PROJECT OR PROGRAM MANAGER

Name:	Robert Mulderig
Office:	Public Housing Investments	Title:	Acting DAS
Phone:	202-402-4780	Email:	Robert.e.mulderig@hud.gov

INFORMATION SYSTEM SECURITY OFFICER (ISSO) (if applicable)

Name:	N/A
Phone:	N/A	Email:	N/A

Specific PTA Questions

1. Reason for submitting the PTA:

The Quality Housing and Work Responsibility Act of 1998 (P.L. 195-276, approved October 21, 1998), also known as the Public Housing Reform Act, created Section 35 of the U.S. Housing Act of 1937, 42 U.S.C. 1437. Section 35 allows PHAs to own, operate, assist or otherwise participate in the development and operation of mixed-finance projects. Mixed-finance development refers to the development or rehabilitation of public housing, where the public housing units are owned in whole or in part by an entity other than a PHA. Prior to this, all public housing had to be developed and owned by a Public Housing Authority (PHA). However, Section 35 allowed PHAs to provide Section 9 capital and operating assistance to mixed-finance projects, which are also financially assisted by private and other resources. Private and other resources include tax credit equity, private mortgages and other federal, state or local funds. Section 35 also allows non-PHA owner entities to own and operate mixed-finance projects that contain both public housing and non-public housing units, or only public housing units. Along with public housing unit development, mixed-finance real estate development or rehabilitation transactions are used to extend public housing appropriations in housing development and to develop mixed-income housing, where public housing residents are anonymously mixed in with affordable and market rate housing residents.

In order to approve the development of mixed-finance projects, HUD collects certain information from each PHA/Ownership Entity. Under current regulations, HUD collects and reviews the essential documents included in this ICR in order to determine whether or not approval should be given. After approval is given and the documents are recorded by the associated county, HUD collects the recorded versions of the documents in this ICR, along with all financing and legal agreements that the PHA/owner entity has with HUD and with third-parties in connection with that mixed-finance project. This includes unique legal documents along with standardized forms and “Certifications and Assurances,” which are not exempted under PRA. Regulations for the processing of mixed-finance public housing projects are at 24 CFR part 905 subpart F (§905).

Does this system employ the following technologies? If you are using these technologies and want coverage under the respective PIA for that technology, please stop here and contact the HUD Privacy Branch for further guidance.

Social Media Web portal2 (e.g., SharePoint) Contact Lists Public website (e.g. A website operated by HUD, contractor, or other organization on behalf of the HUD: There is no PII. Contractor site with access limited to HUD personal. None of these

From whom does the Project or Program collect, maintain, use, or disseminate information? Please check all that apply.

This program collects no personally identifiable information3 Members of the public HUD employees/contractors (list programs): Mixed-finance development process used on the HOPE VI and Choice Neighborhoods Initiative programs. Contractors working on behalf of HUD Employees of other federal agencies Other (e.g. business entity) Real estate developers, PHAs

No information about individuals is collected, generated or retained
This program collects no personally identifiable information
4(a) Does the project, program, or system retrieve information from the system about a U.S. Citizen or lawfully admitted permanent resident aliens by a personal identifier?	No. Please continue to next question. Yes. If yes, please list all personal identifiers used:
4(b) Does the project, program, or system have an existing System of Records Notice (SORN) that has already been published in the Federal Register that covers the information collected?	No. Please continue to next question. Yes. If yes, provide the system name and number, and the Federal Register citation(s) for the most recent complete notice and any subsequent notices reflecting amendment to the system
4(c)Has the project, program, or system undergone any significant changes since the SORN?	No. Please continue to next question. Yes. If yes, please describe.
4(d) Does the project, program, or system use Social Security Numbers (SSN)?	No. Yes.
4(e) If yes, please provide the specific legal authority and purpose for the collection of SSNs:	N/A
4(f) If yes, please describe the uses of the SSNs within the project, program, or system:	N/A
4(g) If this project, program, or system is an information technology/system, does it relate solely to infrastructure? For example, is the system a Local Area Network (LAN) or Wide Area Network (WAN)?	No. Please continue to next question. Yes. If a log kept of communication traffic, please answer this question.
4(h) If header or payload data4 is stored in the communication traffic log, please detail the data elements stored.
Data is not stored in the communication traffic log.

Does this project, program, or system connect, receive, or share PII with any other HUD programs or systems?	No. Yes. If yes, please list: Click here to enter text.
Does this project, program, or system connect, receive, or share PII with any external (non-HUD) partners or systems?	No. Yes. If yes, please list: Click here to enter text.
6(a) Is this external sharing pursuant to new or existing information sharing access agreement (MOU, MOA, etc.)?	This program collects no personally identifiable information
7. Does the project, program, or system provide role-based training for personnel who have access in addition to annual privacy training required of all HUD personnel?	No. Yes. If yes, please list: Training is given to each person that is given access and on an as-needed basis. Although there is no PII, HUD IT and privacy requirements are included in the contract. All users take annual privacy training, even though there is no PII. It’s mandatory for all Grant Managers, along with ethics training, etc.
Per NIST SP 800-53 Rev. 4, Appendix J, does the project, program, or system maintain an accounting of disclosures of PII to individuals/agencies who have requested access to their PII? maintain an accounting of disclosures of PII to individuals/agencies who have requested access to their PII?	No. What steps will be taken to develop and maintain the accounting: This program collects no personally identifiable information Yes. In what format is the accounting maintained:
Is there a FIPS 199 determination?5	Unknown. No. Yes. Please indicate the determinations for each of the following: Confidentiality: Low Moderate High Integrity: Low Moderate High Availability: Low Moderate High

PRIVACY THRESHOLD ANALYSIS REVIEW

(To be Completed by PROGRAM PLO)

Program Privacy Liaison Reviewer:	John Bravacos, Senior Agency Official for Privacy
Date submitted to Program Privacy Office:	November 28, 2018
Date submitted to HUD Privacy Branch:	November 28, 2018
Program Privacy Liaison Officer Recommendation: Please include recommendation below, including what new privacy compliance documentation is needed.
Click here to enter text.

(To be Completed by the HUD Privacy Branch)

HUD Privacy Branch Reviewer:	Cindy Etheridge
Date approved by HUD Privacy Branch:	Click here to enter a date.
PTA Expiration Date:	Click here to enter a date.

DESIGNATION

Privacy Sensitive System:		If “no” PTA adjudication is complete.
Category of System:		If “other” is selected, please describe: Click here to enter text.
Determination: PTA sufficient at this time. Privacy compliance documentation determination in progress. New information sharing arrangement is required. HUD Policy for Computer-Readable Extracts Containing Sensitive PII applies. Privacy Act Statement required. Privacy Impact Assessment (PIA) required. System of Records Notice (SORN) required. Paperwork Reduction Act (PRA) Clearance may be required. Contact your program PRA Officer. A Records Schedule may be required. Contact your program Records Officer.
PIA:	If covered by existing PIA, please list: Click here to enter text.
SORN:	If covered by existing SORN, please list: Click here to enter text.
HUD Privacy Branch Comments: Please describe rationale for privacy compliance determination above.
Click here to enter text.

DOCUMENT ENDORSEMENT

DATE REVIEWED:

PRIVACY REVIEWING OFFICIALS NAME:

By signing below, you attest that the content captured in this document is accurate and complete and meet the requirements of applicable federal regulations and HUD internal policies.

Signed		11/23/2018
Robert E. Mulderig Acting Deputy Assistant Secretary Office of Public Housing Investments		Date
Marcus Smallwood ACTING CHIEF PRIVACY OFFICER OFFICE OF ADMINISTRATION		Date

2 Informational and collaboration-based portals in operation at HUD and its programs that collect, use, maintain, and share limited personally identifiable information (PII) about individuals who are “members” of the portal or “potential members” who seek to gain access to the portal.

3 HUD defines personal information as “Personally Identifiable Information” or PII, which is any information that permits the identity of an individual to be directly or indirectly inferred, including any information that is linked or linkable to that individual, regardless of whether the individual is a U.S. citizen, lawful permanent resident, visitor to the U.S., or employee or contractor to the Department. “Sensitive PII” is PII, which if lost, compromised, or disclosed without authorization, could result in substantial harm, embarrassment, inconvenience, or unfairness to an individual. For the purposes of this PTA, SPII and PII are treated the same.

4 Header: Information that is placed before the actual data. The header normally contains a small number of bytes of control information, which is used to communicate important facts about the data that the message contains and how it is to be interpreted and used. It serves as the communication and control link between protocol elements on different devices.

Payload data: The actual data to be transmitted, often called the payload of the message (metaphorically borrowing a term from the space industry!) Most messages contain some data of one form or another, but some actually contain none: they are used only for control and communication purposes. For example, these may be used to set up or terminate a logical connection before data is sent.

5 FIPS 199 is the Federal Information Processing Standard Publication 199, Standards for Security Categorization of Federal Information and Information Systems and is used to establish security categories of information systems.