<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="cfr.xsl"?>
<CFRGRANULE xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="CFRMergedXML.xsd">
  <FDSYS>
    <CFRTITLE>32</CFRTITLE>
    <CFRTITLETEXT>National Defense</CFRTITLETEXT>
    <VOL>2</VOL>
    <DATE>2002-07-01</DATE>
    <ORIGINALDATE>2002-07-01</ORIGINALDATE>
    <COVERONLY>false</COVERONLY>
    <TITLE>PRIVACY PROGRAM</TITLE>
    <GRANULENUM>O</GRANULENUM>
    <HEADING>SUBCHAPTER O</HEADING>
    <ANCESTORS>
      <PARENT HEADING="Title 32" SEQ="2">National Defense</PARENT>
      <PARENT HEADING="Subtitle A" SEQ="1">Department of Defense (Continued)</PARENT>
      <PARENT HEADING="CHAPTER I" SEQ="0">OFFICE OF THE SECRETARY OF DEFENSE (CONTINUED)</PARENT>
    </ANCESTORS>
  </FDSYS>
  <SUBCHAP TYPE="P">
    <PRTPAGE P="809"/>
    <HD SOURCE="HED">SUBCHAPTER O—PRIVACY PROGRAM</HD>
    <PART>
      <EAR>Pt. 310</EAR>
      <HD SOURCE="HED">PART 310—DoD PRIVACY PROGRAM</HD>
      <CONTENTS>
        <SUBPART>
          <HD SOURCE="HED">Subpart A—DoD Policy</HD>
          <SECHD>Sec.</SECHD>
          <SECTNO>310.1</SECTNO>
          <SUBJECT>Reissuance</SUBJECT>
          <SECTNO>310.2</SECTNO>
          <SUBJECT>Purpose.</SUBJECT>
          <SECTNO>310.3</SECTNO>
          <SUBJECT>Applicability and scope.</SUBJECT>
          <SECTNO>310.4</SECTNO>
          <SUBJECT>Definitions.</SUBJECT>
          <SECTNO>310.5</SECTNO>
          <SUBJECT>Policy.</SUBJECT>
          <SECTNO>310.6</SECTNO>
          <SUBJECT>Responsibilities.</SUBJECT>
          <SECTNO>310.7</SECTNO>
          <SUBJECT>Information requirements.</SUBJECT>
          <SECTNO>310.8</SECTNO>
          <SUBJECT>Rules of conduct.</SUBJECT>
          <SECTNO>310.9</SECTNO>
          <SUBJECT>Privacy boards and office composition and responsibilities.</SUBJECT>
        </SUBPART>
        <SUBPART>
          <HD SOURCE="HED">Subpart B—Systems of Records</HD>
          <SECTNO>310.10</SECTNO>
          <SUBJECT>General.</SUBJECT>
          <SECTNO>310.11</SECTNO>
          <SUBJECT>Standards of accuracy.</SUBJECT>
          <SECTNO>310.12</SECTNO>
          <SUBJECT>Government contractors.</SUBJECT>
          <SECTNO>310.13</SECTNO>
          <SUBJECT>Safeguarding personal information.</SUBJECT>
        </SUBPART>
        <SUBPART>
          <HD SOURCE="HED">Subpart C—Collecting Personal Information</HD>
          <SECTNO>310.20</SECTNO>
          <SUBJECT>General considerations.</SUBJECT>
          <SECTNO>310.21</SECTNO>
          <SUBJECT>Forms.</SUBJECT>
        </SUBPART>
        <SUBPART>
          <HD SOURCE="HED">Subpart D—Access by Individuals</HD>
          <SECTNO>310.30</SECTNO>
          <SUBJECT>Individual access to personal information.</SUBJECT>
          <SECTNO>310.31</SECTNO>
          <SUBJECT>Denial of individual access.</SUBJECT>
          <SECTNO>310.32</SECTNO>
          <SUBJECT>Amendment of records.</SUBJECT>
          <SECTNO>310.33</SECTNO>
          <SUBJECT>Reproduction fees.</SUBJECT>
        </SUBPART>
        <SUBPART>
          <HD SOURCE="HED">Subpart E—Disclosure of Personal Information to Other Agencies and Third Parties</HD>
          <SECTNO>310.40</SECTNO>
          <SUBJECT>Conditions of disclosure.</SUBJECT>
          <SECTNO>310.41</SECTNO>
          <SUBJECT>Nonconsensual disclosures.</SUBJECT>
          <SECTNO>310.42</SECTNO>
          <SUBJECT>Disclosures to commercial enterprises.</SUBJECT>
          <SECTNO>310.43</SECTNO>
          <SUBJECT>Disclosures to the public from health care records.</SUBJECT>
          <SECTNO>310.44</SECTNO>
          <SUBJECT>Disclosure accounting.</SUBJECT>
        </SUBPART>
        <SUBPART>
          <HD SOURCE="HED">Subpart F—Exemptions</HD>
          <SECTNO>310.50</SECTNO>
          <SUBJECT>Use and establishment of exemptions.</SUBJECT>
          <SECTNO>310.51</SECTNO>
          <SUBJECT>General exemptions.</SUBJECT>
          <SECTNO>310.52</SECTNO>
          <SUBJECT>Specific exemptions.</SUBJECT>
        </SUBPART>
        <SUBPART>
          <HD SOURCE="HED">Subpart G—Publication Requirements</HD>
          <SECTNO>310.60</SECTNO>
          <SUBJECT>
            <E T="04">Federal Register</E> publication.</SUBJECT>
          <SECTNO>310.61</SECTNO>
          <SUBJECT>Exemption rules.</SUBJECT>
          <SECTNO>310.62</SECTNO>
          <SUBJECT>System notices.</SUBJECT>
          <SECTNO>310.63</SECTNO>
          <SUBJECT>New and altered record systems.</SUBJECT>
          <SECTNO>310.64</SECTNO>
          <SUBJECT>Amendment and deletion of systems notices.</SUBJECT>
        </SUBPART>
        <SUBPART>
          <HD SOURCE="HED">Subpart H—Training Requirements</HD>
          <SECTNO>310.70</SECTNO>
          <SUBJECT>Statutory training requirements.</SUBJECT>
          <SECTNO>310.71</SECTNO>
          <SUBJECT>OMB training guidelines.</SUBJECT>
          <SECTNO>310.72</SECTNO>
          <SUBJECT>DoD training programs.</SUBJECT>
          <SECTNO>310.73</SECTNO>
          <SUBJECT>Training methodology and procedures.</SUBJECT>
          <SECTNO>310.74</SECTNO>
          <SUBJECT>Funding for training.</SUBJECT>
        </SUBPART>
        <SUBPART>
          <HD SOURCE="HED">Subpart I—Reports</HD>
          <SECTNO>310.80</SECTNO>
          <SUBJECT>Requirements for reports.</SUBJECT>
          <SECTNO>310.81</SECTNO>
          <SUBJECT>Suspense for submission of reports.</SUBJECT>
          <SECTNO>310.82</SECTNO>
          <SUBJECT>Reports control symbol.</SUBJECT>
        </SUBPART>
        <SUBPART>
          <HD SOURCE="HED">Subpart J—Inspections</HD>
          <SECTNO>310.90</SECTNO>
          <SUBJECT>Privacy Act inspections.</SUBJECT>
          <SECTNO>310.91</SECTNO>
          <SUBJECT>Inspection reporting.</SUBJECT>
        </SUBPART>
        <SUBPART>
          <HD SOURCE="HED">Subpart K—Privacy Act Enforcement Actions</HD>
          <SECTNO>310.100</SECTNO>
          <SUBJECT>Administrative remedies.</SUBJECT>
          <SECTNO>310.101</SECTNO>
          <SUBJECT>Civil actions.</SUBJECT>
          <SECTNO>310.102</SECTNO>
          <SUBJECT>Civil remedies.</SUBJECT>
          <SECTNO>310.103</SECTNO>
          <SUBJECT>Criminal penalties.</SUBJECT>
          <SECTNO>310.104</SECTNO>
          <SUBJECT>Litigation status sheet.</SUBJECT>
        </SUBPART>
        <SUBPART>
          <HD SOURCE="HED">Subpart L—Matching Program Procedures</HD>
          <SECTNO>310.110</SECTNO>
          <SUBJECT>OMB matching guidelines.</SUBJECT>
          <SECTNO>310.111</SECTNO>
          <SUBJECT>Requesting matching programs.</SUBJECT>
          <SECTNO>310.112</SECTNO>
          <SUBJECT>Time limits for submitting matching reports.</SUBJECT>
          <SECTNO>310.113</SECTNO>
          <SUBJECT>Matching programs among DoD components.</SUBJECT>
          <SECTNO>310.114</SECTNO>
          <SUBJECT>Annual review of systems of records.</SUBJECT>
          <APP>Appendix A to Part 310—Special Considerations for Safeguarding Personal Information in ADP Systems</APP>
          <APP>Appendix B to Part 310—Special Considerations for Safeguarding Personal Information During Word Processing</APP>
          <APP>Appendix C to Part 310—DoD Blanket Routine Uses</APP>
          <APP>Appendix D to Part 310—Provisions of the Privacy Act From Which a General or Specific Exemption May be Claimed</APP>
          <APP>Appendix E to Part 310—Sample of New or Altered System of Records Notice in “Federal Register” Format</APP>
          <APP>Appendix F to Part 310—Format for New or Altered System Report</APP>
          <APP>Appendix G to Part 310—Sample Deletions and Amendments to Systems Notices in “Federal Register” Format</APP>
          <APP>Appendix H to Part 310—Litigation Status Sheet</APP>
          <APP>Appendix I to Part 310—Office of Management and Budget (OMB) Matching Guidelines</APP>
        </SUBPART>
      </CONTENTS>
      <AUTH>
        <PRTPAGE P="810"/>
        <HD SOURCE="HED">Authority:</HD>
        <P>Pub. L. 93-579, 88 Stat. 1896 (5 U.S.C. 552a).</P>
      </AUTH>
      <SOURCE>
        <HD SOURCE="HED">Source:</HD>
        <P>51 FR 2364, Jan. 16, 1986, unless otherwise noted. Redesignated at 56 FR 55631, Oct. 29, 1991.</P>
      </SOURCE>
      <SUBPART>
        <HD SOURCE="HED">Subpart A—DoD Policy</HD>
        <SOURCE>
          <HD SOURCE="HED">Source:</HD>
          <P>65 FR 7732, Feb. 16, 2000, unless otherwise noted.</P>
        </SOURCE>
        <SECTION>
          <SECTNO>§ 310.1</SECTNO>
          <SUBJECT>Reissuance.</SUBJECT>
          <P>This part is reissued to consolidate into a single document (32 CFR part 310) Department of Defense (DoD) policies and procedures for implementing the Privacy Act of 1974, as amended (5 U.S.C. 522a) by authorizing the development, publication and maintenance of the DoD Privacy Program set forth by DoD Directive 5400.11,<SU>1</SU>
            <FTREF/> December 13, 1999, and 5400.11-R,<SU>2</SU>
            <FTREF/> August 31, 1983, both entitled: “DoD Privacy Program.”</P>
          <FTNT>
            <P>
              <SU>1</SU> Copies may be obtained: http://web7.whs.osd.mil/corres.htm.</P>
          </FTNT>
          <FTNT>
            <P>
              <SU>2</SU> See footnote 1 to § 310.1.</P>
          </FTNT>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.2</SECTNO>
          <SUBJECT>Purpose.</SUBJECT>
          <P>This part:</P>
          <P>(a) Updates policies and responsibilities of the DoD Privacy Program under 5 U.S.C. 552a, and under OMB Circular A-130.<SU>3</SU>
            <FTREF/>
          </P>
          <FTNT>
            <P>
              <SU>3</SU> Copies may be obtained: EOP Publications, NEOB, 725 17th Street, NW Washington, DC 20503.</P>
          </FTNT>
          <P>(b) Authorizes the Defense Privacy Board, the Defense Privacy Board Legal Committee and the Defense Data Integrity Board.</P>
          <P>(c) Continues to authorize the publication of DoD 5400.11-R.</P>
          <P>(d) Continues to delegate authorities and responsibilities for the effective administration of the DoD Privacy Program.</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.3</SECTNO>
          <SUBJECT>Applicability and scope.</SUBJECT>
          <P>This part:</P>
          <P>(a) Applies to the Office of the Secretary of Defense (OSD), the Military Departments, the Chairman of the Joint Chiefs of Staff, the Combatant Commands, the Inspector General of the Department of Defense (IG, DoD), the Uniformed Services University of the Health Sciences, the Defense agencies, and the DoD Field Activities (hereafter referred to collectively as “the DoD Components”). This part is mandatory for use by all DoD Components. Heads of DoD Components may issue supplementary instructions only when necessary to provide for unique requirements within their Components. Such instructions will not conflict with the provisions of this part.</P>
          <P>(b) Shall be made applicable to DoD contractors who are operating a system of records on behalf of a DoD Component, to include any of the activities, such as collecting and disseminating records, associated with maintaining a system of records.</P>
          <P>(c) This part does not apply to:</P>
          <P>(1) Requests for information from systems of records controlled by the Office of Personnel Management (OPM), although maintained by a DoD Component. These are processed in accordance with OPM's ‘Privacy Procedures for Personnel Records’ (5 CFR part 297).</P>
          <P>(2) Requests for personal information from the General Accounting Office (GAO). These are processed in accordance with DoD Directive 7650.1,<SU>4</SU>
            <FTREF/> “General Accounting Office Access to Records,” September 11, 1997.</P>
          <FTNT>
            <P>
              <SU>4</SU> See footnote 1 to § 310.1.</P>
          </FTNT>
          <P>(3) Requests for personal information from Congress. These are processed in accordance with DoD Directive 5400.4,<SU>5</SU>
            <FTREF/> “Provisions of Information to Congress,” January 30, 1978, except for those specific provisions in Subpart E—Disclosure of Personal Information to Other Agencies and Third Parties.</P>
          <FTNT>
            <P>
              <SU>5</SU> See footnote 1 to § 310.1.</P>
          </FTNT>
          <P>(4) Requests for information made under the Freedom of Information Act (5 U.S.C. 552). These are processed in accordance with “DoD Freedom of Information Act Program Regulation” (32 CFR part 286).</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.4</SECTNO>
          <SUBJECT>Definitions.</SUBJECT>
          <P>
            <E T="03">Access.</E> The review of a record or a copy of a record or parts thereof in a system of records by any individual.</P>
          <P>
            <E T="03">Agency.</E> For the purposes of disclosing records subject to the Privacy Act among DoD Components, the Department of Defense is considered a single agency. For all other purposes to include applications for access and <PRTPAGE P="811"/>amendment, denial of access or amendment, appeals from denials, and record keeping as regards release to non-DoD agencies; each DoD Component is considered an agency within the meaning of the Privacy Act.</P>
          <P>
            <E T="03">Confidential source.</E> A person or organization who has furnished information to the federal government under an express promise that the person's or the organization's identity will be held in confidence or under an implied promise of such confidentiality if this implied promise was made before September 27, 1975.</P>
          <P>
            <E T="03">Disclosure.</E> The transfer of any personal information from a system of records by any means of communication (such as oral, written, electronic, mechanical, or actual review) to any person, private entity, or government agency, other than the subject of the record, the subject's designated agent or the subject's legal guardian.</P>
          <P>
            <E T="03">Individual.</E> A living person who is a citizen of the United States or an alien lawfully admitted for permanent residence. The parent of a minor or the legal guardian of any individual also may act on behalf of an individual. Corporations, partnerships, sole proprietorships, professional groups, businesses, whether incorporated or unincorporated, and other commercial entities are not “individuals.”</P>
          <P>
            <E T="03">Law enforcement activity.</E> Any activity engaged in the enforcement of criminal laws, including efforts to prevent, control, or reduce crime or to apprehend criminals, and the activities of prosecutors, courts, correctional, probation, pardon, or parole authorities.</P>
          <P>
            <E T="03">Maintain.</E> Includes maintain, collect, use or disseminate.</P>
          <P>
            <E T="03">Official use.</E> Within the context of this part, this term is used when officials and employees of a DoD Component have a demonstrated need for the use of any record or the information contained therein in the performance of their official duties, subject to DoD 5200.1-R <SU>6</SU>
            <FTREF/> “DoD Information Security Program Regulation.”</P>
          <FTNT>
            <P>
              <SU>6</SU> See footnote 1 to § 310.1.</P>
          </FTNT>
          <P>
            <E T="03">Personal information.</E> Information about an individual that identifies, relates or is unique to, or describes him or her; <E T="03">e.g.,</E> a social security number, age, military rank, civilian grade, marital status, race, salary, home/office phone numbers, etc.</P>
          <P>
            <E T="03">Privacy Act request.</E> A request from an individual for notification as to the existence of, access to, or amendment of records pertaining to that individual. These records must be maintained in a system of records.</P>
          <P>
            <E T="03">Member of the public.</E> Any individual or party acting in a private capacity to include federal employees or military personnel.</P>
          <P>
            <E T="03">Record.</E> Any item, collection, or grouping of information, whatever the storage media (<E T="03">e.g.,</E> paper, electronic, etc.), about an individual that is maintained by a DoD Component, including but not limited to, his or her education, financial transactions, medical history, criminal or employment history and that contains his or her name, or the identifying number, symbol, or other identifying particular assigned to the individual, such as a finger or voice print or a photograph.</P>
          <P>
            <E T="03">Risk assessment.</E> An analysis considering information sensitivity, vulnerabilities, and the cost to a computer facility or word processing activity in safeguarding personal information processed or stored in the facility or activity.</P>
          <P>
            <E T="03">Routine use.</E> The disclosure of a record outside the Department of Defense for a use that is compatible with the purpose for which the information was collected and maintained by the Department of Defense. The routine use must be included in the published system notice for the system of records involved.</P>
          <P>
            <E T="03">Statistical record.</E> A record maintained only for statistical research or reporting purposes and not used in whole or in part in making determinations about specific individuals.</P>
          <P>
            <E T="03">System manager.</E> The DoD Component official who is responsible for the operation and management of a system of records.</P>
          <P>
            <E T="03">System of records.</E> A group of records under the control of a DoD Component from which personal information is retrieved by the individual's name or by some identifying number, symbol, or other identifying particular assigned to an individual.<PRTPAGE P="812"/>
          </P>
          <P>
            <E T="03">Word processing system.</E> A combination of equipment employing automated technology, systematic procedures, and trained personnel for the primary purpose of manipulating human thoughts and verbal or written or graphic presentations intended to communicate verbally or visually with another individual.</P>
          <P>
            <E T="03">Word processing equipment.</E> Any combination of electronic hardware and computer software integrated in a variety of forms (firmware, programable software, handwiring, or similar equipment) that permits the processing of textual data. Generally, the equipment contains a device to receive information, a computer-like processor with various capabilities to manipulate the information, a storage medium, and an output device.</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.5</SECTNO>
          <SUBJECT>Policy.</SUBJECT>
          <P>It is DoD policy that:</P>
          <P>(a) The personal privacy of an individual shall be respected and protected.</P>
          <P>(b) Personal information shall be collected, maintained, used or disclosed to ensure that:</P>
          <P>(1) It shall be relevant and necessary to accomplish a lawful DoD purpose required to be accomplished by statute or Executive Order.</P>
          <P>(2) It shall be collected to the greatest extent practicable directly from the individual.</P>
          <P>(3) The individual shall be informed as to why the information is being collected, the authority for collection, what uses will be made of it, whether disclosure is mandatory or voluntary, and the consequences of not providing that information.</P>
          <P>(4) It shall be relevant, timely, complete and accurate for its intended use; and</P>

          <P>(5) Appropriate administrative, technical, and physical safeguards shall be established, based on the media (<E T="03">e.g.,</E> paper, electronic, etc.) involved, to ensure the security of the records and to prevent compromise or misuse during storage or transfer.</P>
          <P>(c) No record shall be maintained on how an individual exercises rights guaranteed by the First Amendment to the Constitution, except as follows:</P>
          <P>(1) Specifically authorized by statute.</P>
          <P>(2) Expressly authorized by the individual on whom the record is maintained; or</P>
          <P>(3) When the record is pertinent to and within the scope of an authorized law enforcement activity.</P>
          <P>(d) Notices shall be published in the <E T="04">Federal Register</E> and reports shall be submitted to Congress and the Office of Management and Budget, in accordance with, and as required by, 5 U.S.C. 552a, OMB Circular A-130, and DoD 5400.11-R, as to the existence and character of any system of records being established or revised by the DoD Components. Information shall not be collected, maintained, used, or disseminated until the required publication/review requirements, as set forth in 5 U.S.C. 552a, OMB Circular A-130, and DoD 5400.11-R, are satisfied.</P>
          <P>(e) Individuals shall be permitted, to the extent authorized by 5 U.S.C. 552a and DoD 5400.11-R, to:</P>
          <P>(1) Determine what records pertaining to them are contained in a system of records.</P>
          <P>(2) Gain access to such records and to obtain a copy of those records or a part thereof.</P>
          <P>(3) Correct or amend such records on a showing that the records are not accurate, relevant, timely or complete.</P>
          <P>(4) Appeal a denial of access or a request for amendment.</P>
          <P>(f) Disclosure of records pertaining to an individual from a system of records shall be prohibited except with the consent of the individual or as otherwise authorized by 5 U.S.C. 552a, DoD 5400.11-R, and DoD 5400.7-R.<SU>7</SU>
            <FTREF/> When disclosures are made, the individual shall be permitted, to the extent authorized by 5 U.S.C. and DoD 5400.11-R, to seek an accounting of such disclosures from the DoD Component making the release.</P>
          <FTNT>
            <P>
              <SU>7</SU> See footnote 1 to § 310.1.</P>
          </FTNT>
          <P>(g) Disclosure of records pertaining to personnel of the National Security Agency, the Defense Intelligence Agency, the National Reconnaissance Office, and the National Imagery and Mapping Agency shall be prohibited to the extent authorized by Pub. L. 86-36 (1959) and 10 U.S.C. 424.</P>

          <P>(h) Computer matching programs between the DoD Components and the <PRTPAGE P="813"/>Federal, State, or local governmental agencies shall be conducted in accordance with the requirements of 5 U.S.C. 552a, OMB Circular A-130, and DoD 5400.11-R.</P>
          <P>(i) DoD personnel and system managers shall conduct themselves, consistent with § 310.8 so that personal information to be stored in a system of records only shall be collected, maintained, used, and disseminated as is authorized by this part, 5 U.S.C. 552a, and DoD 5400.11-R.</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.6</SECTNO>
          <SUBJECT>Responsibilities.</SUBJECT>
          <P>(a) The Director of Administration and Management, Office of the Secretary of Defense, shall:</P>
          <P>(1) Serve as the Senior Privacy Official for the Department of Defense.</P>
          <P>(2) Provide policy guidance for, and coordinate and oversee administration of, the DoD Privacy Program to ensure compliance with policies and procedures in 5 U.S.C. 552a and OMB A-130.</P>
          <P>(3) Publish DoD 5400.11-R and other guidance, to include Defense Privacy Board Advisory Opinions, to ensure timely and uniform implementation of the DoD Privacy Program.</P>
          <P>(4) Serve as the Chair to the Defense Privacy Board and the Defense Data Integrity Board (§ 310.7).</P>
          <P>(b) The Director of Washington Headquarters Services shall supervise and oversee the activities of the Defense Privacy Office (§ 310.7).</P>
          <P>(c) The General Counsel of the Department of Defense shall:</P>
          <P>(1) Provide advice and assistance on all legal matters arising out of, or incident to, the administration of the DoD Privacy Program.</P>
          <P>(2) Review and be the final approval authority on all advisory opinions issued by the Defense Privacy Board or the Defense Privacy Board Legal Committee.</P>
          <P>(3) Serve as a member of the Defense Privacy Board, the Defense Data Integrity Board, and the Defense Privacy Board Legal Committee (§ 310.7).</P>
          <P>(d) The Secretaries of the Military Departments and the Heads of the Other DoD Components shall:</P>
          <P>(1) Provide adequate funding and personnel to establish and support an effective DoD Privacy Program, to include the appointment of a senior official to serve as the principal point of contact (POC) for DoD Privacy Program matters.</P>
          <P>(2) Establish procedures, as well as rules of conduct, necessary to implement this part and DoD 5400.11-R so as to ensure compliance with the requirements of 5 U.S.C. 552a and OMB Circular A-130.</P>
          <P>(3) Conduct training, consistent with the requirements of DoD 5400.11-R, on the provisions of this part, 5 U.S.C. 552a, and OMB Circular A-130, and DoD 5400.11-R, for assigned and employed personnel and for those individuals having primary responsibility for implementing the DoD Privacy Program.</P>
          <P>(4) Ensure that the DoD Privacy Program periodically shall be reviewed by the Inspectors General or other officials, who shall have specialized knowledge of the DoD Privacy Program.</P>
          <P>(5) Submit reports, consistent with the requirements of DoD 5400.11-R, as mandated by 5 U.S.C. 552a and Chapter 8, OMB Circular A-130, and 32 CFR part 275, and as otherwise directed by the Defense Privacy Office.</P>
          <P>(e) The Secretaries of the Military Departments shall provide support to the Combatant Commands, as identified in DoD Directive 5100.3,<SU>8</SU>
            <FTREF/> in the administration of the DoD Privacy Program.</P>
          <FTNT>
            <P>
              <SU>8</SU> See footnote 1 to § 310.1.</P>
          </FTNT>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.7</SECTNO>
          <SUBJECT>Information requirements.</SUBJECT>
          <P>The reporting requirements in § 310.6(d)(5) are assigned Report Control Symbol DD-DA&amp;M(A)1379.</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.8</SECTNO>
          <SUBJECT>Rules of conduct.</SUBJECT>
          <P>(a) DoD personnel shall:</P>
          <P>(1) Take such actions, as considered appropriate, to ensure that personal information contained in a system of records, to which they have access to or are using incident to the conduct of official business, shall be protected so that the security and confidentiality of the information shall be preserved.</P>

          <P>(2) Not disclose any personal information contained in any system of records except as authorized by DoD 5400.11-R or other applicable law or regulation. Personnel willfully making such a disclosure when knowing that disclosure is prohibited are subject to <PRTPAGE P="814"/>possible criminal penalties and/or administrative sanctions.</P>
          <P>(3) Report any unauthorized disclosures of personal information from a system of records or the maintenance of any system of records that are not authorized by this part to the applicable Privacy POC for his or her DoD Component.</P>
          <P>(b) DoD system managers for each system of records shall:</P>
          <P>(1) Ensure that all personnel who either shall have access to the system of records or who shall develop or supervise procedures for handling records in the system of records shall be aware of their responsibilities for protecting personal information being collected and maintained under the DoD Privacy Program.</P>

          <P>(2) Prepare promptly any required new, amended, or altered system notices for the system of records and submit them through their DoD Component Privacy POC to the Defense Privacy Office for publication in the <E T="04">Federal Register</E>.</P>

          <P>(3) Not maintain any official files on individuals that are retrieved by name or other personal identifier without first ensuring that a notice for the system of records shall have been published in the <E T="04">Federal Register</E>. Any official who willfully maintains a system of records without meeting the publication requirements, as prescribed by 5 U.S.C. 552a, OMB Circular A-130, and DoD 5400.11-R, is subject to possible criminal penalties and/or administrative sanctions.</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.9</SECTNO>
          <SUBJECT>Privacy boards and office composition and responsibilities.</SUBJECT>
          <P>(a) <E T="03">The Defense Privacy Board.</E>—(1) <E T="03">Membership</E>. The Board shall consist of the Director of Administration and Management, OSD (DA&amp;M), who shall serve as the Chair; the Director of the Defense Privacy Office, Washington Headquarters Services (WHS), who shall serve as the Executive Secretary and as a member; the representatives designated by the Secretaries of the Military Departments; and the following officials or their designees: the Deputy Under Secretary of Defense for Program Integration (DUSD(PI)); the Assistant Secretary of Defense for Command, Control, Communications, and Intelligence (ASD(C31)); the Director, Freedom of Information and Security Review, WHS; the General Counsel of the Department of Defense (GC, DoD); and the Director for Information Operations and Reports, WHS (DIO&amp;R). The designees also may be the principal POC for the DoD Component for privacy matters.</P>
          <P>(2) <E T="03">Responsibilities.</E> (i) The Board shall have oversight responsibility for implementation of the DoD Privacy Program. It shall ensure that the policies, practices, and procedures of that Program are premised on the requirements of 5 U.S.C. 552a and OMB Circular A-130, as well as other pertinent authority, and that the Privacy Programs of the DoD Component are consistent with, and in furtherance of, the DoD Privacy Program.</P>
          <P>(ii) The Board shall serve as the primary DoD policy forum for matters involving the DoD Privacy Program, meeting as necessary, to address issues of common concern so as to ensure that uniform and consistent policy shall be adopted and followed by the DoD Components. The Board shall issue advisory opinions as necessary on the DoD Privacy Program so as to promote uniform and consistent application of 5 U.S.C. 552a, OMB Circular A-130, and DoD 5400.11-R.</P>
          <P>(iii) Perform such other duties as determined by the Chair or the Board.</P>
          <P>(b) <E T="03">The Defense Data Integrity Board.</E>—(1) <E T="03">Membership.</E> The Board shall consist of the DA&amp;M, OSD, who shall serve as the Chair; the Director of the Defense Privacy Office, WHS, who shall serve as the Executive Secretary; and the following officials or their designees: the representatives designated by the Secretaries of the Military Departments; the DUSD (PI); the ASD(C3I); the GC, DoD; the IG, DoD; the DIOR (WHS); and the Director, Defense Manpower Data Center. The designees also may be the principal POC for the DoD Component for privacy matters.</P>
          <P>(2) <E T="03">Responsibilities.</E> (i) The Board shall oversee and coordinate, consistent with the requirements of 5 U.S.C. 552a, OMB Circular A-130, and DoD 5400.11-R, all computer matching programs involving personal records contained in system of records maintained by the DoD Components.<PRTPAGE P="815"/>
          </P>
          <P>(ii) The Board shall review and approve all computer matching agreements between the Department of Defense and the other Federal, State or local governmental agencies, as well as memoranda of understanding when the match is internal to the Department of Defense, to ensure that, under 5 U.S.C. 552a, and OMB Circular A-130 and DoD 5400.11-R, appropriate procedural and due process requirements shall have been established before engaging in computer matching activities.</P>
          <P>(c) <E T="03">The Defense Privacy Board Legal Committee.</E>—(1) <E T="03">Membership.</E> The Committee shall consist of the Director, Defense Privacy Office, WHS, who shall serve as the Chair and the Executive Secretary; the GC, DoD, or designee; and civilian and/or military counsel from each of the DoD Components. The General Counsels (GCs) and The Judge Advocates General of the Military Departments shall determine who shall provide representation for their respective Department to the Committee. That does not preclude representation from each office. The GCs of the other DoD Components shall provide legal representation to the Committee. Other DoD civilian or military counsel may be appointed by the Executive Secretary, after coordination with the DoD Component concerned, to serve on the Committee on those occasions when specialized knowledge or expertise shall be required.</P>
          <P>(2) <E T="03">Responsibilities.</E> (i) The Committee shall serve as the primary legal forum for addressing and resolving all legal issues arising out of or incident to the operation of the DoD Privacy Program.</P>
          <P>(ii) The Committee shall consider legal questions regarding the applicability of 5 U.S.C. 552a, OMB Circular A-130, and DoD 5400.11-R and questions arising out of or as a result of other statutory and regulatory authority, to include the impact of judicial decisions, on the DoD Privacy Program. The Committee shall provide advisory opinions to the Defense Privacy Board and, on request, to the DoD Components.</P>
          <P>(c) <E T="03">The Defense Privacy Office.</E>—(1) <E T="03">Membership.</E> It shall consist of a Director and a staff. The Director also shall serve as the Executive Secretary and a member of the Defense Privacy Board; as the Executive Secretary to the Defense Data Integrity Board; and as the Chair and the Executive Secretary to the Defense Privacy Board Legal Committee.</P>
          <P>(2) <E T="03">Responsibilities.</E> (i) Manage activities in support of the Privacy Program oversight responsibilities of the DA&amp;M.</P>
          <P>(ii) Provide operational and administrative support to the Defense Privacy Board, the Defense Data Integrity Board, and the Defense Privacy Board Legal Committee.</P>
          <P>(iii) Direct the day-to-day activities of the DoD Privacy Program.</P>
          <P>(iv) Provide guidance and assistance to the DoD Components in their implementation and execution of the DoD Privacy Program.</P>

          <P>(v) Review proposed new, altered, and amended systems of records, to include submission of required notices for publication in the <E T="04">Federal Register</E> and, when required, providing advance notification to the Office of Management and Budget (OMB) and the Congress, consistent with 5 U.S.C. 552a, OMB Circular A-130, and DoD 5400.11-R.</P>
          <P>(vi) Review proposed DoD Component privacy rulemaking, to include submission of the rule to the Office of the Federal Register for publication and providing to the OMB and the Congress reports, consistent with 5 U.S.C. 552a, OMB Circular A-130, and DoD 5400.11-R, and to the Office of the Comptroller General of the United States, consistent with 5 U.S.C. Chapter 8.</P>

          <P>(vii) Develop, coordinate, and maintain all DoD computer matching agreements, to include submission of required match notices for publication in the <E T="04">Federal Register</E> and advance notification to the OMB and the Congress of the proposed matches, consistent with 5 U.S.C. 552a, OMB Circular A-130, and DoD 5400.11-R.</P>
          <P>(viii) Provide advice and support to the DoD Components to ensure that:</P>
          <P>(A) All information requirements developed to collect or maintain personal data conform to DoD Privacy Program standards.</P>

          <P>(B) Appropriate procedures and safeguards shall be developed, implemented, and maintained to protect personal information when it is stored in <PRTPAGE P="816"/>either a manual and/or automated system of records or transferred by electronic on non-electronic means; and</P>
          <P>(C) Specific procedures and safeguards shall be developed and implemented when personal data is collected and maintained for research purposes.</P>
          <P>(ix) Serve as the principal POC for coordination of privacy and related matters with the OMB and other Federal, State, and local governmental agencies.</P>
          <P>(x) Compile and submit the “Biennial ‘Privacy Act’ Report” and the “Biennial Matching Activity Report” to the OMB as required by OMB Circular A-130 and DoD 5400.11-R</P>
          <P>(xi) Update and maintain this part and DoD 5400.11-R.</P>
        </SECTION>
      </SUBPART>
      <SUBPART>
        <HD SOURCE="HED">Subpart B—Systems of Records</HD>
        <SECTION>
          <SECTNO>§ 310.10</SECTNO>
          <SUBJECT>General.</SUBJECT>
          <P>(a) <E T="03">System of records.</E> To be subject to the provisions of this part a “system of records” must:</P>
          <P>(1) Consist of “records” (as defined in § 310.3(n)) that are retrieved by the name of an individual or some other personal identifier, and</P>
          <P>(2) Be under the control of a DoD Component.</P>
          <P>(b) <E T="03">Retrieval practices.</E> (1) Records in a group of records that <E T="03">may be</E> retrieved by a name or personal identifier are not covered by this part even if the records contain personal data and are under control of a DoD Component. The records <E T="03">must be,</E> in fact, retrieved by name or other personal identifier to become a system of records for the purpose of this part.</P>
          <P>(2) If files that are not retrieved by name or personal identifier are rearranged in such manner that they are retrieved by name or personal identifier, a new systems notice must be submitted in accordance with §310.63(c) of subpart G.</P>
          <P>(3) If records in a system of records are rearranged so that retrieval is no longer by name or other personal identifier, the records are no longer subject to this part and the system notice for the records shall be deleted in accordance with § 310.64(c) of subpart G.</P>
          <P>(c) <E T="03">Relevance and necessity.</E> Retain in a system of records only that personal information which is relevant and necessary to accomplish a purpose required by a federal statute or an Executive Order.</P>
          <P>(d) <E T="03">Authority to establish systems of records.</E> Identify the specific statute or the Executive Order that authorize maintaining personal information in each system of records. The existance of a statute or Executive order mandating the maintenance of a system of records does not abrogate the responsibility to ensure that the information in the system of records is relevant and necessary.</P>
          <P>(e) <E T="03">Exercise of First Amendment rights.</E> (1) Do not maintain any records describing how an individual exercises his or her rights guaranteed by the First Amendment of the U.S. Constitution except when:</P>
          <P>(i) Expressly authorized by federal statute;</P>
          <P>(ii) Expressly authorized by the individual; or</P>
          <P>(iii) Maintenance of the information is pertinent to and within the scope of an authorized law enforcement activity.</P>
          <P>(2) First Amendment rights include, but are not limited to, freedom of religion, freedom of political beliefs, freedom of speech, freedom of the press, the right to assemble, and the right to petition.</P>
          <P>(f) <E T="03">System manager's evaluation.</E> (1) Evaluate the information to be included in each new system before establishing the system and evaluate periodically the information contained in each existing system of records for relevancy and necessity. Such a review shall also occur when a system notice amendment or alteration is prepared (see §§ 310.63 and 310.64 of subpart G).</P>
          <P>(2) Consider the following:</P>
          <P>(i) The relationship of each item of information retained and collected to the purpose for which the system is maintained;</P>
          <P>(ii) The specific impact on the purpose or mission of not collecting each category of information contained in the system;</P>

          <P>(iii) The possibility of meeting the information requirements through use of information not individually identifiable or through other techniques, such as sampling;<PRTPAGE P="817"/>
          </P>
          <P>(iv) The length of time each item of personal information must be retained;</P>
          <P>(v) The cost of maintaining the information; and</P>
          <P>(vi) The necessity and relevancy of the information to the purpose for which it was collected.</P>
          <P>(g) <E T="03">Discontinued information requirements.</E> (1) Stop collecting immediately any category or item of personal information from which retention is no longer justified. Also excise this information from existing records, when feasible.</P>
          <P>(2) Do not destroy any records that must be retained in accordance with disposal authorizations established under 44 U.S.C. 303a, “Examination by the Administrator of General Services of Lists and Schedules of Records Lacking Preservation Value, Disposal of Records.”</P>
          <CITA>[51 FR 2364, Jan. 16, 1986. Redesignated at 56 FR 55631, Oct. 29, 1991, and amended at 56 FR 57800, Nov. 14, 1991]</CITA>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.11</SECTNO>
          <SUBJECT>Standards of accuracy.</SUBJECT>
          <P>(a) <E T="03">Accuracy of information maintained.</E> Maintain all personal information that is used or may be used to make any determination about an individual with such accuracy, relevance, timeliness, and completeness as is reasonably necessary to ensure fairness to the individual in making any such determination.</P>
          <P>(b) <E T="03">Accuracy determination before dissemination.</E> Before disseminating any personal information from a system of records to any person outside the Department of Defense, other than a federal agency, make reasonable efforts to ensure that the information to be disclosed is accurate, relevant, timely, and complete for the purpose it is being maintained (see also § 310.30(d), subpart D and § 310.40(d), subpart E).</P>
          <CITA>[51 FR 2364, Jan. 16, 1986. Redesignated at 56 FR 55631, Oct. 29, 1991, and amended at 56 FR 57800, Nov. 14, 1991]</CITA>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.12</SECTNO>
          <SUBJECT>Government contractors.</SUBJECT>
          <P>(a) <E T="03">Applicability to government contractors.</E> (1) When a DoD Component contracts for the operation or maintenance of a system of records or a portion of a system of records by a contractor, the record system or the portion of the record system affected are considered to be maintained by the DoD Component and are subject to this part. The Component is responsible for applying the requirements of this part to the contractor. The contractor and its employees are to be considered employees of the DoD Component for purposes of the sanction provisions of the Privacy Act during the performance of the contract. Consistent with the Defense Acquisition Regulation (DAR), § 1.327, “Protection of Individual Privacy” contracts requiring the maintenance of a system of records or the portion of a system of records shall identify specifically the record system and the work to be performed and shall include in the solicitation and resulting contract such terms as are prescribed by the DAR.</P>
          <P>(2) If the contractor must use or have access to individually identifiable information subject to this part to perform any part of a contract, and the information would have been collected and maintained by the DoD Component but for the award of the contract, these contractor activities are subject to this Regulation.</P>
          <P>(3) The restriction in paragraphs (a) (1) and (2) of § 310.12 do not apply to records:</P>
          <P>(i) Established and maintained to assist in making internal contractor management decisions, such as records maintained by the contractor for use in managing the contract;</P>
          <P>(ii) Maintained as internal contractor employee records even when used in conjunction with providing goods and services to the Department of Defense; or</P>
          <P>(iii) Maintained as training records by an educational organization contracted by a DoD Component to provide training when the records of the contract students are similar to and comingled with training records of other students (for example, admission forms, transcripts, academic counselling and similar records);</P>
          <P>(iv) Maintained by a consumer reporting agency to which records have been disclosed under contract in accordance with the Federal Claims Collection Act of 1966, 31 U.S.C. 952(d).</P>
          <P>(4) DoD Components must publish instruction that:<PRTPAGE P="818"/>
          </P>
          <P>(i) Furnish DoD Privacy Program guidance to their personnel who solicit, award, or administer government contracts;</P>
          <P>(ii) Inform prospective contractors of their responsibilities regarding the DoD Privary Program; and</P>
          <P>(iii) Establish an internal system of contractor performance review to ensure compliance with the DoD Privacy Program.</P>
          <P>(b) <E T="03">Contracting procedures</E>. The Defense Systems Acquisition Regulatory Council (DSARC) is responsible for developing the specific policies and procedures to be followed when soliciting bids, awarding contracts or administering contracts that are subject to this part.</P>
          <P>(c) <E T="03">Contractor compliance</E>. Through the various contract surveillance programs, ensure contractors comply with the procedures established in accordance with paragraph (b) above of this subpart.</P>
          <P>(d) <E T="03">Disclosure of records to contractors</E>. Disclosure of personal records to a contractor for the use in the performance of any DoD contrtact by a DoD Component is considered a disclosure within the Department of Defense (see § 310.40(b), subpart E). The contractor is considered the agent of the contracting DoD Component and to be maintaining and receiving the records for that Component.</P>
          <CITA>[51 FR 2364, Jan. 16, 1986. Redesignated at 56 FR 55631, Oct. 29, 1991, and amended at 56 FR 57800, Nov. 14, 1991]</CITA>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.13</SECTNO>
          <SUBJECT>Safeguarding personal information.</SUBJECT>
          <P>(a) <E T="03">General responsibilities</E>. Establish appropriate administrative, technical and physical safeguards to ensure that the records in every system of records are protected from unauthorized alteration or disclosure and that their confidentiality is protected. Protect the records against reasonably anticipated threats or hazards that could result in substantial harm, embarrassment, inconvenience, or unfairness to any individual about whom information is kept.</P>
          <P>(b) <E T="03">Minimum standards</E>. (1) Tailor system safeguards to conform to the type of records in the system, the sensitivity of the personal information stored, the storage medium used and, to a degree, the number of records maintained.</P>
          <P>(2) Treat all unclassified records that contain personal information that normally would be withheld from the public under Exemption Numbers 6 and 7, of § 286.31, subpart D of 32 CFR part 286 (DoD Freedom of Information Act Program) as if they were designated “For Official Use Only” and safeguard them in accordance with the standards established by subpart E of 32 CFR part 286 (DoD FOIA Program) even if they are not actually marked “For Official Use Only.”</P>
          <P>(3) Afford personal information that does not meet the criteria discussed in paragraph (c)(3) of this section that degree of security which provides protection commensurate with the nature and type of information involved.</P>
          <P>(4) Special administrative, physical, and technical procedures are required to protect data that is stored or being processed temporarily in an automated data processing (ADP) system or in a word processing activity to protect it against threats unique to those environments (see Appendices A and B).</P>
          <P>(5) Tailor safeguards specifically to the vulnerabilities of the system.</P>
          <P>(c) <E T="03">Records disposal</E>. (1) Dispose of records containing personal data so as to prevent inadvertent compromise. Disposal methods such as tearing, burning, melting, chemical decomposition, pulping, pulverizing, shredding, or mutilation are considered adequate if the personal data is rendered unrecognizable or beyond reconstruction.</P>
          <P>(2) The transfer of large quantities of records containing personal data (for example, computer cards and printouts) in bulk to a disposal activity, such as the Defense Property Disposal Office, is not a release of personal information under this part. The sheer volume of such transfers make it difficult or impossible to identify readily specific individual records.</P>

          <P>(3) When disposing of or destroying large quantities of records containing personal information, care must be exercised to ensure that the bulk of the records is maintained so as to prevent specific records from being readily identified. If bulk is maintained, no special procedures are required. If bulk <PRTPAGE P="819"/>cannot be maintained or if the form of the records make individually identifiable information easily available, dispose of the record in accordance with paragraph (c)(1) of this section.</P>
        </SECTION>
      </SUBPART>
      <SUBPART>
        <HD SOURCE="HED">Subpart C—Collecting Personal Information</HD>
        <SECTION>
          <SECTNO>§ 310.20</SECTNO>
          <SUBJECT>General considerations.</SUBJECT>
          <P>(a) <E T="03">Collect directly from the individual</E>. Collect to the greatest extent practicable personal information directly from the individual to whom it pertains if the information may be used in making any determination about the rights, privileges, or benefits of the individual under any federal program (see also paragraph (c) of this section).</P>
          <P>(b) <E T="03">Collecting Social Security Numbers (SSNs)</E>. (1) It is unlawful for any federal, state, or local governmental agency to deny an individual any right, benefit, or privilege provided by law because the individual refuses to provide his or her SSN. However, if a federal statute requires that the SSN be furnished or if the SSN is required to verify the identity of the individual in a system of records that was established and in use before January 1, 1975, and the SSN was required as an identifier by a statute or regulation adopted before that date, this restriction does not apply.</P>
          <P>(2) When an individual is requested to provide his or her SSN, he or she must be advised:</P>
          <P>(i) The uses that will be made of the SSN;</P>
          <P>(ii) The statute, regulation, or rule authorizing the solicitation of the SSN; and</P>
          <P>(iii) Whether providing the SSN is voluntary or mandatory.</P>
          <P>(3) Include in any systems notice for any system of records that contains SSNs a statement indicating the authority for maintaining the SSN and the sources of the SSNs in the system. If the SSN is obtained directly from the individual indicate whether this is voluntary or mandatory.</P>

          <P>(4) Executive Order 9397, “Numbering System For Federal Accounts Relating to Individual Persons,” November 30, 1943, authorizes solicitation and use of SSNs as numerical identifier for individuals in most Federal records systems. However, it does not provide <E T="03">mandatory</E> authority for soliciting SSNs.</P>
          <P>(5) Upon entrance into military service or civilian employment with the Department of Defense, individuals are asked to provide their SSNs. The SSN becomes the service or employment number for the individual and is used to establish personnel, financial, medical, and other official records. Provide the notification in paragraph (b)(2) of this section to the individual when originally soliciting his or her SSN. After an individual has provided his or her SSN for the purpose of establishing a record, the notification in paragraph (b)(2) is not required if the individual is only requested to furnish or verify the SSNs for identification purposes in connection with the normal use of his or her records. However, if the SSN is to be written down and retained for any purpose by the requesting official, the individual must be provided the notification required by paragraph (b)(2) of this section.</P>
          <P>(6) Consult the Office of Personnel Management, Federal Personnel Manual (5 CFR parts 293, 294, 297 and 735) when soliciting SSNs for use in OPM records systems.</P>
          <P>(c) <E T="03">Collecting personal information from third parties.</E> It may not be practical to collect personal information directly from the individual in all cases. Some examples of this are:</P>
          <P>(1) Verification of information through third party sources for security or employment suitability determinations;</P>
          <P>(2) Seeking third party opinions such as supervisory comments as to job knowledge, duty performance, or other opinion-type evaluations;</P>
          <P>(3) When obtaining the needed information directly from the individual is exceptionally difficult or may result in unreasonable costs; or</P>
          <P>(4) Contacting a third party at the request of the individual to furnish certain information such as exact periods of employment, termination dates, copies of records, or similar information.</P>
          <P>(d) <E T="03">Privacy Act Statements.</E> (1) When an individual is requested to furnish personal information about himself or herself for inclusion in a system of <PRTPAGE P="820"/>records, a Privacy Act Statement is required regardless of the medium used to collect the information (forms, personal interviews, stylized formats, telephonic interviews, or other methods). The Privacy Act Statement consists of the elements set forth in paragraph (d)(2) of this section. The statement enables the individual to make an informed decision whether to provide the information requested. If the personal information solicited is not to be incoporated into a system of records, the statement need not be given. However, personal information obtained without a Privacy Act Statement shall not be incorporated into any system of records. When soliciting SSNs for any purpose, see paragraph (b)(2) of this section.</P>
          <P>(2) The Privacy Act Statement shall include:</P>
          <P>(i) The specific federal statute or Executive Order that authorizes collection of the requested information (see paragraph (d) of § 310.10).</P>
          <P>(ii) The principal purpose or purposes for which the information is to be used;</P>
          <P>(iii) The routine uses that will be made of the information (see § 310.41(e), subpart E);</P>
          <P>(iv) Whether providing the information is voluntary or mandatory (see paragraph (e) of this section); and</P>
          <P>(v) The effects on the individual if he or she chooses not to provide the requested information.</P>
          <P>(3) The Privacy Act Statement shall be concise, current, and easily understood.</P>
          <P>(4) The Privacy Act statement may appear as a public notice (sign or poster), conspicuously displayed in the area where the information is collected, such as at check-cashing facilities or identification photograph facilities.</P>
          <P>(5) The individual normally is not required to sign the Privacy Act Statement.</P>
          <P>(6) Provide the individual a written copy of the Privacy Act Statement upon request. This must be done regardless of the method chosen to furnish the initial advisement.</P>
          <P>(e) <E T="03">Mandatory as opposed to voluntary disclosures.</E> Include in the Privacy Act Statement specifically whether furnishing the requested personal data is mandatory or voluntary. A requirement to furnish personal data is mandatory only when a federal statute, Executive Order, regulation, or other lawful order specifically imposes a duty on the individual to provide the information sought, and the individual is subject to a penalty if he or she fails to provide the requested information. If providing the information is only a condition of or prerequisite to granting a benefit or privilege and the individual has the option of requesting the benefit or privilege, providing the information is always voluntary. However, the loss or denial of the privilege, benefit, or entitlement sought may be listed as a consequence of not furnishing the requested information.</P>
          <CITA>[51 FR 2364, Jan. 16, 1986. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57800, Nov. 14, 1991]</CITA>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.21</SECTNO>
          <SUBJECT>Forms.</SUBJECT>
          <P>(a) <E T="03">DoD forms.</E> (1) DoD Directive 5000.21, “Forms Management Program” provides guidance for preparing Privacy Act Statements for use with forms (see also paragraph (b)(1) of this section).</P>
          <P>(2) When forms are used to collect personal information, the Privacy Act Statement shall appear as follows (listed in the order of preference):</P>

          <P>(i) In the body of the form, preferably just below the title so that the reader will be advised of the contents of the statement <E T="03">before</E> he or she begins to complete the form;</P>
          <P>(ii) On the reverse side of the form with an appropriate annotation under the title giving its location;</P>
          <P>(iii) On a tear-off sheet attached to the form; or</P>
          <P>(iv) As a separate supplement to the form.</P>
          <P>(b) <E T="03">Forms issued by non-DoD activities.</E> (1) Forms subject to the Privacy Act issued by other federal agencies have a Privacy Act Statement attached or included. Always ensure that the statement prepared by the originating agency is adequate for the purpose for which the form will be used by the DoD activity. If the Privacy Act Statement provided is inadequate, the DoD Component concerned shall prepare a new statement or a supplement to the existing statement before using the form.<PRTPAGE P="821"/>
          </P>
          <P>(2) Forms issued by agencies not subject to the Privacy Act (state, municipal, and other local agencies) do not contain Privacy Act Statements. Before using a form prepared by such agencies to collect personal data subject to this part, an appropriate Privacy Act Statement must be added.</P>
        </SECTION>
      </SUBPART>
      <SUBPART>
        <HD SOURCE="HED">Subpart D—Access by Individuals</HD>
        <SECTION>
          <SECTNO>§ 310.30</SECTNO>
          <SUBJECT>Individual access to personal information.</SUBJECT>
          <P>(a) <E T="03">Individual access.</E> (1) The access provisions of this part are intended for use by individuals about whom records are maintained in systems of records. Release of personal information to individuals under this part is not considered public release of information.</P>
          <P>(2) Make available to the individual to whom the record pertains all of the personal information that can be released consistent with DoD responsibilities.</P>
          <P>(b) <E T="03">Individual requests for access.</E> Individuals shall address requests for access to personal information in a system of records to the system manager or to the office designated in the DoD Component rules or the system notice.</P>
          <P>(c) <E T="03">Verification of identity.</E> (1) Before granting access to personal data, an individual may be required to provide reasonable verification of his or her identity.</P>
          <P>(2) Identity verification procedures shall not:</P>
          <P>(i) Be so complicated as to discourage unnecessarily individuals from seeking access to information about themselves; or</P>
          <P>(ii) Be required of an individual seeking access to records which normally would be available under the “DoD Freedom of Information Act Program” (32 CFR part 286).</P>
          <P>(3) Normally, when individuals seek personal access to records pertaining to themselves, identification is made from documents that normally are readily available, such as employee and military identification cards, driver's license, other licenses, permits or passes used for routine identification purposes.</P>
          <P>(4) When access is requested by mail, identity verification may consist of the individual providing certain minimum identifying data, such as full name, date and place of birth, or such other personal information necessary to locate the record sought. If the information sought is of a sensitive nature, additional identifying data may be required. If notarization of requests is required, procedures shall be established for an alternate method of verification for individuals who do not have access to notary services, such as military members overseas.</P>
          <P>(5) If an individual wishes to be accompanied by a third party when seeking access to his or her records or to have the records released directly to a third party, the individual may be required to furnish a signed access authorization granting the third party access.</P>
          <P>(6) An individual shall not be refused access to his or her record solely because he or she refuses to divulge his or her SSN unless the SSN is the only method by which retrieval can be made. (See § 310.20(b)).</P>
          <P>(7) The individual is not required to explain or justify his or her need for access to any record under this part.</P>
          <P>(8) Only a denial authority may deny access and the denial must be in writing and contain the information required by paragraph (b) of § 310.31.</P>
          <P>(d) <E T="03">Granting individual access to records.</E> (1) Grant the individual access to the original record or an exact copy of the original record without any changes or deletions, except when changes or deletions have been made in accordance with paragraph (e) of this section. For the purpose of granting access, a record that has been amended under § 310.31(b) is considered to be the original. See pargraph (e) of this section for the policy regarding the use of summaries and extracts.</P>
          <P>(2) Provide exact copies of the record when furnishing the individual copies of records under this part.</P>
          <P>(3) Explain in terms understood by the requestor any record or portion of a record that is not clear.</P>
          <P>(e) <E T="03">Illegible, incomplete, or partially exempt records.</E> (1) Do not deny an individual access to a record or a copy of a record solely because the physical condition or format of the record does not make it readily available (for example, deteriorated state or on magnetic <PRTPAGE P="822"/>tape). Either prepare an extract or recopy the document exactly.</P>
          <P>(2) If a portion of the record contains information that is exempt from access, an extract or summary containing all of the information in the record that is releasable shall be prepared.</P>
          <P>(3) When the physical condition of the record or its state makes it necessary to prepare an extract for release, ensure that the extract can be understood by the requester.</P>
          <P>(4) Explain to the requester all deletions or changes to the records.</P>
          <P>(f) <E T="03">Access to medical records.</E> (1) Disclose medical records to the individual to whom they pertain, even if a minor, unless a judgment is made that access to such records could have an adverse effect on the mental or physical health of the individual. Normally, this determination shall be made in consultation with a medical doctor.</P>
          <P>(2) If it is determined that the release of the medical information may be harmful to the mental or physical health of the individual:</P>
          <P>(i) Send the record to a physician named by the individual; and</P>
          <P>(ii) In the transmittal letter to the physician explain why access by the individual without proper professional supervision could be harmful (unless it is obvious from the record).</P>
          <P>(3) Do not require the physician to request the records for the individual.</P>
          <P>(4) If the individual refuses or fails to designate a physician, the record shall not be provided. Such refusal of access is not considered a denial for Privacy Act reporting purposes. (See paragraph (a) of § 310.31).</P>
          <P>(5) Access to a minor's medical records may be granted to his or her parents or legal guardians. However, observe the following procedures:</P>
          <P>(i) In the United States, the laws of the particular state in which the records are located may afford special protection to certain types of medical records (for example, records dealing with treatment for drug or alcohol abuse and certain psychiatric records). Even if the records are maintained by a military medical facilities these statutes may apply.</P>
          <P>(ii) For the purposes of parental access to the medical records and medical determinations regarding minors at overseas installation the age of majority is 18 years except when:</P>
          <P>(A) A minor at the time he or she sought or consented to the treatment was between 15 and 17 years of age;</P>
          <P>(B) The treatment was sought in a program which was authorized by regulation or statute to offer confidentiality of treatment records as a part of the program;</P>
          <P>(C) The minor specifically requested or indicated that he or she wished the treatment record to be handled with confidence and not released to a parent or guardian; and</P>
          <P>(D) The parent or guardian seeking access does not have the written authorization of the minor or a valid court order granting access.</P>
          <P>(iii) If all four of the above conditions are met, the parent or guardian shall be denied access to the medical records of the minor. Do not use these procedures to deny the minor access to his or her own records under this part or any other statutes.</P>
          <P>(6) All members of the Military Services and all married persons are not considered minors regardless of age, and the parents of these individuals do not have access to their medical records without written consent of the individual.</P>
          <P>(g) <E T="03">Access to information compiled in anticipation of civil action.</E> (1) An individual is not entitled under this part to gain access to information compiled in reasonable anticipation of a civil action or proceeding.</P>
          <P>(2) The term “civil proceeding” is intended to include quasi-judicial and pretrial judicial proceedings that are the necessary preliminary steps to formal litigation.</P>
          <P>(3) Attorney work products prepared in conjunction with quasi-judicial pretrial, and trial proceedings, to include those prepared to advise DoD Component officials of the possible legal consequences of a given course of action, are protected.</P>
          <P>(h) <E T="03">Access to investigatory records.</E> (1) Requests by individuals for access to investigatory records pertaining to themselves and compiled for law enforcement purposes are processed under <PRTPAGE P="823"/>this part of the DoD Freedom of Information Program (32 CFR part 286) depending on which part gives them the greatest degree of access.</P>
          <P>(2) Process requests by individuals for access to investigatory record pertaining to themselves compiled for law enforcement purposes and in the custody of law enforcement activities that have been incorporated into systems of records exempted from the access provisions of this part in accordance with section B of chapter 5 under reference (f). Do not deny an individual access to the record solely because it is in the exempt system, but give him or her automatically the same access he or she would receive under the Freedom of Information Act (5 U.S.C. 552). (See also paragraph (h) of this section.)</P>
          <P>(3) Process requests by individuals for access to investigatory records pertaining to themselves that are in records systems exempted from access provisions under paragraph (a) of § 310.52, subpart F, under this part, or the DoD Freedom of Information Act Program (32 CFR part 286) depending upon which regulation gives the greatest degree of access (see also paragraph (j) of this section).</P>
          <P>(4) Refer individual requests for access to investigatory records exempted from access under a general exemption temporarily in the hands of a noninvestigatory element for adjudicative or personnel actions to the originating investigating agency. Inform the requester in writing of these referrals.</P>
          <P>(i) <E T="03">Nonagency records.</E> (1) Certain documents under the physical control of DoD personnel and used to assist them in performing official functions, are not considered “agency records” within the meaning of this Regulation. Uncirculated personal notes and records that are not disseminated or circulated to any person or organization (for example, personal telephone lists or memory aids) that are retained or discarded at the author's discretion and over which the Component exercises no direct control, are not considered agency records. However, if personnel are officially directed or encouraged, either in writing or orally, to maintain such records, they may become “agency records,” and may be subject to this part.</P>
          <P>(2) The personal uncirculated handwritten notes of unit leaders, office supervisors, or military supervisory personnel concerning subordinates are not systems of records within the meaning of this part. Such notes are an extension of the individual's memory. These notes, however, must be maintained and discarded at the discretion of the individual supervisor and not circulated to others. Any established requirement to maintain such notes (such as, written or oral directives, regulations, or command policy) make these notes “agency records” and they then must be made a part of a system of records. If the notes are circulated, they must be made a part of a system of records. Any action that gives personal notes the appearance of official agency records is prohibited, unless the notes have been incorporated into a system of records.</P>
          <P>(j) <E T="03">Relationship between the Privacy Act and the Freedom of Information Act.</E> (1) Process requests for individual access as follows:</P>
          <P>(i) Requests by individuals for access to records pertaining to themselves made under the Freedom of Information Act (5 U.S.C. 552) or the DoD Freedom of Information Act Program (32 CFR part 286) or DoD Component instuctions implementing the DoD Freedom of Information Act Program are processed under the provisions of that reference.</P>
          <P>(ii) Requests by individuals for access to records pertaining to themselves made under the Privacy Act of 1971 (5 U.S.C. 552a), this part, or the DoD Component instructions implementing this part are processed under this part.</P>
          <P>(iii) Requests by individuals for access to records about themselves that cite both Acts or the implementing regulations and instructions for both Acts are processed under this part except:</P>
          <P>(A) When the access provisions of the DoD Freedom of Information Act Program (32 CFR part 286) provide a greater degree of access; or</P>
          <P>(B) When access to the information sought is controlled by another federal statute.</P>

          <P>(C) If the former applies, follow the provisions of 32 CFR part 286; and if the <PRTPAGE P="824"/>later applies, follow the access procedures established under the controlling statute.</P>
          <P>(iv) Requests by individuals for access to information about themselves in systems of records that do not cite either Act or the implementing regulations or instructions for either Act are processed under the procedures established by this part. However, there is no requirement to cite the specific provisions of this part or the Privacy Act (5 U.S.C. 552a) when responding to such requests. Do not count these requests as Privacy Act request for reporting purposes (see subpart I).</P>
          <P>(2) Do not deny individuals access to personal information concerning themselves that would otherwise be releasable to them under either Act solely because they fail to cite either Act or cite the wrong Act, regulation, or instruction.</P>
          <P>(3) Explain to the requester which Act or procedures have been used when granting or denying access under either Act (see also paragraph (j)(1)(iv) of this section).</P>
          <P>(k) <E T="03">Time limits.</E> Normally acknowledge requests for access within 10 working days after receipt and provide access within 30 working days.</P>
          <P>(l) <E T="03">Privacy case file.</E> Establish a Privacy Act case file when required (see paragraph (p) of § 310.32 of this subpart).</P>
          <CITA>[51 FR 2364, Jan. 16, 1986. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57800, Nov. 14, 1991]</CITA>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.31</SECTNO>
          <SUBJECT>Denial of individual access.</SUBJECT>
          <P>(a) <E T="03">Denying individual access.</E> (1) An individual may be denied formally access to a record pertaining to him or her only if the record:</P>
          <P>(i) Was compiled in reasonable anticipation of civil action (see paragraph (g) of § 310.30)</P>
          <P>(ii) Is in a system of records that has been exempted from the access provisions of this regulation under one of the permitted exemptions (see subpart F).</P>
          <P>(iii) Contains classified information that has been exempted from the access provision of this part under blanket exemption for such material claimed for all DoD records system (see §310.50(c) of subpart F).</P>
          <P>(iv) Is contained in a system of records for which access may be denied under some other federal statute.</P>
          <P>(2) Only deny the individual access to those portions of the records from which the denial of access serves some legitimate governmental purpose.</P>
          <P>(b) <E T="03">Other reasons to refuse access.</E> (1) An individual may be refused access if:</P>
          <P>(i) The record is not described well enough to enable it to be located with a reasonable amount of effort on the part of an employee familiar with the file; or</P>
          <P>(ii) Access is sought by an individual who fails or refuses to comply with the established procedural requirements, including refusing to name a physician to receive medical records when required (see paragraph (f) of §310.30) or to pay fees (see §310.33 of this subpart).</P>
          <P>(2) Always explain to the individual the specific reason access has been refused and how he or she may obtain access.</P>
          <P>(c) <E T="03">Notifying the individual.</E> Formal denials of access must be in writing and include as a minimum:</P>
          <P>(1) The name, title or position, and signature of a designated Component denial authority;</P>
          <P>(2) The date of the denial;</P>
          <P>(3) The specific reason for the denial, including specific citation to the appropriate sections of the Privacy Act (5 U.S.C. 552a) or other statutes, this part, DoD Component instructions or Code of Federal Regulations (CFR) authorizing the denial;</P>
          <P>(4) Notice to the individual of his or her right to appeal the denial through the Component appeal procedure within 60 calendar days; and</P>
          <P>(5) The title or position and address of the Privacy Act appeals official for the Component.</P>
          <P>(d) <E T="03">DoD Component appeal procedures.</E> Establish internal appeal procedures that, as a minimum, provide for:</P>
          <P>(1) Review by the head of the Component or his or her designee of any appeal by an individual from a denial of access to Component records.</P>
          <P>(2) Formal written notification to the individual by the appeal authority that shall:</P>

          <P>(i) If the denial is sustained totally or in part, include as a minimum:<PRTPAGE P="825"/>
          </P>
          <P>(A) The exact reason for denying the appeal to include specific citation to the provisions of the Act or other statute, this part, Component instructions or the CFR upon which the determination is based;</P>
          <P>(B) The date of the appeal determination;</P>
          <P>(C) The name, title, and signature of the appeal authority;</P>
          <P>(D) A statement informing the applicant of his or her right to seek judicial relief.</P>
          <P>(ii) If the appeal is granted, notify the individual and provide access to the material to which access has been granted.</P>
          <P>(3) The written appeal notification granting or denying access is the final Component action as regards access.</P>
          <P>(4) The individual shall file any appeals from denial of access within no less than 60 calendar days of receipt of the denial notification.</P>
          <P>(5) Process all appeals within 30 days of receipt unless the appeal authority determines that a fair and equitable review cannot be made within that period. Notify the applicant in writing if additional time is required for the appellate review. The notification must include the reasons for the delay and state when the individual may expect an answer to the appeal.</P>
          <P>(e) <E T="03">Denial of appeals by failure to act.</E> A requester may consider his or her appeal formally denied if the authority fails:</P>
          <P>(1) To act on the appeal within 30 days;</P>
          <P>(2) To provide the requester with a notice of extension within 30 days; or</P>
          <P>(3) To act within the time limits established in the Component's notice of extension (see paragraph (d)(5) of this section).</P>
          <P>(f) <E T="03">Denying access to OPM records held by DoD Components.</E> (1) The records in all systems of records maintained in accordance with the OPM government-wide system notices are technically only in the temporary custody of the Department of Defense.</P>
          <P>(2) All requests for access to these records must be processed in accordance with the Federal Personnel Manual (5 CFR parts 293, 294, 297 and 735) as well as the applicable Component procedures.</P>
          <P>(3) When a DoD Component refuses to grant access to a record in an OPM system, the Component shall instruct the individual to direct his or her appeal to the appropriate Component appeal authority, not the Office of Personnel Management.</P>
          <P>(4) The Component is responsible for the administrative review of its denial of access to such records.</P>
          <CITA>[51 FR 2364, Jan. 16, 1986. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57800, Nov. 14, 1991]</CITA>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.32</SECTNO>
          <SUBJECT>Amendment of records.</SUBJECT>
          <P>(a) <E T="03">Individual review and correction.</E> Individuals are encouraged to review the personnel information being maintained about them by DoD Components periodically and to avail themselves of the procedures established by this part and any other Component regulations to update their records.</P>
          <P>(b) <E T="03">Amending records.</E> (1) An individual may request the amendment of any record contained in a system of records pertaining to him or her unless the system of record has been exempted specifically from the amendment procedures of this part under paragraph (b) of § 310.50, subpart F. Normally, amendments under this part are limited to correcting factual matters and not matters of official judgment, such as performance ratings, promotion potential, and job performance appraisals.</P>
          <P>(2) While a Component may require that the request for amendment be in writing, this requirement shall not be used to discourage individuals from requesting valid amendments or to burden needlessly the amendment process.</P>
          <P>(3) A request for amendment must include:</P>
          <P>(i) A description of the item or items to be amended;</P>
          <P>(ii) The specific reason for the amendment;</P>
          <P>(iii) The type of amendment action sought (deletion, correction, or addition); and</P>
          <P>(iv) Copies of available documentary evidence supporting the request.</P>
          <P>(c) <E T="03">Burden of proof.</E> The applicant must support adequately his or her claim.</P>
          <P>(d) <E T="03">Identification of requesters.</E> (1) Individuals may be required to provide <PRTPAGE P="826"/>identification to ensure that they are indeed seeking to amend a record pertaining to themselves and not, inadvertently or intentionally, the record of others.</P>
          <P>(2) The indentification procedures shall not be used to discourage legitimate requests or to burden needlessly or delay the amendment process. (See paragraph (c) of § 310.30).</P>
          <P>(e) <E T="03">Limits on attacking evidence previously submitted.</E> (1) The amendment process is not intended to permit the alteration of evidence presented in the course of judicial or quasi-judicial proceedings. Any amendments or changes to these records normally are made through the specific procedures established for the amendment of such records.</P>
          <P>(2) Nothing in the amendment process is intended or designed to permit a collateral attack upon what has already been the subject of a judicial or quasi-judicial determination. However, while the individual may not attack the accuracy of the judicial or quasi-judicial determination under this part, he or she may challenge the accuracy of the recording of that action.</P>
          <P>(f) <E T="03">Sufficiency of a request to amend.</E> Consider the following factors when evaluating the sufficiency of a request to amend:</P>
          <P>(1) The accuracy of the information itself; and</P>
          <P>(2) The relevancy, timeliness, completeness, and necessity of the recorded information for accomplishing an assigned mission or purpose.</P>
          <P>(g) <E T="03">Time limits.</E> (1) Provide written acknowledgement of a request to amend within 10 working days of its receipt by the appropriate systems manager. There is no need to acknowledge a request if the action is completed within 10 working days and the individual is so informed.</P>
          <P>(2) The letter of acknowledgement shall clearly identify the request and advise the individual when he or she may expect to be notified of the completed action.</P>
          <P>(3) Only under the most exceptional circumstances shall more than 30 days be required to reach a decision on a request to amend. Document fully and explain in the Privacy Act case file (see paragraph (p) of this section) any such decision that takes more than 30 days to resolve.</P>
          <P>(h) <E T="03">Agreement to amend.</E> If the decision is made to grant all or part of the request for amendment, amend the record accordingly and notify the requester.</P>
          <P>(i) <E T="03">Notification of previous recipients.</E> (1) Notify all previous recipients of the information, as reflected in the disclosure accounting records, that an amendment has been made and the substance of the amendment. Recipients who are known to be no longer retaining the information need not be advised of the amendment. All DoD Components and federal agencies known to be retaining the record or information, even if not reflected in a disclosure record, shall be notified of the amendment. Advise the requester of these notifications.</P>
          <P>(2) Honor all requests by the requester to notify specific federal agencies of the amendment action.</P>
          <P>(j) <E T="03">Denying amendment.</E> If the request for amendment is denied in whole or in part, promptly advise the individual in writing of the decision to include:</P>
          <P>(1) The specific reason and authority for not amending;</P>
          <P>(2) Notification that he or she may seek further independent review of the decision by the head of the Component or his or her designee;</P>
          <P>(3) The procedures for appealing the decision citing the position and address of the official to whom the appeal shall be addressed; and</P>
          <P>(4) Where he or she can receive assistance in filing the appeal.</P>
          <P>(k) <E T="03">DoD Component appeal procedures.</E> Establish procedures to ensure the prompt, complete, and independent review of each amendment denial upon appeal by the individual. These procedures must ensure that:</P>
          <P>(1) The appeal with all supporting materials both that furnished the individual and that contained in Component records is provided to the reviewing official, and</P>
          <P>(2) If the appeal is denied completely or in part, the individual is notified in writing by the reviewing official that:</P>

          <P>(i) The appeal has been denied and the specific reason and authority for the denial;<PRTPAGE P="827"/>
          </P>
          <P>(ii) The individual may file a statement of disagreement with the appropriate authority and the procedures for filing this statement;</P>
          <P>(iii) If filed properly, the statement of disagreement shall be included in the records, furnished to all future recipients of the records, and provided to all prior recipients of the disputed records who are known to hold the record; and</P>
          <P>(iv) The individual may seek a judicial review of the decision not to amend.</P>
          <P>(3) If the record is amended, ensure that:</P>
          <P>(i) The requester is notified promptly of the decision;</P>
          <P>(ii) All prior known recipients of the records who are known to be retaining the record are notified of the decision and the specific nature of the amendment (see paragraph (i) of this section); and</P>
          <P>(iii) The requester is notified as to which DoD Components and federal agencies have been told of the amendment.</P>
          <P>(4) Process all appeals within 30 days unless the appeal authority determines that a fair review cannot be made within this time limit. If additional time is required for the appeal, notify the requester, in writing, of the delay, the reason for the delay, and when he or she may expect a final decision on the appeal. Document fully all requirements for additional time in the Privacy Case File. (See paragraph (p) of this section)</P>
          <P>(l) <E T="03">Denying amendment of OPM records held by DoD Components.</E> (1) The records in all systems of records controlled by the Office of Personnel Management (OPM) government-wide system notices are technically only temporarily in the custody of the Department of Defense.</P>
          <P>(2) All requests for amendment of these records must be processed in accordance with the OPM Federal Personnel Manual (5 CFR parts 293, 294, 297 and 735). The Component denial authority may deny a request. However, the appeal process for all such denials must include a review by the Assistant Director for Agency Compliance and Evaluation, Office of Personnel Management, 1900 E Street NW, Washington, DC 20415.</P>
          <P>(3) When an appeal is received from a Component's denial of amendment of the OPM controlled record, process the appeal in accordance with the OPM Federal Personnel Manual (5 CFR parts 293, 294, 297 and 735) and notify the OPM appeal authority listed above.</P>
          <P>(4) The individual may appeal any Component decision not to amend the OPM records directly to OPM.</P>
          <P>(5) OPM is the final review authority for any appeals from a denial to amend the OPM records.</P>
          <P>(m) <E T="03">Statements of disagreement submitted by individuals.</E> (1) If the reviewing authority refuses to amend the record as requested, the individual may submit a concise statement of disagreement setting forth his or her reasons for disagreeing with the decision not to amend.</P>
          <P>(2) If an individual chooses to file a statement of disagreement, annotate the record to indicate that the statement has been filed (see paragraph (n) of this section).</P>
          <P>(3) Furnish copies of the statement of disagreement to all DoD Components and federal agencies that have been provided copies of the disputed information and who may be maintaining the information.</P>
          <P>(n) <E T="03">Maintaining statements of disagreement.</E> (1) When possible, incorporate the statement of disagreement into the record.</P>
          <P>(2) If the statement cannot be made a part of the record, establish procedures to ensure that it is apparent from the records that a statement of disagreement has been filed and maintain the statement so that it can be obtained readily when the disputed information is used or disclosed.</P>
          <P>(3) Automated record systems that are not programed to accept statements of disagreement shall be annotated or coded so that they clearly indicate that a statement of disagreement is on file, and clearly identify the statement with the disputed information in the system.</P>

          <P>(4) Provide a copy of the statement of disagreement whenever the disputed information is disclosed for any purpose.<PRTPAGE P="828"/>
          </P>
          <P>(o) <E T="03">DoD Component summaries of reasons for refusing to amend.</E> (1) A summary of reasons for refusing to amend may be included with any record for which a statement of disagreement is filed.</P>
          <P>(2) Include in this summary only the reasons furnished to the individual for not amending the record. Do not include comments on the statement of disagreement. Normally, the summary and statement of disagreement are filed together.</P>
          <P>(3) When disclosing information for which a summary has been filed, a copy of the summary may be included in the release, if the Component desires.</P>
          <P>(p) <E T="03">Privacy Case Files.</E> (1) Establish a separate Privacy Case File to retain the documentation received and generated during the amendment or access process.</P>
          <P>(2) The Privacy Case File shall contain as a minimum:</P>
          <P>(i) The request for amendment or access;</P>
          <P>(ii) Copies of the DoD Component's reply granting or denying the request;</P>
          <P>(iii) Any appeals from the individual;</P>
          <P>(iv) Copies of the action regarding the appeal with supporting documentation which is not in the basic file; and</P>
          <P>(v) Any other correspondence generated in processing the appeal, to include coordination documentation.</P>

          <P>(3) Only the items listed in paragraphs (p)(4) and (s) of this section may be included in the system of records challenged for amendment or for which access is sought. Do <E T="03">not</E> retain copies of unamended records in the basic record system if the request for amendment is granted.</P>
          <P>(4) The following items relating to an amendment request may be included in the disputed record system:</P>
          <P>(i) Copies of the amended record.</P>
          <P>(ii) Copies of the individual's statement of disagreement (see paragraph (m) of this section).</P>
          <P>(iii) Copies of Component summaries (see paragraph (o) of this section).</P>
          <P>(iv) Supporting documentation submitted by the individual.</P>
          <P>(5) The following items relating to an access request may be included in the basic records system:</P>
          <P>(i) Copies of the request;</P>
          <P>(ii) Copies of the Component's action granting total access.</P>
          <NOTE>
            <HD SOURCE="HED">Note.—A</HD>
            <P>separate Privacy case file need not be created in such cases.</P>
          </NOTE>
          <P>(iii) Copies of the Component's action denying access;</P>
          <P>(iv) Copies of any appeals filed;</P>
          <P>(v) Copies of the reply to the appeal.</P>
          <P>(6) There is no need to establish a Privacy case file if the individual has not cited the Privacy Act (reference (b)), this part, or the Component implementing instruction for this part.</P>
          <P>(7) Privacy case files shall not be furnished or disclosed to anyone for use in making any determination about the individual other than determinations made under this part.</P>
          <CITA>[51 FR 2364, Jan. 16, 1986. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57800, Nov. 14, 1991]</CITA>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.33</SECTNO>
          <SUBJECT>Reproduction fees.</SUBJECT>
          <P>(a) <E T="03">Assessing fees.</E> (1) Charge the individual only the direct cost of reproduction.</P>
          <P>(2) Do not charge reproduction fees if copying is:</P>
          <P>(i) The only means to make the record available to the individual (for example, a copy of the record must be made to delete classified information); or</P>
          <P>(ii) For the convenience of the DoD Component (for example, the Component has no reading room where an individual may review the record, or reproduction is done to keep the original in the Component's file).</P>
          <P>(3) No fees shall be charged when the record may be obtained without charge under any other regulation, directive, or statute.</P>
          <P>(4) Do not use fees to discourage requests.</P>
          <P>(b) <E T="03">No minimum fees authorized.</E> Use fees only to recoup direct reproduction costs associated with granting access. Minimum fees for duplication are not authorized and there is no automatic charge for processing a request.</P>
          <P>(c) <E T="03">Prohibited fees.</E> Do not charge or collect fees for:</P>
          <P>(1) Search and retrieval of records;</P>
          <P>(2) Review of records to determine releasability;<PRTPAGE P="829"/>
          </P>
          <P>(3) Copying records for DoD Component convenience or when the individual has not specifically requested a copy;</P>
          <P>(4) Transportation of records and personnel; or</P>
          <P>(5) Normal postage.</P>
          <P>(d) <E T="03">Waiver of fees.</E> (1) Normally, fees are waived automatically if the direct costs of a given request is less than $30. This fee waiver provision does not apply when a waiver has been granted to the individual before, and later requests appear to be an extension or duplication of that original request. A DoD Component may, however, set aside this automatic fee waiver provision when on the basis of good evidence it determines that the waiver of fees is not in the public interest.</P>
          <P>(2) Decisions to waiver or reduce fees that exceed the automatic waiver threshold shall be made on a case-by-case basis.</P>
          <P>(e) <E T="03">Fees for members of Congress.</E> Do not charge members of Congress for copying records furnished even when the records are requested under the Privacy Act on behalf of a constituent (see § 310.41(k) of subpart E). When replying to a constituent inquiry and the fees involved are substantial, consider suggesting to the Congressman that the constituent can obtain the information directly by writing to the appropriate offices and paying the costs. When practical, suggest to the Congressman that the record can be examined at no cost if the constituent wishes to visit the custodian of the record.</P>
          <P>(f) <E T="03">Reproduction fees computation.</E> Compute fees using the appropriate portions of the fee schedule in subpart G of the DoD Freedom of Information Program (32 CFR part 286).</P>
          <CITA>[51 FR 2364, Jan. 16, 1986. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57800, Nov. 14, 1991]</CITA>
        </SECTION>
      </SUBPART>
      <SUBPART>
        <HD SOURCE="HED">Subpart E—Disclosure of Personal Information to Other Agencies and Third Parties</HD>
        <SECTION>
          <SECTNO>§ 310.40</SECTNO>
          <SUBJECT>Conditions of disclosure.</SUBJECT>
          <P>(a) <E T="03">Disclosures to third parties.</E> (1) The Privacy Act only compels disclosure of records from a system of records to the individuals to whom they pertain.</P>
          <P>(2) All requests by individual for personal information about other individuals (third parties) shall be processed under the DoD Freedom of Information Program (32 CFR part 286), except for requests by the parents of a minor, or legal guardians of an individual, for access to the records pertaining to the minor or individual.</P>
          <P>(b) <E T="03">Disclosures among DoD Components.</E> For the purposes of disclosure and disclosure accounting, the Department of Defense is considered a single agency (see § 310.41(a)).</P>
          <P>(c) <E T="03">Disclosures outside the Department of Defense.</E> Do not disclose personal information from a system of records outside the Department of Defense unless:</P>
          <P>(1) The record has been requested by the individual to whom it pertains.</P>
          <P>(2) The written consent of the individual to whom the record pertains has been obtained for release of the record to the requesting agency, activity, or individual, or</P>
          <P>(3) The release is for one of the specific nonconsensual purposes set forth in § 310.41 of this part.</P>
          <P>(d) <E T="03">Validation before disclosure.</E> Except for releases made in accordance with the Freedom of Information Act (5 U.S.C. 552), before disclosing any personal information to any recipient outside the Department of Defense other than a federal agency or the individual to whom it pertains:</P>
          <P>(1) Ensure that the records are accurate, timely, complete, and relevant for agency purposes;</P>
          <P>(2) Contact the individual, if reasonably available, to verify the accuracy, timeliness, completeness, and relevancy of the information, if the cannot be determined from the record; or</P>
          <P>(3) If the information is not current and the individual is not reasonably available, advise the recipient that the information is believed accurate as of a specific date and any other known factors bearing on its accuracy and relevancy.</P>
          <CITA>[51 FR 2364, Jan. 16, 1986. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57800, Nov. 14, 1991]</CITA>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.41</SECTNO>
          <SUBJECT>Nonconsensual disclosures.</SUBJECT>
          <P>(a) <E T="03">Disclosures within the Department of Defense.</E> (1) Records pertaining to an <PRTPAGE P="830"/>individual may be disclosed without the consent of the individual to any DoD official who has need for the record in the performance of his or her assigned duties.</P>
          <P>(2) Rank, position, or title alone do not authorize access to personal information about others. An official need for the information must exist before disclosure.</P>
          <P>(b) <E T="03">Disclosures under the Freedom of Information Act.</E> (1) All records must be disclosed if their release is required by the Freedom of Information Act (5 U.S.C 552) see also the DoD Freedom of Information Program (32 CFR part 286). The Freedom of Information Act requires that records be made available to the public unless exempted from disclosure by one of the nine exemptions found in the Act. It follows, therefore, that if a record is not exempt from disclosure it must be disclosed.</P>
          <P>(2) The standard for exempting most personal records, such as personnel records, medical records, and similar records, is found in Exemption Number 6 of 32 CFR 286.31. Under that exemption, release of personal information can only be denied when its release would be a “clearly unwarranted invasion of personal privacy.”</P>
          <P>(3) Release of personal information in investigatory records including personnel security investigation records is controlled by the broader standard of an “unwarranted invasion of personal privacy” found in Exemption Number 7 of 32 CFR 286.31. This broader standard applies only to investigatory records.</P>
          <P>(4) See 32 CFR part 286 for the standards to use in applying these exemptions.</P>
          <P>(c) <E T="03">Personal information that is normally releasable—</E>(1) <E T="03">DoD civilian employees.</E> (i) Some examples of personal information regarding DoD civilian employees that normally may be released without a clearly unwarranted invasion of personal privacy include:</P>
          <P>(A) Name.</P>
          <P>(B) Present and past postion titles.</P>
          <P>(C) Present and past grades.</P>
          <P>(D) Present and past salaries.</P>
          <P>(E) Present and past duty stations.</P>
          <P>(F) Office or duty telephone numbers.</P>
          <P>(ii) All disclosures of personal information regarding federal civilian employees shall be made in accordance with the Federal Personnel Manual (FPM) 5 CFR parts 293, 294, 297 and 735.</P>
          <P>(2) <E T="03">Military members.</E> (i) While it is not possible to identify categorically information that must be released or withheld from military personnel records in every instance, the following items of personal information regarding military members normally may be disclosed without a clearly unwarranted invasion of their personal privacy:</P>
          <P>(A) Full name.</P>
          <P>(B) Rank.</P>
          <P>(C) Date of rank.</P>
          <P>(D) Gross salary.</P>
          <P>(E) Past duty assignments.</P>
          <P>(F) Present duty assignment.</P>
          <P>(G) Future assignments that are officially established.</P>
          <P>(H) Office of duty telephone numbers.</P>
          <P>(I) Source of commission.</P>
          <P>(J) Promotion sequence number.</P>
          <P>(K) Awards and decorations.</P>
          <P>(L) Attendance at professional military schools.</P>
          <P>(M) Duty status at any given time.</P>
          <P>(ii) All releases of personal information regarding military members shall be made in accordance with the standards established by 32 CFR part 286.</P>
          <P>(3) <E T="03">Civilian employees not under the FPM.</E> (i) While it is not possible to identify categorically those items of personal information that must be released regarding civilian employees not subject to the Federal Personnel Manual (5 CFR parts 293, 294, 297 and 735), such as nonappropriated fund employees, normally the following items may be released without a clearly unwarranted invasion of personal privacy:</P>
          <P>(A) Full name.</P>
          <P>(B) Grade or position.</P>
          <P>(C) Date of grade.</P>
          <P>(D) Gross salary.</P>
          <P>(E) Present and past assignments.</P>
          <P>(F) Future assignments, if officially established.</P>
          <P>(G) Office or duty telephone numbers.</P>
          <P>(ii) All releases of personal information regarding civilian personnel in this category shall be made in accordance with the standards established by 32 CFR part 286, the DoD Freedom of Information Program.</P>
          <P>(d) <E T="03">Release of home addresses and home telephone numbers.</E> (1) The release of home addresses and home telephone numbers normally is considered a <PRTPAGE P="831"/>clearly unwarranted invasion of personal privacy and is prohibited. However, these may be released without prior specific consent of the individual if:</P>
          <P>(i) The individual has indicated previously that he or she interposes no objection to their release (see paragraphs (d) (3) and (4) of this section);</P>
          <P>(ii) The source of the information to be released is a public document such as commercial telephone directory or other public listing;</P>
          <P>(iii) The release is required by federal statute (for example, pursuant to federally-funded state programs to locate parents who have defaulted on child support payments (42 U.S.C. 653); or</P>
          <P>(iv) The releasing official releases the information under the provisions of the DoD Freedom of Information Act Program (32 CFR part 286).</P>
          <P>(2) A request for a home address or telephone number may be referred to the last known address of the individual for a direct reply by him or her to the requester. In such cases the requester shall be notified of the referral.</P>
          <P>(3) When collecting lists of home addresses and telephone numbers, the individual may be offered the option of authorizing the information pertaining to him or her to be disseminated without further permission for specific purposes, such as locator services. In these cases, the information may be disseminated for the stated purpose without further consent. However, if the information is to be disseminated for any other purpose, a new consent is required. Normally such consent for release is in writing and signed by the individual.</P>
          <P>(4) Before listing home addresses and home telephone numbers in DoD telephone directories, give the individuals the opportunity to refuse such a listing. Excuse the individual from paying any additional cost that may be associated with maintaining an unlisted number for government-owned telephone services if the individual requests his or her number not be listed in the directory under this part.</P>
          <P>(5) Do not sell or rent lists of individual names and addresses unless such action is specifically authorized.</P>
          <P>(e) <E T="03">Disclosures for established routine uses.</E> (1) Records may be disclosed outside the Department of Defense without consent of the individual to whom they pertain for an established routine use.</P>
          <P>(2) A routine use shall:</P>
          <P>(i) Be compatible with and related to the purpose for which the record was compiled;</P>
          <P>(ii) Identify the persons or organizations to whom the record may be released;</P>
          <P>(iii) Identify specifically the uses to which the information may be put by the receiving agency; and</P>
          <P>(iv) Have been published previously in the <E T="04">Federal Register</E> (see § 310.62(i), subpart G).</P>
          <P>(3) Establish a routine use for each user of the information outside the Department of Defense who need official access to the records.</P>

          <P>(4) Routine uses may be established, discontinued, or amended without the consent of the individuals involved. However, new or changed routine uses must be published in the <E T="04">Federal Register</E> at least 30 days before actually disclosing any records under their provisions (see subpart G).</P>

          <P>(5) In addition to the routine uses established by the individual system notices, common blanket routine uses for all DoD-maintained systems of records have been established (see appendix C). These blanket routine uses are published only at the beginning of the listing of system notices for each Component in the <E T="04">Federal Register</E> (see paragraph § 310.62(a)(1), subpart G). Unless a system notice specifically excludes a system from a given blanket routine use, all blanket routine uses apply.</P>
          <P>(6) If the recipient has not been identified in the <E T="04">Federal Register</E> or a use to which the recipient intends to put the record has not been published in the system notice as a routine use, the written permission of the individual is required before release or use of the record for that purpose.</P>
          <P>(f) <E T="03">Disclosures to the Bureau of the Census.</E> Records in DoD systems of records may be disclosed without the consent of the individuals to whom <PRTPAGE P="832"/>they pertain to the Bureau of the Census for purposes of planning or carrying out a census survey or related activities pursuant to the provisions of 13 U.S.C. 8.</P>
          <P>(g) <E T="03">Disclosures for statistical research and reporting.</E> (1) Records may be disclosed for statistical research and reporting without the consent of the individuals to whom they pertain. Before such disclosures the recipient must provide advance written assurance that:</P>
          <P>(i) The records will be used as statistical research or reporting records;</P>
          <P>(ii) The records will only be transferred in a form that is not individually identifiable; and</P>
          <P>(iii) The records will not be used, in whole or in part, to make any determination about the rights, benefits, or entitlements of specific individuals.</P>
          <P>(2) A disclosure accounting (see paragraph (a) of § 310.44) is not required when information that is not identifiable individually is released for statistical research or reporting.</P>
          <P>(h) <E T="03">Disclosures to the National Archives and Records Administration (NARA).</E> (1) Records may be disclosed without the consent of the individual to whom they pertain to the NARA if they:</P>
          <P>(i) Have historical or other value to warrant continued preservation; or</P>
          <P>(ii) For evaluation by the NARA to determine if a record has such historical or other value.</P>
          <P>(2) Records transferred to a Federal Records Center (FRC) for safekeeping and storage do not fall within this category. These remain under the control of the transferring Component, and the FRC personnel are considered agents of the Component which retains control over the records. No disclosure accounting is required for the transfer of records to the FRCs.</P>
          <P>(i) <E T="03">Disclosures for law enforcement purposes.</E> (1) Records may be disclosed without the consent of the individual to whom they pertain to another agency or an instrumentality of any governmental jurisdiction within or under the control of the United States for a civil or criminal law enforcement activity, provided:</P>
          <P>(i) The civil or criminal law enforcement activity is authorized by law;</P>
          <P>(ii) The head of the law enforcement activity or a designee has made a written request specifying the particular records desired and the law enforcement purpose (such as criminal investigations, enforcement of a civil law, or a similar purpose) for which the record is sought; and</P>
          <P>(iii) There is no federal statute that prohibits the disclosure of the records.</P>
          <P>(2) Normally, blanket requests for access to any and all records pertaining to an individual are not honored.</P>
          <P>(3) When a record is released to a law enforcement activity under paragraph (i)(1) of this section, maintain a disclosure accounting. This disclosure accounting shall not be made available to the individual to whom the record pertains if the law enforcement activity requests that the disclosure not be released.</P>
          <P>(4) The blanket routine use for Law Enforcement (appendix C, section A.) applies to all DoD Component systems notices (see paragraph (e)(5) of this section). Only by including this routine use can a Component, on its own initiative, report indications of violations of law found in a system of records to a law enforcement activity without the consent of the individual to whom the record pertains (see paragraph (i)(1) of this section when responding to requests from law enforcement activities).</P>
          <P>(j) <E T="03">Emergency disclosures.</E> (1) Records may be disclosed without the consent of the individual to whom they pertain if disclosure is made under compelling circumstances affecting the health or safety of any individual. The affected individual need not be the subject of the record disclosed.</P>
          <P>(2) When such a disclosure is made, notify the individual who is the subject of the record. Notification sent to the last known address of the individual as reflected in the records is sufficient.</P>
          <P>(3) The specific data to be disclosed is at the discretion of releasing authority.</P>
          <P>(4) Emergency medical information may be released by telephone.</P>
          <P>(k) <E T="03">Disclosures to Congress and the General Accounting Office.</E> (1) Records may be disclosed without the consent of the individual to whom they pertain to either House of the Congress or to <PRTPAGE P="833"/>any committee, joint committee or subcommittee of Congress if the release pertains to a matter within the jurisdiction of the committee. Records may also be disclosed to the General Accounting Office (GAO) in the course of the activities of GAO.</P>
          <P>(2) The blanket routine use for “Congressional Inquiries” (see appendix C, section D.) applies to all systems; therefore, there is no need to verify that the individual has authorized the release of his or her record to a congressional member when responding to a congressional constituent inquiry.</P>
          <P>(3) If necessary, accept constituent letters requesting a member of Congress to investigate a matter pertaining to the individual as written authorization to provide access to the records to the congressional member or his or her staff.</P>
          <P>(4) The verbal statement by a congressional staff member is acceptable to establish that a request has been received from the person to whom the records pertain.</P>
          <P>(5) If the constituent inquiry is being made on behalf of someone other than the individual to whom the record pertains, provide the congressional member only that information releasable under the Freedom of Information Act (5 U.S.C. 552). Advise the congressional member that the written consent of the individual to whom the record pertains is required before any additional information may be released. Do not contact individuals to obtain their consents for release to congressional members unless a congressional office specifically requests that this be done.</P>
          <P>(6) Nothing in paragraph (k)(2) of this section prohibits a Component, when appropriate, from providing the record directly to the individual and notifying the congressional office that this has been done without providing the record to the congressional member.</P>
          <P>(7) See paragraph (e) of § 310.33 for the policy on assessing fees for Members of Congress.</P>
          <P>(8) Make a disclosure accounting each time a record is disclosed to either House of Congress, to any committee, joint committee, or subcommittee of Congress, to any congressional member, or GAO.</P>
          <P>(l) <E T="03">Disclosures under court orders.</E> (1) Records may be disclosed without the consent of the person to whom they pertain under a court order signed by a judge of a court of competent jurisdiction. Releases may also be made under the compulsory legal process of federal or state bodies having authority to issue such process.</P>
          <P>(2) When a record is disclosed under this provision, make reasonable efforts to notify the individual to whom the record pertains, if the legal process is a matter of public record.</P>
          <P>(3) If the process is not a matter of public record at the time it is issued, seek to be advised when the process is made public and make reasonable efforts to notify the individual at that time.</P>
          <P>(4) Notification sent to the last known address of the individual as reflected in the records is considered reasonable effort to notify.</P>
          <P>(5) Make a disclosure accounting each time a record is disclosed under a court order or compulsory legal process.</P>
          <P>(m) <E T="03">Disclosures to consumer reporting agencies.</E> (1) Certain personal information may be disclosed to consumer reporting agencies as defined by the Federal Claims Collection Act of 1966, as amended (31 U.S.C. 952(d)).</P>
          <P>(2) Under the provisions of paragraph (m)(1) of this section, the following information may be disclosed to a consumer reporting agency:</P>
          <P>(i) Name, address, taxpayer identification number (SSN), and other information necessary to establish the identity of the individual.</P>
          <P>(ii) The amount, status, and history of the claim.</P>
          <P>(iii) The agency or program under which the claim arose.</P>
          <P>(3) The Federal Claims Collection Act of 1966, as amended (31 U.S.C. 952(d)) specifically requires that the system notice for the system of records from which the information will be disclosed indicates that the information may be disclosed to a “consumer reporting agency.”</P>
          <CITA>[51 FR 2364, Jan. 16, 1986. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57800, Nov. 14, 1991; 62 FR 26389, May 14, 1997]</CITA>
        </SECTION>
        <SECTION>
          <PRTPAGE P="834"/>
          <SECTNO>§ 310.42</SECTNO>
          <SUBJECT>Disclosures to commercial enterprises.</SUBJECT>
          <P>(a) <E T="03">General policy.</E> (1) Make releases of personal information to commercial enterprises under the criteria established by the DoD Freedom of Information Program (32 CFR part 286).</P>
          <P>(2) The relationship of commercial enterprises to their clients or customers and to the Department of Defense are not changed by this part.</P>
          <P>(3) The DoD policy on personal indebtedness for military personnel is contained in 32 CFR part 43a and for civilian employees in the Office of Personnel Management, Federal Personnel Manual (5 CFR part 550).</P>
          <P>(b) <E T="03">Release of personal information.</E> (1) Any information that must be released under the Freedom of Information (5 U.S.C. 552) may be released to a commercial enterprise without the individual's consent (see paragraph (b) of § 310.41 of this subpart).</P>

          <P>(2) Commercial enterprises may present a signed consent statement setting forth specific conditions for release of personal information. Statements such as the following, if signed by the individual, are considered valid:
          </P>
          <EXTRACT>
            <P>I hereby authorize the Department of Defense to verify my Social Security Number or other identifying information and to disclose my home address and telephone number to authorized representatives of (name of commercial enterprise) so that they may use this information in connection with my commercial dealings with that enterprise. All information furnished will be used in connection with my financial relationship with (name of commercial enterprise).</P>
          </EXTRACT>
          
          <P>(3) When a statement of consent as outlined in paragraph (b)(2) of this section is presented, provide the requested information if its release is not prohibited by some other regulation or statute.</P>
          <P>(4) Blanket statements of consent that do not identify specifically the Department of Defense or any of its Components, or that do not specify exactly the type of information to be released, may be honored if it is clear that the individual in signing the consent statement intended to obtain a personal benefit (for example, a loan to buy a house) and was aware of the type information that would be sought. Care should be exercised in these situations to release only the minimum amount of personal information essential to obtain the benefit sought.</P>
          <P>(5) Do not honor request from commercial enterprises for official evaluation of personal characteristics, such as evaluation of personal financial habits.</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.43</SECTNO>
          <SUBJECT>Disclosures to the public from health care records.</SUBJECT>
          <P>(a) <E T="03">Section applicability.</E> This section applies to the release of information to the news media or the public concerning persons treated or hospitalized in DoD medical facilities and patients of nonfederal medical facilities for whom the cost of the care is paid by the Department of Defense.</P>
          <P>(b) <E T="03">General disclosure.</E> Normally, the following may be released without the patient's consent.</P>
          <P>(1) Personal information concerning the patient. See 32 CFR part 286, The DoD Freedom of Information Act Program and paragraph (c) of § 310.41.</P>
          <P>(2) Medical condition:</P>
          <P>(i) Date of admission or disposition;</P>
          <P>(ii) The present medical assessment of the individual's condition in the following terms if the medical doctor has volunteered the information:</P>
          <P>(A) The individual's condition is presently (stable) (good) (fair) (serious) or (critical), and</P>
          <P>(B) Whether the patient is conscious, semiconscious, or unconscious.</P>
          <P>(c) <E T="03">Individual consent.</E> (1) Detailed medical and other personal information may be released in response to inquiries from the news media and public if the patient has given his or her informed consent to such a release.</P>
          <P>(2) If the patient is not conscious or competent, no personal information except that required by the Freedom of Information Act (5 U.S.C. 552) shall be released until there has been enough improvement in the patient to ensure he or she can give informed consent or a guardian has been appointed legally for the patient and the guardian has given consent on behalf of the patient.</P>
          <P>(3) The consent described in paragraph (c)(1) of this section regarding patients who are minors must be given by the parent of legal guardian.</P>
          <P>(d) <E T="03">Information that may be released with individual consent.</E> (1) Any item of <PRTPAGE P="835"/>personal information may be released, if the patient has given his or her informed consent to its release.</P>
          <P>(2) Releasing medical information about patients shall be done with discretion, so as not to embarrass the patient, his or her family, or the Department of Defense, needlessly.</P>
          <P>(e) <E T="03">Disclosures to other government agencies.</E> This subpart does not limit the disclosures of personal medical information to other government agencies for use in determining eligibility for special assistance or other benefits.</P>
          <CITA>[51 FR 2364, Jan. 16, 1986. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57800, Nov. 14, 1991]</CITA>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.44</SECTNO>
          <SUBJECT>Disclosure accounting.</SUBJECT>
          <P>(a) <E T="03">Disclosure accountings.</E> (1) Keep an accurate record of all disclosures made from any system of records except disclosures:</P>
          <P>(i) To DoD personnel for use in the performance of their official duties; or</P>
          <P>(ii) Under 32 CFR part 286, The DoD Freedom of Information Program.</P>
          <P>(2) In all other cases a disclosure accounting is required even if the individual has consented to the disclosure of the information pertaining to him or her.</P>
          <P>(3) Disclosure accountings:</P>
          <P>(i) Permit individuals to determine to whom information has been disclosed;</P>
          <P>(ii) Enable the activity to notify past recipients of disputed or corrected information (§ 310.32(i)(1), subpart D); and</P>
          <P>(iii) Provide a method of determining compliance with paragraph (c) of § 310.40.</P>
          <P>(b) <E T="03">Contents of disclosure accountings.</E> As a minimum, disclosure accounting shall contain:</P>
          <P>(1) The date of the disclosure.</P>
          <P>(2) A description of the information released.</P>
          <P>(3) The purpose of the disclosure.</P>
          <P>(4) The name and address of the person or agency to whom the disclosure was made.</P>
          <P>(c) <E T="03">Methods of disclosure accounting.</E> Use any system of disclosure accounting that will provide readily the necessary disclosure information (see paragraph (a)(3) of this section).</P>
          <P>(d) <E T="03">Accounting for mass disclosures.</E> When numerous similar records are released (such as transmittal of payroll checks to a bank), identify the category of records disclosed and include the data required by paragraph (b) of this section in some form that can be used to construct an accounting disclosure record for individual records if required (see paragraph (a)(3) of this section).</P>
          <P>(e) <E T="03">Disposition of disclosure accounting records.</E> Retain disclosure accounting records for 5 years after the disclosure or the life of the record, whichever is longer.</P>
          <P>(f) <E T="03">Furnishing disclosure accountings to the individual.</E> (1) Make available to the individual to whom the record pertains all disclosure accountings except when:</P>
          <P>(i) The disclosure has been made to a law enforcement activity under paragraph (i) of § 310.41 and the law enforcement activity has requested that disclosure not be made; or</P>
          <P>(ii) The system of records has been exempted from the requirement to furnish the disclosure accounting under the provisions of § 310.50(b), subpart F.</P>
          <P>(2) If disclosure accountings are not maintained with the record and the individual requests access to the accounting, prepare a listing of all disclosures (see paragraph (b) of this section) and provide this to the individual upon request.</P>
          <CITA>[51 FR 2364, Jan. 16, 1986. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57800, Nov. 14, 1991]</CITA>
        </SECTION>
      </SUBPART>
      <SUBPART>
        <HD SOURCE="HED">Subpart F—Exemptions</HD>
        <SECTION>
          <SECTNO>§ 310.50</SECTNO>
          <SUBJECT>Use and establishment of exemptions.</SUBJECT>
          <P>(a) <E T="03">Types of exemptions.</E> (1) There are two types of exemptions permitted by the Privacy Act.</P>
          <P>(i) General exemptions that authorize the exemption of a system of records from all but certain specifically identified provisions of the Act.</P>
          <P>(ii) Specific exemptions that allow a system of records to be exempted only from certain designated provisions of the Act.</P>

          <P>(2) Nothing in the Act permits exemption of any system of records from all provisions of the Act (see appendix D).<PRTPAGE P="836"/>
          </P>
          <P>(b) <E T="03">Establishing exemptions.</E> (1) Neither general nor specific exemptions are established automatically for any system of records. The head of the DoD Component maintaining the system of records must make a determination whether the system is one for which an exemption properly may be claimed and then propose and establish an exemption rule for the system. No system of records within the Department of Defense shall be considered exempted until the head of the Component has approved the exemption and an exemption rule has been published as a final rule in the <E T="04">Federal Register</E> (see § 310.60(e), subpart G).</P>
          <P>(2) Only the head of the DoD Component or an authorized designee may claim an exemption for a system of records.</P>
          <P>(3) A system of records is considered exempt only from those provisions of the Privacy Act (5 U.S.C. 552a) which are identified specifically in the Component exemption rule for the system and which are authorized by the Privacy Act.</P>
          <P>(4) To establish an exemption rule, see § 310.61 of subpart G.</P>
          <P>(c) <E T="03">Blanket exemption for classified material.</E> (1) Include in the Component rules a blanket exemption under 5 U.S.C. 552a(k)(1) of the Privacy Act from the access provisions (5 U.S.C. 552a(d)) and the notification of access procedures (5 U.S.C. 522a(e)(4)(H)) of the Act for all classified material in any system of records maintained.</P>
          <P>(2) Do not claim specifically an exemption under section 552a(k)(1) of the Privacy Act for any system of records. The blanket exemption affords protection to all classified material in all systems of records maintained.</P>
          <P>(d) <E T="03">Provisions from which exemptions may be claimed.</E> (1) The head of a DoD Component may claim an exemption from any provision of the Act from which an exemption is allowed (see appendix D).</P>
          <P>(2) Notify the Defense Privacy Office ODASD(A) before claiming an exemption for any system of records from the following:</P>
          <P>(i) The exemption rule publication requirement (5 U.S.C. 552a(j)) of the Privacy Act.</P>
          <P>(ii) The requirement to report new systems of records (5 U.S.C. 552a(o)); or</P>
          <P>(iii) The annual report requirement (5 U.S.C. 552a(p)).</P>
          <P>(e) <E T="03">Use of exemptions.</E> (1) Use exemptions only for the specific purposes set forth in the exemption rules (see paragraph (b) of § 310.61, subpart G).</P>
          <P>(2) Use exemptions only when they are in the best interest of the government and limit them to the specific portions of the records requiring protection.</P>
          <P>(3) Do not use an exemption to deny an individual access to any record to which he or she would have access under the Freedom of Information Act (5 U.S.C. 552).</P>
          <P>(f) <E T="03">Exempt records in nonexempt systems.</E> (1) Exempt records temporarily in the hands of another Component are considered the property of the originating Component and access to these records is controlled by the system notices and rules of the originating Component.</P>
          <P>(2) Records that are actually incorporated into a system of records may be exempted only to the extent the system of records into which they are incorporated has been granted an exemption, regardless of their original status or the system of records for which they were created.</P>
          <P>(3) If a record is accidentally misfiled into a system of records, the system notice and rules for the system in which it should actually be filed will govern.</P>
          <CITA>[51 FR 2364, Jan. 16, 1986. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57800, Nov. 14, 1991]</CITA>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.51</SECTNO>
          <SUBJECT>General exemptions.</SUBJECT>
          <P>(a) <E T="03">Use of the general exemptions.</E> (1) No DoD Component is authorized to claim the exemption for records maintained by the Central Intelligence Agency established by 5 U.S.C. 552a(j)(1) of the Privacy Act.</P>
          <P>(2) The general exemption established by 5 U.S.C. 552a(j)(2) of the Privacy Act may be claimed to protect investigative records created and maintained by law-enforcement activities of a DoD Component.</P>

          <P>(3) To qualify for the (j)(2) exemption, the system of records must be <PRTPAGE P="837"/>maintained by an element that performs as its principal function enforcement of the criminal law, such as U.S. Army Criminal Investigation Command (CIDC), Naval Investigative Service (NIS), the Air Force Office of Special Investigations (AFOSI), and military police activities. Law enforcement includes police efforts to detect, prevent, control, or reduce crime, to apprehend or identify criminals; and the activities of correction, probation, pardon, or parole authorities.</P>
          <P>(4) Information that may be protected under the (j)(2) exemption include:</P>
          <P>(i) Records compiled for the purpose of identifying criminal offenders and alleged offenders consisting only of identifying data and notations of arrests, the nature and disposition of criminal charges, sentencing, confinement, release, parole, and probation status (so-called criminal history records);</P>
          <P>(ii) Reports and other records compiled during criminal investigations, to include supporting documentation.</P>
          <P>(iii) Other records compiled at any stage of the criminal law enforcement process from arrest or indictment through the final release from parole supervision, such as presentence and parole reports.</P>
          <P>(5) The (j)(2) exemption does not apply to:</P>
          <P>(i) Investigative records prepared or maintained by activities without primary law-enforcement missions. It may not be claimed by any activity that does not have law enforcement as its principal function.</P>
          <P>(ii) Investigative records compiled by any activity concerning employee suitability, eligibility, qualification, or for individual access to classified material regardless of the principal mission of the compiling DoD Component.</P>
          <P>(6) The (j)(2) exemption claimed by the law-enforcement activity will not protect investigative records that are incorporated into the record system of a nonlaw enforcement activity or into nonexempt systems of records (see paragraph (f)(2) of § 310.50). Therefore, all system managers are cautioned to comply with the various regulations prohibiting or limiting the incorporation of investigatory records into system of records other than those maintained by law-enforcement activities.</P>
          <P>(b) <E T="03">Access to records for which a (j)(2) exemption is claimed.</E> Access to investigative records in the hands of a law-enforcement activity or temporarily in the hands of a military commander or other criminal adjudicative activity shall be processed under 32 CFR part 286, The DoD Freedom of Information Act Program, provided that the system of records from which the file originated is a law enforcement record system that has been exempted from the access provisions of this part (see paragraph (h) of § 310.30, subpart D).</P>
          <CITA>[51 FR 2364, Jan. 16, 1986. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57800, Nov. 14, 1991]</CITA>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.52</SECTNO>
          <SUBJECT>Specific exemptions.</SUBJECT>
          <P>(a) <E T="03">Use of the specific exemptions.</E> The specific exemptions permit certain categories of records to be exempted from certain specific provisions of the Privacy Act (see appendix D). To establish a specific exemption, the records must meet the following criteria (parenthetical references are to the appropriate subsection of the Privacy Act (5 U.S.C. 552a(k)):</P>
          <P>(1) <E T="03">The (k)(1).</E> Information specifically authorized to be classified under the DoD Information Security Program Regulation, 32 CFR part 159. (see also paragraph (c) of this section).</P>
          <P>(2) <E T="03">The (k)(2).</E> Investigatory information compiled for law-enforcement purposes by nonlaw enforcement activities and which is not within the scope of § 310.51(a). If an individual is denied any right, privilege or benefit that he or she is otherwise entitled by federal law or for which he or she would otherwise be eligible as a result of the maintenance of the information, the individual will be provided access to the information except to the extent that disclosure would reveal the identity of a confidential source. This subsection when claimed allows limited protection of investigative reports maintained in a system of records used in personnel or administrative actions.</P>
          <P>(3) <E T="03">The (k)(3).</E> Records maintained in connection with providing protective services to the President and other individuals under 18 U.S.C. 3506.<PRTPAGE P="838"/>
          </P>
          <P>(4) <E T="03">The (k)(4).</E> Records maintained solely for statistical research or program evaluation purposes and which are not used to make decisions on the rights, benefits, or entitlement of an individual except for census records which may be disclosed under 13 U.S.C. 8.</P>
          <P>(5) <E T="03">The (k)(5).</E> Investigatory material compiled solely for the purpose of determining suitability, eligibility, or qualifications for federal civilian employment, military service, federal contracts, or access to classified information, but only to the extent such material would reveal the identity of a confidential source. This provision allows protection of confidential sources used in background investigations, employment inquiries, and similar inquiries that are for personnel screening to determine suitability, eligibility, or qualifications.</P>
          <P>(6) <E T="03">The (k)(6).</E> Testing or examination material used solely to determine individual qualifications for appointment or promotion in the federal or military service, if the disclosure would compromise the objectivity or fairness of the test or examination process.</P>
          <P>(7) <E T="03">The (k)(7).</E> Evaluation material used to determine potential for promotion in the Military Services, but only to the extent that the disclosure of such material would reveal the identity of a confidential source.</P>
          <P>(b) <E T="03">Promises of confidentiality.</E> (1) Only the identity of sources that have been given an express promise of confidentiality may be protected from disclosure under paragraphs (a)(2), (5) and (7) of this section. However, the identity of sources who were given implied promises of confidentiality in inquiries conducted before September 27, 1975, may also be protected from disclosure.</P>
          <P>(2) Ensure that promises of confidentiality are used on a limited basis in day-to-day operations. Establish appropriate procedures and identify fully those categories of individuals who may make such promises. Promises of confidentiality shall be made only when they are essential to obtain the information sought.</P>
          <P>(c) <E T="03">Access to records for which specific exemptions are claimed.</E> Deny the individual access only to those portions of the records for which the claimed exemption applies.</P>
          <CITA>[51 FR 2364, Jan. 16, 1986. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57800, Nov. 14, 1991]</CITA>
        </SECTION>
      </SUBPART>
      <SUBPART>
        <HD SOURCE="HED">Subpart G—Publication Requirements</HD>
        <SECTION>
          <SECTNO>§ 310.60</SECTNO>
          <SUBJECT>Federal Register publication.</SUBJECT>
          <P>(a) <E T="03">What must be published in the</E>
            <E T="04">Federal Register.</E> (1) Three types of documents relating to the Privacy Program must be published in the <E T="04">Federal Register:</E>
          </P>
          <P>(i) DoD Component Privacy Program rules;</P>
          <P>(ii) Component exemption rules; and</P>
          <P>(iii) System notices.</P>

          <P>(2) See DoD 5025.1-M, “Directives Systems Procedures,” and DoD Directive 5400.9, (32 CFR part 296) “Publication of Proposed and Adopted Regulations Affecting the Public” for information pertaining to the preparation of documents for publication in the <E T="04">Federal Register.</E>
          </P>
          <P>(b) <E T="03">The effect of publication in the</E>
            <E T="04">Federal Register.</E> Publication of a document in the <E T="04">Federal Register</E> constitutes official public notice of the existence and content of the document.</P>
          <P>(c) <E T="03">DoD Component rules.</E> (1) Component Privacy Program procedures and Component exemption rules are subject to the rulemaking procedures prescribed in 32 CFR part 296.</P>

          <P>(2) System notices are not subject to formal rulemaking and are published in the <E T="04">Federal Register</E> as “Notices,” not rules.</P>
          <P>(3) Privacy procedural and exemption rules are incorporated automatically into the Code of Federal Regulations (CFR). System notices are not published in the CFR.</P>
          <P>(d) <E T="03">Submission of rules for publication.</E> (1) Submit to the Defense Privacy Office, ODASD(A), all proposed rules implementing this part in proper format (see Appendices E, F and G) for publication in the <E T="04">Federal Register.</E>
          </P>
          <P>(2) This part has been published as a final rule in the <E T="04">Federal Register</E> (32 CFR part 310). Therefore, incorporate it into your Component rules by reference rather than by republication.<PRTPAGE P="839"/>
          </P>

          <P>(3) DoD Component rules that simply implement this part need only be published as final rules in the <E T="04">Federal Register</E> (see DoD 5025.1-M, “Directives System Procedures,” and DoD Directive 5400.9, “Publication of Proposed and Adopted Regulations Affecting the Public,” (32 CFR part 296).</P>
          <P>(4) Amendments to Component rules are submitted like the basic rules.</P>

          <P>(5) The Defense Privacy Office ODASD(A) submits the rules and amendments thereto to the <E T="04">Federal Register</E> for publication.</P>
          <P>(e) <E T="03">Submission of exemption rules for publication.</E> (1) No system of records within the Department of Defense shall be considered exempt from any provision of this part until the exemption and the exemption rule for the system has been published as a final rule in the <E T="04">Federal Register</E> (see paragraph (c) of this section).</P>

          <P>(2) Submit exemption rules in proper format to the Defense Privacy Office ODASD(A). After review, the Defense Privacy Office will submit the rules to the <E T="04">Federal Register</E> for publication.</P>
          <P>(3) Exemption rules require publication both as proposed rules and final rules (see DoD Directive 5400.9, 32 CFR part 296).</P>
          <P>(4) Section 310.61 of this subpart discusses the content of an exemption rule.</P>
          <P>(5) Submit amendments to exemption rules in the same manner used for establishing these rules.</P>
          <P>(f) <E T="03">Submission of system notices for publication.</E> (1) While system notices are not subject to formal rulemaking procedures, advance public notice must be given before a Component may begin to collect personal information or use a new system of records. The notice procedures require that:</P>
          <P>(i) The system notice describes the contents of the record system and the routine uses for which the information in the system may be released.</P>
          <P>(ii) The public be given 30 days to comment on any proposed routine uses before implementation; and</P>
          <P>(iii) The notice contain the data on which the system will become effective.</P>

          <P>(2) Submit system notices to the Defense Privacy Office in the Federal Register format (see appendix E). The Defense Privacy Office transmits the notices to the <E T="04">Federal Register</E> for publication.</P>
          <P>(3) Section 310.62 of this subpart discusses the specific elements required in a system notice.</P>
          <CITA>[51 FR 2364, Jan. 16, 1986. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57800, Nov. 14, 1991]</CITA>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.61</SECTNO>
          <SUBJECT>Exemption rules.</SUBJECT>
          <P>(a) <E T="03">General procedures.</E> Paragraph (b)(1) of § 310.50, subpart F, provides the general guidance for establishing exemptions for systems of records.</P>
          <P>(b) <E T="03">Contents of exemption rules.</E> (1) Each exemption rule submitted for publication must contain the following:</P>
          <P>(i) The record system identification and title of the system for which the exemption is claimed (see § 310.62 of this subpart);</P>
          <P>(ii) The specific subsection of the Privacy Act under which exemptions for the system are claimed (for example, 5 U.S.C. 552a(j)(2), 5 U.S.C. 552a(k)(3); or 5 U.S.C. 552a(k)(7);</P>
          <P>(iii) The specific provisions and subsections of the Privacy Act from which the system is to be exempted (for example, 5 U.S.C. 552a(c)(3), or 5 U.S.C. 552a(d)(1)-(5)) (see appendix D); and</P>
          <P>(iv) The specific reasons why an exemption is being claimed from each subsection of the Act identified.</P>
          <P>(2) Do not claim an exemption for classified material for individual systems of records, since the blanket exemption applies (see paragraph (c) of § 310.50 of subpart F).</P>
          <CITA>[51 FR 2364, Jan. 16, 1986. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57800, Nov. 14, 1991]</CITA>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.62</SECTNO>
          <SUBJECT>System notices.</SUBJECT>
          <P>(a) <E T="03">Contents of the system notices.</E> (1) The following data captions are included in each system notice:</P>
          <P>(i) System identification (see paragraph (b) of this section).</P>
          <P>(ii) System name (see paragraph (c) of this section).</P>
          <P>(iii) System location (see paragraph (d) of this section).</P>

          <P>(iv) Categories of individuals covered by the system (see paragraph (e) of this section).<PRTPAGE P="840"/>
          </P>
          <P>(v) Categories of records in the system (see paragraph (f) of this section).</P>
          <P>(vi) Authority for maintenance of the system (see paragraph (g) of this section).</P>
          <P>(vii) Purpose(s) (see paragraph (h) of this section).</P>
          <P>(viii) Routine uses of records maintained in the system, including categories of users, uses, and purposes of such uses (see paragraph (i) of this section).</P>
          <P>(ix) Policies and practices for storing, retrieving, accessing, retaining, and disposing of records in the system (see paragraph (j) of this section).</P>
          <P>(x) Systems manager(s) and address (see paragraph (k) of this section).</P>
          <P>(xi) Notification procedure (see paragraph (l) of this section).</P>
          <P>(xii) Record access procedures (see paragraph (m) of this section).</P>
          <P>(xiii) Contesting records procedures (see paragraph (n) of this section.)</P>
          <P>(xiv) Record source categories (see paragraph (o) of this section).</P>
          <P>(xv) Systems exempted from certain provision of the Act (see paragraph (p) of this section).</P>
          <P>(2) The captions listed in paragraph (a)(1) of this section have been mandated by the Office of Federal Register and must be used exactly as presented.</P>
          <P>(3) A sample system notice is shown in appendix E.</P>
          <P>(b) <E T="03">System identification.</E> The system identifier must appear on all system notices and is limited to 21 positions, including Component code, file number and symbols, punctuation, and spacing.</P>
          <P>(c) <E T="03">System name.</E> (1) The name of the system should reasonably identify the general purpose of the system and, if possible, the general categories of individuals involved.</P>
          <P>(2) Use acronyms only parenthetically following the title or any portion thereof, such as, “Joint Uniform Military Pay System (JUMPS).” Do not use acronyms that are not commonly known unless they are preceded by an explanation.</P>
          <P>(3) The system name may not exceed 55 character positions including punctuation and spacing.</P>
          <P>(d) <E T="03">System location.</E> (1) For systems maintained in a single location provide the exact office name, organizational identity, and address or routing symbol.</P>
          <P>(2) For geographically or organizationally decentralized systems, specify each level of organization or element that maintains a segment of the system.</P>
          <P>(3) For automated data systems with a central computer facility and input/output terminals at several geographically separated locations, list each location by category.</P>

          <P>(4) When multiple locations are identified by type of organization, the system location may indicate that official mailing addresses are contained in an address directory published as an appendix to the Component system notices in the <E T="04">Federal Register.</E> Information concerning format requirements for preparation of an address directory may be obtained from the project officer, Air Force 1st Information Systems Group (AF/1ISG/GNR), Washington, DC 20330-6345.</P>
          <P>(5) If no address directory is used or the addresses in the directory are incomplete, the address of each location where a segment of the record system is maintained must appear under the “System Location” caption.</P>
          <P>(6) Classified addresses are not listed, but the fact that they are classified is indicated.</P>
          <P>(7) Use the standard U.S. Postal Service two letter state abbreviation symbols and zip codes for all domestic addresses.</P>
          <P>(e) <E T="03">Categories of individuals covered by the system.</E> (1) Set forth the specific categories of individuals to whom records in the system pertain in clear, easily understood, nontechnical terms.</P>
          <P>(2) Avoid the use of broad over-general descriptions, such as “all Army personnel” or “all military personnel” unless this actually reflects the category of individuals involved.</P>
          <P>(f) <E T="03">Categories of records in the system.</E> (1) Describe in clear, nontechnical terms the types of records maintained in the system.</P>
          <P>(2) Only documents actually retained in the system of records shall be described, not source documents that are used only to collect data and then destroyed.</P>
          <P>(g) <E T="03">Authority for maintenance of the system.</E> (1) Cite the specific provision of <PRTPAGE P="841"/>the federal statute or Executive Order that authorizes the maintenance of the system.</P>
          <P>(2) Include with citations for statutes the popular names, when appropriate (for example, Title 51, U.S. Code, section 2103, “Tea-Tasters Licensing Act”), and for Executive Orders, the official title (for example, Executive Order No. 9397, “Numbering System for Federal Accounts Relating to Individual Persons”).</P>
          <P>(3) Cite the statute or Executive Order establishing the Component for administrative housekeeping records.</P>
          <P>(4) If the Component is chartered by a DoD Directive, cite that Directive as well as the Secretary of Defense authority to issue the Directive. For example, “Pursuant to the authority contained in the National Security Act of 1947, as amended (10 U.S.C. 133d), the Secretary of Defense has issued DoD Directive 5105.21, the charter of the Defense Intelligence Agency (DIA) as a separate Agency of the Department of Defense under his control. Therein, the Director, DIA, is charged with the responsibility of maintaining all necessary and appropriate records.”</P>
          <P>(h) <E T="03">Purpose or purposes.</E> (1) List the specific purposes for maintaining the system of records by the Component.</P>
          <P>(2) Include the uses made of the information within the Component and the Department of Defense (so-called “internal routine uses”).</P>
          <P>(i) <E T="03">Routine uses.</E> (1) The blanket routine uses (appendix C) that appear at the beginning of each Component compilation apply to all systems notices unless the individual system notice specifically states that one or more of them do not apply to the system. List the blanket routine uses at the beginning of the Component listing of system notices (see paragraph (e)(5) of § 310.41 of subpart E).</P>
          <P>(2) For all other routine uses, when practical, list the specific activity to which the record may be released, to include any routine automated system interface (for example, “to the Department of Justice, Civil Rights Compliance Division,” “to the Veterans Administration, Office of Disability Benefits,” or “to state and local health agencies”).</P>
          <P>(3) For each routine user identified, include a statement as to the purpose or purposes for which the record is to be released to that activity (see § 310.41(e) of subpart E). The routine uses should be compatible with the purpose for which the record was collected or obtained (see § 310.3(p), subpart A).</P>
          <P>(4) Do not use general statements, such as, “to other federal agencies as required” or “to any other appropriate federal agency.”</P>
          <P>(j) <E T="03">Policies and practices for storing, retiring, accessing, retaining, and disposing of records.</E> This caption is subdivided into four parts:</P>
          <P>(1) <E T="03">Storage.</E> Indicate the medium in which the records are maintained. (For example, a system may be “automated”, maintained on magnetic tapes or disks, “manual”, maintained in paper files, or “hybrid”, maintained in a combination of paper and automated form.) Storage does not refer to the container or facility in which the records are kept.</P>
          <P>(2) <E T="03">Retrievability.</E> Specify how the records are retrieved (for example, name and SSN, name, SSN) and indicate whether a manual or computerized index is required to retrieve individual records.</P>
          <P>(3) <E T="03">Safeguards.</E> List the categories of Component personnel having immediate access and those responsible for safeguarding the records from unauthorized access. Generally identify the system safeguards (such as storage in safes, vaults, locked cabinets or rooms, use of guards, visitor registers, personnel screening, or computer “fail-safe” systems software). Do not describe safeguards in such detail so as to compromise system security.</P>
          <P>(4) <E T="03">Retention and disposal.</E> Indicate how long the record is retained. When appropriate, also state the length of time the records are maintained by the Component, when they are transferred to a Federal Records Center, length of retention at the Record Center and when they are transferred to the National Archivist or are destroyed. A reference to a Component regulation without further detailed information is insufficient.</P>
          <P>(k) <E T="03">System manager(s) and address.</E> (1) List the title and address of the official <PRTPAGE P="842"/>responsible for the management of the system.</P>
          <P>(2) If the title of the specific official is unknown, such as for a local system, specify the local commander or office head as the systems manager.</P>
          <P>(3) For geographically separated or organizationally decentralized activities for which individuals may deal directly with officials at each location in exercising their rights, list the position or duty title of each category of officials responsible for the system or a segment thereof.</P>
          <P>(4) Do not include business or duty addresses if they are listed in the Component address directory.</P>
          <P>(l) <E T="03">Notification procedures.</E> (1) If the record system has been exempted from subsection (e)(4)(G) of the Privacy Act (5 U.S.C. 552a) (see § 310.50)(d), so indicate.</P>
          <P>(2) For all nonexempt systems, describe how an individual may determine if there are records pertaining to him or her in the system. The procedural rules may be cited, but include a brief procedural description of the needed data. Provide sufficient information in the notice to allow an individual to exercise his or her rights without referral to the formal rules.</P>
          <P>(3) As a minimum, the caption shall include:</P>
          <P>(i) The official title (normally the system manager) and official address to which the request is to be directed;</P>
          <P>(ii) The specific information required to determine if there is a record of the individual in the system.</P>
          <P>(iii) Identification of the offices through which the individual may obtain access; and</P>
          <P>(iv) A description of any proof of identity required (see § 310.30(c)(1)).</P>
          <P>(4) When appropriate, the individual may be referred to a Component official who shall provide this data to him or her.</P>
          <P>(m) <E T="03">Record access procedures.</E> (1) If the record system has been exempted from subsection (e)(4)(H) of the Privacy Act (5 U.S.C. 552a) (see § 310.50(d)), so indicate.</P>
          <P>(2) For all nonexempt records systems, describe the procedures under which individuals may obtain access to the records pertaining to them in the system.</P>
          <P>(3) When appropriate, the individual may be referred to the system manager or Component official to obtain access procedures.</P>
          <P>(4) Do not repeat the addresses listed in the Component address directory but refer the individual to that directory.</P>
          <P>(n) <E T="03">Contesting record procedures.</E> (1) If the record system has been exempted from subsection (e)(4)(H) of the Privacy Act (5 U.S.C. 552a) (see § 310.50(d)), so indicate.</P>
          <P>(2) For all nonexempt systems of records, state briefly how an individual may contest the content of a record pertaining to him or her in the system.</P>
          <P>(3) The detailed procedures for contesting record accuracy, refusal of access or amendment, or initial review and appeal need not be included if they are readily available elsewhere and can be referred to by the public. (For example, “The Defense Mapping Agency rules for contesting contents and for appealing initial determinations are contained in DMA Instruction 5400.11 (32 CFR part 295c).”)</P>
          <P>(4) The individual may also be referred to the system manager to determine these procedures.</P>
          <P>(o) <E T="03">Record source categories.</E> (1) If the record system has been exempted from subsection (e)(4)(I) of the Privacy Act (5 U.S.C. 552a) (see § 310.50(d), subpart F), so indicate.</P>
          <P>(2) For all nonexempt systems of records, list the sources of the information in the system.</P>
          <P>(3) Specific individuals or institutions need not be identified by name, particularly if these sources have been granted confidentiality (see § 310.52(b), subpart F).</P>
          <P>(p) <E T="03">System exempted from certain provisions of the Act.</E> (1) If no exemption has been claimed for the system, indicate “None.”</P>
          <P>(2) If there is an exemption claimed indicate specifically under which subsection of the Privacy Act (5 U.S.C. 552a) it is claimed.</P>

          <P>(3) Cite the regulation and CFR section containing the exemption rule for the system. (For example, “Parts of this record system may be exempt under Title 5 U.S. Code, 552a(k)(2) and (5), as applicable. See exemption rules <PRTPAGE P="843"/>contained in Army Regulation 340-21 (32 CFR part 505).”)</P>
          <P>(q) <E T="03">Maintaining the master DoD system notice registry.</E> (1) The Defense Privacy Office, ODASD(A) maintains a master registry of all DoD record systems notices.</P>
          <P>(2) Coordinate with the Defense Privacy Office, ODASD(A) to ensure that all new systems are added to the master registry and all amendments and alterations are incorporated into the master registry.</P>
          <CITA>[51 FR 2364, Jan. 16, 1986. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57800, Nov. 14, 1991]</CITA>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.63</SECTNO>
          <SUBJECT>New and altered record systems.</SUBJECT>
          <P>(a) <E T="03">Criteria for a new record system.</E> (1) A new system of records is one for which there has been no system notice published in the <E T="04">Federal Register.</E>
          </P>

          <P>(2) If a notice for a system of records has been canceled or deleted before reinstating or reusing the system, a new system notice must be published in the <E T="04">Federal Register.</E>
          </P>
          <P>(b) <E T="03">Criteria for an altered record system.</E> A system is considered altered whenever one of the following actions occurs or is proposed:</P>
          <P>(1) A significant increase or change in the number or type of individuals about whom records are maintained.</P>
          <P>(i) Only changes that alter significantly the character and purpose of the record system are considered alterations.</P>
          <P>(ii) Increases in numbers of individuals due to normal growth are not considered alterations unless they truly alter the character and purpose of the system;</P>
          <P>(iii) Increases that change significantly the scope of population covered (for example, expansion of a system of records covering a single command's enlisted personnel to include all of the Component's enlisted personnel would be considered an alteration).</P>
          <P>(iv) A reduction in the number of individuals covered is not an alteration, but only an amendment (see paragraph (a) of § 310.64 of this subpart).</P>
          <P>(v) All changes that add new categories of individuals to system coverage require a change to the “Categories of individuals covered by the system” caption of the notice (§ 310.62(e)) and may require changes to the “Purpose(s)” caption (§ 310.62(h)).</P>
          <P>(2) An expansion in the types or categories of information maintained.</P>
          <P>(i) The addition of any new category of records not described under the “Categories of Records in System” caption is considered an alteration.</P>
          <P>(ii) Adding a new data element which is clearly within the scope of the categories of records described in the existing notice is an amendment (see § 310.64(a) of this subpart).</P>
          <P>(iii) All changes under this criterion require a change to the “Categories of Records in System” caption of the notice (see § 310.62(f) of this subpart).</P>
          <P>(3) An alteration in the manner in which the records are organized or the manner in which the records are indexed and retrieved.</P>
          <P>(i) The change must alter the nature of use or scope of the records involved (for example, combining records systems in a reorganization).</P>
          <P>(ii) Any change under this criteria requires a change in the “Retrievability” caption of the system notice (see § 310.62(j)(2) of this subpart).</P>
          <P>(iii) If the records are no longer retrieved by name or personal identifier cancel the system notice (see § 310.10(a) of subpart B).</P>
          <P>(4) A change in the purpose for which the information in the system is used.</P>
          <P>(i) The new purpose must not be compatible with the existing purposes for which the system is maintained or a use that would not reasonably be expected to be an alteration.</P>
          <P>(ii) If the use is compatible and reasonably expected, there is no change in purpose and no alteration occurs.</P>
          <P>(iii) Any change under this criterion requires a change in the “Purpose(s)” caption (see § 310.62(h) of this subpart) and may require a change in the “Authority for maintenance of the system” caption (see § 310.62(g) of this subpart).</P>
          <P>(5) Changes that alter the computer environment (such as changes to equipment configuration, software, or procedures) so as to create the potential for greater or easier access.</P>
          <P>(i) Increasing the number of offices with direct access is an alteration.</P>

          <P>(ii) Software releases, such as operating systems and system utilities that <PRTPAGE P="844"/>provide for easier access are considered alterations.</P>
          <P>(iii) The addition of an on-line capability to a previously batch-oriented system is an alteration.</P>
          <P>(iv) The addition of peripheral devices such as tape devices, disk devices, card readers, printers, and similar devices to an existing ADP system constitute an amendment if system security is preserved (see paragraph (a) of § 310.64 of this subpart).</P>
          <P>(v) Changes to existing equipment configuration with on-line capability need not be considered alterations to the system if:</P>
          <P>(A) The change does not alter the present security posture; or</P>
          <P>(B) The addition of terminals does not extend the capacity of the current operating system and existing security is preserved;</P>
          <P>(vi) The connecting of two or more formerly independent automated systems or networks together creating a potential for greater access is an alteration.</P>
          <P>(vii) Any change under this caption requires a change to the “Storage” caption element of the systems notice (see § 310.62(j)(1) of this subpart).</P>
          <P>(c) <E T="03">Reports of new and altered systems.</E> (1) Submit a report of a new or altered system to the Defense Privacy Office before collecting information for or using a new system or altering an existing system (see appendix F and paragraph (d) of this section).</P>
          <P>(2) The Defense Privacy Office, ODASD(A) coordinates all reports of new and altered systems with the Office of the Assistant Secretary of Defense (Legislative Affairs) and the Office of the General Counsel, Department of Defense.</P>
          <P>(3) The Defense Privacy Office prepares for the DASD(A)'s approval and signature the transmittal letters sent to OMB and Congress (see paragraph (e) of this section).</P>
          <P>(d) <E T="03">Time restrictions on the operation of a new or altered system.</E> (1) All time periods begin from the date the DASD(A) signs the transmittal letters (see paragraph (c)(3) of this section). The specific time limits are:</P>
          <P>(i) 60 days must elapse before data collection forms or formal instructions pertaining to the system may be issued.</P>
          <P>(ii) 60 days must elapse before the system may become operational; (that is, collecting, maintaining, using, or disseminating records from the system) (see also § 310.60(f) of this subpart).</P>
          <P>(iii) 60 days must elapse before any public issuance of a Request for Proposal or Invitation to Bid for a new ADP or telecommunication system.</P>
          <NOTE>
            <HD SOURCE="HED">Note:</HD>
            <P>Requests for delegation of procurement authority may be submitted to the General Services Administration during the 60 days’ waiting period, but these shall include language that the Privacy Act reporting criteria have been reviewed and that a system report is required for such procurement.</P>
          </NOTE>

          <P>(iv) Normally 30 days must elapse before publication in the <E T="04">Federal Register</E>  of the notice of a new or altered system (see § 310.60(f) of this subpart) and the preamble to the <E T="04">Federal Register</E> notice must reflect the date the transmittal letters to OMB and Congress were signed by DASD(A).</P>
          <P>(2) Do not operate a system of records until the waiting periods have expired (see § 310.103 of subpart K).</P>
          <P>(e) <E T="03">Outside review of new and altered systems reports.</E> If no objections are received within 30 days of a submission to the President of the Senate, Speaker of the House of Representatives, and the Director, OMB, of a new or altered system report it is presumed that the new or altered systems have been approved as submitted.</P>
          <P>(f) <E T="03">Exemptions for new systems.</E> See § 310.60(e) of this subpart for the procedures to follow in submitting exemption rules for a new system of records.</P>
          <P>(g) <E T="03">Waiver of time restrictions.</E> (1) The OMB may authorize a federal agency to begin operation of a system of records before the expiration of time limits set forth in § 310.63(d) of this subpart.</P>
          <P>(2) When seeking such a waiver, include in the letter of transmittal to the Defense Privacy Office, ODASD(A) an explanation why a delay of 60 days in establishing the system of records would not be in the public interest. The transmittal must include:</P>
          <P>(i) How the public interest will be affected adversely if the established time limits are followed; and</P>
          <P>(ii) Why earlier notice was not provided.<PRTPAGE P="845"/>
          </P>
          <P>(3) When appropriate, the Defense Privacy Office, ODASD(A) shall contact OMB and attempt to obtain the waiver.</P>

          <P>(i) If a waiver is granted, the Defense Privacy Office, ODASD(A) shall notify the subcommittee and submit the new or altered system notice along with any applicable procedural or exemption rules for publication in the <E T="04">Federal Register</E>.</P>
          <P>(ii) If the waiver is disapproved, the Defense Privacy Office, ODASD(A) shall process the system the same as any other new or altered system and notify the subcommittee of the OMB decision.</P>

          <P>(4) Under no circumstances shall the routine uses for new or altered system be implemented before 30 days have elapsed after publication of the system notice containing the routine uses in the <E T="04">Federal Register.</E> This period cannot be waived.</P>
          <CITA>[51 FR 2364, Jan. 16, 1986. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57800, Nov. 14, 1991]</CITA>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.64</SECTNO>
          <SUBJECT>Amendment and deletion of systems notices.</SUBJECT>
          <P>(a) <E T="03">Criteria for an amended system notice.</E> (1) Certain minor changes to published systems notices are considered amendments and not alterations (see § 310.63(b) of this subpart).</P>

          <P>(2) Amendments do not require a report of an altered system (see § 310.63(c) of this subpart), but must be published in the <E T="04">Federal Register.</E>
          </P>
          <P>(b) <E T="03">System notices for amended systems.</E> When submitting an amendment for a system notice for publication in the <E T="04">Federal Register</E> include:</P>
          <P>(1) The system identification and name (see paragraph (b) and (c) of § 310.62 of this subpart).</P>
          <P>(2) A description of the nature and specific changes proposed.</P>
          <P>(3) The full text of the system notice is not required if the master registry contains a current system notice for the system (see § 310.62(q) of this subpart).</P>
          <P>(c) <E T="03">Deletion of system notices.</E> (1) Whenever a system is discontinued, combined into another system, or determined no longer to be subject to this part, a deletion notice is required.</P>
          <P>(2) The notice of deletion shall include:</P>
          <P>(i) The system identification and name.</P>
          <P>(ii) The reason for the deletion.</P>
          <P>(3) When the system is eliminated through combination or merger, identify the successor system or systems in the deletion notice.</P>
          <P>(d) <E T="03">Submission of amendments and deletions for publication.</E> (1) Submit amendments and deletions to the Defense Privacy Office, ODASD(A) for transmittal to the <E T="04">Federal Register</E> for publication.</P>

          <P>(2) Include in the submission at least one original (not a reproduced copy) in proper <E T="04">Federal Register</E> format (see appendix G).</P>
          <P>(3) Multiple deletions and amendments may be combined into a single submission.</P>
          <CITA>[51 FR 2364, Jan. 16, 1986. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57801, Nov. 14, 1991]</CITA>
        </SECTION>
      </SUBPART>
      <SUBPART>
        <HD SOURCE="HED">Subpart H—Training Requirements</HD>
        <SECTION>
          <SECTNO>§ 310.70</SECTNO>
          <SUBJECT>Statutory training requirements.</SUBJECT>
          <P>The Privacy Act of 1974, as amended (5 U.S.C. 552a), requires each agency to establish rules of conduct for all persons involved in the design, development, operation, and maintenance of any system of record and to train these persons with respect to these rules.</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.71</SECTNO>
          <SUBJECT>OMB training guidelines.</SUBJECT>
          <P>The OMB guidelines require all agencies additionally to:</P>
          <P>(a) Instruct their personnel in their rules of conduct and other rules and procedures adopted in implementing the Act, and inform their personnel of the penalties for noncompliance.</P>
          <P>(b) Incorporate training on the special requirements of the Act into both formal and informal (on-the-job) training programs.</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.72</SECTNO>
          <SUBJECT>DoD training programs.</SUBJECT>

          <P>(a) To meet these training requirements, establish three general levels of training for those persons who are involved in any way with the design, development, operation, or maintenance of any system of records. These are:<PRTPAGE P="846"/>
          </P>
          <P>(1) <E T="03">Orientation.</E> Training that provides basic understanding of this Regulation as it applies to the individual's job performance. This training shall be provided to personnel, as appropriate, and should be a prerequisite to all other levels of training.</P>
          <P>(2) <E T="03">Specialized training</E>. Training that provides information as to the application of specific provisions of this part to specialized areas of job performance. Personnel of particular concern include, but are not limited to personnel specialists, finance officers, DoD personnel who may be expected to deal with the news media or the public, special investigators, paperwork managers, and other specialists (reports, forms, records, and related functions), computer systems development personnel, computer systems operations personnel, statisticians dealing with personal data and program evaluations, and anyone responsible for implementing or carrying out functions under this part. Specialized training should be provided on a periodic basis.</P>
          <P>(3) <E T="03">Management.</E> Training designed to identify for responsible managers (such as, senior system managers, denial authorities, decision-makers, and the managers of the functions described in § 310.70 of this subpart) considerations that they shall take into account when making management decisions regarding the Defense Privacy Program.</P>
          <P>(b) Include Privacy Act training in courses of training when appropriate. Stress individual responsibilities and advise individuals of their rights and responsibilities under this part.</P>
          <CITA>[51 FR 2364, Jan. 16, 1986. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57801, Nov. 14, 1991; 65 FR 48170, Aug. 7, 2000]</CITA>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.73</SECTNO>
          <SUBJECT>Training methodology and procedures.</SUBJECT>
          <P>(a) Each DoD Component is responsible for the development of training procedures and methodology.</P>
          <P>(b) The Defense Privacy Office, ODASD(A) will assist the Components in developing these training programs and may develop Privacy training programs for use by all DoD Components.</P>
          <P>(c) All training programs shall be coordinated with the Defense Privacy Office, ODASD(A) to avoid duplication and to ensure maximum effectiveness.</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.74</SECTNO>
          <SUBJECT>Funding for training.</SUBJECT>
          <P>Each DoD Component shall fund its own Privacy training program.</P>
        </SECTION>
      </SUBPART>
      <SUBPART>
        <HD SOURCE="HED">Subpart I—Reports</HD>
        <SECTION>
          <SECTNO>§ 310.80</SECTNO>
          <SUBJECT>Requirements for reports.</SUBJECT>
          <P>The Defense Privacy Office, ODASD(A) shall establish requirements for DoD Privacy Reports and DoD Components may be required to provide data.</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.81</SECTNO>
          <SUBJECT>Suspense for submission of reports.</SUBJECT>
          <P>The suspenses for submission of all reports shall be established by the Defense Privacy Office, ODASD(A).</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.82</SECTNO>
          <SUBJECT>Reports control symbol.</SUBJECT>
          <P>Any report established by this subpart in support of the Defense Privacy Program shall be assigned Report Control Symbol DD-COMP(A)1379. Special one-time reporting requirements shall be licensed separately in accordance with DoD Directive 5000.19 “Policies for the Management and Control of Information Requirements” and DoD Directive 5000.11, “Data Elements and Data Codes Standardization Program.”</P>
        </SECTION>
      </SUBPART>
      <SUBPART>
        <HD SOURCE="HED">Subpart J—Inspections</HD>
        <SECTION>
          <SECTNO>§ 310.90</SECTNO>
          <SUBJECT>Privacy Act inspections.</SUBJECT>
          <P>During internal inspections, Component inspectors shall be alert for compliance with this part and for managerial, administrative, and operational problems associated with the implementation of the Defense Privacy Program.</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.91</SECTNO>
          <SUBJECT>Inspection reporting.</SUBJECT>
          <P>(a) Document the findings of the inspectors in official reports that are furnished the responsible Component officials. These reports, when appropriate, shall reflect overall assets of the Component Privacy Program inspected, or portion thereof, identify deficiencies, irregularities, and significant problems. Also document remedial actions taken to correct problems identified.</P>

          <P>(b) Retain inspections reports and later follow-up reports in accordance with established records disposition standards. These reports shall be made <PRTPAGE P="847"/>available to the Privacy Program officials concerned upon request.</P>
        </SECTION>
      </SUBPART>
      <SUBPART>
        <HD SOURCE="HED">Subpart K—Privacy Act Enforcement Actions</HD>
        <SECTION>
          <SECTNO>§ 310.100</SECTNO>
          <SUBJECT>Administrative remedies.</SUBJECT>
          <P>Any individual who feels he or she has a legitimate complaint or grievance against the Department of Defense or any DoD employee concerning any right granted by this part shall be permitted to seek relief through appropriate administrative channels.</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.101</SECTNO>
          <SUBJECT>Civil actions.</SUBJECT>
          <P>An individual may file a civil suit against a DoD Component or its employees if the individual feels certain provisions of the Act have been violated (see 5 U.S.C. 552a(g), of the Privacy Act.</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.102</SECTNO>
          <SUBJECT>Civil remedies.</SUBJECT>
          <P>In addition to specific remedial actions, subsection (g) of the Privacy Act (5 U.S.C. 552a) provides for the payment of damages, court cost, and attorney fees in some cases.</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.103</SECTNO>
          <SUBJECT>Criminal penalties.</SUBJECT>
          <P>(a) The Act also provides for criminal penalties (see 5 U.S.C. 552a(i). Any official or employee may be found guilty of a misdemeanor and fined not more than $5,000 if he or she willfully:</P>
          <P>(1) Discloses personal information to anyone not entitled to receive the information (see subpart E); or</P>

          <P>(2) Maintains a system of records without publishing the required public notice in the <E T="04">Federal Register</E> (see subpart G).</P>
          <P>(b) A person who requests or obtains access to any record concerning another individual under false pretenses may be found guilty of misdemeanor and fined up to $5,000.</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.104</SECTNO>
          <SUBJECT>Litigation status sheet.</SUBJECT>
          <P>Whenever a complaint citing the Privacy Act is filed in a U.S. District Court against the Department of Defense, a DoD Component, or any DoD employee, the responsible system manager shall notify promptly the Defense Privacy Office, ODASD(A). The litigation status sheet at appendix H provides a standard format for this notification. The initial litigation status sheet forwarded shall, as a minimum, provide the information required by items 1 through 6. A revised litigation status sheet shall be provided at each stage of the litigation. When a court renders a formal opinion or judgment, copies of the judgment and opinion shall be provided to the Defense Privacy Office with the litigation status sheet reporting that judgment or opinion.</P>
        </SECTION>
      </SUBPART>
      <SUBPART>
        <HD SOURCE="HED">Subpart L—Matching Program Procedures</HD>
        <SECTION>
          <SECTNO>§ 310.110</SECTNO>
          <SUBJECT>OMB matching guidelines.</SUBJECT>
          <P>The OMB has issued special guidelines to be followed in programs that match the personal records in the computerized data bases of two or more federal agencies by computer (see appendix I). These guidelines are intended to strike a balance between the interest of the government in maintaining the integrity of federal programs and the need to protect individual privacy expectations. They do not authorize matching programs as such and each matching program must be justified individually in accordance with the OMB guidelines.</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.111</SECTNO>
          <SUBJECT>Requesting matching programs.</SUBJECT>
          <P>(a) Forward all requests for matching programs to include necessary routine use amendments (see § 310.62(i) of subpart G) and analysis and proposed matching program reports (see subsection E.6. of appendix I) to the Defense Privacy Office, ODASD(A).</P>

          <P>(b) The Defense Privacy Office shall review each request and supporting material and forward the report and system notice amendments to the <E T="04">Federal Register,</E> OMB, and Congress, as appropriate.</P>
          <P>(c) Changes to existing matching programs shall be processed in the same manner as a new matching program report.</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.112</SECTNO>
          <SUBJECT>Time limits for submitting matching reports.</SUBJECT>

          <P>(a) No time limits are set by the OMB guidelines. However, in order to establish a new routine use for a matching <PRTPAGE P="848"/>program, the amended system notice must have been published in the <E T="04">Federal Register</E> at least 30 days before implementation (see § 310.60(f) of subpart G).</P>
          <P>(b) Submit the documentation required by § 310.111(a) of this subpart to the Defense Privacy Office at least 45 days before the proposed initiation date of the matching program.</P>
          <P>(c) The Defense Privacy Office may grant waivers to the 45 days’ deadline for good cause shown. Requests for waivers shall be in writing and fully justified.</P>
          <CITA>[51 FR 2364, Jan. 16, 1986. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57801, Nov. 14, 1991]</CITA>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.113</SECTNO>
          <SUBJECT>Matching programs among DoD components.</SUBJECT>
          <P>(a) For the purpose of the OMB guidelines, the Department of Defense and all DoD Components are considered a single agency.</P>
          <P>(b) Before initiating a matching program using only the records of two or more DoD Components, notify the Defense Privacy Office that the match is to occur. The Defense Privacy Office may request further information from the Component proposing the match.</P>
          <P>(c) There is no need to notify the Defense Privacy Office of computer matches using only the records of a single Component.</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 310.114</SECTNO>
          <SUBJECT>Annual review of systems of records.</SUBJECT>
          <P>The system manager shall review annually each system of records to determine if records from the system are being used in matching programs and whether the OMB Guidelines have been complied with.</P>
        </SECTION>
        <APPENDIX>
          <EAR>Pt. 310, App. A</EAR>
          <HD SOURCE="HED">Appendix A to Part 310—Special Considerations for Safeguarding Personal Information in ADP Systems</HD>
          <HD SOURCE="HD3">(See paragraph (b) of § 310.13, subpart B)</HD>
          <HD SOURCE="HD2">A. General</HD>
          <P>1. The Automated Data Processing (ADP) environment subjects personal information to special hazards as to unauthorized compromise alteration, dissemination, and use. Therefore, special considerations must be given to safeguarding personal information in ADP systems.</P>
          <P>2. Personal information must also be protected while it is being processed or accessed in computer environments outside the data processing installation (such as, remote job entry stations, terminal stations, minicomputers, microprocessors, and similar activities).</P>
          <P>3. ADP facilities authorized to process classified material have adequate procedures and security for the purposes of this Regulation. However, all unclassified information subject to this Regulation must be processed following the procedures used to process and access information designated “For Official Use Only” (see “DoD Freedom of Information Act Program” (32 CFR part 286)).</P>
          <HD SOURCE="HD2">B. Risk Management and Safeguarding Standards</HD>
          <P>1. Establish administrative, technical, and physical safeguards that are adequate to protect the information against unauthorized disclosure, access, or misuse (see Transmittal Memorandum No. 1 to OMB Circular A-71—Security of Federal Automated Information Systems).</P>
          <P>2. Technical and physical safeguards alone will not protect against unintentional compromise due to errors, omissions, or poor procedures. Proper administrative controls generally provide cheaper and surer safeguards.</P>
          <P>3. Tailor safeguards to the type of system, the nature of the information involved, and the specific threat to be countered.</P>
          <HD SOURCE="HD2">C. Minimum Administrative Safeguard</HD>
          <P>The minimum safeguarding standards as set forth in paragraph (b) of § 310.13, subpart B apply to all personal data within any ADP system. In addition:</P>
          <P>1. Consider the following when establishing ADP safeguards:</P>
          <P>a. The sensitivity of the data being processed, stored and accessed;</P>
          <P>b. The installation environment;</P>
          <P>c. The risk of exposure;</P>
          <P>d. The cost of the safeguard under consideration.</P>
          <P>2. Label or designate output and storage media products (intermediate and final) containing personal information that do not contain classified material in such a manner as to alert those using or handling the information of the need for special protection. Designating products “For Official Use Only” in accordance with subpart E of 32 CFR part 286, “DoD Freedom of Information Act Program,” satisfies this requirement.</P>

          <P>3. Mark and protect all computer products containing classified data in accordance with the DoD Information Security Program Regulation (32 CFR part 159) and the ADP Security Manual (DoD 5200.28-M).<PRTPAGE P="849"/>
          </P>
          <P>4. Mark and protect all computer products containing “For Official Use Only” material in accordance with subpart E of 32 CFR part 286.</P>
          <P>5. Ensure that safeguards for protected information stored at secondary sites are appropriate.</P>
          <P>6. If there is a computer failure, restore all protected information being processed at the time of the failure using proper recovery procedures to ensure data integrity.</P>
          <P>7. Train all ADP personnel involved in processing information subject to this part in proper safeguarding procedures.</P>
          <HD SOURCE="HD2">D. Physical Safeguards</HD>
          <P>1. For all unclassified facilities, areas, and devices that process information subject to this part, establish physical safeguards that protect the information against reasonably identifiable threats that could result in unauthorized access or alteration.</P>
          <P>2. Develop access procedures for unclassified computer rooms, tape libraries, micrographic facilities, decollating shops, product distribution areas, or other direct support areas that process or contain personal information subject to this part that control adequately access to these areas.</P>
          <P>3. Safeguard on-line devices directly coupled to ADP systems that contain or process information from systems of records to prevent unauthorized disclosure use or alteration.</P>
          <P>4. Dispose of paper records following appropriate record destruction procedures.</P>
          <HD SOURCE="HD2">E. Technical Safeguards</HD>
          <P>1. The use of encryption devices solely for the purpose of protecting unclassified personal information transmitted over communication circuits or during processing in computer systems is normally discouraged. However, when a comprehensive risk assessment indicates that encryption is cost-effective it may be used.</P>
          <P>2. Remove personal data stored on magnetic storage media by methods that preclude reconstruction of the data.</P>
          <P>3. Ensure that personal information is not inadvertently disclosed as residue when transferring magnetic media between activities.</P>
          <P>4. When it is necessary to provide dial-up remote access for the processing of personal information, control access by computer-verified passwords. Change passwords periodically or whenever compromise is known or suspected.</P>
          <P>5. Normally the passwords shall give access only to those data elements (fields) required and not grant access to the entire data base.</P>
          <P>6. Do not rely totally on proprietary software products to protect personnel data during processing or storage.</P>
          <HD SOURCE="HD2">F. Special Procedures</HD>
          <HD SOURCE="HD3">1. System Managers shall:</HD>
          <P>a. Notify the ADP manager whenever personal information subject to this Regulation is to be processed by an ADP facility.</P>
          <P>b. Prepare and submit for publication all system notices and amendments and alterations thereto (see paragraph (f) of § 310.60 of subpart G).</P>
          <P>c. Identify to the ADP manager those activities and individuals authorized access to the information and notify the manager of any changes to the access authorizations.</P>
          <HD SOURCE="HD3">2. ADP personnel shall:</HD>
          <P>a. Permit only authorized individuals access to the information.</P>
          <P>b. Adhere to the established information protection procedures and rules of conduct.</P>
          <P>c. Notify the system manager and ADP manager whenever unauthorized personnel seek access to the information.</P>
          <HD SOURCE="HD3">3. ADP installation managers shall:</HD>
          <P>a. Maintain an inventory of all computer program applications used to process information subject to this part to include the identity of the systems of records involved.</P>
          <P>b. Verify that requests for new programs or changes to existing programs have been published as required (see paragraphs (a) and (b) of § 310.63, subpart G).</P>
          <P>c. Notify the system manager whenever changes to computer installations, communications networks, or any other changes in the ADP environment occur that require an altered system report be submitted (see paragraph (b) of § 310.63, subpart G).</P>
          <HD SOURCE="HD2">G. Record Disposal</HD>
          <P>1. Dispose of records subject to this part so as to prevent compromise (see paragraph (c) of § 310.13 of subpart B). Magnetic tapes or other magnetic medium, may be cleared by degaussing, overwriting, or erasing. Unclassified carbon ribbons are considered destroyed when placed in a trash receptacle.</P>
          <P>2. Do not use respliced waste computer products containing personal data.</P>
          <HD SOURCE="HD2">H. Risk Assessment for ADP Installations That Process Personal Data</HD>

          <P>1. A separate risk assessment is not required for ADP installations that process classified material. A simple certification by the appropriate ADP official that the facility is cleared to process a given level of classified material (such as, Top Secret, Secret, or Confidential) and that the procedures followed in processing “For Official Use Only” material are to be followed in processing personal data subject to this Regulation is sufficient to meet the risk assessment requirement.<PRTPAGE P="850"/>
          </P>
          <P>2. Prepare a formal risk assessment for each ADP installation (to include those activities with terminals and devices having access to ADP facilities) that processes personal information subject to this part and that do not process classified material.</P>
          <P>3. Address the following in the risk assessment:</P>
          <P>a. Identify the specific systems of records supported and determine their impact on the mission of the user.</P>
          <P>b. Identify the threats (internal, external, and natural) to the data.</P>
          <P>c. Determine the physical and operational (to include software) vulnerabilities.</P>
          <P>d. Evaluate the relationships between vulnerabilities and threats.</P>
          <P>e. Assess the impact of unauthorized disclosure or modification of the personal information.</P>
          <P>f. Identify possible safeguards and their relationships to the threats to be countered.</P>
          <P>g. Analyze the economic feasibility of adopting the identified safeguards.</P>
          <P>h. Determine the safeguard to be used and develop implementation plans.</P>
          <P>i. Discuss contingency plans including operational exercise plans.</P>
          <P>j. Determine if procedures proposed are consistent with those identified in the system notices for system of records concerned.</P>
          <P>k. Include a vulnerability assessment.</P>
          <P>3. The risk assessment shall be reviewed by the appropriate Component officials.</P>
          <P>4. Conduct a risk assessment at least every 5 years or when there is a change to the installation, its hardware, software, or administrative procedures that increase or decrease the likelihood of compromise or present new threats to the information.</P>
          <P>5. Protect the risk assessment as it is a sensitive document.</P>
          <P>6. Retain a copy of the risk assessment at the installation and make it available to appropriate inspectors and authorized personnel.</P>
          <P>7. Include a summary of the current risk assessment with any report of new or altered system submitted in accordance with paragraph (c) of § 310.63, subpart G, for any system from which information will be processed.</P>
          <P>8. Complete a formal risk assessment at the beginning of the design phase for each new unclassified ADP installation and before beginning the processing of personal data on a regular basis in existing ADP facility that do not process classified data.</P>
          <CITA>[51 FR 2364, Jan. 16, 1986. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57801, Nov. 14, 1991]</CITA>
        </APPENDIX>
        <APPENDIX>
          <EAR>Pt. 310, App. B</EAR>
          <HD SOURCE="HED">Appendix B to Part 310—Special Considerations for Safeguarding Personal Information During Word Processing</HD>
          <HD SOURCE="HD3">(See paragraph (b) of § 310.13, subpart B)</HD>
          <HD SOURCE="HD2">A. Introduction</HD>
          <P>1. Normally, word processing support is provided under two general concepts. They are:</P>
          <P>a. Word processing centers (WPCs), and</P>
          <P>b. Work groups or clusters.</P>
          <P>2. A WPC generally provides support to one or more functional areas. Characteristically, the customer delivers (by written draft or dictation) the information to be processed to the WPC. The WPC process the information and returns it to the customer. There are generally two types of WPCs.</P>
          <P>a. A WPC may operate independent of the customer's functon, providing service in much the same manner as a data processing installation provides ADP support, or a message center provides electronic message service, or</P>
          <P>b. A WPC may work within a customer's function providing support to that function. The support being centralized in a WPC to take advantage of increased productivity.</P>
          <P>3. A work group or cluster generally consists of one or more pieces of word processing equipment that are integrated into the functional office support system. The overall word processing and functional management may be one and the same. Depending on the size of the support job, there may be a work group or cluster manager. Normally, however, they will be located within or in close proximity to the functional area supported. Information flows in and out of the work group or cluster by normal office routine and the personnel are an integral part of the office staff.</P>
          <HD SOURCE="HD2">B. Minimum Standards of Protection</HD>
          <P>1. Regardless of configuration (WPC or work group), all personal data processed using word processing equipment shall be afforded the standards of protection required by paragaph (b) of § 310.13, subpart B.</P>
          <P>2. The remaining special considerations discussed in this appendix are primarily for WPCs operating independent of the customer's function. However, managers of other WPCs, work groups, and work clusters are encouraged to consider and adopt, when appropriate, the special considerations discussed herein.</P>

          <P>3. WPCs that are not independent of a customer's function, work groups, and work clusters are not required to prepare formal written risk assessments (see section H., below).<PRTPAGE P="851"/>
          </P>
          <HD SOURCE="HD2">C. WPC Information Flow</HD>
          <P>1. In analyzing procedures required to safeguard adequately personal information in a WPC, the basic elements of WPC information flow and control must be considered. These are:</P>
          <P>a. Information receipt.</P>
          <P>b. Information processing.</P>
          <P>c. Information return.</P>
          <P>d. Information storage or filing.</P>
          <P>2. WPCs do not control information acquisition or its ultimate use by the customers and, therefore, these are not addressed.</P>
          <HD SOURCE="HD2">D. Safeguarding Information During Receipt</HD>
          <P>1. The word processing manager shall establish procedures.</P>
          <P>a. That require each customer who requests that information subject to this part be processed to identify specifically that information to the WPC personnel. This may be done by:</P>
          <P>(1) Providing a check-off type entry on the WPC work requests;</P>
          <P>(2) Requiring that the WPC work requests be stamped with a special legend, or that a special notation be made on the work requests;</P>
          <P>(3) Predesignating specifically a class of documents as coming within the provisions of this part (such as, all officer effectiveness reports, all recall rosters, and all medical protocols).</P>
          <P>(4) Using a special cover sheet both to alert the WPC personnel as to the type information, and to protect the document during transmittal;</P>
          <P>(5) Requiring an oral warning on all dictation; or</P>
          <P>(6) Any other procedures that ensure the WPC personnel are alerted to the fact that personal data subject to this part is to be processed.</P>
          <P>b. To ensure that the operators or other WPC personnel receiving data for processing that has not been identified to be under the provisions of this part but that appear to be personal promptly call the information to the attention of the WPC supervisor or the customer;</P>
          <P>c. To ensure that any request for the processing of personal data that the customer has not identified as being in a system of records and that appears to meet the criteria set forth in paragraph (a) of § 310.10, subpart B is called to the attention of the appropriate supervisory personnel and system manager.</P>
          <P>2. The WPC supervisor shall ensure that personal information is not inadvertently compromised within the WPC.</P>
          <HD SOURCE="HD2">E. Safeguarding Information During Processing</HD>
          <P>1. Each WPC supervisor shall establish internal safeguards that shall protect personal data from compromise while it is being processed.</P>
          <P>2. Physical safeguards may include:</P>
          <P>a. Controls on individual access to the center;</P>
          <P>b. Machine configurations that reduce external access to the information being processed, or arrangements that alert the operator to the presence of others;</P>
          <P>c. Using certain specific machines to process personal data;</P>
          <P>d. Any other physical safeguards, to include special technical arrangements that will protect the data during processing.</P>
          <P>3. Other safeguards may include:</P>
          <P>a. Using only certain selected operators to process personal data;</P>
          <P>b. Processing personal data only at certain times during the day without the WPC manager's specific authorization;</P>
          <P>c. Using only certain tapes or diskettes to process and store personal data;</P>
          <P>d. Using continuous tapes for dictation of personal data;</P>
          <P>e. Requiring all WPC copies of documents to be marked specifically so as to prevent inadvertent compromise;</P>
          <P>f. Returning extra copies and mistakes to the customer with the product;</P>
          <P>g. Disposing of waste containing personal data in a special manner;</P>
          <P>h. Any other local procedures that provide adequate protection to the data being processed.</P>
          <HD SOURCE="HD2">F. Safeguarding Information During Return</HD>
          <P>1. The WPC shall protect the data until it is returned to the customer or placed into a formal distribution channel.</P>
          <P>2. In conjunction with the appropriate administrative support personnel and the WPC customers, the WPC manager shall establish procedures that protect the information from the time word processing is completed until it is returned to the customer.</P>
          <P>3. Safeguarding procedures may include:</P>
          <P>a. Releasing products only to specifically identifiable individuals;</P>
          <P>b. Using sealed envelopes to transmit products to the customer;</P>
          <P>c. Using special cover sheets to protect products similar to the one discussed in subparagraph D.1.a.(4), above;</P>
          <P>d. Handcarrying products to the customers;</P>
          <P>e. Using special messengers to return the products;</P>
          <P>f. Any other procedures that protect adequately products from compromise while they are awaiting return or being returned to the customer.</P>
          <HD SOURCE="HD2">G. Safeguards During Storage</HD>

          <P>1. The WPC manager shall ensure that all personal data retained in the center for any purpose (including samples) are protected properly.<PRTPAGE P="852"/>
          </P>
          <P>2. Safeguarding procedures may include:</P>
          <P>a. Marking all hard copies retained with special legends or designators;</P>
          <P>b. Storing media containing personal data in separate files or areas;</P>
          <P>c. Marking the storage containers for media containing personal data with special legends or notations;</P>
          <P>d. Restricting the reuse of media used to process personal data or erasing automatically the media before reuse;</P>
          <P>e. Establishing special criteria for the WPC retention of media used to store and process personal data;</P>
          <P>f. Returning the media to the customer for retention with the file copies of the finished products;</P>
          <P>g. Discouraging, when practical, the long-term storage of personal data in any form within the WPC;</P>
          <P>h. Any other filing or storage procedures that safeguard adequately any personal information retained or filed within the WPC.</P>
          <HD SOURCE="HD2">H. Risk Assessment for WPCs</HD>
          <P>1. Each WPC manager shall ensure that a formal, written risk assessment is prepared for each WPC that processes personal information subject to this part.</P>
          <P>2. The assessment shall address the areas discussed in sections D., E., F., and G. of this appendix, as well as any special risks that the WPC location, configuration, or organization may present to the compromise or alteration of personal data being processed or stored.</P>
          <P>3. A risk assessment shall be conducted at least every 5 years or whenever there is a change of equipment, equipment configuration, WPC location, WPC configuration or modification of the WPC facilities that either increases or decreases the likelihood of compromise of personal data.</P>
          <P>4. Copies of the assessment shall be retained by the WPC manager and made available to appropriate inspectors, as well as to personnel studying equipment for facility upgrading or modification.</P>
          <P>5. Every new WPC shall have a formal risk assessment completed before beginning the processing of personal data.</P>
          <HD SOURCE="HD2">I. Special Considerations in WPC Design and Modification</HD>
          <P>Procedures shall be established to ensure that all personnel involved in the design of WPCs or the acquisition of word processing equipment are aware of the special considerations required when processing personal data subject to this part.</P>
          <CITA>[51 FR 2364, Jan. 16, 1986. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57801, Nov. 14, 1991]</CITA>
        </APPENDIX>
        <APPENDIX>
          <EAR>Pt. 310, App. C</EAR>
          <HD SOURCE="HED">Appendix C to Part 310—DoD Blanket Routine Uses</HD>
          <HD SOURCE="HD3">(See paragraph (e) of § 310.41, subpart E)</HD>
          <HD SOURCE="HD2">A. Routine Use—Law Enforcement</HD>
          <P>If a system of records maintained by a DoD Component to carry out its functions indicates a violation or potential violation of law, whether civil, criminal, or regulatory in nature, and whether arising by general statute or by regulation, rule, or order issued pursuant thereto, the relevant records in the system of records may be referred, as a routine use, to the agency concerned, whether federal, state, local, or foreign, charged with the responsibility of investigating or prosecuting such violation or charged with enforcing or implementing the statute, rule, regulation, or order issued pursuant thereto.</P>
          <HD SOURCE="HD2">B. Routine Use—Disclosure when Requesting Information</HD>
          <P>A record from a system of records maintained by a Component may be disclosed as a routine use to a federal, state, or local agency maintaining civil, criminal, or other relevant enforcement information or other pertinent information, such as current licenses, if necessary to obtain information relevant to a Component decision concerning the hiring or retention of an employee, the issuance of a security clearance, the letting of a contract, or the issuance of a license, grant, or other benefit.</P>
          <HD SOURCE="HD2">C. Routine Use—Disclosure of Requested Information</HD>
          <P>A record from a system of records maintained by a Component may be disclosed to a federal agency, in response to its request, in connection with the hiring or retention of an employee, the issuance of a security clearance, the reporting of an investigation of an employee, the letting of a contract, or the issuance of a license, grant, or other benefit by the requesting agency, to the extent that the information is relevant and necessary tothe requesting agency's decision on the matter.</P>
          <HD SOURCE="HD2">D. Routine Use—Congressional Inquiries</HD>
          <P>Disclosure from a system of records maintained by a Component may be made to a congressional office from the record of an individual in response to an inquiry from the congressional office made at the request of that individual.</P>
          <HD SOURCE="HD2">E. Routine Use—Private Relief Legislation</HD>

          <P>Relevant information contained in all systems of records of the Department of Defense published on or before August 22, 1975, will be disclosed to the OMB in connection with the review of private relief legislation as set forth in OMB Circular A-19 (reference (u)) at <PRTPAGE P="853"/>any stage of the legislative coordination and clearance process as set forth in that Circular.</P>
          <HD SOURCE="HD2">F. Routine Use—Disclosures Required by International Agreements</HD>
          <P>A record from a system of records maintained by a Component may be disclosed to foreign law enforcement, security, investigatory, or administrative authorities to comply with requirements imposed by, or to claim rights conferred in, international agreements and arrangements including those regulating the stationing and status in foreign countries of DoD military and civilian personnel.</P>
          <HD SOURCE="HD2">G. Routine Use—Disclosure to State and Local Taxing Authorities</HD>
          <P>Any information normally contained in Internal Revenue Service (IRS) Form W-2 which is maintained in a record from a system of records maintained by a Component may be disclosed to state and local taxing authorities with which the Secretary of the Treasury has entered into agreements under 5 U.S.C., sections 5516, 5517, and 5520 (reference (v)) and only to those state and local taxing authorities for which an employee or military member is or was subject to tax regardless of whether tax is or was withheld. This routine use is in accordance with Treasury Fiscal Requirements Manual Bulletin No. 76-07.</P>
          <HD SOURCE="HD2">H. Routine Use—Disclosure to the Office of Personnel Management</HD>
          <P>A record from a system of records subject to the Privacy Act and maintained by a Component may be disclosed to the Office of Personnel Management (OPM) concerning information on pay and leave, benefits, retirement deduction, and any other information necessary for the OPM to carry out its legally authorized government-wide personnel management functions and studies.</P>
          <HD SOURCE="HD2">I. Routine Use—Disclosure to the Department of Justice for Litigation</HD>
          <P>A record from a system of records maintained by this component may be disclosed as a routine use to any component of the Department of Justice for the purpose of representing the Department of Defense, or any officer, employee or member of the Department in pending or potential litigation to which the record is pertinent.</P>
          <HD SOURCE="HD2">J. Routine Use—Disclosure to Military Banking Facilities Overseas</HD>
          <P>Information as to current military addresses and assignments may be provided to military banking facilities who provide banking services overseas and who are reimbursed by the Government for certain checking and loan losses. For personnel separated, discharged, or retired from the Armed Forces, information as to last known residential or home of record address may be provided to the military banking facility upon certification by a banking facility officer that the facility has a returned or dishonored check negotiated by the individual or the individual has defaulted on a loan and that if restitution is not made by the individual, the U.S. Government will be liable for the losses the facility may incur.</P>
          <HD SOURCE="HD2">K. Routine Use—Disclosure of Information to the General Services Administration (GSA)</HD>
          <P>A record from a system of records maintained by this component may be disclosed as a routine use to the General Services Administration (GSA) for the purpose of records management inspections conducted under authority of 44 U.S.C. 2904 and 2906.</P>
          <HD SOURCE="HD2">L. Routine Use—Disclosure of Information to the National Archives and Records Administration (NARA)</HD>
          <P>A record from a system of records maintained by this component may be disclosed as a routine use to the National Archives and Records Administration (NARA) for the purpose of records management inspections conducted under authority of 44 U.S.C. 2904 and 2906.</P>
          <HD SOURCE="HD2">M. Routine Use—Disclosure to the Merit Systems Protection Board</HD>
          <P>A record from a system of records maintained by this component may be disclosed as a routine use to the Merit Systems Protection Board, including the Office of the Special Counsel for the purpose of litigation, including administrative proceedings, appeals, special studies of the civil service and other merit systems, review of OPM or component rules and regulations, investigation of alleged or possible prohibited personnel practices; including administrative proceedings involving any individual subject of a DoD investigation, and such other functions, promulgated in 5 U.S.C. 1205 and 1206, or as may be authorized by law.</P>
          <HD SOURCE="HD2">N. Routine Use-Counterintelligence Purpose</HD>
          <P>A record from a system of records maintained by this component may be disclosed as a routine use outside the DoD or the U.S. Government for the purpose of counterintelligence activities authorized by U.S. Law or Executive Order or for the purpose of enforcing laws which protect the national security of the United States.</P>
          <CITA>[51 FR 2364, Jan. 16, 1986. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57801, Nov. 14, 1991; 62 FR 18518, Apr. 16, 1997]</CITA>
        </APPENDIX>
        <APPENDIX>
          <PRTPAGE P="854"/>
          <EAR>Pt. 310, App. D</EAR>
          <HD SOURCE="HED">Appendix D to Part 310—Provisions of the Privacy Act From Which a General or Specific Exemption May Be Claimed</HD>
          <GPOTABLE CDEF="xs25,xs25,r10" COLS="3" OPTS="L2">
            <TDESC>[See paragraph (d) of § 310.50, subpart F]</TDESC>
            <BOXHD>
              <CHED H="1">Exemption</CHED>
              <CHED H="2">(j)(2)</CHED>
              <CHED H="2">(k)(1-7)</CHED>
              <CHED H="1">Section of the Privacy Act</CHED>
            </BOXHD>
            <ROW>
              <ENT I="01">No</ENT>
              <ENT>No</ENT>
              <ENT>(b)(1) Disclosures within the Department of Defense.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">No</ENT>
              <ENT>No</ENT>
              <ENT>(2) Disclosures to the public.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">No</ENT>
              <ENT>No</ENT>
              <ENT>(3) Disclosures for a “routine use.”</ENT>
            </ROW>
            <ROW>
              <ENT I="01">No</ENT>
              <ENT>No</ENT>
              <ENT>(4) Disclosures to the Bureau of Census.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">No</ENT>
              <ENT>No</ENT>
              <ENT>(5) Disclosures for statistical research and reporting.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">No</ENT>
              <ENT>No</ENT>
              <ENT>(6) Disclosures to the National Archives.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">No</ENT>
              <ENT>No</ENT>
              <ENT>(7) Disclosures for law enforcement purposes.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">No</ENT>
              <ENT>No</ENT>
              <ENT>(8) Disclosures under emergency circumstances.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">No</ENT>
              <ENT>No</ENT>
              <ENT>(9) Disclosures to the Congress.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">No</ENT>
              <ENT>No</ENT>
              <ENT>(10) Disclosures to the General Accounting Office.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">No</ENT>
              <ENT>No</ENT>
              <ENT>(11) Disclosures pursuant to court orders.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">No</ENT>
              <ENT>No</ENT>
              <ENT>(12) Disclosure to consumer reporting agencies.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">No</ENT>
              <ENT>No</ENT>
              <ENT>(c)(1) Making disclosure accountings.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">No</ENT>
              <ENT>No</ENT>
              <ENT>(2) Retaining disclosure accountings.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>Yes</ENT>
              <ENT>(c)(3) Making disclosure accounting available to the individual.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>No</ENT>
              <ENT>(c)(4) Informing prior recipients of corrections.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>Yes</ENT>
              <ENT>(d)(1) Individual access to records.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>Yes</ENT>
              <ENT>(2) Amending records.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>Yes</ENT>
              <ENT>(3) Review of the component's refusal to amend a record.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>Yes</ENT>
              <ENT>(4) Disclosure of disputed information.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>Yes</ENT>
              <ENT>(5) Access to information compiled in anticipation of civil action.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>Yes</ENT>
              <ENT>(e)(1) Restrictions on collecting information.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>No</ENT>
              <ENT>(e)(2) Collecting directly from the individual.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>No</ENT>
              <ENT>(3) Informing individuals from whom information is requested.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">No</ENT>
              <ENT>No</ENT>
              <ENT>(e)(4)(A) Describing the name and location of the system.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">No</ENT>
              <ENT>No</ENT>
              <ENT>(B) Describing categories of individuals.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">No</ENT>
              <ENT>No</ENT>
              <ENT>(C) Describing categories of records.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">No</ENT>
              <ENT>No</ENT>
              <ENT>(D) Describing routine uses.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">No</ENT>
              <ENT>No</ENT>
              <ENT>(E) Describing records management policies and practices.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">No</ENT>
              <ENT>No</ENT>
              <ENT>(F) Identifying responsible officials.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>Yes</ENT>
              <ENT>(e)(4)(G) Procedures for determining if a system contains a record on an individual.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>Yes</ENT>
              <ENT>(H) Procedures for gaining access.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>Yes</ENT>
              <ENT>(I) Describing categories of information sources.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>No</ENT>
              <ENT>(e)(5) Standards of accuracy.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">No</ENT>
              <ENT>No</ENT>
              <ENT>(e)(6) Validating records before disclosure.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">No</ENT>
              <ENT>No</ENT>
              <ENT>(e)(7) Records of first amendment activities.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">No</ENT>
              <ENT>No</ENT>
              <ENT>(e)(8) Notification of disclosure under compulsory legal process.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">No</ENT>
              <ENT>No</ENT>
              <ENT>(e)(9) Rules of conduct.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">No</ENT>
              <ENT>No</ENT>
              <ENT>(e)(10) Administrative, technical and physical safeguards.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">No</ENT>
              <ENT>No</ENT>
              <ENT>(11) Notice for new and revised routine uses.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>Yes</ENT>
              <ENT>(f)(1) Rules for determining if an individual is subject of a record.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>Yes</ENT>
              <ENT>(f)(2) Rules for handling access requests.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>Yes</ENT>
              <ENT>(f)(3) Rules for granting access.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>Yes</ENT>
              <ENT>(f)(4) Rules for amending records.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>Yes</ENT>
              <ENT>(f)(5) Rules regarding fees.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>No</ENT>
              <ENT>(g)(1) Basis for civil action.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>No</ENT>
              <ENT>(g)(2) Basis for judicial review and remedies for refusal to amend.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>No</ENT>
              <ENT>(g)(3) Basis for judicial review and remedies for denial of access.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>No</ENT>
              <ENT>(g)(4) Basis for judicial review and remedies for other failure to comply.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>No</ENT>
              <ENT>(g)(5) Jurisdiction and time limits.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>No</ENT>
              <ENT>(h) Rights of legal guardians.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">No</ENT>
              <ENT>No</ENT>
              <ENT>(i)1) Criminal penalties for unauthorized disclosure.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">No</ENT>
              <ENT>No</ENT>
              <ENT>(2) Criminal penalties for failure to publish.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">No</ENT>
              <ENT>No</ENT>
              <ENT>(3) Criminal penalties for obtaining records under false pretenses.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes <SU>1</SU>
              </ENT>
              <ENT>No</ENT>
              <ENT>(j) Rulemaking requirement.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">N/A</ENT>
              <ENT>No</ENT>
              <ENT>(j)(1) General exemption for the Central Intelligence Agency.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">N/A</ENT>
              <ENT>No</ENT>
              <ENT>(i)(2) General exemption for criminal law enforcement records.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>N/A</ENT>
              <ENT>(k)(1) Exemption for classified material.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">N/A</ENT>
              <ENT>N/A</ENT>
              <ENT>(k)(2) Exemption for law enforcement material.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>N/A</ENT>
              <ENT>(k)(3) Exemption for records pertaining to Presidential protection.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>N/A</ENT>
              <ENT>(k)(4) Exemption for statistical records.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>N/A</ENT>
              <ENT>(k)(5) Exemption for investigatory material compiled for determining suitability for employment or service.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>N/A</ENT>
              <ENT>(k)(6) Exemption for testing or examination material.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>N/A</ENT>
              <ENT>(k)(7) Exemption for promotion evaluation materials used by the Armed Forces.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>No</ENT>
              <ENT>(l)(1) Records stored in NARA records centers.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>No</ENT>
              <ENT>(l)(2) Records archived before Sept. 27, 1975.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>No</ENT>
              <ENT>(l)(3) Records archived on or after Sept. 27, 1975.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>No</ENT>
              <ENT>(m) Applicability to Government contractors.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes</ENT>
              <ENT>No</ENT>
              <ENT>(n) Mailing lists.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes <SU>1</SU>
              </ENT>
              <ENT>No</ENT>
              <ENT>(o) Reports on new systems.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yes <SU>1</SU>
              </ENT>
              <ENT>No</ENT>
              <ENT>(p) Annual report.</ENT>
            </ROW>
            <TNOTE>
              <SU>1</SU> See paragraph (d) of § 310.50, subpart F.</TNOTE>
          </GPOTABLE>
          <CITA>[51 FR 2364, Jan. 16, 1986. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57801, Nov. 14, 1991; 62 FR 26389, May 14, 1997]</CITA>
        </APPENDIX>
        <APPENDIX>
          <EAR>Pt. 310, App. E</EAR>
          <HD SOURCE="HED">Appendix E to Part 310—Sample of New or Altered System of Records Notice in “Federal Register” Format</HD>
          <FP>(See paragraph (f) of § 310.60, subpart G)</FP>
          
          <FP>
            <E T="04">DEPARTMENT OF DEFENSE</E>
          </FP>
          
          <PRTPAGE P="855"/>
          <FP>
            <E T="04">Defense Nuclear Agency</E>
          </FP>
          
          <FP>
            <E T="04">Privacy Act of</E> 1974; <E T="04">New System of Records</E>
          </FP>
          
          <FP>
            <E T="04">agency:</E> Defense Nuclear Agency (DNA).</FP>
          
          <FP>
            <E T="04">action:</E> Notice of a new record system.</FP>
          
          
          
          
          <FP>
            <E T="04">summary:</E> The Defense Nuclear Agency is adding a new system of records to its inventory of systems of records subject to the Privacy Act of 1974. The system notice for the new system is set forth below.</FP>
          
          <FP>
            <E T="04">dates:</E> This system shall be effective (30 days after publication in the Federal Register) unless comments are received which result in a contrary determination.</FP>
          
          <FP>
            <E T="04">address:</E> Send comments to the System Manager identified in the system notice.</FP>
          
          <FP>
            <E T="04">for further information contact:</E> Robert L. Brittigan, General Counsel, Defense Nuclear Agency, Washington, DC 20305, Telephone (202) 325-7681.</FP>
          
          <FP>
            <E T="04">supplementary information:</E> The Defense Nuclear Agency record system notice as prescribed by the Privacy Act of 1974 (5 U.S.C. 552a), as amended, have appeared in the <E T="04">Federal Register</E> on September 28, 1981 (46 FR 51073) and February 16, 1982 (47 FR 6829).</FP>

          <P>The Defense Nuclear Agency has submitted a new system report on March 27, 1982, for this system of records under the provisions of 5 U.S.C. 552a(o) of the Privacy Act.
          </P>
          <P>Patricia H. Means,
          </P>
          <P>OSD Federal Register Liaison Officer, Department of Defense.</P>
          <HD SOURCE="HD2">Sample</HD>
          <HD SOURCE="HD1">HDNA 609-03</HD>
          <P>
            <E T="03">System name:</E> Personnel Exposed to Radiation from Nuclear Tests.</P>
          <P>
            <E T="03">System Location:</E> Headquarters, Defense Nuclear Agency, Washington, DC 20305, Main computer location.</P>
          <P>
            <E T="03">Categories of individuals covered by the system:</E> All DoD and DoD-affiliated personnel, military and civilian, who participated in the U.S. Government atmospheric nuclear test programs in the Pacific and at the Nevada Test Site.</P>
          <P>
            <E T="03">Categories of records in the system:</E> Personal information consisting of name, rank, service number, last known or current address, dates of test participation, exposure and unit of assignment.</P>
          <P>
            <E T="03">Authority for maintenance of the system:</E> 10 U.S.C. Section 133, Powers of an Executive Department of a Military Department to Prescribe Departmental Regulations; 10 U.S.C. Section 133, Secretary of Defense: Appointment, Powers, Duties and Delegation by; DoD Directive 5105.31, “Defense Nuclear Agency (DNA).”</P>
          <P>
            <E T="03">Purpose(s):</E> To identify those individuals who may have been exposed to radiation from nuclear atmospheric test conducted by the U.S. Government in the Pacific or at the Nevada Test Site.</P>
          <P>Information is provided to the medical services of all the Military Departments to identify military and retired personnel who were exposed to ionizing radiator during testing.</P>
          <P>
            <E T="03">Routine uses of records maintained in the system including categories of users, and the purpose of such uses:</E>
          </P>
          <P>To the National Research Council and Center for Disease Control to determine the effects of ionizing radiation for the limited purpose of conducting epidemiological studies of the atmospheric nuclear weapons tests on DoD participants in those tests.</P>
          <P>To the Department of Energy (DoE) to identify DoE contractor personnel exposed to ionizing radiation during nuclear testing for the limited purpose of conducting epidemiological studies of radiation effects of individuals so identified.</P>
          <P>To the Department of Transportation (DoT) for the limited purpose of identifying DoT and DoT-affiliated personnel exposed to ionizing radiation during nuclear testing.</P>
          <P>To the Veterans Administration to make determinations on service-connected disability for the purpose of resolving claims.</P>
          <P>
            <E T="03">Policies and Practices for storing, retrieving, accessing, retaining, and disposing of records in the system.</E>
          </P>
          <P>
            <E T="03">Storage:</E> Paper records in file folders; computer magnetic tape disks and printouts in secure computer facility.</P>
          <P>
            <E T="03">Retrievability:</E> Paper records filed in folders and computer magnetic tape and disk retrieved by name.</P>
          <P>
            <E T="03">Safeguards:</E> Paper records are filed in folders stored in locked security safes. Magnetic tapes stored in a vault in a secure computer area.</P>
          <P>
            <E T="03">Retention and disposal:</E> Paper records are retained until information is transferred to magnetic tapes; then destroyed. Magnetic tapes and disks are retained indefinitely.</P>
          <P>
            <E T="03">System manager(s) and address:</E> Director, Defense Nuclear Agency, Attn.: Privacy Act Officer, Washington, DC 20305, telephone (202) 325-7681.</P>
          <P>
            <E T="03">Notification procedure:</E> Information may be obtained from the System Manager.</P>
          <P>
            <E T="03">Record access procedures:</E> Requests should be addressed to the System Manager.</P>
          <P>
            <E T="03">Contesting record procedures:</E> The agency's rules for contesting contents and appealing initial determinations are contained in DNA Instruction 5400.11 (32 CFR part 318). Additional information may be obtained from the System Manager.</P>
          <P>
            <E T="03">Record source categories:</E> DNA records, searches of DoD records by other DoD Components, and from individuals voluntarily contacting DNA by telephone or mail.<PRTPAGE P="856"/>
          </P>
          <P>
            <E T="03">Systems exempted from certain provision of the Act:</E> None.</P>
          <CITA>[51 FR 2364, Jan. 16, 1986. Redesignated at 56 FR 55631, Oct. 29, 1991, asd amended at 56 FR 57801, Nov. 14, 1991]</CITA>
        </APPENDIX>
        <APPENDIX>
          <EAR>Pt. 310, App. F</EAR>
          <HD SOURCE="HED">Appendix F to Part 310—Format for New or Altered System Report</HD>
          <HD SOURCE="HD3">(See paragraph (c) of § 310.63, subpart G)</HD>
          <P>The report on a new or altered system shall consist of a transmittal letter, a narrative statement, and include supporting documentation.</P>
          <P>A. <E T="03">Transmittal Letter.</E> The transmittal letter to the Director, Defense Privacy Office, ODASD(A), shall include any request for waivers as set forth in paragraph (g) of § 310.63, subpart G. The narrative statement shall be attached thereto.</P>
          <P>B. <E T="03">Narrative Statement.</E> The narrative statement is typed in double space on standard bond paper in the format shown at attachment 1. The statement includes:</P>
          <P>1. <E T="03">System identification and name.</E> This caption sets forth the identification and name of the system (see paragraphs (b) and (c) of § 310.62, subpart G).</P>
          <P>2. <E T="03">Responsible official.</E> The name, title, address, and telephone number of the privacy official responsible for the report and to whom inquiries and comments about the report may be directed by Congress, the Office of Management and Budget, or Defense Privacy Office.</P>
          <P>3. <E T="03">Purpose of the system or nature of the change proposed.</E> Describe the purpose of the new system. For an altered system, describe the nature of the change being proposed.</P>
          <P>4. <E T="03">Authority for the system.</E> See paragraph (g) of § 310.62, subpart G.</P>
          <P>5. <E T="03">Number of individuals.</E> The approximate number of individuals about whom records are to be maintained.</P>
          <P>6. <E T="03">Information on First Amendment activities.</E> Describe any information to be kept on the exercise of individual's First Amendment rights and the basis for maintaining it as provided for in paragraph (e) of § 310.10, subpart B.</P>
          <P>7. <E T="03">Measures to ensure information accuracy.</E> If the system is to be used to make determinations about the rights, benefits, or entitlements of individuals; describe the measures being established to ensure the accuracy, currency, relevance, and completeness of the information used for these purposes.</P>
          <P>8. <E T="03">Other measures to ensure system security:</E> Describe the steps taken to minimize the risk of unauthorized access to the system. A more detailed assessment of security risks and specific administrative, technical, and physical safeguards shall be available for review upon request.</P>
          <P>9. <E T="03">Relationship to state and local government activities.</E> Describe the relationship of the system to state or local government activities that are the sources, recipients, or users of the information in the system.</P>
          <P>C. <E T="03">Supporting Documentation.</E> Item 10 of the narrative is captioned <E T="03">Supporting Documents.</E> A positive statement for this caption is essential for those enclosures that are not required to be enclosed. For example, “No changes to the existing Army procedural or exemption rules (32 CFR part 505) are required for this proposed system.” List in numerical sequence only those enclosures that are actually furnished. The following are typical enclosures that may be required:</P>
          <P>1. For a new system, an advance copy of the system notice which is proposed for publication. For an altered system (see paragraph (d) of § 310.64, subpart G) an advance copy of the notice reflecting the specific changes proposed.</P>
          <P>2. An advance copy of any new rules or changes to the published Component rules to be issued for the new or altered system. If no change to existing rules is required, so state in the narrative.</P>
          <P>3. An advance copy of any proposed exemption rule if the new or altered system is to be exempted in accordance with subpart F. If there is no exemption, so state in the narrative.</P>
          <P>4. Any other supporting documentation that may be pertinent or helpful in understanding the need for the system or clarifying its intended use. While not required, such documentation, when available, is helpful in evaluating the new or altered system.</P>
          <HD SOURCE="HD1">Attachment 1—Sample Format for Narrative Statement</HD>
          <HD SOURCE="HD1">DEPARTMENT OF DEFENSE</HD>
          <HD SOURCE="HD1">(Component Name)</HD>
          <HD SOURCE="HD1">REPORT ON NEW (OR ALTERED) SYSTEM UNDER THE PRIVACY ACT OF 1974</HD>
          <P>(Indicate none or not applicable, as appropriate.)</P>
          <P>1. <E T="03">System Identification and name:</E>
          </P>
          <P>2. <E T="03">Responsible official:</E>
          </P>
          <P>3. <E T="03">Purpose(s) of the System:</E> (for a new system only) or <E T="03">Nature of the Change(s) Proposed:</E> (for altered system).</P>
          <P>4. <E T="03">Authority for the System:</E>
          </P>
          <P>5. <E T="03">Number of Individuals:</E>
          </P>
          <P>6. <E T="03">Information on First Amendment Activities:</E>
          </P>
          <P>7. <E T="03">Measures to Ensure Information Accuracy:</E>
          </P>
          <P>8. <E T="03">Other Measures to Ensure System Security:</E>
          </P>
          <P>9. <E T="03">Relations to State or Local Government Activities:</E>
          </P>
          <P>10. <E T="03">Supporting Documentation:</E> (Indicate here, as a positive statement, those enclosures <E T="03">not</E> required as set forth in section C. of the format instructions.)<PRTPAGE P="857"/>
          </P>
          <HD SOURCE="HD1">SIGNATURE BLOCK OF SUBMITTING OFFICIAL</HD>
          <HD SOURCE="HD1">Attachment 2—Sample Report</HD>
          <HD SOURCE="HD1">DEPARTMENT OF DEFENSE</HD>
          <HD SOURCE="HD3">Defense Nuclear Agency</HD>
          <HD SOURCE="HD3">REPORT ON NEW SYSTEM UNDER THE PRIVACY ACT OF 1974</HD>
          <P>1. <E T="03">System Identification and Name:</E> HDNA 609-03, entitled “Personnel Exposed To Radiation From Nuclear Tests.”</P>
          <P>2. <E T="03">Responsible Official:</E> Robert L. Brittigan, General Counsel, Defense Nuclear Agency, Washington, DC 20305. Telephone: Area Code 202 325-7781.</P>
          <P>3. <E T="03">Purpose(s) of the System:</E> To consolidate into one system the names, addresses, and exposures of all DoD or DoD-assoicated personnel who may have been exposed to ionizing radiation during the atmospheric nuclear testing programs in the Pacific and at the Nevada Test Site.</P>
          <P>4. <E T="03">Authority for the System:</E> See “Authority for Maintenance of the System” caption of the attached proposed system notice.</P>
          <P>5. Number of Individuals: Approximately 300,00 individuals will be affected by this new system, since the system includes all DoD and DoD-affiliated participants in the atmospheric nuclear tests program.</P>
          <P>6. <E T="03">Information on First Amendment Activities:</E> None.</P>
          <P>7. <E T="03">Measures to Ensure Information Accuracy:</E> Records consist of personal data to be provided by the individual such as name, rank, service number, last known or current address, dates of test participation, exposure date, if available, and unit of assignment. When the information has been obtained from sources other than the individual, follow-up is attempted to ensure accuracy.</P>
          <P>8. <E T="03">Other Measures to Ensure System Security:</E>
          </P>
          <P>a. Paper records before processing for computer storage are retained in locked filing cabinets located in limited access facilities at DNA Headquarters and the Armed Forces Radiobiology Research Institute.</P>
          <P>b. Privacy data in the Headquarters, DNA, ADP facility is afforded the same protection as classified data in that the DNA computer system employs a File Security System (FSS) to protect classified and privacy data files from being accessed by unauthorized user.</P>
          <P>9. <E T="03">Relations to State and Local Government Activities:</E> None</P>
          <P>10. <E T="03">Supporting Documentation:</E> No changes to existing procedural or exemption rules are required for this proposed new system.
          </P>
          <P>Robert L. Brittigan</P>
          <P>General Counsel</P>
          <HD SOURCE="HD1">Enclosures—2</HD>
          <P>1. Advance copy of proposed system notice.</P>
          <P>2. Copy of tasking memorandum from the Assistant Secretary of Defense (Manpower, Reserve Affairs, and Logistics) to the Director, Defense Nuclear Agency, “DoD Personnel Participation in Atmosperic Nuclear Weapons Testing,” January 28, 1978.</P>
          <NOTE>
            <HD SOURCE="HED">Note:</HD>
            <P>Enclosures are not included in the sample, above.</P>
          </NOTE>
          <CITA>[51 FR 2364, Jan. 16, 1986. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57801, Nov. 14, 1991]</CITA>
        </APPENDIX>
        <APPENDIX>
          <EAR>Pt. 310, App. G</EAR>
          <HD SOURCE="HED">Appendix G to Part 310—Sample Deletions and Amendments to Systems Notices in “Federal Register” Format</HD>
          <HD SOURCE="HD3">(See paragraph (d) of § 310.64, subpart G)</HD>
          <HD SOURCE="HD3">DEPARTMENT OF DEFENSE</HD>
          <HD SOURCE="HD3">Department of Air Force</HD>
          
          <FP>
            <E T="04">Privacy Act of</E> 1974<E T="04">; Deletions and Amendments to Systems of Records Notices</E>
          </FP>
          <FP>
            <E T="04">Agency:</E> Department of the Air Force, DoD.</FP>
          
          <FP>
            <E T="04">Action:</E> Notice of deletions and amendments to systems of records.</FP>
          
          
          
          
          <FP>
            <E T="04">Summary:</E> The Air Force proposes to delete three and amend two notices for systems of records subject to the Privacy Act of 1974. The specific changes to the notices being amended are set forth below followed by the system notices, as amended, published in their entirety.</FP>
          
          <FP>
            <E T="04">Dates:</E> These systems notices shall be amended as proposed without further notice on (30 days after publication in the <E T="04">Federal Register</E> unless comments are received that would result in a contrary determination.</FP>
          
          <FP>
            <E T="04">Address:</E> Send comments to the system manager identified in the particular system notice concerned.</FP>
          
          <FP>
            <E T="04">For Further Information Contact:</E> Mr. Jon E. Updike, HQ USAF/DAQD, The Pentagon, Washington, DC 20330-5024, Telephone: (202) 694-3431 Autovon: 224-3431</FP>
          
          <FP>
            <E T="04">Supplementary Information:</E> The Air Force sytems of records notices inventory subject to the Privacy Act of 1974 (5 U.S.C. 552a), as amended, have been published to date in the <E T="04">Federal Register</E> as follows:</FP>
          
          <FP SOURCE="FP-1">FR Doc. 80-28255 (46 FR 50785) September 28, 1980</FP>
          <FP SOURCE="FP-1">FR Doc. 80-31218 (46 FR 56774) October 28, 1980</FP>
          <FP SOURCE="FP-1">FR Doc. 80-32284 (46 FR 58195) November 8, 1980</FP>
          <FP SOURCE="FP-1">FR Doc. 80-33780 (46 FR 59996) November 23, 1980</FP>
          

          <P>The proposed amendments are not within the purview of the provisions of 5 U.S.C. 552a(o) which requires the submission of an altered system report.
            <PRTPAGE P="858"/>
          </P>
          <P>Patricia H. Means,</P>
          <P>OSD Federal Register Liaison Officer, Department of Defense.</P>
          <HD SOURCE="HD1">Deletions</HD>
          <HD SOURCE="HD2">F01001 OQPTFLA</HD>
          <P>
            <E T="03">System name:</E> Human Reliability for Special Missions.</P>
          <P>
            <E T="03">Reason:</E> This system is covered by F03004 AFDPMDB Advanced Personnel Data System (APDS) (46 FR 50821) August 28, 1981.</P>
          <HD SOURCE="HD2">F01003 OBXQPCA</HD>
          <P>
            <E T="03">System name:</E> Cadet Promotion List.</P>
          <P>
            <E T="03">Reason:</E> This system has been incorporated into F03502 AFA A Cadet Management System (46 FR 50875) July 28, 1981.</P>
          <HD SOURCE="HD2">F01102 OYUEBLA</HD>
          <P>
            <E T="03">System name:</E> Locator or Personnel Data file.</P>
          <P>
            <E T="03">Reason:</E> This sytem is covered by F01102 DAYX A Base, Unit, and Organizational Military and Civilian Personnel Locator Files (46 FR 50800) October 28, 1981.</P>
          <HD SOURCE="HD1">Amendments</HD>
          <HD SOURCE="HD2">F03501 DPMDQIA</HD>
          <P>
            <E T="03">System name:</E> Military Personnel Records System.</P>
          <P>
            <E T="03">Changes:</E>
          </P>
          <P>
            <E T="03">System Location:</E> In line 8, change “Adjustment” to Adjutant”.</P>
          <P>
            <E T="03">External users, uses and purposes:</E>
          </P>
          <P>
            <E T="03">Add at end:</E>
          </P>
          <P>“American National Red Cross. Information to local Red Cross offices for emergency assistance to military members, dependents, relatives, or other persons if conditions are compelling.”</P>
          <P>“Drug Enforcement Administration” (added to those agencies listed under Department of Justice).</P>
          <P>“Department of Labor: Bureau of Employees’ Compensation—medical information for claims of civilian employees formerly in military service; Employment and Training Administration—verification of service-related information for unemployment compensation claims; Labor-Management Services Administration—for investigations of possible violations of labor laws and preemployment investigations; National Research Council—for medical research purposes; U.S. Soldiers’ and Airmen's Home—service information to determine eligibility.”</P>
          <HD SOURCE="HD2">F03504 OJMPLSC</HD>
          <P>
            <E T="03">System name:</E> Assessments Screening Records.</P>
          <P>
            <E T="03">Changes:</E>
          </P>
          <P>
            <E T="03">System location:</E> In line 1, change “3700 Personnel Processing Group” to “3507 Airman Classification Squadron.”</P>
          <P>Retention and disposal: Delete entry and substitute: “Records on airmen accepted for sensitive or high risk assignments are retained in the office files for 18 months, then destroyed. Records of nonselectees are retained in office files for 1 year, then destroyed. Destruction is by tearing into pieces, shredding, pulping, macerating, or burning.”</P>
          <P>
            <E T="03">Systems manager:</E> In line 1, change “3700 PPGP (CCO),” to “3507 Airman Classification Squadron.”</P>
          <P>
            <E T="03">Record source categories:</E> Add at end, “peers, character references, and the individual member.”</P>
          <CITA>[51 FR 2364, Jan. 16, 1986. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57801, Nov. 14, 1991]</CITA>
        </APPENDIX>
        <APPENDIX>
          <EAR>Pt. 310, App. H</EAR>
          <HD SOURCE="HED">Appendix H to Part 310—Litigation Status Sheet</HD>
          <HD SOURCE="HD3">(See § 310.104, subpart K)</HD>
          <P>1. Case Number.<SU>1</SU>
            <FTREF/>
          </P>
          <FTNT>
            <P>
              <SU>1</SU> Number used by the Component for reference purposes</P>
          </FTNT>
          <P>2. Requester.</P>
          <P>3. Document Title or Description. <SU>2</SU>
            <FTREF/>
          </P>
          <FTNT>
            <P>
              <SU>2</SU> Indicate the nature of the case, such as, “Denial of access,” “Refusal to amend,” “Incorrect records,” or other violations of the Act (specify).</P>
          </FTNT>
          <P>4. Litigation:</P>
          <P>a. Date Complaint Filed.</P>
          <P>b. Court.</P>
          <P>c. Case File Number <SU>1</SU>
          </P>
          <P>5. Defendants (DoD Component and individual).</P>
          <P>6. Remarks (brief explanation of what the case is about).</P>
          <P>7. Court Action:</P>
          <P>a. Court's Finding.</P>
          <P>b. Disciplinary Action (as appropriate).</P>
          <P>8. Appeal (as appropriate):</P>
          <P>a. Date Complaint Filed.</P>
          <P>b. Court.</P>
          <P>c. Case File Number. <SU>1</SU>
          </P>
          <P>d. Court's Finding.</P>
          <P>e. Disciplinary Action (as appropriate).</P>
          <CITA>[51 FR 2364, Jan. 16, 1986. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57801, Nov. 14, 1991]</CITA>
        </APPENDIX>
        <APPENDIX>
          <EAR>Pt. 310, App. I</EAR>
          <HD SOURCE="HED">Appendix I to Part 310—Office of Management and Budget (OMB) Matching Guidelines</HD>
          <HD SOURCE="HD3">(See § 310.110, subpart L)</HD>
          <P>A. <E T="03">Purpose.</E> These guidelines supplement and shall be used in conjunction with OMB <PRTPAGE P="859"/>Guidelines on the Administration of the Privacy Act of 1974, issued on July 1, 1975, and supplemented on November 21, 1975. They replace earlier guidance on conducting computerized matching programs issued on March 30, 1979. They are intended to help agencies relate the procedural requirements of the Privacy Act to the operational requirements of computerized matching. They are designed to address the concerns expressed by the Congress in the Privacy Act of 1974 that “the increasing use of computers and sophisticated information technology, while essential to the efficient operation of the Government, has greatly magnified the harm to individual privacy that can occur from any collection, maintenance, use, or dissemination of personal information.” These guidelines do not authorize activities that are not permitted by law, nor do they prohibit activities expressly required to be performed by law. Complying with these guidelines, however, does not relieve a federal agency of the obligation to comply with the provisions of the Privacy Act, including any provisions not cited in these guidelines.</P>
          <P>B. <E T="03">Scope.</E> These guidelines apply to all agencies subject to the Privacy Act of 1974 (5 U.S.C. 552a) and to all matching programs:</P>
          <P>1. Performed by a federal agency, whether the personal records used in the match are federal or nonfederal.</P>
          <P>2. For which a federal agency discloses any personal records for use in a matching program performed by any other federal agency or any nonfederal organization.</P>
          <P>C. <E T="03">Effective Date.</E> These guidelines are effective on May 11, 1982.</P>
          <P>D. <E T="03">Definitions.</E> For the purposes of the Guidelines, all the terms defined in the Privacy Act of 1974 apply.</P>
          <P>1. <E T="03">Personal Record.</E> Any information pertaining to an individual that is stored in an automated system of records; for example, a data base which contains information about individuals that is retrieved by name or some other personal identifier.</P>
          <P>2. <E T="03">Matching Program.</E> A procedure in which a computer is used to compare two or more automated systems of records or a system of records with a set of nonfederal records to find individuals who are common to more than one system or set. The procedure includes all of the steps associated with the match, including obtaining the records to be matched, actual use of the computer, administrative and investigative action on the hits, and disposition of the personal records maintained in connection with the match. It should be noted that a single matching program may involve several matches among a number of participants. Matching programs do not include the following:</P>
          <P>a. Matches that do not compare a substantial number of records, such as, comparison of the Department of Education's defaulted student loan data base with the Office of Personnel Management's federal employee data base would be covered; comparison of six individual student loan defaultees with the OPM file would not be covered.</P>
          <P>b. Checks on specific individuals to verify data in an application for benefits done reasonably soon after the application is received.</P>
          <P>c. Checks on specific individuals based on information which raises questions about an individual's eligibility for benefits or payments done reasonably soon after the information is received.</P>
          <P>d. Matches done to produce aggregate statistical data without any personal identifiers.</P>
          <P>e. Matches done to support any research or statistical project when the specific data are not to be used to make decisions about the rights, benefits, or privileges of specific individuals.</P>
          <P>f. Matches done by an agency using its own records.</P>
          <P>3. <E T="03">Matching Agency.</E> The federal agency which actually performs the match.</P>
          <P>4. <E T="03">Source Agency.</E> The federal agency which discloses records from a system of records to be used in the match. Note that in some circumstances a source agency may be the instigator and ultimate beneficiary of the matching program, as when an agency lacking computer resources uses another agency to perform the match. The disclosure of records to the matching agency and any later disclosure of “hits” (by either the matching or the source agencies) must be done in accordance with the provisions of paragraph (b) of the Privacy Act.</P>
          <P>5. <E T="03">Hit.</E> The identification, through a matching program, of a specific individual.</P>
          <P>E. <E T="03">Guidelines for Agencies Participating in Matching Programs.</E> Agencies should acquire and disclose matching records and conduct matching programs in accordance with the provisions of this section and the Privacy Act.</P>
          <P>1. <E T="03">Disclosing Personal Records for Matching Programs.</E>
          </P>
          <P>a. <E T="03">To another federal agency.</E> Source agencies are responsible for determining whether or not to disclose personal records from their systems and for making sure they meet the necessary Privacy Act disclosure provisions when they do. Among the factors source agencies should consider are:</P>
          <P>(1) Legal authority for the match;</P>
          <P>(2) Purpose and description of the match;</P>
          <P>(3) Description of the records to be matched;</P>

          <P>(4) Whether the record subjects have consented to the match; or whether disclosure of records for the match would be compatible with the purpose for which the records were <PRTPAGE P="860"/>originally collected; that is, whether disclosure under a “routine use” would be appropriate; whether the soliciting agency is seeking the records for a legitimate law enforcement activity—whichever is appropriate; or any other provision of the Privacy Act under which disclosure may be made;</P>
          <P>(5) Description of additional information which may be subsequently disclosed in relation to “hits”;</P>
          <P>(6) Subsequent actions expected of the source (for example, verification of the identity of the “hits” or follow-up with individuals who are “hits”);</P>
          <P>(7) Safeguards to be afforded the records involved, including disposition.</P>

          <P>b. If the agency is satisfied that disclosure of the records would not violate its responsibilities under the Privacy Act, it may proceed to make the disclosure to the matching agency. It should ensure that only the minimum information necessary to conduct the match is provided. If disclosure is to be made pursuant to a “routine use” (Section (b)(3) of the Privacy Act), it should ensure that the system of records contains such a use, or it should publish a routine use notice in the <E T="04">Federal Register.</E> The agency should also be sure to maintain an accounting of the disclosures pursuant to Section (c) of the Privacy Act.</P>
          <P>c. To a nonfederal entity. Before disclosing records to a nonfederal entity for a matching program to be carried out by that entity, a source agency should, in addition to all of the consideration in paragraph E.1.a., above, also make reasonable efforts, pursuant to Section (e)(6) of the Privacy Act, to “assure that such records are accurate, complete, timely, and relevant for agency purposes.”</P>
          <P>2. <E T="03">Written Agreements.</E> Before disclosing to either a federal or nonfederal entity, the source agency should require the matching entity to agree in writing to certain conditions governing the use of the matching file; for example, that the matching file will remain the property of the source agency and be returned at the end of the matching program (or destroyed as appropriate); that the file will be used and accessed only to match the file or files previously agreed to; that it will not be used to extract information concerning “non-hit” individuals for any purpose, and that it will not be duplicated or disseminated within or outside the matching agency unless authorized in writing by the source agency.</P>
          <P>3. <E T="03">Performing Matching Programs.</E> (a) Matching agencies should maintain reasonable administrative, technical, and physical security safeguards on all files involved in the matching program.</P>

          <P>(b) Matching agencies should insure that they have appropriate systems of records including those containing “hits,” and that such systems and any routine uses have been appropriately noticed in the <E T="04">Federal Register</E> and reported to OMB and the Congress, as appropriate.</P>
          <P>4. <E T="03">Disposition of Records.</E> a. Matching agencies will return or destroy source matching files (by mutual agreement) immediately after the match.</P>
          <P>b. Records relating to hits will be kept only so long as an investigation, either criminal or administrative, is active, and will be disposed of in accordance with the requirements of the Privacy Act and the Federal Records Schedule.</P>
          <P>5. <E T="03">Publication Requirements.</E> a. Agencies, before disclosing records outside the agency, will publish appropriate “routine use” notices in the <E T="04">Federal Register,</E> if necessary.</P>

          <P>b. If the matching program will result in the creation of a new or the substantial alteration of an existing system of records, the agency involved should publish the appropriate <E T="04">Federal Register</E> notice and submit the requisite report to OMB and the Congress pursuant to OMB Circular No. A-108.</P>
          <P>6. <E T="03">Reporting Requirements.</E> a. As close to the initiation of the matching program as possible, matching agencies shall publish in the <E T="04">Federal Register</E> a brief public notice describing the matching program. The notice should include:</P>
          <P>(1) The legal authority under which the match is being conducted;</P>
          <P>(2) A description of the matching program including whether the program is one time or continuing, the organizations involved, the purpose or purposes for which the program is being conducted, and the procedures to be used in matching and following up on the “hits”;</P>

          <P>(3) A complete description of the personal records to be matched, including the source or sources, system of records identifying data, date or dates and page number of the most recent <E T="04">Federal Register</E> full text publication when appropriate;</P>
          <P>(4) The projected start and ending dates of the program;</P>
          <P>(5) The security safeguards to be used to protect against unauthorized access or disclosure of the personal records; and</P>
          <P>(6) Plans for disposition of the source records and “hits.”</P>

          <P>7. Agencies should send a copy of this notice to the Congress and to OMB at the same time it is sent to the <E T="04">Federal Register.</E>
          </P>
          <P>a. Agencies should report new or altered systems of records as described in paragraph E.5.b., above, as necessary.</P>

          <P>b. Agencies should also be prepared to report on matching programs pursuant to the reporting requirements of either the Privacy Act or the Paperwork Reduction Act. Reports will be solicited by the Office of Information and Regulatory Affairs and will focus on both the protection of individual privacy and the government's effective use of information technology. Reporting instructions will be disseminated to the agencies as part <PRTPAGE P="861"/>of either the reports required by paragraph (p) of the Privacy Act, or Section 3514 of Pub. L. 96-511.</P>
          <P>8. <E T="03">Use of Contractors.</E> Matching programs should, as far as practicable, be conducted “in-house” by federal agencies using agency personnel, rather than by contract. When contractors are used, however,</P>
          <P>a. The matching agency should, consistent with paragraph (m) of the Privacy Act, cause the requirements of that Act to be applied to the contractor's performance of the matching program. The contract should include the Privacy Act clause required by Federal Personnel Regulation Amendment 155 (41 CFR 1-1.337-5);</P>
          <P>b. The terms of the contract should include appropriate privacy and security provisions consistent with policies, regulations, standards, and guidelines issued by OMB, GSA, and the Department of Commerce;</P>
          <P>c. The terms of the contract should preclude the contractor from using, disclosing, copying, or retaining records associated with the matching program for the contractor's own use;</P>
          <P>d. Contractor personnel involved in the matching program shall be made explicitly aware of their obligations under the Act and of these guidelines, agency rules, and any special safeguards in relation to each specific match performed.</P>
          <P>e. Any disclosures of records by the agency to the contractor should be made pursuant to a “routine use” (5 U.S.C. 552a(b)(3)).</P>
          <P>F. <E T="03">Implementation and Oversight.</E> OMB will oversee the implementation of these guidelines and shall interpret and advise upon agency proposals and actions within their scope, consistent with section 6 of the Privacy Act.</P>
          <CITA>[51 FR 2364, Jan. 16, 1986. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57801, Nov. 14, 1991]</CITA>
        </APPENDIX>
      </SUBPART>
    </PART>
    <PART>
      <EAR>Pt. 311</EAR>
      <HD SOURCE="HED">PART 311—OSD PRIVACY PROGRAM</HD>
      <CONTENTS>
        <SECHD>Sec.</SECHD>
        <SECTNO>311.1</SECTNO>
        <SUBJECT>Purpose.</SUBJECT>
        <SECTNO>311.2</SECTNO>
        <SUBJECT>Applicability and scope.</SUBJECT>
        <SECTNO>311.3</SECTNO>
        <SUBJECT>Definitions.</SUBJECT>
        <SECTNO>311.4</SECTNO>
        <SUBJECT>Policy.</SUBJECT>
        <SECTNO>311.5</SECTNO>
        <SUBJECT>Responsibilities.</SUBJECT>
        <SECTNO>311.6</SECTNO>
        <SUBJECT>Procedures.</SUBJECT>
        <SECTNO>311.7</SECTNO>
        <SUBJECT>Information requirements.</SUBJECT>
        <SECTNO>311.8</SECTNO>
        <SUBJECT>Procedures for exemptions.</SUBJECT>
      </CONTENTS>
      <AUTH>
        <HD SOURCE="HED">Authority:</HD>
        <P>Pub. L. 93-579, 88 Stat. 1986 (5 U.S.C. 552a).</P>
      </AUTH>
      <SOURCE>
        <HD SOURCE="HED">Source:</HD>
        <P>64 FR 22785, Apr. 28, 1999, unless otherwise noted.</P>
      </SOURCE>
      <SECTION>
        <SECTNO>§ 311.1</SECTNO>
        <SUBJECT>Purpose.</SUBJECT>
        <P>This part updates and implements basic policies and procedures outlined in 5 U.S.C. 552a, OMB Circular A-130,<SU>1</SU>
          <FTREF/> and DoD 5400.11-R <SU>2</SU>
          <FTREF/> and provides guidance and procedures for use in establishing the Privacy Program in the Office of the Secretary of Defense (OSD) and those organizations assigned to OSD for administrative support.</P>
        <FTNT>
          <P>
            <SU>1</SU> Copies may be obtained by contacting EOP Publications, 725 16th Street, NW., NEOB, Washington, DC 20503.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>2</SU> Copies may be obtained via internet at http://web7.whs.osd.mil/corres.htm.</P>
        </FTNT>
      </SECTION>
      <SECTION>
        <SECTNO>§ 311.2</SECTNO>
        <SUBJECT>Applicability and scope.</SUBJECT>
        <P>This part:</P>
        <P>(a) Applies to the OSD, the Chairman of the Joint Chiefs of Staff, Uniformed Services University of the Health Sciences (USUHS) and other activities assigned to OSD for administrative support hereafter referred to collectively as “OSD Components.”</P>
        <P>(b) Covers record systems maintained by OSD Components and governs the maintenance, access, change, and release of information contained in OSD Component record systems, from which information about an individual is retrieved by a personal identifier.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 311.3</SECTNO>
        <SUBJECT>Definitions.</SUBJECT>
        <P>
          <E T="03">Access.</E> Any individual's review of a record or a copy of a record or parts of a system of records.</P>
        <P>
          <E T="03">Disclosure.</E> The transfer of any personal information from a system of records by any means of oral, written, electronic, mechanical, or other  communication, to any person, private entity, or Government agency, other than the subject of the record, the subject's designated agent, or the subject's guardian.</P>
        <P>
          <E T="03">Individual.</E> A living citizen of the United States or an alien lawfully admitted to the United States for permanent residence. The legal guardian of an individual has the same rights as the individual and may act on his or her behalf.</P>
        <P>
          <E T="03">Individual access.</E> Access to personal information pertaining to the individual, by the individual, his or her designated agent or legal guardian.<PRTPAGE P="862"/>
        </P>
        <P>
          <E T="03">Maintain.</E> Includes maintenance, collection, use or dissemination.</P>
        <P>
          <E T="03">Personal information.</E> Information about an individual that is intimate or private, as distinguished from information related solely to the individual's official functions or public life.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 311.4</SECTNO>
        <SUBJECT>Policy.</SUBJECT>
        <P>(a) It is DoD policy to safeguard personal information contained in any system of records maintained by any DoD Component and to permit any individual to know what existing records pertain to him or her in any OSD Component covered by this part.</P>
        <P>(b) Each office maintaining records and information about individuals shall ensure that their privacy is protected from unauthorized disclosure of personal information. These offices shall permit individuals to have access to, and to have a copy made of all, or any portion of records about them, except as provided in Chapters 3 and 5, DoD 5400.11-R, and to have an opportunity to request that such records be amended as provided by the Privacy Act of 1974 and Chapter 3 of DoD 5400.11-R. Individuals requesting access to their records shall receive concurrent consideration under 5 U.S.C. 552a and the Freedom of Information Act, as amended, if appropriate.</P>
        <P>(c) Heads of OSD Components shall maintain any necessary record of a personal nature that is individually identifiable in a manner that complies with the law and DoD policy. Any information collected must be as accurate, relevant, timely, and complete as is reasonable to ensure fairness to the individual. Adequate safeguards must be provided to prevent misuse or unauthorized release of such information.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 311.5</SECTNO>
        <SUBJECT>Responsibilities.</SUBJECT>
        <P>(a) The Director of Administration and Management, Office of the Secretary of Defense (DA&amp;M, OSD) shall:</P>
        <P>(1) Direct and administer the DoD Privacy Program for OSD Components.</P>
        <P>(2) Establish standards and procedures to ensure implementation of and compliance with the Privacy Act of 1974, OMB Circular No. A-130, and DoD 5400.11-R.</P>
        <P>(3) Designate the Director for Freedom of Information and Security Review as the point of contact for individuals requesting information of access to records and copies about themselves.</P>
        <P>(4) Serve as the appellate authority within OSD when a requester appeals a denial for access to records under the Privacy Act.</P>
        <P>(5) Serve as the appellate authority within OSD when a requester appeals a denial for amendment of a record or initiates legal action to correct a record.</P>
        <P>(6) Evaluate and decide, in coordination with The General Counsel of the Department of Defense (GC, DoD), appeals resulting from denials of access or amendments to records by the OSD Components.</P>
        <P>(7) Designate the Directives and Records Division, Correspondence and Directives Directorate, Washington Headquarters Services (WHS) as the office responsible for all aspects of the Privacy Act, except that portion about receiving and acting on public requests for personal records. As such, the Directives and Records Division shall:</P>
        <P>(i) Exercise oversight and administrative control of the Privacy Act Program in OSD and those organizations assigned to OSD for administrative support.</P>
        <P>(ii) Provide guidance and training to organizational entities as required by 5 U.S.C. 552a and OMB Circular A-130. Periodic training will be provided to public affairs officers and others who may be expected to deal with the news media or the public.</P>
        <P>(iii) Collect and consolidate data from OSD Components, and submit an annual report to the Defense Privacy Office, as required by 5 U.S.C. 552a, OMB Circular A-130, and DoD -5400.11-R.</P>

        <P>(iv) Coordinate and consolidate information for reporting all record systems, as well as changes to approved systems, to the OMB, the Congress, and the <E T="04">Federal Register,</E> as required by 5 U.S.C. 552a, OMB Circular E A-130, and DoD -5400.11-R.</P>
        <P>(v) Collect information from OSD Components, and prepare consolidated reports required by 5 U.S.C. 552a and DoD 5400.11-R.</P>
        <P>(b) The Director for Freedom of Information and Security Review shall:</P>

        <P>(1) Forward requests for information or access to records to the appropriate <PRTPAGE P="863"/>OSD Component having primary responsibility for any pertinent system of records under 5 U.S.C. 552a, or to OSD Components, under the Freedom of Information Act, as amended.</P>
        <P>(2) Maintain deadlines to ensure that responses are made within the time limits prescribed in DoD 5400.7-R,<SU>3</SU>
          <FTREF/> DoD Instruction 5400.10,<SU>4</SU>
          <FTREF/> and this part.</P>
        <FTNT>
          <P>
            <SU>3</SU> See footnote 2 to § 311.1.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>4</SU> See footnote 2 to § 311.1.</P>
        </FTNT>
        <P>(3) Collect fees charged and assessed for reproducing requested materials.</P>
        <P>(4) Refer all matters about amendments of records and general and specific exemptions under the 5 U.S.C. 552a to the proper OSD Components.</P>
        <P>(c) The General Counsel of the Department of Defense shall:</P>
        <P>(1) Coordinate all OSD final denials of appeals for amending records, and review actions to confirm denial of access to records, as appropriate.</P>
        <P>(2) Provide advice and assistance to the DA&amp;M, OSD in the discharge of appellate and review responsibilities, and to the DFOISR on all access matters.</P>
        <P>(3) Provide advice and assistance to OSD Components on legal matters pertaining to the Privacy Act of 1974.</P>
        <P>(d) The Heads of the OSD Components shall:</P>
        <P>(1) Designate an individual as the point of contact for Privacy Act matters; designate an official to deny initial requests for access to an individual's records or changes to records; and advise both DA&amp;M, OSD and DFOISR of names of officials so designated.</P>
        <P>(2) Report any new record system, or changes to an existing system, to the Chief, Directives and Records Division, WHS, at least 90 days before the intended use of the system.</P>
        <P>(3) Review all contracts that provide for maintaining records systems, by or on behalf of his or her office, to ensure within his or her authority, that language is included that provides that such systems shall be maintained in a manner consistent with 5 U.S.C. 552a.</P>
        <P>(4) Revise procurement guidance to ensure that any contract providing for the maintenance of a records system, by or on behalf of his or her office, includes language that ensures that such system shall be maintained in accordance with 5 U.S.C. 552a.</P>
        <P>(5) Revise computer and telecommunications procurement policies to ensure that agencies review all proposed contracts for equipment and services to comply with 5 U.S.C. 552a.</P>
        <P>(6) Coordinate with Automatic Data Processing (ADP) and word processing managers providing services to ensure that an adequate risk analysis is conducted to comply with DoD 5400.11-R.</P>
        <P>(7) Review all Directives that require forms or other methods used to collect information about individuals to ensure that they are in compliance with 5 U.S.C. 552a.</P>
        <P>(8) Establish administrative systems in OSD Component organizations to comply with the procedures listed in this part and DoD 5400.11-R.</P>
        <P>(9) Coordinate with the GC, DoD on all proposed denials of access to records.</P>
        <P>(10) Provide justification to the DFOISR when access to a record is denied in whole or in part.</P>
        <P>(11) Provide the record to the DFOISR when the initial denial of a request for access to such record has been appealed by the requester, or at the time of initial denial when appeal seems likely.</P>
        <P>(12) Maintain an accurate account of the actions resulting in a denial for access to a record or for the correction of a record. This account should be maintained so that it can be readily certified as the complete record of proceedings if litigation occurs.</P>
        <P>(13) Ensure that all personnel who either have access to the system of records, or who are engaged in developing or supervising procedures for handling records in the system, are aware of their responsibilities for protecting personal information as established in the Privacy Act and DoD 5400.11-R.</P>
        <P>(14) Forward all requests for access to records received directly from an individual to the DFOISR for appropriate suspense control and recording.</P>
        <P>(15) Provide DFOISR with a copy of the requested record when the request is granted.</P>
        <P>(e) The requester who desires to submit a request is responsible for:</P>

        <P>(1) Determining whether to submit the request in writing or in person. A requester who seeks access to records <PRTPAGE P="864"/>pertaining to himself or herself which are filed by his or her name or personal identifier:</P>
        <P>(i) May make such a request in person to the custodian of the records. If the requester is not satisfied with the response, however, in order to invoke any provision of 5 U.S.C. 552a, DoD 5400.11-R, or this part, the requester must file a request in writing as provided in § 311.6(b)(10). The requester must provide proof of identify by showing drivers license or similar credentials.</P>
        <P>(ii) Describing the record sought, and providing sufficient information to enable the material to be located (e.g., identification of system of records, approximate date it was initiated, originating organization, and type of document).</P>
        <P>(iii) Complying with procedures provided in DoD 5400.11-R for inspecting and/or obtaining copies of requested records.</P>
        <P>(iv) Submitting  a written request to amend the record to the system manager or to the office designated in the system notice.</P>
        <CITA>[64 FR 22785, Apr. 28, 1999, as amended at 66 FR 41780, Aug. 9, 2001]</CITA>
      </SECTION>
      <SECTION>
        <SECTNO>§ 311.6</SECTNO>
        <SUBJECT>Procedures.</SUBJECT>
        <P>(a) <E T="03">Publication of notice in the Federal Register.</E> (1) A notice shall be published in the <E T="04">Federal Register</E> of any record system meeting the definition of a system of records in DoD 5400.11-R.</P>
        <P>(2) Regarding new or revised records systems, each OSD Component shall provide the Chief, Directives and Records Division with 90 days advance notice of any anticipated new or revised system of records. This material shall be submitted to the OMB and to Congress at least 60 days before use and to the Federal Register at least 30 days before being put into use, to provide an opportunity for interested persons to submit written data, views, or arguments to the OSD Components. Instructions on content and preparation are outlined in DoD 5400.11-R.</P>
        <P>(b) <E T="03">Access to information on records systems.</E> (1) Upon request,  and as provided by the Privacy Act, records shall be disclosed only to the individual they pertain to and under whose individual name or identifier they are filed, unless exempted by provisions stated in DoD 5400.11-R.</P>
        <P>(2) There is not requirement under 5 U.S.C. 552a that a record be created or that an individual be given access to records that are not in a group of records that meet this definition of a system of records in 5 U.S.C. 552a.</P>
        <P>(3) Granting access to a record containing personal information shall not be conditioned upon any requirement that the individual state a reason or otherwise justify the need to gain access.</P>
        <P>(4) No verification of identity shall be required of an individual seeking access to records that are otherwise available to the public.</P>
        <P>(5) Individuals shall not be denied access to a record in a system of records about themselves because those records are exempted from disclosure under DoD 5400.7-R. Individuals may only be denied access to a record in a system of records about themselves when those records are exempted from the access provisions of the Privacy Act under DoD 5400.11-R, Chapter 5.</P>
        <P>(6) Individuals shall not be denied access to their records for refusing to disclose their Social Security Numbers (SSNs), unless disclosure of the SSN is required by statute, by regulation adopted before January 1, 1975, or if the record's filing identifier and only means of retrieval is by SSN.</P>
        <P>(7) Individuals may request access to their records, in person or by mail, in accordance with the procedures outlined in paragraph (b)(8) of this section.</P>

        <P>(8) Information necessary to identify a record is: the individual's name, date of birth, place of birth, identification of the records system  as listed in the <E T="04">Federal Register</E>, or sufficient information to identify the type of records being sought, and the approximate date the records might have been created. Any individual making a request for access to records in person shall come to the Directorate for Freedom of Information and Security Review (DFOISR), Room 2C757, Pentagon, Washington, DC 20301-1155; and shall provide personal identification acceptable to the Director, DFOISR, to verify the individual's identity (e.g., driver's license, other licenses, permits, or <PRTPAGE P="865"/>passes used for routine identification purposes).</P>
        <P>(9) If an individual wishes to be accompanied by a third party when seeking access to records or wishes to have the record released directly to a third party, the individual may be required to furnish a signed access authorization granting the third party access.</P>
        <P>(10) Any individual submitting a request by mail for access to information shall address such request to the Directorate for Freedom of Information and Security Review, Pentagon,  Room 2C757, Washington, DC 20301-1155. To verify the identity of the individual, the request shall include either a signed notarized statement or an unsworn declaration in the format specified by 28 U.S.C. 1746.</P>
        <P>(11) The following procedures shall apply to requests for access to records or information complied for law enforcement purposes:</P>
        <P>(i) Individuals requesting access to records or information about themselves and complied for law enforcement purposes are processed under DoD 5400.11-R and DoD 5400.7-R to give them the greater degree of access.</P>
        <P>(ii) Individual requests for access to records or information about themselves and compiled for law enforcement purposes (and in the custody of law enforcement activities) that have been incorporated into the records system, exempted from the access provisions of 5 U.S.C. 552a, will be processed in accordance with subsection C1.5.13 and Chapter 5, DoD 5400.7-R. Individuals shall not be denied access to records solely because they are in the exempt system, but they will have the same access that they would receive under DoD 5400.7-R. (Also see subsection A.10., Chapter 3, DoD 5400.11-R).)</P>
        <P>(iii) Requests by the individuals for access to records or information about themselves and compiled for law enforcement purposes that are in records systems exempted from access provisions will be processed under subsection C.1., Chapter 5 of DoD 5400.11-R or DoD 5400.7-R, depending upon which regulation gives the greater degree of access. (See also subsection A. 10., Chapter 3, DoD 5400.1-R)</P>
        <P>(iv) Individual requests for access to records or information about themselves and complied for law enforcement purposes exempted from access under Section B, Chapter 5 of DoD 54.11-R, that are temporarily in the hands of a non-law enforcement element for adjudicative or personnal actions, shall be referred to the originating agency. The requester will be informed in writing of these referrals.</P>
        <P>(12) The following procedures shall apply to requests for illegible, incomplete, or partially exempt records:</P>
        <P>(i) An individual shall not be denied access to a record or a copy of a record solely because the physical condition or format of the record does not make it readily available (e.g., deteriorated state or on magnetic tape). The document will be prepared as an extract, or it will be exactly recopied.</P>
        <P>(ii) If a portion of the record contains information that is exempt from access, an extract or summary containing all of the information in the record that is releasable shall be prepared.</P>
        <P>(iii) When the physical condition to the record makes it necessary to prepare an extract for release, the extract shall be prepared so that the requester will understand it.</P>
        <P>(iv) The requester shall be informed of all deletions or changes to records.</P>
        <P>(13) Medical records shall be disclosed to the individual they pertain to, unless a determination is made in consultation with a medical doctor, that the disclosure could have adverse effects on the individual's physical or mental health. Such information may be transmitted to a medical doctor named by the individual concerned. If the named medical doctor declines to provide the record to the individual, the OSD Components shall take positive action to ensure that the requested records are provided the individual.</P>
        <P>(14) The individual may be charged reproduction fees for copies or records as outlined in DoD 5400.11-R.</P>
        <P>(c) <E T="03">Requested to amend personal information in records systems and disputes</E>. (1) The Head of an OSD Component, or the designated official, shall allow individuals to request amendment to their records to the extent that such <PRTPAGE P="866"/>records are not accurate, relevant, timely, or complete. Requests should be as brief and as simple as possible and should contain, as a minimum, identifying information to locate the record, as description of the items to be amended, and the reason for a change. A request shall not be rejected nor required to be resubmitted unless additional information is essential to process the request. Requesters shall be required to provide verification of their identify as stated in paragraph (b)(8) of this section, to ensure that they are seeking to amend records about themselves, and not, inadvertently or intentially, the records of others.</P>
        <P>(2) The appropriate system manager shall mail a written acknowledgement to an individual's request to amend a record within 10 days after receipt, excluding Saturdays, Sundays, and legal public holidays. Such acknowledgement shall identify the request and may, if necessary, request any additional information needed to make a determination. No acknowledgment is necessary if the request can be reviewed, processed, and if the individual can be notified of compliance or denial within the 10-day period. Whenever practical, the decision shall be made within 30 working days. For requests presented in person, written acknowledgment may be provided at the time the request is presented.</P>
        <P>(3) The Head of an OSD Component, or designated official, shall promptly take one of the following actions on requests to amend the records:</P>
        <P>(i) If the OSD Component official agrees with any portion or all of an individual's request, he or she will proceed to amend the records in accordance with existing statutes, requlations, or administrative procedures, and inform the requester of the action taken. The OSD Component official shall also notify all previous holders of the record that the amendment has been made, and shall explain the substance of the correction.</P>
        <P>(ii) If the OSD Component official disagrees with all or any portion of a request, the individual shall be informed promptly of the refusal to amend a record, the reason for the refusal, and the procedure established by OSD for an appeal as outlined in paragraph (c)(6) of this section.</P>
        <P>(iii) If the request for an amendment pertains to a record controlled and maintained by another Federal Agency, the request shall be referred to the appropriate Agency, and the requester advised of this:</P>
        <P>(4) The following procedures shall be used when reviewing records under dispute:</P>
        <P>(i) In response to a request for an amendment to records, officials shall determine whether the requester has adequately supported their claim that the record is inaccurate, irrelevant, untimely, or incomplete.</P>
        <P>(ii) The Head of an OSD Component, or designated official, shall limit the review of a record of those items of information that clearly bear on any determination to amend the records and shall ensure that all those elements are present before determination is made.</P>
        <P>(5) If the Head of an OSD Component, or designated official, after an initial review of a request to amend a record, disagrees with all or any portion of a record, he or she shall:</P>
        <P>(i) Advise the individual of the denial and the reason for it.</P>
        <P>(ii) Inform the individual that he or she may appeal the denial.</P>
        <P>(iii) Describe the procedures for appealing the denial including the name and address of the official to whom the appeal should be directed. The procedures should be as brief and simple as possible.</P>
        <P>(iv) Furnish a copy of the justification of any denial to amend a record to the DA&amp;M, OSD.</P>
        <P>(6) If an individual disagrees with the initial OSD determination, he or she may file an appeal. The request should be sent to the Director of Administration and Management, Office of the Secretary of Defense (DA&amp;M, OSD), 1950 Defense Pentagon, Washington, D.C. 20301-1950, if the record is created and maintained by an OSD Component.</P>
        <P>(7) If, after review, the DA&amp;M, OSD further refuses to amend the record as requested, he shall advise the individual:</P>

        <P>(i) Of the refusal and the reason and authority for the denial.<PRTPAGE P="867"/>
        </P>
        <P>(ii) Of his or her right to file a statement of the reason for disagreeing with the DA&amp;M's decision.</P>
        <P>(iii) Of the procedures for filing a statement of disagreements.</P>
        <P>(iv) That the statement filed shall be made available to anyone the record is dislosed to, together with a brief statement, at the discretion of the OSD Component, summarizing its reasons for refusing to amend the records.</P>
        <P>(v) That prior recipients of copies of disputed records by provided by a copy of any statement of dispute to the extent that an accounting of disclosure is maintained.</P>
        <P>(vi) Of his or her right to seek judicial review of the DA&amp;M's refusal to amend a record.</P>
        <P>(8) If, after the review, the DA&amp;M, OSD, determines that the record should be amended in accordance with the individual's request, the OSD Component shall amend the record, advise the individual, and inform previous recipients where an accounting of disclosure has been maintained.</P>
        <P>(9) All appeals should be processed within 30 days (excluding Saturdays, Sundays, and legal public holidays) after receipt by the proper office. If the DA&amp;M determines that a fair and equitable review cannot be made within that time, the individual shall be informed in writing of the reasons for the delay and of the approximate date the review is expected to be completed.</P>
        <P>(d) <E T="03">Disclosure of disputed information.</E> (1) If the DA&amp;M, OSD, has refused to amend a record and the individual has filed a statement under paragraph (c)(7) of this section, the OSD Component shall clearly annotate the disputed record so that it is apparent to any person to whom the record is disclosed that a statement has been filed. Where feasible, the notation itself shall be integral to the record. Where an accounting of a disclosure has been made, the OSD Component shall advise previous recipients that the record has been disputed and shall provide a copy of the individual's statement.</P>
        <P>(i) This statement shall be maintained to permit ready retrieval whenever the disputed portion of the record is to be disclosed.</P>
        <P>(ii) When information that is the subject of a statement of dispute is subsequently disclosed, the OSD Component's designated official shall note which information is disputed and provide a copy of the individual's statement.</P>
        <P>(2) The OSD Component shall include a brief summary of its reasons for not making a correction when disclosing disputed information. Such statement shall normally be limited to the reasons given to the individual for not amending the record.</P>
        <P>(3) Copies of the OSD Component's summary will be treated as part of the individual's record; however, it will not be subject to the amendment procedure outlined in paragraph (c)(3)(iii) of this section.</P>
        <P>(e) <E T="03">Penalties</E>—(1) <E T="03">Civil action.</E> (i) An individual may file a civil suit against the United States and may recover damages, for:</P>
        <P>(A) Refusal to amend a record.</P>
        <P>(B) Improper denial of the access to a record.</P>
        <P>(C) Failure to maintain an accurate, relevant, timely, and complete record that is used to make determinations adverse to the individual.</P>
        <P>(ii) An individual may also file a suit against the United States for failure to implement a provision of the Privacy Act when such failure leads to an adverse determination.</P>
        <P>(iii) If the individual's suit is upheld, the court may direct the United States to pay the court costs and attorney's fees.</P>
        <P>(2) <E T="03">Criminal action.</E> (i) Criminal penalties may be imposed against an OSD officer or employee for certain offenses listed in section (i) of the Privacy Act, as follows: willful unauthorized disclosure of protected information in the records; failure to publish a notice of the existence of a record system in the <E T="04">Federal Register</E>; requesting or gaining access to the individual's record under false pretenses.</P>
        <P>(ii) An OSD officer or employee may be fine up to $5,000 for a violation as outlined in paragraph (e)(2)(i) of this section.</P>
        <P>(3) <E T="03">Litigation status sheet.</E> Whenever a complaint citing 5 U.S.C. 552a is filed in a U.S. District Court against the Department of Defense, a DoD component, or any DoD employee, the responsible system manager shall promptly <PRTPAGE P="868"/>notify the Defense Privacy Office. The litigation status sheet in DoD 5400.II-R provides a standard format for this notification. (The initial litigation status sheet shall, as a minimum, provide the information required by items 1. through 6.) A revised litigation status sheet shall be provided at each stage of the litigation. When a court renders a formal opinion or judgment, copies of the judgment or opinion shall be provided to the Defense Privacy Office with the litigation status sheet reporting that judgment or opinion.</P>
        <P>(f) <E T="03">Computer matching programs.</E> Paragraph B of Chapter 11 of DoD 5400.11-R prescribes that all requests for participation in a matching program (either as a matching agency or a source agency) be submitted to the Defense Privacy Office for review and compliance. OSD Components shall submit these request through the Directives and Records Division.</P>
        <CITA>[64 FR 22785, Apr. 28, 1999; 64 FR 27694, May 21, 1999]</CITA>
      </SECTION>
      <SECTION>
        <SECTNO>§ 311.7</SECTNO>
        <SUBJECT>Information requirements.</SUBJECT>
        <P>The Defense Privacy Office shall establish requirements and deadlines for DoD privacy reports. These reports shall be licensed in accordance with DoD Directive 8910.1.<SU>5</SU>
          <FTREF/>
          
        </P>
        <FTNT>
          <P>
            <SU>5</SU> See footnote 2 to § 311.1.</P>
        </FTNT>
      </SECTION>
      <SECTION>
        <SECTNO>§ 311.8</SECTNO>
        <SUBJECT>Procedures for exemptions.</SUBJECT>
        <P>(a) <E T="03">General information.</E> The Secretary of Defense designates those Office of the Secretary of Defense (OSD) systems of records which will be exempt from certain provisions of the Privacy Act. There are two types of exemptions, general and specific. The general exemption authorizes the exemption of a system of records from all but a few requirements of the Act. The specific exemption authorizes exemption of a system of records or portion thereof, from only a few specific requirements. If an OSD Component originates a new system of records for which it proposes an exemption, or if it proposes an additional or new exemption for an existing system of records, it shall submit the recommended exemption with the records system notice as outlined in § 311.6. No exemption of a system of records shall be considered automatic for all records in the system. The systems manager shall review each requested record and apply the exemptions only when this will serve significant and legitimate Government purpose.</P>
        <P>(b) <E T="03">General exemptions.</E> The general exemption provided by 5 U.S.C. 552a(j)(2) may be invoked for protection of systems of records maintained by law enforcement activities. Certain functional records of such activities are not subject to access provisions of the Privacy Act of 1974. Records identifying criminal offenders and alleged offenders consisting of identifying data and notations of arrests, the type and disposition of criminal charges, sentencing, confinement, release, parole, and probation status of individuals are protected from disclosure. Other records and reports compiled during criminal investigations, as well as any other records developed at any stage of the criminal law enforcement process from arrest to indictment through the final release from parole supervision are excluded from release.</P>
        <P>(1) <E T="03">System identifier and name:</E> DWHS P42.0, DPS Incident Reporting and Investigations Case Files.</P>
        <P>(i) <E T="03">Exemption.</E> Portions of this system that fall within 5 U.S.C. 552a(j)(2) are exempt from the following provisions of 5 U.S.C. 552a, Sections (c) (3) and (4); (d)(1) through (d)(5); (e)(1) through (e)(3); (e)(5); (f)(1) through (f)(5); (g)(1) through (g)(5); and (h) of the Act.</P>
        <P>(ii) <E T="03">Authority:</E> 5 U.S.C. 552a(j)(2).</P>
        <P>(iii) <E T="03">Reason:</E> The Defense Protective Service is the law enforcement body for the jurisdiction of the Pentagon and immediate environs. The nature of certain records created and maintained by the DPS requires exemption from access provisions of the Privacy Act of 1974. The general exemption, 5 U.S.C. 552a(j)(2), is invoked to protect ongoing investigations and to protect from access criminal investigation information contained in this record system, so as not to jeopardize any subsequent judicial or administrative process taken as a result of information contained in the file.</P>
        <P>(2) <E T="03">System identifier and name:</E> JS006.CND, Department of Defense Counternarcotics C4I System.<PRTPAGE P="869"/>
        </P>
        <P>(i) Exemption: Portions of this system that fall within 5 U.S.C. 552a(j)(2) are exempt from the following provisions of 5 U.S.C. 552a, section (c) (3) and (4); (d)(1) through (d)(5); (e)(1) through (e)(3); (e)(4)(G) and (e)(4)(H); (e)(5); (f)(1) through (f)(5); (g)(1) through (g)(5) of the Act.</P>
        <P>(ii) Authority: 5 U.S.C. 552a(j)(2).</P>
        <P>(iii) Reason: From subsection (c)(3) because the release of accounting of disclosure would inform a subject that he or she is under investigation. This information would provide considerable advantage to the subject in providing him or her with knowledge concerning the nature of the investigation and the coordinated investigative efforts and techniques employed by the cooperating agencies. This would greatly impede USSOUTHCOM's criminal law enforcement.</P>
        <P>(iv) For subsections (c)(4) and (d) because notification would alert a subject to the fact that an investigation of that individual is taking place, and might weaken the on-going investigation, reveal investigatory techniques, and place confidential informants in jeopardy.</P>
        <P>(v) From subsections (e)(4) (G) and (H) because this system of records is exempt from the access provisions of subsection (d) pursuant to subsection (j).</P>
        <P>(vi) From subsection (f) because the agency's rules are inapplicable to those portions of the system that are exempt and would place the burden on the agency of either confirming or denying the existence of a record pertaining to a requesting individual might in itself provide an answer to that individual relating to an on-going criminal investigation. The conduct of a successful investigation leading to the indictment of a criminal offender precludes the applicability of established agency rules relating to verification of record, disclosure of the record to that individual, and record amendment procedures for this record system.</P>
        <P>(vii) For compatibility with the exemption claimed from subsection (f), the civil remedies provisions of subsection (g) must be suspended for this record system. Because of the nature of criminal investigations, standards of accuracy, relevance, timeliness and completeness cannot apply to this record system. Information gathered in criminal investigations is often fragmentary and leads relating to an individual in the context of one investigation may instead pertain to a second investigation.</P>
        <P>(viii) From subsection (e)(1) because the nature of the criminal investigative function creates unique problems in prescribing a specific parameter in a particular case with respect to what information is relevant or necessary. Also, due to USSOUTHCOM's close liaison and working relationships with the other Federal, as well as state, local and foreign country law enforcement agencies, information may be received which may relate to a case under the investigative jurisdiction of another agency. The maintenance of this information may be necessary to provide leads for appropriate law enforcement purposes and to establish patterns of activity which may relate to the jurisdiction of other cooperating agencies.</P>
        <P>(ix) From subsection (e)(2) because collecting information to the greatest extent possible directly from the subject individual may or may not be practicable in a criminal investigation. The individual may choose not to provide information and the law enforcement process will rely upon significant information about the subject from witnesses and informants.</P>
        <P>(x) From subsection (e)(3) because supplying an individual with a form containing a Privacy Act Statement would tend to inhibit cooperation by many individuals involved in a criminal investigation. The effect would be somewhat inimical to established investigative methods and techniques.</P>

        <P>(xi) From subsection (e)(5) because the requirement that records be maintained with attention to accuracy, relevance, timeliness, and completeness would unfairly hamper the criminal investigative process. It is the nature of criminal law enforcement for investigations to uncover the commission of illegal acts at diverse stages. It is frequently impossible to determine initially what information is accurate, relevant, timely, and least of all complete. With the passage of time, seemingly irrelevant or untimely information may acquire new significant as <PRTPAGE P="870"/>further investigation brings new details to light.</P>
        <P>(xii) From subsection (e)(8) because the notice requirements of this provision could present a serious impediment to criminal law enforcement by revealing investigative techniques, procedures, and existence of confidential investigations.</P>
        <P>(c) <E T="03">Specific exemptions.</E> All systems of records maintained by any OSD Component shall be exempt from the requirements of 5 U.S.C. 552a(d) pursuant to subsection (k)(1) of that section to the extent that the system contains any information properly classified under Executive Order 11265, ‘National Security Information,' dated June 28, 552a(d) pursuant to subsection (k)(1) of that section to the extent that the system contains any information properly classified under E.O. 11265, ‘National Security Information,' dated June 28, 1979, as amended, and required by the Executive Order to be kept classified in the interest of national defense or foreign policy. This exemption, which may be applicable to parts of all systems of records, is necessary because certain record systems not otherwise specifically designated for exemptions may contain isolated information which has been properly classified. The Secretary of Defense has designated the following OSD system of records described below specifically exempted from the appropriate provisions of the Privacy Act pursuant to the designated authority contained therein:</P>
        <P>(1) <E T="03">System identifier and name:</E> DGC 16, Political Appointment Vetting Files.</P>
        <P>(i) <E T="03">Exemption.</E> Portions of this system of records that fall within the provisions of 5 U.S.C. 552a(k)(5) may be exempt from the following subsections (d)(1) through (d)(5).</P>
        <P>(ii) <E T="03">Authority.</E> 5 U.S.C. 552a(k)(5).</P>
        <P>(iii) <E T="03">Reasons.</E> From (d)(1) through (d)(5) because the agency is required to protect the confidentiality of sources who furnished information to the Government under an expressed promise of confidentiality or, prior to September 27, 1975, under an implied promise that the identity of the source would be held in confidence. This confidentiality is needed to maintain the Government's continued access to information from persons who otherwise might refuse to give it. This exemption is limited to disclosures that would reveal the identity of a confidential source.</P>
        <P>(2) <E T="03">System identifier and name:</E> DWHS P28, The Office of the Secretary of Defense Clearance File.</P>
        <P>(i) <E T="03">Exemption.</E> This system of records is exempt from subsections (c)(3) and (d) of 5 U.S.C. 552a, which would require the disclosure of investigatory material compiled solely for the purpose of determining access to classified information but only to the extent that disclosure of such material would reveal the identity of a source who furnished information to the Government under an expressed promise that the identity of the source would be held in confidence or, prior to September 27, 1975, under an implied promise that the identity of the source would be held in confidence. A determination will be made at the time of the request for a record concerning the specific information which would reveal the identity of the source.</P>
        <P>(ii) <E T="03">Authority.</E> 5 U.S.C. 552a(k)(5).</P>
        <P>(iii) <E T="03">Reasons.</E> This exemption is required to protect the confidentiality of the sources of information compiled for the purpose of determining access to classified information. This confidentiality helps maintain the Government's continued access to information from persons who would otherwise refuse to give it.</P>
        <P>(3) <E T="03">System identifier and name:</E> DGC 04, Industrial Personnel Security Clearance Case Files.</P>
        <P>(i) <E T="03">Exemption.</E> All portions of this system which fall under 5 U.S.C. 552a(k)(5) are exempt from the following provisions of Title 5 U.S.C. 552a: (c)(3); (d).</P>
        <P>(ii) <E T="03">Authority.</E> 5 U.S.C. 552a(k)(5).</P>
        <P>(iii) <E T="03">Reasons.</E> This system of records is exempt from subsections (c)(3) and (d) of section 552a of 5 U.S.C. which would require the disclosure of investigatory material compiled solely for the purpose of determining access to classified information, but only to the extent that the disclosure of such material would reveal the identity of a source who furnished information to the Government under an expressed promise that the identity of the source would be held in confidence, or prior to September 27, 1975, under an implied <PRTPAGE P="871"/>promise that the identity of the source would be held in confidence. A determination will be made at the time of the request for a record concerning whether specific information would reveal the identity of a source. This exemption is required in order to protect the confidentiality of the sources of information compiled for the purpose of determining access to classified information. This confidentiality helps maintain the Government's continued access to information from persons who would otherwise refuse to give it.</P>
        <P>(4) <E T="03">System identifier and name:</E> DWHS P32, Standards of Conduct Inquiry File.</P>
        <P>(i) <E T="03">Exemption.</E> This system of records is exempted from subsections (c)(3) and (d) of 5 U.S.C. 552a, which would require the disclosure of: Investigatory material compiled for law enforcement purposes; or investigatory material compiled solely for the purpose of determining suitability, eligibility, or qualifications for Federal civilian employment, military service, or Federal contracts, but only to the extent that the disclosure of such material would reveal the identity of a source who furnished information to the Government under an express promise or, prior to September 27, 1975, under an implied promise that the identity of the source would be held in confidence. If any individual is denied any right, privilege, or benefit that he would otherwise be entitled by Federal law, or otherwise be eligible, as a result of the maintenance of investigatory material compiled for law enforcement purposes, the material shall be provided to that individual, except to the extent that its disclosure would reveal the identity of a source who furnished information to the Government under an express promise or, prior to September 27, 1975, under an implied promise that the identity of the source would be held in confidence. At the time of the request for a record, a determination will be made concerning whether a right, privilege, or benefit is denied or specific information would reveal the identity of a source.</P>
        <P>(ii) <E T="03">Authority.</E> 5 U.S.C. 552a(k) (2) and (5).</P>
        <P>(iii) <E T="03">Reasons.</E> These exemptions are necessary to protect the confidentiality of the records compiled for the purpose of: enforcement of the conflict of interest statutes by the Department of Defense Standards of Conduct Counselor, General Counsel, or their designees; and determining suitability, eligibility or qualifications for Federal civilian employment, military service, or Federal contracts of those alleged to have violated or caused others to violate the Standards of Conduct regulations of the Department of Defense.</P>
        <P>(5) <E T="03">System identifier and name:</E> DUSDP 02, Special Personnel Security Cases.</P>
        <P>(i) <E T="03">Exemption:</E> All portions of this system which fall under 5 U.S.C. 552a(k)(5) are exempt from the following provisions of 5 U.S.C. 552a: (c)(3); (d).</P>
        <P>(ii) <E T="03">Authority:</E> 5 U.S.C. 552a(k)(5).</P>
        <P>(iii) <E T="03">Reasons:</E> This system of records is exempt from subsections (c)(3) and (d) of 5 U.S.C. 552a which would require the disclosure of investigatory material compiled solely for the purpose of determining access to classified information, but only to the extent that the disclosure of such material would reveal the identity of a source who furnished information to the Government under an expressed promise that the identity of the source would be held in confidence or, prior to September 27, 1975, under an implied promise that the identity of the source would be held in confidence. A determination will be made at the time of the request for a record concerning whether specific information would reveal the identity of a source. This exemption is required in order to protect the confidentiality of the sources of information compiled for the purpose of determining access to classified information. This confidentiality helps maintain the Government's continued access to information from persons who would otherwise refuse to give it.</P>
        <P>(6) <E T="03">System identifier and name:</E> DODDS 02.0, Educator Application Files.</P>
        <P>(i) <E T="03">Exemption.</E> All portions of this system which fall within 5 U.S.C. 552a(k)(5) may be exempt from the following provisions of 5 U.S.C. 552a: (c)(3); (d).</P>
        <P>(ii) <E T="03">Authority.</E> 5 U.S.C. 552a(k)(5).</P>
        <P>(iii) <E T="03">Reasons.</E> It is imperative that the confidential nature of evaluation and investigatory material on teacher application files furnished the Department of Defense Dependent Schools <PRTPAGE P="872"/>(DoDDS) under promises of confidentiality be exempt from disclosure to the individual to insure the candid presentation of information necessary to make determinations involving applicants suitability for DoDDS teaching positions.</P>
        <P>(7) System identifier and name: DGC 20, DoD Presidential Appointee Vetting File.</P>
        <P>(i) Exemption: Investigatory material compiled solely for the purpose of determining suitability, eligibility, or qualifications for federal civilian employment, military service, federal contracts, or access to classified information may be exempt pursuant to 5 U.S.C. 552a(k)(5), but only to the extent that such material would reveal the identity of a confidential source. Portions of this system of records that may be exempt pursuant to 5 U.S.C. 552a(k)(5) are subsections (d)(1) through (d)(5).</P>
        <P>(ii) Authority: 5 U.S.C. 552a(k)(5).</P>
        <P>(iii) Reason: From (d)(1) through (d)(5) because the agency is required to protect the confidentiality of sources who furnished information to the government under an expressed promise of confidentiality or, prior to September 27, 1975, under an implied promise that the identity of the source would be held in confidence. This confidentiality is needed to maintain the Government's continued access to information from persons who otherwise might refuse to give it.</P>
        <P>(8) <E T="03">System identifier and name:</E> DWHS P29, Personnel Security Adjudications File.</P>
        <P>(i) <E T="03">Exemption:</E> Portions of this system of records that fall within the provisions of 5 U.S.C. 552a(k)(5) may be exempt from the following subsections (d)(1) through (d)(5).</P>
        <P>(ii) <E T="03">Authority:</E> 5 U.S.C. 552a(k)(5).</P>
        <P>(iii) <E T="03">Reasons.</E> From (d)(1) through (d)(5) because the agency is required to protect the confidentiality of sources who furnished information to the Government under an expressed promise of confidentiality or, prior to September 27, 1975, under an implied promise that the identity of the source would be held in confidence. This confidentiality is needed to maintain the Government's continued access to information from persons who otherwise might refuse to give it. This exemption is limited to disclosures that would reveal the identity of a confidential source. At the time of the request for a record, a determination will be made concerning whether a right, privilege, or benefit is denied or specific information would reveal the identity of a source.</P>
        <P>(9) <E T="03">System identifier and name:</E> JS004SECDIV, Joint Staff Security Clearance Files.</P>
        <P>(i) <E T="03">Exemption:</E> Portions of this system of records are exempt pursuant to the provisions of 5 U.S.C. 552a(k)(5) from subsections 5 U.S.C. 552a(d)(1) through (d)(5).</P>
        <P>(ii) <E T="03">Authority:</E> 5 U.S.C. 552a(k)(5).</P>
        <P>(iii) <E T="03">Reasons:</E> From subsections (d)(1) through (d)(5) because the agency is required to protect the confidentiality of sources who furnished information to the government under an expressed promise of confidentiality or, prior to September 27, 1975, under an implied promise that the identity of the source would be held in confidence. This confidentiality is needed to maintain the Government's continued access to information from persons who otherwise might refuse to give it. This exemption is limited to disclosures that would reveal the identity of a confidential source. At the time of the request for a record, a determination will be made concerning whether a right, privilege, or benefit is denied or specific information would reveal the identity of a source.</P>
        <P>(10) <E T="03">System identifier and name:</E> DFMP 26, Vietnamese Commando Compensation Files.</P>
        <P>(i) <E T="03">Exemption:</E> Information classified under E.O. 12958, as implemented by DoD 5200.1-R, may be exempt pursuant to 5 U.S.C. 552a(k)(1).</P>
        <P>(ii) <E T="03">Authority:</E> 5 U.S.C. 552a(k)(1).</P>
        <P>(iii) <E T="03">Reasons:</E> From subsection 5 U.S.C. 552a(d) because granting access to information that is properly classified pursuant to E.O. 12958, as implemented by DoD 5200.1-R, may cause damage to the national security.</P>
        <P>(11) <E T="03">System identifier and name:</E> DUSP 11, POW/Missing Personnel Office Files.</P>
        <P>(i) <E T="03">Exemption:</E> Information classified under E.O. 12958, as implemented by DoD 5200.1-R, may be exempt pursuant to 5 U.S.C. 552a(k)(1).<PRTPAGE P="873"/>
        </P>
        <P>(ii) <E T="03">Authority:</E> 5 U.S.C. 552a(k)(1).</P>
        <P>(iii) <E T="03">Reasons:</E> From subsection 5 U.S.C. 552a(d) because granting access to information that is properly classified pursuant to E.O. 12958, as implemented by DoD 5200.1-R, may cause damage to the national security.</P>
        <CITA>[65 FR 53168, Sept. 1, 2000, as amended at 66 FR 41780, Aug. 8, 2001]</CITA>
      </SECTION>
    </PART>
    <PART>
      <EAR>Pt. 312</EAR>
      <HD SOURCE="HED">PART 312—OFFICE OF THE INSPECTOR GENERAL (OIG) PRIVACY PROGRAM</HD>
      <CONTENTS>
        <SECHD>Sec.</SECHD>
        <SECTNO>312.1</SECTNO>
        <SUBJECT>Purpose.</SUBJECT>
        <SECTNO>312.2</SECTNO>
        <SUBJECT>Definitions.</SUBJECT>
        <SECTNO>312.3</SECTNO>
        <SUBJECT>Procedure for requesting information.</SUBJECT>
        <SECTNO>312.4</SECTNO>
        <SUBJECT>Requirements for identification.</SUBJECT>
        <SECTNO>312.5</SECTNO>
        <SUBJECT>Access by subject individuals.</SUBJECT>
        <SECTNO>312.6</SECTNO>
        <SUBJECT>Fees.</SUBJECT>
        <SECTNO>312.7</SECTNO>
        <SUBJECT>Request for correction or amendment.</SUBJECT>
        <SECTNO>312.8</SECTNO>
        <SUBJECT>OIG review of request for amendment.</SUBJECT>
        <SECTNO>312.9</SECTNO>
        <SUBJECT>Appeal of initial amendment decision.</SUBJECT>
        <SECTNO>312.10</SECTNO>
        <SUBJECT>Disclosure of OIG records to other than subject.</SUBJECT>
        <SECTNO>312.11</SECTNO>
        <SUBJECT>Penalties.</SUBJECT>
        <SECTNO>312.12</SECTNO>
        <SUBJECT>Exemptions.</SUBJECT>
        <SECTNO>312.13</SECTNO>
        <SUBJECT>Ownership of OIG investigative records.</SUBJECT>
        <SECTNO>312.14</SECTNO>
        <SUBJECT>Referral of records.</SUBJECT>
      </CONTENTS>
      <AUTH>
        <HD SOURCE="HED">Authority:</HD>
        <P>Pub. L. 93-579, 88 Stat 1896 (5 U.S.C. 552a).</P>
      </AUTH>
      <SOURCE>
        <HD SOURCE="HED">Source:</HD>
        <P>56 FR 51976, Oct. 17, 1991, unless otherwise noted.</P>
      </SOURCE>
      <SECTION>
        <SECTNO>§ 312.1</SECTNO>
        <SUBJECT>Purpose.</SUBJECT>
        <P>Pursuant to the requirements of the Privacy Act of 1974 (5 U.S.C. 552a) and 32 CFR part 286a-DoD Privacy Program, the following rules of procedures are established with respect to access and amendment of records maintained by the Office of the Inspector General (OIG) on individual subjects of these records.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 312.2</SECTNO>
        <SUBJECT>Definitions.</SUBJECT>
        <P>(a) All terms used in this part which are defined in 5 U.S.C. 552a shall have the same meaning herein.</P>
        <P>(b) As used in this part, the term “agency” means the Office of the Inspector General (OIG), Department of Defense.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 312.3</SECTNO>
        <SUBJECT>Procedure for requesting information.</SUBJECT>
        <P>Individuals should submit inquiries regarding all OIG files by mail to the Assistant Inspector General for Investigations, ATTN: FOIA/PA Division, 400 Army Navy Drive, Arlington, VA 22202-2884. All personal visits will require some form of common identification.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 312.4</SECTNO>
        <SUBJECT>Requirements for identification.</SUBJECT>
        <P>Only upon proper identification will any individual be granted access to records which pertain to him/her. Identification is required both for accurate record identification and to avoid disclosing records to unauthorized individuals. Requesters must provide their full name and as much information as possible about the record being sought in order that a proper search for records can be accomplished. Inclusion of a telephone number for the requester is recommended to expedite certain matters. Requesters applying in person must provide an identification with photograph, such as a driver's license, military identification card, building pass, etc.</P>
        <CITA>[59 FR 2746, Jan. 19, 1994]</CITA>
      </SECTION>
      <SECTION>
        <SECTNO>§ 312.5</SECTNO>
        <SUBJECT>Access by subject individuals.</SUBJECT>
        <P>(a) No individual will be allowed access to any information compiled or maintained in reasonable anticipation of civil or criminal actions or proceedings or otherwise exempt under § 312.12. Requests for pending investigations will be denied and the requester instructed to forward another request giving adequate time for the investigation to be completed. Requesters shall be provided the telephone number so they can call and check on the status in order to know when to resubmit the request.</P>
        <P>(b) Any individual may authorize the OIG to provide a copy of his/her records to a third part. This authorization must be in writing, must designate the recipient by name, must specify the records or portion to be provided to the recipient, and should accompany the initial request to the OIG.</P>
        <CITA>[56 FR 51976, Oct. 17, 1991, as amended at 59 FR 2746, Jan. 19, 1994]</CITA>
      </SECTION>
      <SECTION>
        <SECTNO>§ 312.6</SECTNO>
        <SUBJECT>Fees.</SUBJECT>

        <P>Requesters will be charged only for the reproduction of requested documents and special postal methods, such <PRTPAGE P="874"/>as express mail, if applicable. There will be no charge for the first copy of a record provided to any individual. Thereafter, fees will be computed as set forth in appropriate DoD Directives and Regulations.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 312.7</SECTNO>
        <SUBJECT>Request for correction or amendment.</SUBJECT>
        <P>(a) Requests to correct or amend a file shall be addressed to the system manager in which the file is located. The request must reasonably describe the record to be amended, the items to be changed as specifically as possible, the type of amendment (e.g., deletion, correction, amendment), and the reason for amendment. Reasons should address at least one of the following categories: Accuracy, relevance, timeliness, completeness, fairness. The request should also include appropriate evidence which provide a basis for evaluating the request. Normally all documents submitted, to include court orders, should be certified. Amendments under this part are limited to correcting factual matters and not matters of official judgment or opinions, such as performance ratings, promotion potential, and job performance appraisals.</P>
        <P>(b) Requirements of identification as outlined in § 312.4 apply to requests to correct or amend a file.</P>
        <P>(c) Incomplete requests shall not be honored, but the requester shall be contacted for the additional information needed to process the request.</P>
        <P>(d) The amendment process is not intended to permit the alteration of evidence presented in the course of judicial or quasi-judicial proceedings. Any amendments or changes to these records normally are made through the specific procedures established for the amendment of such records.</P>
        <P>(e) Nothing in the amendment process is intended or designed to permit a collateral attack upon what has already been the subject of a judicial or quasi-judicial determination. However, while the individual may not attack the accuracy of the judicial or quasi-judicial determination, he or she may challenge the accuracy of the recording of that action.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 312.8</SECTNO>
        <SUBJECT>OIG review of request for amendment.</SUBJECT>
        <P>(a) A written acknowledgement of the receipt of a request for amendment of a record will be provided to the requester within 10 working days, unless final action regarding approval or denial will constitute acknowledgement.</P>
        <P>(b) Where there is a determination to grant all or a portion of a request to amend a record, the record shall be promptly amended and the requesting individual notified. Individuals, agencies or DoD components shown by disclosure accounting records to have received copies of the record, or to whom disclosure has been made, will be notified of the amendment by the responsible OIG official.</P>
        <P>(c) Where there is a determination to deny all or a portion of a request to amend a record, OIG will promptly advise the requesting individual of the specifics of the refusal and the reasons; and inform the individual that he/she may request a review of the denial(s) from the OIG designated official.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 312.9</SECTNO>
        <SUBJECT>Appeal of initial amendment decision.</SUBJECT>
        <P>(a) All appeals of an initial amendment decision should be addressed to the Assistant Inspector General for Investigations, ATTN: FOIA/PA Division, 400 Army Navy Drive, Arlington, VA 22202-2884. The appeal should be concise and should specify the reasons the requester believes that the initial amendment action by the OIG was not satisfactory. Upon receipt of the appeal, the designated official will review the request and make a determination to approve or deny the appeal.</P>

        <P>(b) If the OIG designated official decides to amend the record, the requester and all previous recipients of the disputed information will be notified of the amendment. If the appeal is denied, the designated official will notify the requester of the reason of the denial, of the requester's right to file a statement of dispute disagreeing with the denial, that such statement of dispute will be retained in the file, that the statement will be provided to all future users of the file, and that the requester may file suit in a federal district court to contest the OIG decision not to amend the record.<PRTPAGE P="875"/>
        </P>
        <P>(c) The OIG designated official will respond to all appeals within 30 working days or will notify the requester of an estimated date of completion if the 30 day limit cannot be met.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 312.10</SECTNO>
        <SUBJECT>Disclosure of OIG records to other than subject.</SUBJECT>
        <P>No record containing personally identifiable information within a OIG system of records shall be disclosed by any means to any person or agency outside the Department of Defense, except with the written consent of the individual subject of the record or as provided for in the Act and DoD 5400.11-R (32 CFR part 286a).</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 312.11</SECTNO>
        <SUBJECT>Penalties.</SUBJECT>
        <P>(a) An individual may bring a civil action against the OIG to correct or amend the record, or where there is a refusal to comply with an individual request or failure to maintain any records with accuracy, relevance, timeliness and completeness, so as to guarantee fairness, or failure to comply with any other provision of the Privacy Act. The court may order correction or amendment of records. The court may enjoin the OIG from withholding the records and order the production of the record.</P>
        <P>(b) Where it is determined that the action was willful or intentional with respect to 5 U.S.C. 552a(g)(1) (C) or (D), the United States shall be liable for the actual damages sustained, but in no case less than the sum of $1,000 and the costs of the action with attorney fees.</P>
        <P>(c) Criminal penalties may be imposed against an officer or employee of the OIG who discloses material, which he/she knows is prohibited from disclosure, or who willfully maintains a system of records without compliance with the notice requirements.</P>
        <P>(d) Criminal penalties may be imposed against any person who knowingly and willfully requests or obtains any record concerning another individual from an agency under false pretenses.</P>
        <P>(e) All of these offenses are misdemeanors with a fine not to exceed $5,000.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 312.12</SECTNO>
        <SUBJECT>Exemptions.</SUBJECT>
        <P>(a) <E T="03">Exemption for classified records.</E> Any record in a system of records maintained by the Office of the Inspector General which falls within the provisions of 5 U.S.C. 552a(k)(1) may be exempt from the following subsections of 5 U.S.C. 552a: (c)(3), (d), (e)(1), (e)(4)(G) through (I) and (f) to the extent that a record system contains any record properly classified under Executive Order 12958 and that the record is required to be kept classified in the interest of national defense or foreign policy. This specific exemption rule, claimed by the Inspector General under authority of 5 U.S.C. 552a(k)(1), is applicable to all systems of records maintained, including those individually designated for an exemption herein as well as those not otherwise specifically designated for an exemption, which may contain isolated items of properly classified information</P>
        <P>(b) The Inspector General of the Department of Defense claims an exemption for the following record systems under the provisions of 5 U.S.C. 552a(j) and (k)(1)-(7) from certain indicated subsections of the Privacy Act of 1974. The exemptions may be invoked and exercised on a case by case basis by the Deputy Assistant Inspector General for Investigations or the Director, Investigative Support Directorate and Freedom of Information Act/Privacy Act Division Chief which serves as the Systems Program Managers. Exemptions will be exercised only when necessary for a specific, significant and legitimate reason connected with the purpose of the records system.</P>
        <P>(c) No personal records releasable under the provisions of The Freedom of Information Act (5 U.S.C. 552) will be withheld from the subject individual based on these exemptions.</P>
        <P>(d) <E T="03">System Identifier:</E> CIG-04</P>
        <P>(1) <E T="03">System name:</E> Case Control System.</P>
        <P>(2) <E T="03">Exemption:</E> Any portion of this system which falls within the provisions of 5 U.S.C. 552a(j)(2) may be exempt from the following subsections of 5 U.S.C. 552a: (c)(3), (c)(4), (d), (e)(1), (e)(2), (e)(3), (e)(4)(G), (H), (I), (e)(5), (e)(8), (f), and (g).</P>
        <P>(3) <E T="03">Authority:</E> 5 U.S.C. 552a(j)(2).<PRTPAGE P="876"/>
        </P>
        <P>(4) <E T="03">Reasons:</E> From subsection (c)(3) because the release of accounting of disclosure would inform a subject that he or she is under investigation. This information would provide considerable advantage to the subject in providing him or her with knowledge concerning the nature of the investigation and the coordinated investigative efforts and techniques employed by the cooperating agencies. This would greatly impede OIG's criminal law enforcement.</P>
        <P>(5) From subsection (c)(4) and (d), because notification would alert a subject to the fact that an open investigation on that individual is taking place, and might weaken the on-going investigation, reveal investigatory techniques, and place confidential informants in jeopardy.</P>
        <P>(6) From subsection (e)(1) because the nature of the criminal and/or civil investigative function creates unique problems in prescribing a specific parameter in a particular case with respect to what information is relevant or necessary. Also, due to OIG's close liaison and working relationships with other Federal, state, local and foreign country law enforcement agencies, information may be received which may relate to a case under the investigative jurisdiction of another agency. The maintenance of this information may be necessary to provide leads for appropriate law enforcement purposes and to establish patterns of activity which may relate to the jurisdiction of other cooperating agencies.</P>
        <P>(7) From subsection (e)(2) because collecting information to the fullest extent possible directly from the subject individual may or may not be practical in a criminal and/or civil investigation.</P>
        <P>(8) From subsection (e)(3) because supplying an individual with a form containing a Privacy Act Statement would tend to inhibit cooperation by many individuals involved in a criminal and/or civil investigation. The effect would be somewhat adverse to established investigative methods and techniques.</P>
        <P>(9) From subsection (e)(4) (G) through (I) because this system of records is exempt from the access provisions of subsection (d).</P>
        <P>(10) From subsection (e)(5) because the requirement that records be maintained with attention to accuracy, relevance, timeliness, and completeness would unfairly hamper the investigative process. It is the nature of law enforcement for investigations to uncover the commission of illegal acts at diverse stages. It is frequently impossible to determine initially what information is accurate, relevant, timely, and least of all complete. With the passage of time, seemingly irrelevant or untimely information may acquire new significance as further investigation brings new details to light.</P>
        <P>(11) From subsection (e)(8) because the notice requirements of this provision could present a serious impediment to law enforcement by revealing investigative techniques, procedures, and existence of confidential investigations.</P>
        <P>(12) From subsection (f) because the agency's rules are inapplicable to those portions of the system that are exempt and would place the burden on the agency of either confirming or denying the existence of a record pertaining to a requesting individual might in itself provide an answer to that individual relating to an on-going investigation. The conduct of a successful investigation leading to the indictment of a criminal offender precludes the applicability of established agency rules relating to verification of record, disclosure of the record to that individual, and record amendment procedures for this record system.</P>
        <P>(13) For comparability with the exemption claimed from subsection (f), the civil remedies provisions of subsection (g) must be suspended for this record system. Because of the nature of criminal investigations, standards of accuracy, relevance, timeliness, and completeness cannot apply to this record system. Information gathered in an investigation is often fragmentary and leads relating to an individual in the context of one investigation may instead pertain to a second investigation.</P>
        <P>(e) <E T="03">System Identification:</E> CIG-06.</P>
        <P>(1) <E T="03">System name:</E> Investigative Files.<PRTPAGE P="877"/>
        </P>
        <P>(2) <E T="03">Exemption:</E> Any portion of this system which falls within the provisions of 5 U.S.C. 552a(j)(2) may be exempt from the following subsections of 5 U.S.C. 552a (c)(3), (c)(4), (d), (e)(1), (e)(2), (e)(3), (e)(4) (G), (H), (I), (e)(5), (e)(8), (f), and (g).</P>
        <P>(3) <E T="03">Authority:</E> 5 U.S.C. 552a(j)(2).</P>
        <P>(4) <E T="03">Reasons:</E> From subsection (c)(3) because the release of accounting of disclosure would inform a subject that he or she is under investigation. This information would provide considerable advantage to the subject in providing him or her with knowledge concerning the nature of the investigation and the coordinated investigative efforts and techniques employed by the cooperating agencies. This would greatly impede OIG's criminal law enforcement.</P>
        <P>(5) From subsection (c)(4) and (d), because notification would alert a subject to the fact that an open investigation on that individual is taking place, and might weaken the on-going investigation, reveal investigatory techniques, and place confidential informants in jeopardy.</P>
        <P>(6) From subsection (e)(1) because the nature of the criminal and/or civil investigative function creates unique problems in prescribing a specific parameter in a particular case with respect to what information is relevant or necessary. Also, due to OIG's close liaison and working relationships with other Federal, state, local and foreign country law enforcement agencies, information may be received which may relate to a case under the investigative jurisdiction of another agency. The maintenance of this information may be necessary to provide leads for appropriate law enforcement purposes and to establish patterns of activity which may relate to the jurisdiction of other cooperating agencies.</P>
        <P>(7) From subsection (e)(2) because collecting information to the fullest extent possible directly from the subject individual may or may not be practical in a criminal and/or civil investigation.</P>
        <P>(8) From subsection (e)(3) because supplying an individual with a form containing a Privacy Act Statement would tend to inhibit cooperation by many individuals involved in a criminal and/or civil investigation. The effect would be somewhat adverse to established investigative methods and techniques.</P>
        <P>(9) From subsection (e)(4) (G) through (I) because this system of records is exempt from the access provisions of subsection (d).</P>
        <P>(10) From subsection (e)(5) because the requirement that records be maintained with attention to accuracy, relevance, timeliness, and completeness would unfairly hamper the investigative process. It is the nature of law enforcement for investigations to uncover the commission of illegal acts at diverse stages. It is frequently impossible to determine initially what information is accurate, relevant, timely, and least of all complete. With the passage of time, seemingly irrelevant or untimely information may acquire new significance as further investigation brings new details to light.</P>
        <P>(11) From subsection (e)(8) because the notice requirements of this provision could present a serious impediment to law enforcement by revealing investigative techniques, procedures, and existence of confidential investigations.</P>
        <P>(12) From subsection (f) because the agency's rules are inapplicable to those portions of the system that are exempt and would place the burden on the agency of either confirming or denying the existence of a record pertaining to a requesting individual might in itself provide an answer to that individual relating to an on-going investigation. The conduct of a successful investigation leading to the indictment of a criminal offender precludes the applicability of established agency rules relating to verification of record, disclosure of the record to that individual, and record amendment procedures for this record system.</P>

        <P>(13) For comparability with the exemption claimed from subsection (f), the civil remedies provisions of subsection (g) must be suspended for this record system. Because of the nature of criminal investigations, standards of accuracy, relevance, timeliness, and completeness cannot apply to this record system. Information gathered in an investigation is often fragmentary and leads relating to an individual in <PRTPAGE P="878"/>the context of one investigation may instead pertain to a second investigation.</P>
        <P>(f) <E T="03">System identifier:</E> CIG-15.</P>
        <P>(1) <E T="03">System name:</E> Departmental Inquiries Case System.</P>
        <P>(2) <E T="03">Exemption:</E> Investigatory material compiled for law enforcement purposes may be exempt pursuant to 5 U.S.C. 552a(k)(2). However, if an individual is denied any right, privilege, or benefit for which he would otherwise be entitled by Federal law or for which he would otherwise be eligible, as a result of the maintenance of such information, the individual will be provided access to such information except to the extent that disclosure would reveal the identity of a confidential source. Any portions of this system which fall under the provisions of 5 U.S.C. 552a(k)(2) may be exempt from the following subsection of 5 U.S.C. 552a(c)(3), (d), (e)(1), (e)(4)(G), (H), and (I).</P>
        <P>(3) <E T="03">Authority:</E> 5 U.S.C. 552a(k)(2).</P>
        <P>(4) <E T="03">Reasons:</E> From subsection (c)(3) because disclosures from this system could interfere with the just, thorough and timely resolution of the compliant or inquiry, and possibly enable individuals to conceal their wrongdoing or mislead the course of the investigation by concealing, destroying or fabricating evidence or documents.</P>
        <P>(5) From subsection (d) because disclosures from this system could interfere with the just thorough and timely resolution of the compliant or inquiry, and possibly enable individuals to conceal their wrongdoing or mislead the course of the investigation by concealing, destroying or fabricating evidence or documents. Disclosures could also subject sources and witnesses to harassment or intimidation which jeopardize the safety and well-being of themselves and their families.</P>
        <P>(6) From subsection (e)(1) because the nature of the investigation function creates unique problems in prescribing specific parameters in a particular case as to what information is relevant or necessary. Due to close liaison and working relationships with other Federal, state, local and foreign country law enforcement agencies, information may be received which may relate to a case under the investigative jurisdiction of another government agency. It is necessary to maintain this information in order to provide leads for appropriate law enforcement purposes and to establish patterns of activity which may relate to the jurisdiction of other cooperating agencies.</P>
        <P>(7) From subsection (e)(4) (G) through (H) because this system of records is exempt from the access provisions of subsection (d).</P>
        <P>(8) From subsection (f) because the agency's rules are inapplicable to those portions of the system that are exempt and would place the burden on the agency of either confirming or denying the existence of a record pertaining to a requesting individual might in itself provide an answer to that individual relating to an on-going investigation. The conduct of a successful investigation leading to the indictment of a criminal offender precludes the applicability of established agency rules relating to verification of record, disclosure of the record to that individual, and record amendment procedures for this record system.</P>
        <P>(g) <E T="03">System Identifier:</E> CIG-16.</P>
        <P>(1) <E T="03">System name:</E> DOD Hotline Program Case Files.</P>
        <P>(2) <E T="03">Exemption:</E> Any portions of this system of records which fall under the provisions of 5 U.S.C. 552a(k)(2) and (k)(5) may be exempt from the following subsections of 5 U.S.C. 552a: (c)(3), (d), (e)(1), (e)(4)(G), (H), and (f).</P>
        <P>(3) <E T="03">Authority:</E> 5 U.S.C. 552a(k)(2) and (k)(5).</P>
        <P>(4) <E T="03">Reasons:</E> From subsection (c)(3) because disclosures from this system could interfere with the just, thorough and timely resolution of the complaint or inquiry, and possibly enable individuals to conceal their wrongdoing or mislead the course of the investigation by concealing, destroying or fabricating evidence or documents.</P>

        <P>(5) From subection (d) because disclosures from this system could interfere with the just, thorough and timely resolution of the complaint or inquiry, and possibly enable individuals to conceal their wrongdoing or mislead the course of the investigation by concealing, destroying or fabricating evidence or documents. Disclosures could also subject sources and witnesses to harassment or intimidation which <PRTPAGE P="879"/>jeopardize the safety and well-being of themselves and their families.</P>
        <P>(6) From subsection (e)(1) because the nature of the investigation functions creates unique problems in prescribing specific paramenters in a particular case as to what information is relevant or necessary. Due to close liaison and working relationships with other Federal, state, local, and foreign country law enforcement agencies, information may be received which may relate to a case under the investigative jurisdiction of another government agency. It is necessary to maintain this information in order to provide leads for appropriate law enforcment purposes and to establish patterns of activity which may relate to the jurisdiction of other cooperating agencies.</P>
        <P>(7) From subsection (e)(4)(G) through (H) because this system of records is exempt from the access provisions of subsection (d).</P>
        <P>(8) From subsection (f) because the agency's rules are inapplicable to those portions of the system that are exempt and would place the burden on the agency of either confirming or denying the existence of a record pertaining to a requesting individual might in itself provide an answer to that individual relating to an on-going investigation. The conduct of a successful investigation leading to the indictment of a criminal offender precludes the applicability of established agency rules relating to verification of record, disclosure of the record to that individual, and record amendment procedures for this record system.</P>
        <CITA>[56 FR 51976, Oct. 17, 1991, as amended at 57 FR 24547, June 10, 1992; 61 FR 2916, Jan. 30, 1996; 64 FR 72929, Dec. 29, 1999]</CITA>
      </SECTION>
      <SECTION>
        <SECTNO>§ 312.13</SECTNO>
        <SUBJECT>Ownership of OIG investigative records.</SUBJECT>
        <P>(a) Criminal and or civil investigative reports shall not be retained by DoD recipient organizations. Such reports are the property of OIG and are on loan to the recipient organization for the purpose for which requested or provided. All copies of such reports shall be destroyed within 180 days after the completion of the final action by the requesting organization.</P>
        <P>(b) Investigative reports which require longer periods of retention may be retained only with the specific written approval of OIG.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 312.14</SECTNO>
        <SUBJECT>Referral of records.</SUBJECT>
        <P>An OIG system of records may contain records other DoD Components or Federal agencies originated, and who may have claimed exemptions for them under the Privacy Act of 1974. When any action is initiated on a portion of any several records from another agency which may be exempt, consultation with the originating agency or component will be affected. Documents located within OIG system of records coming under the cognizance of another agency will be referred to that agency for review and direct response to the requester.</P>
      </SECTION>
    </PART>
    <PART>
      <EAR>Pt. 313</EAR>
      <HD SOURCE="HED">PART 313—THE CHAIRMAN OF THE JOINT CHIEFS OF STAFF AND THE JOINT STAFF PRIVACY PROGRAM</HD>
      <AUTH>
        <HD SOURCE="HED">Authority:</HD>
        <P>Pub. L. 93-579, 88 Stat. 1896 (5 U.S.C. 552a).</P>
      </AUTH>
      <SECTION>
        <SECTNO>§ 313.1</SECTNO>
        <SUBJECT>Source of regulations.</SUBJECT>
        <P>The Office of the Joint Chiefs of Staff is governed by the Privacy Act implementation regulations of the Office of the Secretary of Defense, 32 CFR part 311.</P>
        <CITA>[40 FR 55535, Nov. 28, 1975. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57802, Nov. 14, 1991]</CITA>
      </SECTION>
    </PART>
    <PART>
      <EAR>Pt. 314</EAR>
      <HD SOURCE="HED">PART 314—DEFENSE ADVANCED RESEARCH PROJECTS AGENCY, PRIVACY ACT OF 1974</HD>
      <AUTH>
        <HD SOURCE="HED">Authority:</HD>
        <P>Pub. L. 93-579, 88 Stat. 1896 (5 U.S.C. 552a).</P>
      </AUTH>
      <SECTION>
        <SECTNO>§ 314.1</SECTNO>
        <SUBJECT>Source of regulations.</SUBJECT>
        <P>The Defense Advanced Research Projects Agency is governed by the Privacy Act implementation regulations of the Office of the Secretary of Defense, 32 CFR part 311.</P>
        <CITA>[40 FR 55535, Nov. 28, 1975. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57802, Nov. 14, 1991]</CITA>
      </SECTION>
    </PART>
    <PART>
      <PRTPAGE P="880"/>
      <EAR>Pt. 315</EAR>
      <HD SOURCE="HED">PART 315—UNIFORMED SERVICES UNIVERSITY OF HEALTH SCIENCES, PRIVACY ACT OF 1974</HD>
      <AUTH>
        <HD SOURCE="HED">Authority:</HD>
        <P>Pub. L. 93-579, 88 Stat. 1896 (5 U.S.C. 552a).</P>
      </AUTH>
      <SECTION>
        <SECTNO>§ 315.1</SECTNO>
        <SUBJECT>Source of regulations.</SUBJECT>
        <P>The Uniformed Services University of the Health Sciences, is governed by the Privacy Act implementation regulations of the Office of the Secretary of Defense, 32 CFR part 311.</P>
        <CITA>[40 FR 55535, Nov. 28, 1975. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57802, Nov. 14, 1991]</CITA>
      </SECTION>
    </PART>
    <PART>
      <EAR>Pt. 316</EAR>
      <HD SOURCE="HED">PART 316—DEFENSE INFORMATION SYSTEMS AGENCY PRIVACY PROGRAM</HD>
      <CONTENTS>
        <SECHD>Sec.</SECHD>
        <SECTNO>316.1</SECTNO>
        <SUBJECT>Purpose.</SUBJECT>
        <SECTNO>316.2</SECTNO>
        <SUBJECT>Applicability.</SUBJECT>
        <SECTNO>316.3</SECTNO>
        <SUBJECT>Authority.</SUBJECT>
        <SECTNO>316.4</SECTNO>
        <SUBJECT>Definitions.</SUBJECT>
        <SECTNO>316.5</SECTNO>
        <SUBJECT>Policy.</SUBJECT>
        <SECTNO>316.6</SECTNO>
        <SUBJECT>Procedures and responsibilities.</SUBJECT>
        <SECTNO>316.7</SECTNO>
        <SUBJECT>Questions.</SUBJECT>
        <SECTNO>316.8</SECTNO>
        <SUBJECT>Exemptions.</SUBJECT>
      </CONTENTS>
      <AUTH>
        <HD SOURCE="HED">Authority:</HD>
        <P>Pub. L. 93-579, 88 Stat. 1986 (5 U.S.C. 552a).</P>
      </AUTH>
      <SOURCE>
        <HD SOURCE="HED">Source:</HD>
        <P>40 FR 55535, Nov. 28, 1975, unless otherwise noted. Redesignated at 57 FR 6074, Feb. 20, 1992.</P>
      </SOURCE>
      <SECTION>
        <SECTNO>§ 316.1</SECTNO>
        <SUBJECT>Purpose.</SUBJECT>
        <P>This part delineates responsibility and provides guidance for the implementation of Pub. L. 93-579 (Privacy Act of 1974).</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 316.2</SECTNO>
        <SUBJECT>Applicability.</SUBJECT>
        <P>This part applies to Headquarters, Defense Information Systems Agency (DISA) and DISA field activities.</P>
        <CITA>[40 FR 55535, Nov. 28, 1975. Redesignated at 57 FR 6074, Feb. 20, 1992, as amended at 62 FR 26389, May 14, 1997]</CITA>
      </SECTION>
      <SECTION>
        <SECTNO>§ 316.3</SECTNO>
        <SUBJECT>Authority.</SUBJECT>
        <P>This part is published in accordance with the authority contained in 32 CFR part 310, August 1975.</P>
        <CITA>[40 FR 55535, Nov. 28, 1975. Redesignated and amended at 57 FR 6074, Feb. 20, 1992]</CITA>
      </SECTION>
      <SECTION>
        <SECTNO>§ 316.4</SECTNO>
        <SUBJECT>Definitions.</SUBJECT>
        <P>Add to the definitions contained in 32 CFR 310.6 the following:</P>

        <P>System Manager: The DISA official who is responsible for policies and procedures governing a DISA System of Record. His title and duty address will be found in the paragraph entitled Sysmanager in DISA's Record System Notices which are published in the <E T="04">Federal Register</E> in compliance with provisions of the Privacy Act of 1974.</P>
        <CITA>[40 FR 55535, Nov. 28, 1975. Redesignated and amended at 57 FR 6074, Feb. 20, 1992; 62 FR 26389, May 14, 1997]</CITA>
      </SECTION>
      <SECTION>
        <SECTNO>§ 316.5</SECTNO>
        <SUBJECT>Policy.</SUBJECT>
        <P>It is the policy of DISA:</P>
        <P>(a) To preserve the personal privacy of individuals, to permit an individual to know what records exist pertaining to him in the DISA, and to have access to and have a copy made of all or any portion of such records and to correct or amend such records.</P>
        <P>(b) To collect, maintain, use, or disseminate any record of identifiable personal information in a manner that assures that such action is for a necessary and lawful purpose; that the information is timely and accurate for its intended use; and that adequate safeguards are provided to prevent misuse of such information.</P>
        <CITA>[40 FR 55535, Nov. 28, 1975. Redesignated at 57 FR 6074, Feb. 20, 1992, as amended at 62 FR 26389, May 14, 1997]</CITA>
      </SECTION>
      <SECTION>
        <SECTNO>§ 316.6</SECTNO>
        <SUBJECT>Procedures and responsibilities.</SUBJECT>
        <P>(a) The Counsel, DISA, is hereby designated the Privacy Act Officer for DISA and is responsible for insuring that an internal DISA Privacy Program is established and maintained. He will also insure that all echelons of DISA effectively comply with and implement 32 CFR part 310.</P>
        <P>(b) The Civilian Assistant to the Chief of Staff will be responsible for the annual reporting requirements contained in 32 CFR 310.5.</P>
        <P>(c) DISA System Managers and other appropriate DISA officials will:</P>
        <P>(1) Insure compliance with the provisions of 32 CFR 310.9.</P>

        <P>(2) Comply with the provisions of 32 CFR 286a.11. In this area the Assistant <PRTPAGE P="881"/>to the Director for Administration will provide assistance.</P>
        <P>(3) Adhere to the following:</P>
        <P>(i) Within DISA, the System Manager of any record system will assure that records pertaining to an individual will be disclosed, upon request, to the individual to whom the record pertains. The individual need not state a reason or otherwise justify the need to gain access. A person of the individual's choosing may accompany the individual when the record is disclosed. The System Manager may require the individual to furnish a written statement authorizing discussion of the individual's records in the presence of the accompanying person. If requested, the System Manager will have a copy made of all or any portion of the record pertaining to the individual in a form comprehensible to the requester.</P>
        <P>(ii) The System Manager may release records to the individual's representative who has the written consent of the individual. The System Manager will require reasonable identification of individuals to assure that rec-ords are disclosed to the proper person. No verification of identity will be required of an individual seeking access to records which are otherwise available to any member of the public under the Freedom of Information Act. Identification requirements should be consistent with the nature of the records being disclosed. For disclosure of records to an individual in person, the System Manager will require that the individual show some form of identification. For records disclosed to an individual in person or by mail, the System Manager may require whatever identifying information is needed to locate the record; i.e., name, social security number, date of birth. If the sensitivity of the data warrants, the System Manager may require a signed notarized statement of identity. The System Manager may compare the signatures of the requester with those in the records to verify identity. An individual will not be denied access to his record for refusing to disclose his social security number unless disclosure is required by statute or by regulation adopted before 1 January 1975. An individual will not be denied access to records pertaining to him because the records are exempted from disclosure under the provisions of the Freedom of Information Act.</P>
        <P>(iii) The System Manager will not deny access to a record or a copy thereof to an individual solely because its physical presence is not readily available (i.e. on magnetic tape) or because the context of the record may disclose sensitive information about another individual. To protect the personal privacy of other individuals who may be identified in a record, the System Manager shall prepare an extract to delete only that information which would not be releasable to the requesting individual under the Freedom of Information Act.</P>
        <P>(iv) When the System Manager is of the opinion that the disclosure of medical information could have an adverse effect upon the individual to whom it pertains, the System Manager will promptly request the individual to submit the name and address of a doctor who will determine whether the medical record may be disclosed directly to the individual. The System Manager will then request the opinion of the doctor named by the individual on whether a medical record may be disclosed to the individual. The System Manager shall disclose the medical record to the individual to whom it pertains unless, in the judgment of the doctor, access to the record could have an adverse effect upon the individual's physical or mental health. In this event the System Manager will transmit the record to the doctor and immediately inform the individual.</P>
        <P>(v) The fees to be charged, if any, to an individual for making copies of his record, excluding the cost of any search for and review of the record, will be in accordance with the “Schedule of Fees” as set forth in 32 CFR 286.5 and 286.10.</P>

        <P>(vi) The System Manager of the record will permit an individual to request amendment of a record pertaining to the individual. Requests to amend records shall be in person or in writing and shall be submitted to the System Manager who maintains the records. Such requests should contain as a minimum, identifying information <PRTPAGE P="882"/>needed to locate the record, a brief description of the item or items of information to be amended, and the reason for the requested change.</P>
        <P>(vii) The System Manager will provide a written acknowledgment of the receipt of a request to amend a record to the individual who requested the amendment within 10 days (excluding Saturdays, Sundays, and legal public holidays) after the date of receipt of such request. Such an acknowledgment may, if necessary, request any additional information needed to make a determination. No acknowledgment is required if the request can be reviewed and processed and the individual notified of compliance or denial within the 10 day period.</P>
        <P>(viii) The System Manager will promptly take one of the following actions on requests to amend records:</P>
        <P>(A) Refer the request to the agency or office that has control of and maintains the record in those instances where the record requested remains the property of the controlling office or agency.</P>
        <P>(B) In accordance with existing statute, regulation, or administrative procedure, make any correction of any portion thereof which the individual believes is not accurate, relevant, timely or complete, or</P>
        <P>(C) Inform the individual of the System Manager's refusal to amend the record in accordance with the individual's request, the reason for the refusal, and the individual's right to request a review of the refusal by the Director, DISA, through the DISA Privacy Act Board.</P>
        <P>(ix) The DISA Privacy Act Board will be comprised of the DISA Counsel, as Chairman; the Assistant to the Director for Administration, and the Assistant to the Director for Personnel; or in their absence, their authorized representatives. The individual who disagrees with the refusal of the System Manager to amend his record may request a review of this refusal by the DISA Privacy Act Board. The request for the review may be made orally or in writing and shall be made to the System Manager. The System Manager will promptly forward the request for review to the Chairman of the Board to make a proper review. The Board will promptly review the matter. If, after review, the Board is unanimous in its decision that the record be amended in accordance with the request of the individual then the Chairman of the Board shall so notify the System Manager. The System Manager will immediately make the necessary corrections to the record and will promptly notify the individual. The System Manager will, if an accounting of disclosure of the record has been made, advise all previous recipients of the record, which was corrected, of the correction and its substance. This will be done in all instances when a record is amended. If, after review, the Board decides that the request for amendment should be denied, it will promptly forward its recommendation to the Director, DCA. A majority vote of the members of the Board will constitute a recommendation to the Director.</P>
        <P>(x) The Director, DISA, upon receipt of the Board's recommendation, will complete the review and make a final determination.</P>
        <P>(xi) If the Director, DISA, after his review, agrees with the individual's request to amend the record, he will, through the DISA Counsel, so advise the individual in writing. The System Manager will receive a copy of the Director's decision and will assure that the record is corrected accordingly and that if an accounting of disclosure of the record has been made, advise all previous recipients of the record which was corrected of the correction and its substance.</P>

        <P>(xii) If, after his review, the Director refuses to amend the records as the individual requested, he will, through the DISA Counsel, advise the individual of his refusal and the reasons for it; of the individual's right to file a concise statement setting forth the reasons for the individual's disagreement with the decision of the Director, DISA; that the statement which is filed will be made available to anyone to whom the record is subsequently disclosed together with, at the discretion of the Agency, a brief statement by the Agency summarizing its reasons for refusing to amend the record; that prior recipients of the disputed record will be provided a copy of any statement of dispute to the extent that an accounting <PRTPAGE P="883"/>of disclosures was maintained; and of the individual's right to seek judicial review of the Agency's refusal to amend a record.</P>
        <P>(xiii) The Director's final determination on the individual's request for a review of the System Manager's initial refusal to amend the record must be concluded within 30 days (excluding Saturdays, Sundays, and legal public holidays) from the date on which the individual requested such review unless the Director determines that a fair and equitable review cannot be made within that time. If additional time is required, the individual will be informed in writing of reasons for the delay and of the approximate date on which the review is expected to be completed.</P>
        <P>(xiv) After the Director, DISA has refused to amend a record and the individual has filed a statement setting forth the reasons for the individual's disagreement with the decision of the Director, the System Manager will clearly note any portion of the record which is disputed. The System Manager's notation should make clear that the record is disputed and this should be apparent to anyone who may subsequently have access to, use, or disclose the record. When the System Manager has previously disclosed or will subsequently disclose that portion of the record which is disputed he will note that that portion of the record is disputed and will provide the recipients of the record with a copy of the individual's statement setting forth the reasons for the individual's disagreement with the decision of the Director not to amend the record. The System Manager will also provide recipients of the disputed record with a brief summary of the Director's reasons for not making the requested amendments to the record.</P>
        <P>(xv) Nothing herein shall allow an individual access to any information compiled in reasonable anticipation of a civil action or proceeding.</P>
        <P>(xvi) Any requests by an individual for access to or copies of his records shall be processed in accordance with this part and 32 CFR part 310.</P>
        <P>(d) DISA System Managers will be:</P>
        <P>(1) Responsible for complying with the provisions contained in 32 CFR 310.8 relating to the disclosure to others of personal records, obtaining the written consent of individuals to whom the record pertains, and for keeping an accurate accounting of each disclosure of a record.</P>
        <P>(2) Responsible for providing to the Civilian Assistant to the Chief of Staff the information requested in 32 CFR 310.5. However, the information will be reported on a quarterly basis with the first report due to the Civilian Assistant to the Chief of Staff by 31 December 1975.</P>
        <P>(e) The Assistant to the Director for Administration, Headquarters, DCA will:</P>
        <P>(1) Be responsible for furnishing written guidelines to assist System Managers and other DISA officials in evaluating and implementing paperwork management procedures required under the Privacy Act of 1974. In this regard it should be noted that the Act establishes a number of requirements. Among these are the requirements:</P>
        <P>(i) To disclose records contained in a system of records only under conditions specified in the law,</P>
        <P>(ii) To maintain an accounting of such disclosures,</P>
        <P>(iii) To establish procedures for the disclosure to an individual of his record or information pertaining to him,</P>
        <P>(iv) For reviewing a request concerning the amendment of such record, and</P>
        <P>(v) For permitting individuals to file a statement of disagreement which will be forwarded with subsequent disclosures.</P>
        <FP>The guidelines will cover those portions of the Privacy Act which requires paperwork systems for implementation. In preparing those guidelines the Assistant to the Director for Administration will make use of the “Records Management System for Implementing the Privacy Act” as provided by the GSA and National Archives and Records Service, Office of Records Management. The GSA and NARA procedures and guidelines will be adapted and modified as required to meet DISA needs.</FP>
        <P>(2) Be responsible for providing the “Forms” which are required to comply with 32 CFR 310.9(b).</P>

        <P>(f) The Assistant to the Director for Personnel, Headquarters, DISA will:<PRTPAGE P="884"/>
        </P>
        <P>(1) Be responsible for development, within DISA, of an appropriate training program for all DISA personnel whose duties involve responsibilities for systems of records affected by the Privacy Act.</P>
        <P>(2) Assure that DISA personnel involved in the design, development, operation, or maintenance of any system of records, as defined in 32 CFR 310.6 are informed of all requirements to protect the privacy of the individuals who are subjects of the records. The criminal penalties and civil suit aspects of the Privacy Act will be emphasized.</P>
        <P>(3) Assure that within DISA administrative and physical safeguards are established to protect information from unauthorized or unintentional access, disclosure, modification or destruction and to insure that all persons whose official duties require access to or processing and maintenance of personal information are trained in the proper safeguarding and use of such information.</P>
        <CITA>[40 FR 55535, Nov. 28, 1975. Redesignated and amended at 57 FR 6074, Feb. 20, 1992; 62 FR 26389, May 14, 1997]</CITA>
      </SECTION>
      <SECTION>
        <SECTNO>§ 316.7</SECTNO>
        <SUBJECT>Questions.</SUBJECT>
        <P>Questions on both the substance and procedure of the Privacy Act and the DISA implementation thereof should be addressed to the DISA Counsel by the most expeditious means possible, including telephone calls.</P>
        <CITA>[40 FR 55535, Nov. 28, 1975. Redesignated at 57 FR 6074, Feb. 20, 1992, as amended at 62 FR 26390, May 14, 1997]</CITA>
      </SECTION>
      <SECTION>
        <SECTNO>§ 316.8</SECTNO>
        <SUBJECT>Exemptions.</SUBJECT>
        <P>Section 5 U.S.C. 552a (3)(j) and (3)(k) authorize an agency head to exempt certain systems of records or parts of certain systems of records from some of the requirements of the act. This part reserves to the Director, DISA, as head of an agency, the right to create exemptions pursuant to the exemption provisions of the act. All systems of records maintained by DISA shall be exempt from the requirements of 5 U.S.C. 552a (d) pursuant to 5 U.S.C. 552a(3)(k)(1) to the extent that the system contains any information properly classified under Executive Order 11652, “Classification and Declassification of National Security Information and Material,” dated March 8, 1972 (37 FR 10053, May 19, 1972) and which is required by the executive order to be kept secret in the interest of national defense or foreign policy. This exemption, which may be applicable to parts of all systems of records, is necessary because certain record systems not otherwise specifically designated for exemptions may contain isolated information which has been properly classified.</P>
        <CITA>[42 FR 20298, Apr. 19, 1977. Redesignated at 57 FR 6074, Feb. 20, 1992, as amended at 62 FR 26390, May 14, 1997]</CITA>
      </SECTION>
    </PART>
    <PART>
      <EAR>Pt. 317</EAR>
      <HD SOURCE="HED">PART 317—DCAA PRIVACY ACT PROGRAM</HD>
      <CONTENTS>
        <SECHD>Sec.</SECHD>
        <SECTNO>317.1</SECTNO>
        <SUBJECT>Purpose.</SUBJECT>
        <SECTNO>317.2</SECTNO>
        <SUBJECT>Applicability and scope.</SUBJECT>
        <SECTNO>317.3</SECTNO>
        <SUBJECT>Policy.</SUBJECT>
        <SECTNO>317.4</SECTNO>
        <SUBJECT>Responsibilities.</SUBJECT>
        <SECTNO>317.5</SECTNO>
        <SUBJECT>Information requirements.</SUBJECT>
        <SECTNO>317.6</SECTNO>
        <SUBJECT>Procedures.</SUBJECT>
      </CONTENTS>
      <AUTH>
        <HD SOURCE="HED">Authority:</HD>
        <P>Pub. L. 93-579, 88 Stat. 1896 (5 U.S.C. 552a).</P>
      </AUTH>
      <SOURCE>
        <HD SOURCE="HED">Source:</HD>
        <P>65 FR 63799, Oct. 25, 2000, unless otherwise noted.</P>
      </SOURCE>
      <SECTION>
        <SECTNO>§ 317.1</SECTNO>
        <SUBJECT>Purpose</SUBJECT>
        <P>This part provides policies and procedures for the Defense Contract Audit Agency's implementation of the Privacy Act of 1974 (DCAA Regulation 5410.10,<SU>1</SU>
          <FTREF/> as amended, (5 U.S.C. 552a); DoD 5400.11 and DoD 5400.11-R,<SU>2</SU>
          <FTREF/> “DoD Privacy Program” (32 CFR part 310); and is intended to promote uniformity within DCAA.</P>
        <FTNT>
          <P>
            <SU>1</SU> Copies may be obtained from http://www.deskbook.osd.mil.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>2</SU> Copies may be obtained from http://web7.whs.osd.mil.</P>
        </FTNT>
      </SECTION>
      <SECTION>
        <SECTNO>§ 317.2</SECTNO>
        <SUBJECT>Applicability and scope.</SUBJECT>
        <P>(a) This part applies to all DCAA organizational elements and takes precedence over all regional regulatory issuances that supplement the DCAA Privacy Program.</P>

        <P>(b) This part shall be made applicable by contract or other legally binding action to contractors whenever a DCAA contract provides for the operation of a <PRTPAGE P="885"/>system of records or portion of a system of records to accomplish an Agency function.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 317.3</SECTNO>
        <SUBJECT>Policy.</SUBJECT>
        <P>(a) It is DCAA policy that personnel will comply with the DCAA Privacy Program; the Privacy Act of 1974; and the DoD Privacy Program (32 CFR part 310). Strict adherence is necessary to ensure uniformity in the implementation of the DCAA Privacy Program and create conditions that will foster public trust. It is also Agency policy to safeguard personal information contained in any system of records maintained by DCAA organizational elements and to make that information available to the individual to whom it pertains to the maximum extent practicable.</P>
        <P>(b) DCAA policy specifically requires that DCAA organizational elements:</P>
        <P>(1) Collect, maintain, use, and disseminate personal information only when it is relevant and necessary to achieve a purpose required by statute or Executive Order.</P>
        <P>(2) Collect personal information directly from the individuals to whom it pertains to the greatest extent practical.</P>
        <P>(3) Inform individuals who are asked to supply personal information for inclusion in any system of records:</P>
        <P>(i) The authority for the solicitation.</P>
        <P>(ii) Whether furnishing the information is mandatory or voluntary.</P>
        <P>(iii) The intended uses of the information.</P>
        <P>(iv) The routine disclosures of the information that may be made outside of DoD.</P>
        <P>(v) The effect on the individual of not providing all or any part of the requested information.</P>
        <P>(4) Ensure that records used in making determinations about individuals and those containing personal information are accurate, relevant, timely, and complete for the purposes for which they are being maintained before making them available to any recipients outside of DoD, other than a Federal agency, unless the disclosure is made under DCAA Regulation 5410.8, DCAA Freedom of Information Act Program.<SU>3</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>3</SU> Copies may be obtained from http://www.deskbook.osd.mil.</P>
        </FTNT>
        <P>(5) Keep no record that describes how individuals exercise their rights guaranteed by the First Amendment to the U.S. Constitution, unless expressly authorized by statute or by the individual to whom the records pertain or is pertinent to and within the scope of an authorized law enforcement activity.</P>
        <P>(6) Notify individuals whenever records pertaining to them are made available under compulsory legal processes, if such process is a matter of public record.</P>
        <P>(7) Establish safeguards to ensure the security of personal information and to protect this information from threats or hazards that might result in substantial harm, embarrassment, inconvenience, or unfairness to the individual.</P>
        <P>(8) Establish rules of conduct for DCAA personnel involved in the design, development, operation, or maintenance of any system of records and train them in these rules of conduct.</P>
        <P>(9) Assist individuals in determining what records pertaining to them are being collected, maintained, used, or disseminated.</P>
        <P>(10) Permit individual access to the information pertaining to them maintained in any system of records, and to correct or amend that information, unless an exemption for the system has been properly established for an important public purpose.</P>
        <P>(11) Provide, on request, an accounting of all disclosures of the information pertaining to them except when disclosures are made:</P>
        <P>(i) To DoD personnel in the course of their official duties.</P>
        <P>(ii) Under DCAA Regulation 5410.8, DCAA Freedom of Information Act Program.</P>
        <P>(iii) To another agency or to an instrumentality of any governmental jurisdiction within or under control of the United States conducting law enforcement activities authorized by law.</P>

        <P>(12) Advise individuals on their rights to appeal any refusal to grant access to or amend any record pertaining to <PRTPAGE P="886"/>them, and file a statement of disagreement with the record in the event amendment is refused.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 317.4</SECTNO>
        <SUBJECT>Responsibilities.</SUBJECT>
        <P>(a) The Assistant Director, Resources has overall responsibility for the DCAA Privacy Act Program and will serve as the sole appellate authority for appeals to decisions of respective initial denial authorities.</P>
        <P>(b) The Chief, Administrative Management Division under the direction of the Assistant Director, Resources, shall:</P>
        <P>(1) Establish, issue, and update policies for the DCAA Privacy Act Program; monitor compliance with this part; and provide policy guidance for the DCAA Privacy Act Program.</P>
        <P>(2) Resolve conflicts that may arise regarding implementation of DCAA Privacy Act policy.</P>
        <P>(3) Designate an Agency Privacy Act Advisor, as a single point of contact, to coordinate on matters concerning Privacy Act policy.</P>
        <P>(4) Make the initial determination to deny an individual's written Privacy Act request for access to or amendment of documents filed in Privacy Act systems of records. This authority cannot be delegated.</P>
        <P>(c) The DCAA Privacy Act Advisor under the supervision of the Chief, Administrative Management Division shall:</P>
        <P>(1) Manage the DCAA Privacy Act Program in accordance with this part and applicable DCAA policies, as well as DoD and Federal regulations.</P>
        <P>(2) Provide guidelines for managing, administering, and implementing the DCAA Privacy Act Program.</P>
        <P>(3) Implement and administer the Privacy Act program at the Headquarters.</P>
        <P>(4) Ensure that the collection, maintenance, use, or dissemination of records of identifiable personal information is in a manner that assures that such action is for a necessary and lawful purpose; that the information is timely and accurate for its intended use; and that adequate safeguards are provided to prevent misuse of such information.</P>
        <P>(5) Maintain and publish DCAA Pamphlet 5410.13, DCAA Compilation of Privacy Act System Notices.<SU>4</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>4</SU> Copies may be obtained from the Defense Contract Audit Agency, ATTN: DCAA-CMO, 8725 John J. Kingman Road, Suite 2135, Fort Belvoir, VA 22060-6219. Electronic copies of DCAA Privacy notices may be obtained from http://www.defenselink. mil/privacy.</P>
        </FTNT>

        <P>(6) Prepare promptly any required new, amended, or altered system notices for systems of records subject to the Privacy Act and submit them to the Defense Privacy Office for subsequent publication in the <E T="04">Federal Register</E>.</P>
        <P>(7) Prepare the annual Privacy Act Report as required by DoD 5400.11-5, DoD Privacy program.</P>
        <P>(8) Conduct training on the Privacy Act program for Agency personnel.</P>
        <P>(d) Heads of Principal Staff Elements are responsible for:</P>
        <P>(1) Reviewing all regulations or other policy and guidance issuances for which they are the proponent to ensure consistency with the provisions of this part.</P>
        <P>(2) Ensuring that the provisions of this part are followed in processing requests for records.</P>
        <P>(3) Forwarding to the DCAA Privacy Act Advisor, any Privacy Act requests received directly from a member of the public, so that the request may be administratively controlled and processed.</P>
        <P>(4) Ensuring the prompt review of all Privacy Act requests, and when required, coordinating those requests with other organizational elements.</P>
        <P>(5) Providing recommendations to the DCAA Privacy Act Advisor regarding the releasability of DCAA records to members of the public, along with the responsive documents.</P>
        <P>(6) Providing the appropriate documents, along with a written justification for any denial, in whole or in part, of a request for records to the DCAA Privacy Act Advisor. Those portions to be excised should be bracketed in red pencil, and the specific exemption or exemptions cites which provide the basis for denying the requested records.</P>
        <P>(e) The General Counsel is responsible for:<PRTPAGE P="887"/>
        </P>
        <P>(1) Ensuring uniformity is maintained in the legal position, and the interpretation of the Privacy Act; 32 CFR part 310; and this part.</P>
        <P>(2) Consulting with DoD General Counsel on final denials that are inconsistent with decisions of other DoD components, involve issues not previously resolved, or raise new or significant legal issues of potential significance to other Government agencies.</P>
        <P>(3) Providing advice and assistance to the Assistant Director, Resources; Regional Directors; and the Regional Privacy Act Officer, through the DCAA Privacy Act Advisor, as required, in the discharge of their responsibilities.</P>
        <P>(4) Coordinating Privacy Act litigation with the Department of Justice.</P>
        <P>(5) Coordinating on Headquarters denials of initial requests.</P>
        <P>(f) Each Regional Director is responsible for the overall management of the Privacy Act program within their respective regions. Under his/her direction, the Regional Resources Manager is responsible for the management and staff supervision of the program and for designating a Regional Privacy Act Officer. Regional Directors will, as designee of the Director, make the initial determination to deny an individual's written Privacy Act request for access to or amendment of documents filed in Privacy Act systems of records. This authority cannot be delegated.</P>
        <P>(g) Regional Privacy Act Officers will:</P>
        <P>(1) Implement and administer the Privacy Act program throughout the region.</P>
        <P>(2) Ensure that the collection, maintenance, use, or dissemination of records of identifiable personal information is in a DCAAR 5410.10 manner that assures that such action is for a necessary and lawful purpose; that the information is timely and accurate for its intended use; and that adequate safeguards are provided to prevent misuse of such information.</P>
        <P>(3) Prepare input for the annual Privacy Act Report when requested by the DCAA Information and Privacy Advisor.</P>
        <P>(4) Conduct training on the Privacy Act program for regional and FAO personnel.</P>
        <P>(5) Provide recommendations to the Regional Director through the Regional Resources Manager regarding the releasability of DCAA records to members of the public.</P>
        <P>(h) Managers, Field Audit Offices (FAOs) will:</P>
        <P>(1) Ensure that the provisions of this part are followed in processing requests for records.</P>
        <P>(2) Forward to the Regional Privacy Act Officer, any Privacy Act requests received directly from a member of the public, so that the request may be administratively controlled and processed.</P>
        <P>(3) Ensure the prompt review of all Privacy Act requests, and when required, coordinating those requests with other organizational elements.</P>
        <P>(4) Provide recommendation to the Regional Privacy Act Officer regarding the releasability of DCAA records to members of the public, along with the responsive documents.</P>
        <P>(5) Provide the appropriate documents, along with a written justification for any denial, in whole or in part, of a request for records to the Regional Privacy Act Officer. Those portions to be excised should be bracketed in red pencil, and the specific exemption or exemptions cited which provide the basis for denying the requested records.</P>
        <P>(i) DCAA Employees will:</P>
        <P>(1) Not disclose any personal information contained in any system of records, except as authorized by this part.</P>

        <P>(2) Not maintain any official files which are retrieved by name or other personal identifier without first ensuring that a notice for the system has been published in the <E T="04">Federal Register</E>.</P>
        <P>(3) Report any disclosures of personal information from a system of records or the maintenance of any system of records that are not authorized by this part to the appropriate Privacy Act officials for their action.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 317.5</SECTNO>
        <SUBJECT>Information requirements.</SUBJECT>
        <P>The Report Control Symbol. Unless otherwise directed, any report concerning implementation of the Privacy Program shall be assigned Report Control Symbol DD-DA&amp;M(A)1379.</P>
      </SECTION>
      <SECTION>
        <PRTPAGE P="888"/>
        <SECTNO>§ 317.6</SECTNO>
        <SUBJECT>Procedures.</SUBJECT>
        <P>Procedures for processing material in accordance with the Privacy Act of 1974 are outlined in DoD 5400.11-R, DoD Privacy Program (32 CFR part 310).</P>
      </SECTION>
    </PART>
    <PART>
      <EAR>Pt. 318</EAR>
      <HD SOURCE="HED">PART 318—DEFENSE THREAT REDUCTION AGENCY PRIVACY PROGRAM</HD>
      <CONTENTS>
        <SECHD>Sec.</SECHD>
        <SECTNO>318.1</SECTNO>
        <SUBJECT>Reissuance and purpose.</SUBJECT>
        <SECTNO>318.2</SECTNO>
        <SUBJECT>Application.</SUBJECT>
        <SECTNO>318.3</SECTNO>
        <SUBJECT>Definitions.</SUBJECT>
        <SECTNO>318.4</SECTNO>
        <SUBJECT>Policy.</SUBJECT>
        <SECTNO>318.5</SECTNO>
        <SUBJECT>Designations and responsibilities.</SUBJECT>
        <SECTNO>318.6</SECTNO>
        <SUBJECT>Procedures for requests pertaining to individual records in a record system.</SUBJECT>
        <SECTNO>318.7</SECTNO>
        <SUBJECT>Disclosure of requested information to individuals.</SUBJECT>
        <SECTNO>318.8</SECTNO>
        <SUBJECT>Request for correction or amendment to a record.</SUBJECT>
        <SECTNO>318.9</SECTNO>
        <SUBJECT>Agency review of request for correction or amendment of record.</SUBJECT>
        <SECTNO>318.10</SECTNO>
        <SUBJECT>Appeal of initial adverse Agency determination for access, correction or amendment.</SUBJECT>
        <SECTNO>318.11</SECTNO>
        <SUBJECT>Disclosure of record to persons other than the individual to whom it pertains.</SUBJECT>
        <SECTNO>318.12</SECTNO>
        <SUBJECT>Fees.</SUBJECT>
        <SECTNO>318.13</SECTNO>
        <SUBJECT>Enforcement actions.</SUBJECT>
        <SECTNO>318.14</SECTNO>
        <SUBJECT>Blanket routine uses.</SUBJECT>
        <SECTNO>318.15</SECTNO>
        <SUBJECT>Rules of conduct.</SUBJECT>
        <SECTNO>318.16</SECTNO>
        <SUBJECT>Exemption rules.</SUBJECT>
      </CONTENTS>
      <AUTH>
        <HD SOURCE="HED">Authority:</HD>
        <P>Pub. L. 93-579, 88 Stat 1896 (5 U.S.C. 552a).</P>
      </AUTH>
      <SOURCE>
        <HD SOURCE="HED">Source:</HD>
        <P>65 FR 18894, Apr. 10, 2000, unless otherwise noted.</P>
      </SOURCE>
      <SECTION>
        <SECTNO>§ 318.1</SECTNO>
        <SUBJECT>Reissuance and purpose.</SUBJECT>
        <P>(a) This part updates the policies, responsibilities, and procedures of the DTRA Privacy Program under the Privacy Act of 1974, as amended (5 U.S.C. 552a), OMB Circular A-130,<SU>1</SU>
          <FTREF/> and the DoD Privacy Program (32 CFR part 310).</P>
        <FTNT>
          <P>
            <SU>1</SU> Copies may be obtained: http://www.whitehouse.gov/OMB/circulars.</P>
        </FTNT>
        <P>(b) This rule establishes procedures whereby individuals can:</P>
        <P>(1) Request notification of whether Defense Threat Reduction Agency (DTRA) maintains or has disclosed a record pertaining to them in any nonexempt system of records;</P>
        <P>(2) Request a copy or other access to such a record or to an accounting of its disclosure;</P>
        <P>(3) Request that the record be amended; and</P>
        <P>(4) Appeal any initial adverse determination of any such request.</P>
        <P>(c) Specifies those system of records which the Director, Defense Threat Reduction Agency has determined to be exempt from the procedures established by this rule and by certain provisions of the Privacy Act.</P>
        <P>(d) DTRA policy encompasses the safeguarding of individual privacy from any misuse of DTRA records and the provides the fullest access practicable by individuals to DTRA records concerning them.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 318.2</SECTNO>
        <SUBJECT>Applicability.</SUBJECT>
        <P>(a) This part applies to all members of the Armed Forces and Department of Defense civilians assigned to the DTRA at any of its duty locations.</P>
        <P>(b) This part shall be made applicable to DoD contractors who are operating a system of records on behalf of DTRA, to include any of the activities, such as collecting and disseminating records, associated with maintaining a system of records.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 318.3</SECTNO>
        <SUBJECT>Definitions.</SUBJECT>
        <P>
          <E T="03">Access.</E> The review of a record or a copy of a record or parts thereof in a system of records by any individual.</P>
        <P>
          <E T="03">Agency.</E> For the purposes of disclosing records subject to the Privacy Act among DoD Components, the Department of Defense is considered a single agency. For all other purposes to include applications for access and amendment, denial of access or amendment, appeals from denials, and record keeping as regards release to non-DoD agencies; each DoD Component is considered an agency within the meaning of the Privacy Act.</P>
        <P>
          <E T="03">Confidential source.</E> A person or organization who has furnished information to the federal government under an express promise that the person's or the organization's identity will be held in confidence or under an implied promise of such confidentiality if this implied promise was made before September 27, 1975.</P>
        <P>
          <E T="03">Disclosure.</E>  The transfer of any personal information from a system of records by any means of communication (such as oral, written, electronic, <PRTPAGE P="889"/>mechanical, or actual review) to any person, private entity, or government agency, other than the subject of the record, the subject's designated agent or the subject's legal guardian.</P>
        <P>
          <E T="03">Individual.</E>  A living person who is a citizen of the United States or an alien lawfully admitted for permanent residence. The parent of a minor or the legal guardian of any individual also may act on behalf of an individual. Corporations, partnerships, sole proprietorships, professional groups, businesses, whether incorporated or unincorporated, and other commercial entities are not “individuals.”</P>
        <P>
          <E T="03">Law enforcement activity.</E>  Any activity engaged in the enforcement of criminal laws, including efforts to prevent, control, or reduce crime or to apprehend criminals, and the activities of prosecutors, courts, correctional, probation, pardon, or parole authorities.</P>
        <P>
          <E T="03">Maintain.</E> Includes maintain, collect, use or disseminate.</P>
        <P>
          <E T="03">Official use.</E> Within the context of this part, this term is used when officials and employees of a DoD Component have a demonstrated need for the use of any record or the information contained therein in the performance of their official duties, subject to DoD 5200.1-R,<SU>2</SU>
          <FTREF/> “DoD Information Security Program Regulation”.</P>
        <FTNT>
          <P>
            <SU>2</SU> Copies may be obtained: http://web7.whs.osd.mil/corres.htm.</P>
        </FTNT>
        <P>
          <E T="03">Personal information.</E>  Information about an individual that identifies, relates or is unique to, or describes him or her; e.g., a social security number, age, military rank, civilian grade, marital status, race, salary, home/office phone numbers, etc.</P>
        <P>
          <E T="03">Privacy Act request.</E>  A request from an individual for notification as to the existence of, access to, or amendment of records pertaining to that individual. These records must be maintained in a system of records.</P>
        <P>
          <E T="03">Member of the public.</E>  Any individual or party acting in a private capacity to include federal employees or military personnel.</P>
        <P>
          <E T="03">Record.</E>  Any item, collection, or grouping of information, whatever the storage media (e.g., paper, electronic, etc.), about an individual that is maintained by a DoD Component, including but not limited to, his or her education, financial transactions, medical history, criminal or employment history and that contains his or her name, or the identifying number, symbol, or other identifying particular assigned to the individual, such as a finger or voice print or a photograph.</P>
        <P>
          <E T="03">Risk assessment.</E> An analysis considering information sensitivity, vulnerabilities, and the cost to a computer facility or word processing activity in safeguarding personal information processed or stored in the facility or activity.</P>
        <P>
          <E T="03">Routine use.</E> The disclosure of a record outside the Department of Defense for a use that is compatible with the purpose for which the information was collected and maintained by the Department of Defense. The routine use must be included in the published system notice for the system of records involved.</P>
        <P>
          <E T="03">Statistical record.</E> A record maintained only for statistical research or reporting purposes and not used in whole or in part in making determinations about specific individuals.</P>
        <P>
          <E T="03">System manager.</E> The DoD Component official who is responsible for the operation and management of a system of records.</P>
        <P>
          <E T="03">System of records.</E> A group of records under the control of a DoD Component from which personal information is retrieved by the individual's name or by some identifying number, symbol, or other identifying particular assigned to an individual.</P>
        <P>
          <E T="03">Word processing system.</E> A combination of equipment employing automated technology, systematic procedures, and trained personnel for the primary purpose of manipulating human thoughts and verbal or written or graphic presentations intended to communicate verbally or visually with another individual.</P>
        <P>
          <E T="03">Word processing equipment.</E> Any combination of electronic hardware and computer software integrated in a variety of forms (firmware, programmable software, handwiring, or similar equipment) that permits the processing of textual data. Generally, the equipment contains a device to receive information, a computer-like processor with various capabilities to manipulate the <PRTPAGE P="890"/>information, a storage medium, and an output device</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 318.4</SECTNO>
        <SUBJECT>Policy.</SUBJECT>
        <P>(a) It is DTRA policy that:</P>
        <P>(1) The personal privacy of an individual shall be respected and protected. Personal information shall be collected, maintained, used, or disclosed to insure that:</P>
        <P>(2) It shall be relevant and necessary to accomplish a lawful DTRA purpose required to be accomplished by Federal statute or Executive order;</P>
        <P>(3) It shall be collected to the greatest extent practicable directly from the individual;</P>
        <P>(4) The individual shall be informed as to why the information is being collected, the authority for collection, what uses will be made of it, whether disclosure is mandatory or voluntary, and the consequences of not providing the information;</P>
        <P>(5) It shall be relevant, timely, complete and accurate for its intended use; and</P>
        <P>(6) Appropriate administrative, technical, and physical safeguards shall be established, based on the media (e.g., paper, electronic, etc.) involved, to ensure the security of the records and to prevent compromise or misuse during storage or transfer.</P>
        <P>(b) No record shall be maintained on how an individual exercises rights guaranteed by the First Amendment to the Constitution, except as specifically authorized by statute; expressly authorized by the individual on whom the record is maintained; or when the record is pertinent to and within the scope of an authorized law enforcement activity.</P>
        <P>(c) Notices shall be published in the <E T="04">Federal Register</E> and reports shall be submitted to Congress and the Office of Management and Budget, in accordance with, and as required by 5 U.S.C. 552a, OMB Circular A-130, and 32 CFR part 310, as to the existence and character of any system of records being established or revised by the DoD Components. Information shall not be collected, maintained, or disseminated until the required publication/review requirements are satisfied.</P>
        <P>(d) Individuals shall be permitted, to the extent authorized by this part:</P>
        <P>(1) To determine what records pertaining to them are contained in a system of records;</P>
        <P>(2) Gain access to such records and obtain a copy of those records or a part thereof;</P>
        <P>(3) Correct or amend such records on a showing the records are not accurate, relevant, timely, or complete.</P>
        <P>(4) Appeal a denial of access or a request for amendment.</P>
        <P>(e) Disclosure of records pertaining to an individual from a system of records shall be prohibited except with the consent of the individual or as otherwise authorized by 5 U.S.C. 552a and 32 CFR part 286. When disclosures are made, the individual shall be permitted, to the extent authorized by 5 U.S.C. 552a and 32 CFR part 310, to seek an accounting of such disclosures from DTRA.</P>
        <P>(f) Computer matching programs between DTRA and Federal, State, or local governmental agencies shall be conducted in accordance with the requirements of 5 U.S.C. 552a, OMB Circular A-130, and 32 CFR part 310.</P>
        <P>(g) DTRA personnel and Systems Managers shall conduct themselves, pursuant to established rules of conduct, so that personal information to be stored in a system of records shall only be collected, maintained, used, and disseminated as authorized by this part.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 318.5</SECTNO>
        <SUBJECT>Designations and responsibilities</SUBJECT>
        <P>(a) The Director, DTRA shall:</P>
        <P>(1) Provide adequate funding and personnel to establish and support an effective Privacy Program.</P>
        <P>(2) Appoint a senior official to serve as the Agency Privacy Act Officer.</P>
        <P>(3) Serve as the Agency Appellate Authority.</P>
        <P>(b) The Privacy Act Officer shall:</P>
        <P>(1) Implement the Agency's Privacy Program in accordance with the specific requirements set forth in this part, 5 U.S.C. 552a, OMB Circular A-130, and 32 CFR part 310.</P>

        <P>(2) Establish procedures, as well as rules of conduct, necessary to implement this part so as to ensure compliance with the requirements of 5 U.S.C. 552a, OMB Circular A-130, and 32 CFR part 310.<PRTPAGE P="891"/>
        </P>
        <P>(3) Ensure that the DTRA Privacy Program periodically shall be reviewed by the DTRA Inspectors General or other officials, who shall have specialized knowledge of the DoD Privacy Program.</P>
        <P>(4) Serve as the Agency Initial Denial Authority.</P>
        <P>(c) <E T="03">The Privacy Act Program Manager shall:</E>
        </P>
        <P>(1) Manage activities in support of the DTRA Programoversight in accordance with part, 5 U.S.C. 552a, OMB Circular A-130, and 32 CFR part 310.</P>
        <P>(2) Provide operational support, guidance and assistance to Systems Managers for responding to requests for access/amendment of records.</P>
        <P>(3) Direct the day-by-day activities of the DTRA Privacy Program.</P>
        <P>(4) Provide guidance and assistance to DTRA elements in their implementation and execution of the DTRA Privacy Program.</P>
        <P>(5) Prepare and submit proposed new, altered, andamended systems of records, to include submission of required notices for publication in the Federal Register consistent with this part, 5 U.S.C. 552a, OMB Circular A-130, and 32 CFR part 310.</P>
        <P>(6) Prepare and submit proposed DTRA privacy rulemaking, to include documentation for submission of the proposed rule to the Office of the Federal Register for publication. Additionally, provide required documentation for reporting to the OMB and Congress, consistent with this part, 5 U.S.C. 552a, OMB Circular A-130, and 32 CFR part 310.</P>
        <P>(7) Provide advice and support to DTRA elements to ensure that:</P>
        <P>(i) All information requirements developed to collect and/or maintain personal data conform to DoD Privacy Act Program standards;</P>
        <P>(ii) Appropriate procedures and safeguards shall be developed, implemented, and maintained to protect personal information when it is stored in either a manual and/or automated system of records or transferred by electronic or non-electronic means; and</P>
        <P>(iii) Specific procedures and safeguards shall be developed and implemented when personal data is collected and maintained for research purposes.</P>
        <P>(8) Conduct reviews, and prepare and submit reports consistent with the requirements in this part, 5 U.S.C. 552a, OMB Circular A-130, and 32 CFR part 310, or as otherwise directed by the Defense Privacy Office.</P>
        <P>(9) Conduct training for all assigned and employed DTRA personnel and for those individuals having primary responsibility for DTRA Privacy Act Record Systems consistent with requirements of this part, 5 U.S.C. 552a, OMB Circular A-130, and 32 CFR part 310.</P>
        <P>(10) Serve as the principal points of contact for coordination of privacy and related matters.</P>
        <P>(d) <E T="03">The Directorate Heads and Office Chiefs shall:</E>
        </P>
        <P>(1) Recognize and support the DTRA Privacy Act Program.</P>
        <P>(2) Appoint an individual to serve as Privacy Act Point of Contact within their purview.</P>
        <P>(3) Initiate prompt, constructive management actions on agreed-upon actions identified in agency Privacy Act reports.</P>
        <P>(e) <E T="03">The Chief, Information Systems shall:</E>
        </P>
        <P>(1) Ensure that all personnel who have access to information from an automated system of records during processing or who are engaged in developing procedures for processing such information are aware of the provisions of this Instruction.</P>
        <P>(2) Promptly notify automated system managers and the Privacy Act Officer whenever they are changes to Agency Information Technology that may require the submission of an amended system notice for any system of records.</P>
        <P>(3) Establish rules of conduct for Agency personnel involved in the design, development, operation, or maintenance of any automated system of records and train them in these rules of conduct.</P>
        <P>(f) Agency System Managers shall exercise the Rules of Conduct as specified in 32 CFR part 310.</P>
        <P>(g) Agency personnel shall exercise the Rules of Conduct as specified in 32 CFR part 310.</P>
      </SECTION>
      <SECTION>
        <PRTPAGE P="892"/>
        <SECTNO>§ 318.6</SECTNO>
        <SUBJECT>Procedures for requests pertaining to individual records in a record system.</SUBJECT>
        <P>(a) An individual seeking notification of whether a system of records, maintained by the Defense Threat Reduction Agency, contains a record pertaining to himself/herself and who desires to review, have copies made of such records, or to be provided an accounting of disclosures from such records, shall submit his or her request in writing. Requesters are encourage to review the systems of records notices published by the Agency so as to specifically identify the particular record system(s) of interest to be accessed.</P>
        <P>(b) In addition to meeting the requirements set forth in this section 318.6, the individual seeking notification, review or copies, and an accounting of disclosures will provide in writing his or her full name, address, Social Security Number, and a telephone number where the requester can be contacted should questions arise concerning the request. This information will be used only for the purpose of identifying relevant records in response to an individual's inquiry. It is further recommended that individuals indicate any present or past relationship or affiliations, if any, with the Agency and the appropriate dates in order to facilitate a more thorough search. A notarized statement or an unsworn declaration in accordance with 28 U.S.C. 1746 may also be required.</P>
        <P>(c) An individual who wishes to be accompanied by another individual when reviewing his or her records, must provide the Agency with written consent authorizing the Agency to disclose or discuss such records in the presence of the accompanying individual.</P>
        <P>(d) Individuals should mail their written request to the FOIA/Privacy Act Division, Defense Threat Reduction Agency, 45045 Aviation Drive, Dulles, VA 20166-7517 and indicate clearly on the outer envelope “Privacy Act Request.”</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 318.7</SECTNO>
        <SUBJECT>Disclosure of requested information to individuals.</SUBJECT>
        <P>(a) The Defense Threat Reduction Agency, upon receiving a request for notification of the existence of a record or for access to a record, shall acknowledge receipt of the request within 10 working days.</P>
        <P>(b) Determine whether or not such record exists.</P>
        <P>(c) Determine whether or not such request for access is available under the Privacy Act.</P>
        <P>(d) Notify requester of determinations within 30 working days after receipt of such request.</P>
        <P>(e) Provide access to information pertaining to that person which has been determined to be available within 30 working days.</P>
        <P>(f) Notify the individual if fees will be assessed for reproducing copies of the records. Fee schedule and rules for assessing fees are contained in § 318.11.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 318.8</SECTNO>
        <SUBJECT>Request for correction or amendment to a record.</SUBJECT>
        <P>(a) An individual may request that the Defense Threat Reduction Agency correct, amend, or expunge any record, or portions thereof, pertaining to the requester that he/she believe to be inaccurate, irrelevant, untimely, or incomplete.</P>
        <P>(b) Such requests shall specify the particular portions of the records in question, be in writing and should be mailed to the FOIA/Privacy Act Division, Defense Threat Reduction Agency, 45045 Aviation Drive, Dulles, VA 20166-7517.</P>
        <P>(c) The requester shall provide sufficient information to identify the record and furnish material to substantiate the reasons for requesting corrections, amendments, or expurgation.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 318.9</SECTNO>
        <SUBJECT>Agency review of request for correction or amendment of record.</SUBJECT>
        <P>(a) The Agency will acknowledge a request for correction or amendment within 10 working days of receipt. The acknowledgment will be in writing and will indicate the date by which the Agency expects to make its initial determination.</P>
        <P>(b) The Agency shall complete its consideration of requests to correct or amend records within 30 working days, and inform the requester of its initial determination.</P>

        <P>(c) If it is determined that records should be corrected or amended in <PRTPAGE P="893"/>whole or in part, the Agency shall advise the requester in writing of its determination; and correct or amend the records accordingly. The Agency shall then advise prior recipients of the records of the fact that a correction or amendment was made and provide the substance of the change.</P>
        <P>(d) If the Agency determines that a record should not be corrected or amended, in whole or in part, as requested by the individual, the Agency shall advise the requester in writing of its refusal to correct or amend the records and the reasons therefor. The notification will inform the requester that the refusal may be appealed administratively and will advise theindividual of the procedures for such appeals.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 318.10</SECTNO>
        <SUBJECT>Appeal of initial adverse Agency determination for access, correction or amendment.</SUBJECT>
        <P>(a) An individual who disagrees with the denial or partial denial of his or her request for access, correction, or amendment of Agency records pertaining the himself/herself, may file a request for administrative review of such refusal within 30 days after the date of notification of the denial or partial denial.</P>
        <P>(b) Such requests shall be made in writing and mailed to the FOIA/Privacy Act Division, Defense Threat Reduction Agency, 45045 Aviation Drive, Dulles, VA 20166-7517.</P>
        <P>(c) The requester shall provide a brief written statement setting for the reasons for his or her disagreement with the initial determination and provide such additional supporting material as the individual feels necessary to justify the appeal.</P>
        <P>(d) Within 30 working days of receipt of the request for review, the Agency shall advise the individual of the final disposition of the request.</P>
        <P>(e) In those cases where the initial determination is reversed, the individual will be so informed and the Agency will take appropriate action.</P>
        <P>(f) In those cases where the initial determination is sustained, the individual shall be advised:</P>
        <P>(1) In the case of a request for access to a record, of theindividual's right to seek judicial review of the Agency refusal for access.</P>
        <P>(2) In the case of a request to correct or amend the record:</P>
        <P>(i) Of the individual's right to file a concise statement of his or her reasons for disagreeing with the Agency's decision in the record,</P>
        <P>(ii) Of the procedures for filing a statement of the disagreement, and</P>
        <P>(iii) Of the individual's right to seek judicial review of the Agency's refusal to correct or amend a record.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 318.11</SECTNO>
        <SUBJECT>Disclosure of record to persons other than the individual to whom it pertains.</SUBJECT>
        <P>(a) General. No record contained in a system of records maintained by DTRA shall be disclosed by any means to any person or agency within or outside the Department of Defense without the request or consent of the subject of the record, except as described in 32 CFR 310.41, Appendix C to part 310, and/or a Defense Threat Reduction Agency system of records notice.</P>
        <P>(b) Accounting of disclosures. Except for disclosures made to members of the DoD in connection with their official duties, anddisclosures required by the Freedom of Information Act, an accounting will be kept of all disclosures of records maintained in DTRA system of records.</P>
        <P>(1) Accounting entries will normally be kept on a DTRA form, which will be maintained in the record file jacket, or in a document that is part of the record.</P>
        <P>(2) Accounting entries will record the date, nature and purpose of each disclosure, and the name and address of the person or agency to whom the disclosure is made.</P>
        <P>(3) Accounting records will be maintained for at least 5 years after the last disclosure, of for the life of the record, whichever is longer.</P>
        <P>(4) Subjects of DTRA records will be given access to associated accounting records upon request, except for those disclosures made to law enforcement activities when the law enforcement activity has requested that the disclosure not be made, and/or as exempted under § 318.16.</P>
      </SECTION>
      <SECTION>
        <PRTPAGE P="894"/>
        <SECTNO>§318.12</SECTNO>
        <SUBJECT>Fees.</SUBJECT>
        <P>Individuals may request copies for retention of any documents to which they are granted access in DTRA records pertaining to them. Requesters will not be charged for the first copy of any records provided; however, duplicate copies will require a charge to cover costs of reproduction. Such charges will be computed in accordance with 32 CFR part 310.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 318.13</SECTNO>
        <SUBJECT>Enforcement actions.</SUBJECT>
        <P>Procedures and sanctions are set forth in 5 U.S.C. 552a, OMB Circular A-130, and 32 CFR part 310.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 318.14</SECTNO>
        <SUBJECT>Blanket routine uses.</SUBJECT>
        <P>(a)<E T="03"> Blanket routine uses.</E> Certain ‘blanket routine uses’ of the records have been established that are applicable to every record system maintained within the Department of Defense unless specifically stated otherwise within a particular record system. These additional blanket routine uses of the records are published only once in the interest of simplicity, economy and to avoid redundancy.</P>
        <P>(b) <E T="03">Routine Use—Law Enforcement.</E>  If a system of records maintained by a DoD Component, to carry out its functions, indicates a violation or potential violation of law, whether civil, criminal, or regulatory in nature, and whether arising by general statute or by regulation, rule, or order issued pursuant thereto, the relevant records in the system of records may be referred, as a routine use, to the agency concerned, whether Federal, State, local, or foreign, charged with the responsibility of investigating or prosecuting such violation or charged with enforcing or implementing the statute, rule, regulation, or order issued pursuant thereto.</P>
        <P>(c)<E T="03"> Routine Use—Disclosure When Requesting Information.</E>  A record from a system of records maintained by a Component may be disclosed as a routine use to a Federal, State, or local agency maintaining civil, criminal, or other relevant enforcement information or other pertinent information, such as current licenses, if necessary to obtain information relevant to a Component decision concerning the hiring or retention of an employee, the issuance of a security clearance, the letting of a contract, or the issuance of a license, grant, or other benefit.</P>
        <P>(d)<E T="03"> Routine Use—Disclosure of Requested Information.</E>  A record from a system of records maintained by a Component may be disclosed to a Federal agency, in response to its request, in connection with the hiring or retention of an employee, the issuance of a security clearance, the reporting of an investigation of an employee, the letting of a contract, or the issuance of a license, grant, or other benefit by the requesting agency, to the extent that the information is relevant and necessary to the requesting agency's decision on the matter.</P>
        <P>(e) <E T="03">Routine Use—Congressional Inquiries.</E>  Disclosure from a system of records maintained by a Component may be made to a congressional office from the record of an individual in response to an inquiry from the congressional office made at the request of that individual.</P>
        <P>(f) <E T="03">Routine Use—Private Relief Legislation.</E>  Relevant information contained in all systems of records of the Department of Defense published on or before August 22, 1975, will be disclosed to the OMB in connection with the review of private relief legislation as set forth in OMB Circular A-19 at any stage of the legislative coordination and clearance process as set forth in that Circular.</P>
        <P>(g) <E T="03">Routine Use—Disclosures Required by International Agreements.</E>  A record from a system of records maintained by a Component may be disclosed to foreign law enforcement, security, investigatory, or administrative authorities to comply with requirements imposed by, or to claim rights conferred in, international agreements and arrangements including those regulating the stationing and status in foreign countries of DoD military and civilian personnel.</P>
        <P>(h) <E T="03">Routine Use—Disclosure to State and Local Taxing Authorities.</E>  Any information normally contained in Internal Revenue Service (IRS) Form W-2 which is maintained in a record from a system of records maintained by a Component may be disclosed to State and local taxing authorities with which the Secretary of the Treasury has entered into agreements under 5 U.S.C. 5516, 5517, and 5520 and only to those State <PRTPAGE P="895"/>and local taxing authorities for which an employee or military member is or was subject to tax regardless of whether tax is or was withheld. This routine use is in accordance with Treasury Fiscal Requirements Manual Bulletin No. 76-07.</P>
        <P>(i) <E T="03">Routine Use—Disclosure to the Office of Personnel Management.</E>  A record from a system of records subject to the Privacy Act and maintained by a Component may be disclosed to the Office of Personnel Management (OPM) concerning information on pay and leave, benefits, retirement deduction, and any other information necessary for the OPM to carry out its legally authorized government-wide personnel management functions and studies.</P>
        <P>(j) <E T="03">Routine Use—Disclosure to the Department of Justice for Litigation.</E>  A record from a system of records maintained by this component may be disclosed as a routine use to any component of the Department of Justice for the purpose of representing the Department of Defense, or any officer, employee or member of the Department in pending or potential litigation to which the record is pertinent.</P>
        <P>(k) <E T="03">Routine Use—Disclosure to Military Banking Facilities Overseas.</E>  Information as to current military addresses and assignments may be provided to military banking facilities who provide banking services overseas and who are reimbursed by the Government for certain checking and loan losses. For personnel separated, discharged, or retired from the Armed Forces, information as to last known residential or home of record address may be provided to the military banking facility upon certification by a banking facility officer that the facility has a returned or dishonored check negotiated by the individual or the individual has defaulted on a loan and that if restitution is not made by the individual, the U.S. Government will be liable for the losses the facility may incur.</P>
        <P>(l) <E T="03">Routine Use—Disclosure of Information to the General Services Administration (GSA).</E>  A record from a system of records maintained by this component may be disclosed as a routine use to the General Services Administration (GSA) for the purpose of records management inspections conducted under authority of 44 U.S.C. 2904 and 2906.</P>
        <P>(m) <E T="03">Routine Use—Disclosure of Information to the National Archives and Records Administration (NARA).</E>  A record from a system of records maintained by this component may be disclosed as a routine use to the National Archives and Records Administration (NARA) for the purpose of records management inspections conducted under authority of 44 U.S.C. 2904 and 2906.</P>
        <P>
          <E T="03">(n) Routine Use—Disclosure to the Merit Systems Protection Board.</E>  A record from a system of records maintained by this component may be disclosed as a routine use to the Merit Systems Protection Board, including the Office of the Special Counsel for the purpose of litigation, including administrative proceedings, appeals, special studies of the civil service and other merit systems, review of OPM or component rules and regulations, investigation of alleged or possible prohibited personnel practices; including administrative proceedings involving any individual subject of a DoD investigation, and such other functions, promulgated in 5 U.S.C. 1205 and 1206, or as may be authorized by law.</P>
        <P>(o) <E T="03">Routine Use—Counterintelligence Purpose.</E>  A record from a system of records maintained by this component may be disclosed as a routine use outside the DoD or the U.S. Government for the purpose of counterintelligence activities authorized by U.S. Law or Executive Order or for the purpose of enforcing laws which protect the national security of the United States.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 318.15</SECTNO>
        <SUBJECT>Rules of conduct</SUBJECT>
        <P>(a) DTRA personnel shall:</P>
        <P>(1) Take such actions, as considered appropriate, to ensure that personal information contained in a system of records, to which they have access or are using incident to the conduct of official business, shall be protected so that the security and confidentiality of the information shall be preserved.</P>

        <P>(2) Not disclose any personal information contained in any system of records except as authorized by 32 CFR part 310 or other applicable law or regulation. Personnel willfully making such a disclosure when knowing the disclosure is prohibited are subject to <PRTPAGE P="896"/>possible criminal penalties and/or administrative sanctions.</P>
        <P>(3) Report any unauthorized disclosure of personal information from a system of records or the maintenance of any system of records that are not authorized by the Instruction to the DTRA Privacy Act Officer.</P>
        <P>(b) DTRA system managers for each system of records shall:</P>
        <P>(1) Ensure that all personnel who either have access to the system of records or who shall develop or supervise procedures for the handling of records in the system of records shall be aware of their responsibilities for protecting personnel information being collected and maintained under the DTRA Privacy Program.</P>
        <P>(2) Promptly notify the Privacy Act Officer of any required new, amended, or altered system notices for the system of records.</P>
        <P>(3) Not maintain any official files on individuals, which are retrieved by name or other personal identifier without first ensuring that a notice for the system of records shall have been published in the “Federal Register.” Any official who willfully maintains a system of records without meeting the publication requirements, as prescribed by 5 U.S.C. 552a, OMB Circular A-130, and 32 CFR part 310, is subject to possible criminal penalties and/or administrative sanctions.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 318.16</SECTNO>
        <SUBJECT>Exemption rules.</SUBJECT>
        <P>(a) <E T="03">Exemption for classified material.</E> All systems of records maintained by the Defense Threat Reduction Agency shall be exempt under section (k)(1) of 5 U.S.C. 552a, to the extent that the systems contain any information properly classified under E.O. 12598 and that is required by that E.O. to be kept secret in the interest of national defense or foreign policy. This exemption is applicable to parts of all systems of records including those not otherwise specifically designated for exemptions herein which contain isolated items of properly classified information.</P>
        <P>(b) <E T="03">System identifier and name:</E> HDTRA 007, Security Operations.</P>
        <P>(1) Exemption: Portions of this system of records may be exempt from the provisions of 5 U.S.C. 552a(c)(3), (d)(1) through (d)(4), (e)(1), (e)(4)(G), (H), (I), and (f).</P>
        <P>(2) Authority: 5 U.S.C. 552a(k)(5).</P>
        <P>(3) Reasons: (i) From subsection (c)(3) because it will enable DTRA to safeguard certain investigations and relay law enforcement information without compromise of the information, and protect the identities of confidential sources who might not otherwise come forward and who have furnished information under an express promise that the sources' identity would be held in confidence (or prior to the effective date of the Act, under an implied promise.)</P>
        <P>(ii) From subsection (d)(1) through (d)(4) and (f) because providing access to records of a civil investigation and the right to contest the contents of those records and force changes to be made to the information contained therein would seriously interfere with and thwart the orderly and unbiased conduct of security investigations. Providing access rights normally afforded under the Privacy Act would provide the subject with valuable information that would allow interference with or compromise of witnesses or render witnesses reluctant to cooperate; lead to suppression, alteration, or destruction of evidence; and result in the secreting of or other disposition of assets that would make them difficult or impossible to reach in order to satisfy any Government claim growing out of the investigation or proceeding.</P>
        <P>(iii) From subsection (e)(1), (e)(4)(G), (H), (I) because it will provide protection against notification of investigatory material including certain reciprocal investigations and counterintelligence information, which might alert a subject to the fact that an investigation of that individual is taking place, and the disclosure of which would weaken the on-going investigation, reveal investigatory techniques, and place confidential informants in jeopardy who furnished information; under an express promise that the sources' identity would be held in confidence (or prior to the effective date of the Act, under an implied promise.)</P>
        <P>(c) <E T="03">System identifier and name:</E> HDTRA 011, Inspector General Investigation Files.<PRTPAGE P="897"/>
        </P>
        <P>(1) Exemption: Portions of this system of records may be exempt from the provisions of 5 U.S.C. 552a(c)(3); (d)(1) through (4); (e)(1); (e)(4)(G), (H), and (I); and (f).</P>
        <P>(2) Authority: 5 U.S.C. 552a(k)(2).</P>
        <P>(3) Reasons: (i) From subsection (c)(3) because it will enable DTRA to conduct certain investigations and relay law enforcement information without compromise of the information, protection of investigative techniques and efforts employed, and identities of confidential sources who might not otherwise come forward and who furnished information under an express promise that the sources' identity would be held in confidence (or prior to the effective date of the Act, under an implied promise.)</P>
        <P>(ii) From subsection (d)(1) through (d)(4) and (f) because providing access to records of a civil investigation and the right to contest the contents of those records and force changes to be made to the information contained therein would seriously interfere with and thwart the orderly and unbiased conduct of the investigation and impede case preparation. Providing access rights normally afforded under the Privacy Act would provide the subject with valuable information that would allow interference with or compromise of witnesses or render witnesses reluctant to cooperate; lead to suppression, alteration, or destruction of evidence; and result in the secreting of or other disposition of assets that would make them difficult or impossible to reach in order to satisfy any Government claim growing out of the investigation or proceeding.</P>
        <P>(iii) From subsection (e)(1), (e)(4)(G), (H), and (I) because it will provide protection against notification of investigatory material including certain reciprocal investigations and counterintelligence information, which might alert a subject to the fact that an investigation of that individual is taking place, and the disclosure of which would weaken the on-going investigation, reveal investigatory techniques, and place confidential informants in jeopardy who furnished information under an express promise that the sources' identity would be held in confidence (or prior to the effective date of the Act, under an implied promise).</P>
      </SECTION>
    </PART>
    <PART>
      <EAR>Pt. 319</EAR>
      <HD SOURCE="HED">PART 319—DEFENSE INTELLIGENCE AGENCY PRIVACY PROGRAM</HD>
      <CONTENTS>
        <SECHD>Sec.</SECHD>
        <SECTNO>319.1</SECTNO>
        <SUBJECT>Authority.</SUBJECT>
        <SECTNO>319.2</SECTNO>
        <SUBJECT>Purpose.</SUBJECT>
        <SECTNO>319.3</SECTNO>
        <SUBJECT>Scope.</SUBJECT>
        <SECTNO>319.4</SECTNO>
        <SUBJECT>Definitions.</SUBJECT>
        <SECTNO>319.5</SECTNO>
        <SUBJECT>Procedures for requests pertaining to individual records in a record system.</SUBJECT>
        <SECTNO>319.6</SECTNO>
        <SUBJECT>Disclosure of requested information to individuals.</SUBJECT>
        <SECTNO>319.7</SECTNO>
        <SUBJECT>Special procedures: Medical records.</SUBJECT>
        <SECTNO>319.8</SECTNO>
        <SUBJECT>Request for correction or amendment to record.</SUBJECT>
        <SECTNO>319.9</SECTNO>
        <SUBJECT>Agency review of request for correction or amendment of record.</SUBJECT>
        <SECTNO>319.10</SECTNO>
        <SUBJECT>Appeal of initial adverse Agency determination for access, correction or amendment.</SUBJECT>
        <SECTNO>319.11</SECTNO>
        <SUBJECT>Fees.</SUBJECT>
        <SECTNO>319.12</SECTNO>
        <SUBJECT>General exemptions. [Reserved]</SUBJECT>
        <SECTNO>319.13</SECTNO>
        <SUBJECT>Specific exemptions.</SUBJECT>
      </CONTENTS>
      <AUTH>
        <HD SOURCE="HED">Authority:</HD>
        <P>Pub. L. 93-579, 88 Stat 1896 (5 U.S.C. 552a).</P>
      </AUTH>
      <SOURCE>
        <HD SOURCE="HED">Source:</HD>
        <P>51 FR 44064, Dec. 8, 1986, unless otherwise noted. Redesignated at 56 FR 56595, Nov. 6, 1991 and 56 FR 57799, Nov. 14, 1991.</P>
      </SOURCE>
      <SECTION>
        <SECTNO>§ 319.1</SECTNO>
        <SUBJECT>Authority.</SUBJECT>
        <P>Pursuant to the requirements of section 553 of Title 5 of the United States Code, the Defense Intelligence Agency promulgates its rules for the implementation of the Privacy Act of 1974, Pub. L. 93-579, 5 U.S.C. 552a (f) and (k).</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 319.2</SECTNO>
        <SUBJECT>Purpose.</SUBJECT>
        <P>(a) To promulgate rules providing procedures by which individuals may exercise their rights granted by the act to:</P>
        <P>(1) Determine whether a Defense Intelligence Agency system of records contains a record pertaining to themselves;</P>
        <P>(2) Be granted access to all or portions thereof;</P>
        <P>(3) Request administrative correction or amendment of such records;</P>
        <P>(4) Request an accounting of disclosures from such records; and</P>
        <P>(5) Appeal any adverse determination for access or correction/amendment of records.</P>

        <P>(b) To set forth Agency policy and fee schedule for cost of duplication.<PRTPAGE P="898"/>
        </P>
        <P>(c) To identify records subject to the provisions of these rules.</P>
        <P>(d) To specify those systems of records for which the Director, Defense Intelligence Agency, claims an exemption.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 319.3</SECTNO>
        <SUBJECT>Scope.</SUBJECT>
        <P>(a) Any individual who is a citizen of the United States or an alien lawfully admitted for permanent residence in the United States may submit an inquiry to the Defense Intelligence Agency.</P>
        <P>(b) These rules apply to those systems of records:</P>
        <P>(1) Maintained by the Defense Intelligence Agency;</P>
        <P>(2) For which the Defense Intelligence Agency prescribes the content and disposition pursuant to statute or executive order of the President, which may be in the physical custody of another Federal agency;</P>
        <P>(3) Not exempted from certain provisions of the act by the Director, Defense Intelligence Agency.</P>
        <P>(c) The Defense Intelligence Agency may have physical custody of the official records of another Federal agency which exercises dominion and control over the records, their content, and access thereto. In such cases, the Defense Intelligence Agency maintenance of the records is considered subject to the rules of the other Federal agency. Except for a request for a determination of the existence of the record, when the Defense Intelligence Agency receives requests related to these records, the DIA will immediately refer the request to the controlling agency for all decisions regarding the request and will notify the individual making the request of the referral.</P>
        <P>(d) Records subject to provisions of the Act which are transferred to the Washington National Records Center for storage shall be considered to be maintained by the Defense Intelligence Agency. Disclosure from such records—to other than an element of the Defense Intelligence Agency—can only be made with the prior approval of the Defense Intelligence Agency.</P>
        <P>(e) Records subject to provisions of the act which are transferred to the National Archives shall be considered to be maintained by the National Archives and are no longer records of the Agency.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 319.4</SECTNO>
        <SUBJECT>Definitions.</SUBJECT>
        <P>(a) All terms used in this part which are defined in 5 U.S.C. 552a shall have the same meaning herein.</P>
        <P>(b) As used in this part:</P>
        <P>(1) The term <E T="03">Act</E> means the Privacy Act of 1974, Pub. L. 93-579, 5 U.S.C. 552a.</P>
        <P>(2) The term <E T="03">Agency</E> means the Defense Intelligence Agency.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 319.5</SECTNO>
        <SUBJECT>Procedures for requests pertaining to individual records in a record system.</SUBJECT>
        <P>(a) An individual seeking notification of whether a system of records, maintained by the Defense Intelligence Agency, contains a record pertaining to himself/herself and who desires to review, have copies made of such records, or to be provided an accounting of disclosures from such records, shall submit his or her request in writing. Requesters are encouraged to review the systems of records notices published by the Agency so as to specifically identify the particular record system(s) of interest to be accessed.</P>
        <P>(b) In addition to meeting the requirements set forth in § 319.5 of this part, the individual seeking notification, review or copies, and an accounting of disclosures will provide in writing his or her full name, address, social security account number or date of birth and a telephone number where the requester can be contacted should questions arise concerning his or her request. This information will be used only for the purpose of identifying relevant records in response to an individual's inquiry. It is further recommended that individuals indicate any present or past relationship or affiliations, if any, with the Agency and the appropriate dates in order to facilitate a more thorough search of the record system specified and any other system which may contain information concerning the individual. A signed notarized statement may also be required.</P>

        <P>(c) An individual who wishes to be accompanied by another individual when reviewing his or her records, must provide the Agency with written consent authorizing the Agency to disclose or <PRTPAGE P="899"/>discuss such records in the presence of the accompanying individual.</P>
        <P>(d) A request for medical records must be submitted as set forth in § 319.7, of this part.</P>
        <P>(e) Individuals should mail their written request to the Defense Intelligence Agency, DSP-1A, Washington, DC 20340-3299 and indicate clearly on the outer envelope “Privacy Act Request”.</P>
        <P>(f) An individual who makes a request on behalf of a minor or legal incompetent shall provide a signed notarized statement affirming the relationship.</P>
        <P>(g) When an individual wishes to authorize another person access to his or her records, the individual shall provide a signed notarized statement authorizing and consenting to access by the designated person.</P>
        <P>(h) Except as provided by section 552a(b) of the act, 5 U.S.C. 552a(b), the written request or prior written consent of the individual to whom a record pertains shall be required before such record is disclosed to any person or to another agency outside the Department of Defense.</P>
        <P>(i) Any person who knowingly and willfully requests or obtains any record concerning an individual from this Agency under false pretenses shall be guilty of a misdemeanor and fined not more than $5,000.</P>
        <CITA>[51 FR 44064, Dec. 8, 1986. Redesignated at 56 FR 56595, Nov. 6, 1991 and 56 FR 57799, Nov. 14, 1991, and amended at 56 FR 56595, Nov. 6, 1991]</CITA>
      </SECTION>
      <SECTION>
        <SECTNO>§ 319.6</SECTNO>
        <SUBJECT>Disclosure of requested information to individuals.</SUBJECT>
        <P>The Defense Intelligence Agency, upon receiving a request for notification of the existence of a record or for access to a record, shall:</P>
        <P>(a) Determine whether such record exists;</P>
        <P>(b) Determine whether access is available under the Privacy Act;</P>
        <P>(c) Notify the requester of those determinations within 10 days (excluding Saturday, Sunday and legal public holidays); and</P>
        <P>(d) Provide access to information pertaining to that person which has been determined to be available.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 319.7</SECTNO>
        <SUBJECT>Special procedures: Medical records.</SUBJECT>
        <P>Medical records, requested pursuant to § 319.5 of this part, will be disclosed to the requester unless the disclosure of such records directly to the requester could, in the judgment of a physician, have an adverse effect on the physical or mental health or safety and welfare of the requester or other persons with whom he may have contact. In such an instance, the information will be transmitted to a physician named by the requester or to a person qualified to make a psychiatric or medical determination.</P>
        <CITA>[51 FR 44064, Dec. 8, 1986. Redesignated at 56 FR 56595, Nov. 6, 1991 and 56 FR 57799, Nov. 14, 1991, and amended at 56 FR 56595, Nov. 6, 1991]</CITA>
      </SECTION>
      <SECTION>
        <SECTNO>§ 319.8</SECTNO>
        <SUBJECT>Request for correction or amendment to record.</SUBJECT>
        <P>(a) An individual may request that the Defense Intelligence Agency correct, amend, or expunge any record, or portions thereof, pertaining to the requester that he believes to be inaccurate, irrelevant, untimely, or incomplete.</P>
        <P>(b) Such requests shall be in writing and may be mailed to DSP-1A as indicated in § 319.5.</P>
        <P>(c) The requester shall provide sufficient information to identify the record and furnish material to substantiate the reasons for requesting corrections, amendments or expurgation.</P>
        <CITA>[51 FR 44064, Dec. 8, 1986. Redesignated at 56 FR 56595, Nov. 6, 1992 and 56 FR 57799, Nov. 14, 1991, and amended at 56 FR 56595, Nov. 6, 1991]</CITA>
      </SECTION>
      <SECTION>
        <SECTNO>§ 319.9</SECTNO>
        <SUBJECT>Agency review of request for correction or amendment of record.</SUBJECT>
        <P>(a) The Agency will acknowledge a request for correction or amendment of a record within 10 days (excluding Saturday, Sunday, and legal public holidays) of receipt. The acknowledgment will be in writing and will indicate the date by which the Agency expects to make its initial determination.</P>

        <P>(b) The Agency shall complete its consideration of requests to correct or amend records within 30 days (excluding Saturday, Sunday, and legal holidays) and inform the requester of its initial determination.<PRTPAGE P="900"/>
        </P>
        <P>(c) If it is determined that records should be corrected or amended in whole or in part, the Agency shall advise the requester in writing of its determination; and correct or amend the records accordingly. The Agency shall then advise prior recipients of the records of the fact that a correction or amendment was made and provide the substance of the change.</P>
        <P>(d) If the Agency determines that a record should not be corrected or amended, in whole or in part, as requested by the individual, the Agency shall advise the requester in writing of its refusal to correct or amend the records and the reasons therefor. The notification will inform the requester that the refusal may be appealed administratively and will advise the individual of the procedures for such appeals.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 319.10</SECTNO>
        <SUBJECT>Appeal of initial adverse Agency determination for access, correction or amendment.</SUBJECT>
        <P>(a) An individual who disagrees with the denial or partial denial of his or her request for access, correction, or amendment of Agency records pertaining to himself/herself, may file a request for administrative review of such refusal within 30 days after the date of notification of the denial or partial denial.</P>
        <P>(b) Such requests should be in writing and may be mailed to RTS-1 as indicated in § 319.5.</P>
        <P>(c) The requester shall provide a brief written statement setting forth the reasons for his or her disagreement with the initial determination and provide such additional supporting material as the individual feels necessary to justify his or her appeal.</P>
        <P>(d) Within 30 days (excluding Saturday, Sunday, and legal public holidays) of the receipt of request for review, the Agency shall advise the individual of the final disposition of his or her request.</P>
        <P>(e) In those cases where the initial determination is reversed, the individual will be so informed and the Agency will take appropriate action.</P>
        <P>(f) In those cases where the initial determinations are sustained, the individual shall be advised:</P>
        <P>(1) In the case of a request for access to a record, of the individual's right to seek judicial review of the Agency refusal for access.</P>
        <P>(2) In the case of a request to correct or amend the record:</P>
        <P>(i) Of the individual's right to file with record in question a concise statement of his or her reasons for disagreeing with the Agency's decision,</P>
        <P>(ii) Of the procedures for filing a statement of disagreement, and</P>
        <P>(iii) Of the individual's right to seek judicial review of the Agency's refusal to correct or amend a record.</P>
        <CITA>[51 FR 44064, Dec. 8, 1986. Redesignated at 56 FR 56595, Nov. 6, 1991 and 56 FR 57799, Nov. 14, 1991, and amended at 56 FR 56595, Nov. 6, 1991]</CITA>
      </SECTION>
      <SECTION>
        <SECTNO>§ 319.11</SECTNO>
        <SUBJECT>Fees.</SUBJECT>

        <P>(a) The schedule of fees chargeable is contained at § 286.60 <E T="03">et seq.</E> As a component of the Department of Defense, the applicable published Departmental rules and schedules with respect to fees will also be the policy of DIA.</P>
        <P>(b) Current employees of the Agency will not be charged for the first copy of a record provided by the Agency.</P>
        <P>(c) In the absence of an agreement to pay required anticipated costs, the time for responding to a request begins on resolution of this agreement to pay.</P>
        <P>(d) The fees may be paid by check, draft or postal money order payable to the Treasurer of the United States. Remittance will be forwarded to the office designated in § 319.5(e).</P>
        <CITA>[51 FR 44064, Dec. 8, 1986. Redesignated at 56 FR 56595, Nov. 6, 1991 and 56 FR 57799, Nov. 14, 1991, and amended at 56 FR 56595, Nov. 6, 1991]</CITA>
      </SECTION>
      <SECTION>
        <SECTNO>§ 319.12</SECTNO>
        <SUBJECT>General exemptions. [Reserved]</SUBJECT>
      </SECTION>
      <SECTION>
        <SECTNO>§ 319.13</SECTNO>
        <SUBJECT>Specific exemptions.</SUBJECT>

        <P>(a) All systems of records maintained by the Director Intelligence Agency shall be exempt from the requirements of 5 U.S.C. 552a(d) pursuant to 5 U.S.C. 552a(k)(1) to the extent that the system contains any information properly classified under Executive order to be kept secret in the interest of national defense or foreign policy. This exemption, which may be applicable to parts of all systems of records, is necessary <PRTPAGE P="901"/>because certain record systems not specifically designated for exemption may contain isolated information which has been properly classified.</P>
        <P>(b) The Director, Defense Intelligence Agency, designated the systems of records listed below for exemptions under the specified provisions of the Privacy Act of 1974, as amended (Pub. L. 93-579):</P>
        <P>(c) <E T="03">System identification and name:</E> LDIA 0271, Investigations and Complaints.</P>
        <P>(1) <E T="03">Exemption:</E> Any portion of this record system which falls within the provisions of 5 U.S.C. 552a(k) (2) and (5) may be exempt from the following subsections of 5 U.S.C. 552a: (c)(3), (d), (e)(1), (e)(4)(G), (e)(4)(H), and (e)(4)(I).</P>
        <P>(2) <E T="03">Authority:</E> 5 U.S.C. 552a(k) (2) and (5).</P>
        <P>(3) <E T="03">Reasons:</E> The reasons for asserting these exemptions are to ensure the integrity of the Inspector General process within the Agency. The execution requires that information be provided in a free and open manner without fear of retribution or harassment in order to facilitate a just, thorough and timely resolution of the complaint or inquiry. Disclosures from this system can enable individuals to conceal their wrongdoing or mislead the course of the investigation by concealing, destroying or fabricating evidence or documents. Also, disclosures can subject sources and witnesses to harassment or intimidation which may cause individuals not to seek redress for wrongs through Inspector General channels for fear of retribution or harassment.</P>
        <P>(d) <E T="03">System identification and name:</E> LDIA 0275, DoD Hotline Referrals.</P>
        <P>(1) <E T="03">Exemption:</E> Any portion of this record system which falls within the provisions of 5 U.S.C. 552a(k) (2) and (5) may be exempt from the following subsections of 5 U.S.C. 552a: (c)(3), (d), (e)(1), (e)(4)(G), (e)(4)(H), and (e)(4)(I).</P>
        <P>(2) <E T="03">Authority:</E> 5 U.S.C. 552a(k) (2) and (5).</P>
        <P>(3) <E T="03">Reason:</E> The reasons for asserting these exemptions are to ensure that informants can report instances of fraud and mismanagement without fear of reprisal or unauthorized disclosure of their identity. The execution of this function requires that information be provided in a free and open manner without fear of retribution of harassment in order to facilitate a just, thorough and timely resolution of the case. These records are privileged Director, DIA, documents and information contained therein is not routinely released or disclosed to anyone.</P>
        <P>(e) <E T="03">System identification and name:</E> LDIA 0660, Security Files.</P>
        <P>(1) <E T="03">Exemption:</E> Any portion of this record system which falls within the provisions of 5 U.S.C. 552a(k) (2) and (5) may be exempt from the following subsections of 5 U.S.C. 552a: (c)(3), (d), (e)(1), (e)(4)(G), (e)(4)(H), and (e)(4)(I).</P>
        <P>(2) <E T="03">Authority:</E> 5 U.S.C. 552a(k) (2) and (5).</P>
        <P>(3) <E T="03">Reason:</E> The reasons for asserting these exemptions are to ensure the integrity of the adjudication process used by the Agency to determine the suitability, eligibility or qualification for Federal service with the Agency and to make determinations concerning the questions of access to classified materials and activities. The proper execution of this function requires that the Agency have the ability to obtain candid and necessary information in order to fully develop or resolve pertinent information developed in the process. Potential sources, out of fear or retaliation, exposure or other action, may be unwilling to provide needed information or may not be sufficiently frank to be a value in personnel screening, thereby seriously interfering with the proper conduct and adjudication of such matters.</P>
        <P>(f) <E T="03">System identification and name:</E> LDIA 0800, Operation Record System.</P>
        <P>(1) <E T="03">Exemption:</E> Any portion of this record system which falls within the provisions of 5 U.S.C. 552a(k) (2) and (5) may be exempt from the following subsections of 5 U.S.C. 552a: (c)(3), (d), (e)(1), (e)(4)(G), (e)(4)(H), and (e)(4)(I).</P>
        <P>(2) <E T="03">Authority:</E> 5 U.S.C. 552a(k) (2) and (5).</P>
        <P>(3) <E T="03">Reason:</E> The reasons for asserting these exemptions are to ensure the integrity of ongoing foreign intelligence collection and/or training activities conducted by the Defense Intelligence Agency and the Department of Defense. The execution of these functions requires that information in response to national level intelligence requirements be provided in a free and open <PRTPAGE P="902"/>manner without fear of retribution or unauthorized disclosure. Disclosures from this system can jeopardize sensitive sources and methodology.</P>
        <CITA>[56 FR 56595, Nov. 6, 1991]</CITA>
      </SECTION>
    </PART>
    <PART>
      <EAR>Pt. 320</EAR>
      <HD SOURCE="HED">PART 320—NATIONAL IMAGERY AND MAPPING AGENCY PRIVACY PROGRAM</HD>
      <CONTENTS>
        <SECHD>Sec.</SECHD>
        <SECTNO>320.1</SECTNO>
        <SUBJECT>Purpose and scope.</SUBJECT>
        <SECTNO>320.2</SECTNO>
        <SUBJECT>Definitions.</SUBJECT>
        <SECTNO>320.3</SECTNO>
        <SUBJECT>Responsibilities.</SUBJECT>
        <SECTNO>320.4</SECTNO>
        <SUBJECT>Procedures for requesting information.</SUBJECT>
        <SECTNO>320.5</SECTNO>
        <SUBJECT>Disclosure of requested information.</SUBJECT>
        <SECTNO>320.6</SECTNO>
        <SUBJECT>Requests for correction or amendment to record.</SUBJECT>
        <SECTNO>320.7</SECTNO>
        <SUBJECT>Agency review of request for correction or amendment of record.</SUBJECT>
        <SECTNO>320.8</SECTNO>
        <SUBJECT>Appeal of initial adverse agency determination on correction or amendment.</SUBJECT>
        <SECTNO>320.9</SECTNO>
        <SUBJECT>Disclosure of record to person other than the individual to whom it pertains.</SUBJECT>
        <SECTNO>320.10</SECTNO>
        <SUBJECT>Fees.</SUBJECT>
        <SECTNO>320.11</SECTNO>
        <SUBJECT>Penalties.</SUBJECT>
        <SECTNO>320.12</SECTNO>
        <SUBJECT>Exemptions.</SUBJECT>
      </CONTENTS>
      <AUTH>
        <HD SOURCE="HED">Authority:</HD>
        <P>Pub. L. 93-579, 88 Stat. 1986 (5 U.S.C. 552a).</P>
      </AUTH>
      <SOURCE>
        <HD SOURCE="HED">Source:</HD>
        <P>66 FR 52681, Oct. 17, 2001, unless otherwise noted.</P>
      </SOURCE>
      <SECTION>
        <SECTNO>§ 320.1</SECTNO>
        <SUBJECT>Purpose and scope.</SUBJECT>
        <P>(a) This part is published pursuant to the Privacy Act of 1974, as amended (5 U.S.C. 552a), (hereinafter the “Privacy Act”). This part:</P>
        <P>(1) Establishes or advises of the procedures whereby an individual can:</P>
        <P>(i) Request notification of whether the National Imagery and Mapping Agency (NIMA) maintains or has disclosed a record pertaining to him in any nonexempt system of records,</P>
        <P>(ii) Request a copy or other access to such a record or to an accounting of its disclosure,</P>
        <P>(iii) Request that the record be amended and</P>
        <P>(iv) Appeal any initial adverse determination of any such request;</P>
        <P>(2) Specifies those systems of records which the Director, Headquarters NIMA has determined to be exempt from the procedures established by this regulation and from certain provisions of the Privacy Act. NIMA policy encompasses the safeguarding of individual privacy from any misuse of NIMA records and the provision of the fullest access practicable to individuals to NIMA records concerning them.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 320.2</SECTNO>
        <SUBJECT>Definitions.</SUBJECT>
        <P>As used in this part:</P>
        <P>(a) <E T="03">Appellate authority (AA).</E> A NIMA employee who has been granted authority to review the decision of the Initial Denial Authority (IDA) that has been appealed by the Privacy Act requester and make the appeal determination for NIMA on the release ability of the records in question.</P>
        <P>(b) <E T="03">Individual.</E> A living person who is a citizen of the United States or an alien lawfully admitted for permanent residence. The parent of a minor or the legal guardian of any individual also may act on behalf of an individual. Corporations, partnerships, sole proprietorships, professional groups, businesses, whether incorporated or unincorporated, and other commercial entities are not “individuals”.</P>
        <P>(c) <E T="03">Initial denial authority (IDA).</E> A NIMA employee, or designee, who has been granted authority to make an initial determination for NIMA that records requested in a Privacy Act request should be withheld from disclosure or release.</P>
        <P>(d) <E T="03">Maintain.</E> Includes maintain, collect, use or disseminate.</P>
        <P>(e) <E T="03">Personal information.</E> Information about an individual that identifies, relates to or is unique to, or describes him or her; e.g., a social security number, age, military rank, civilian grade, marital status, race, or salary, home/office phone numbers, etc.</P>
        <P>(f) <E T="03">Record.</E> Any item, collection, or grouping of information, whatever the storage media (e.g., paper, electronic, etc.), about an individual that is maintained by NIMA, including, but not limited to education, financial transactions, medical history, criminal or employment history, and that contains the individual's name or the identifying number, symbol or other identifying particulars assigned to the individual such as a finger or voice print or a photograph.</P>
        <P>(g) <E T="03">Routine use.</E> The disclosure of a record outside the Department of Defense for a use that is compatible with the purpose for which the information was collected and maintained by the Department of Defense. The routine <PRTPAGE P="903"/>use must be included in the published system notice for the system of records involved.</P>
        <P>(h) <E T="03">System of records.</E> A group of records under the control of NIMA from which personal information is retrieved by the individual's name or by some identifying number, symbol, or other identifying particular assigned to the individual.</P>
        <P>(i)<E T="03"> System manger.</E> The NIMA official who is responsible for the operation and management of a system of records.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 320.3</SECTNO>
        <SUBJECT>Responsibilities.</SUBJECT>
        <P>(a) Director of NIMA:</P>
        <P>(1) Implements the NIMA privacy program.</P>
        <P>(2) Designates the Director of the Public Affairs Office as the NIMA Initial Denial Authority;</P>
        <P>(3) Designates the Chief of Staff as the Appellate Authority.</P>
        <P>(4) Designates the General Counsel as the NIMA Privacy Act Officer and the principal point of contact for matters involving the NIMA privacy program.</P>
        <P>(b) NIMA General Counsel:</P>

        <P>(1) Oversees systems of records maintained throughout NIMA, administered by Information Services. This includes coordinating all notices of new systems of records and changes to existing systems for publication in the <E T="04">Federal Register</E>.</P>
        <P>(2) Coordinates all denials of requests for access to or amendment of records.</P>
        <P>(3) Assesses and collects fees for costs associated with processing Privacy Act requests and approves or denies requests for fee waivers. Fees collected are forwarded through Financial Management Directorate to the U.S. Treasury.</P>
        <P>(4) Prepares the annual report to the Defense Privacy Office.</P>
        <P>(5) Oversees investigations of allegations of unauthorized maintenance, disclosure, or destruction of records.</P>
        <P>(6) Conducts or coordinates Privacy Act training for NIMA personnel as needed, including training for public affairs officers and others who deal with the public and news media.</P>
        <P>(c) NIMA System Managers:</P>
        <P>(1) Ensure that all personnel who either have access to a system of records or who are engaged in developing or supervising procedures for handling records in a system of records are aware of their responsibilities for protecting personal information.</P>

        <P>(2) Prepare notices of new systems of records and changes to existing systems for publication in the <E T="04">Federal Register</E>.</P>
        <P>(3) Ensure that no records subject to this part are maintained for which a systems notice has not been published.</P>
        <P>(4) Respond to requests by individuals for access, correction, or amendment to records maintained pursuant to the NIMA privacy program.</P>
        <P>(5) Provide recommendations to General Counsel for responses to requests from individuals for access, correction, or amendment to records.</P>
        <P>(6) Safeguard records to ensure that they are protected from unauthorized alteration or disclosure.</P>
        <P>(7) Dispose of records in accordance with accepted records management practices to prevent inadvertent compromise. Disposal methods such as tearing, burning, melting, chemical decomposition, pulping, pulverizing, shredding, or mutilation are considered adequate if the personal data is rendered unrecognizable or beyond reconstruction.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 320.4</SECTNO>
        <SUBJECT>Procedures for requesting information.</SUBJECT>
        <P>(a) Upon request in person or by mail, any individual, as defined in § 320.2, shall be informed whether or not any NIMA system of records contains a record pertaining to him.</P>
        <P>(b) Any individual requesting such information in person may appear at NIMA General Counsel Office (refer to the NIMA address list at paragraph (e) of this section) or at the NIMA office thought to maintain the record in question and shall provide:</P>
        <P>(1) Information sufficient to identify the record, e.g., the individual's own name, date of birth, place of birth, and, if possible, an indication of the type of record believed to contain information concerning the individual, and</P>

        <P>(2) Acceptable identification to verify the individual's identity, e.g., driver's license, employee identification card or Medicare card.<PRTPAGE P="904"/>
        </P>
        <P>(c) Any individual requesting such information by mail shall address the request to the Office of General Counsel (refer to paragraph (e) of this section) or NIMA office thought to maintain the record in question and shall include in such request the following:</P>
        <P>(1) Information sufficient to identify the record, e.g., the individual's own name, date of birth, place of birth, and, if possible, an indication of the type of record believed to contain information concerning the individual, and</P>
        <P>(2) A notarized statement or unsworn declaration in accordance with 28 U.S.C. 1746 to verify the individual's identity, if, in the opinion of the NIMA system manager, the sensitivity of the material involved warrants.</P>
        <P>(d) NIMA procedures on requests for information. Upon receipt of a request for information made in accordance with these regulations, notice of the existence or nonexistence of any records described in such requests will be furnished to the requesting party within ten working days of receipt.</P>
        <P>(e) Written requests for access to records should be sent to NIMA Bethesda, ATTN: NIMA/GC, Mail Stop D-10, 4600 Sangamore Road, Bethesda, MD 20816-5003.</P>
        <P>(f) Requests for information made under the Freedom of Information Act are processed in accordance with “DoD Freedom of Information Act Program Regulation” (32 CFR part 286).</P>
        <P>(g) Requests for personal information from the Government Accounting Office (GAO) are processed in accordance with DoD Directive 7650.1 <FTREF/>
          <SU>1</SU> “GAO Access to Records”.</P>
        <FTNT>
          <P>
            <SU>1</SU> Copies may be obtained via Internet at http://www.dtic.mil/whs/directives</P>
        </FTNT>
      </SECTION>
      <SECTION>
        <SECTNO>§ 320.5</SECTNO>
        <SUBJECT>Disclosure of requested information.</SUBJECT>
        <P>(a) Upon request by an individual made in accordance with the procedures set forth in this section, such individual shall be granted access to any pertinent record which is contained in a nonexempt NIMA system of records. However, nothing in this section shall allow an individual access to any information compiled by NIMA in reasonable anticipation of a civil or criminal action or proceeding.</P>
        <P>(b) Procedures for requests for access to records. Any individual may request access to a pertinent NIMA record in person or by mail.</P>
        <P>(1) Any individual making such request in person shall appear at Office of General Counsel, NIMA Bethesda, ATTN: NIMA/GC, Mail Stop D-10, 4600 Sangamore Road, Bethesda, MD 20816-5003, and shall provide identification to verify the individuals' identity, e.g., driver's license, employee identification card, or Medicare card.</P>
        <P>(2) Any individual making a request for access to records by mail shall address such request to the Office of General Counsel, NIMA Bethesda, ATTN: NIMA/GC, Mail Stop D-10, 4600 Sangamore Road, Bethesda, MD 20816-5003; and shall include therein a signed, notarized statement, or an unsworn statement or declaration in accordance with 28 U.S.C. 1746, to verify identity.</P>
        <P>(3) Any individual requesting access to records under this section in person may be accompanied by a person of the individual's own choosing while reviewing the record requested. If an individual elects to be so accompanied, said individual shall give notice of such election in the request and shall provide a written statement authorizing disclosure of the record in the presence of the accompanying person. Failure to so notify NIMA in a request for access shall be deemed to be a decision by the individual not to be accompanied.</P>
        <P>(c) NIMA determination of requests for access.</P>
        <P>(1) Upon receipt of a request made in accordance with this section, the NIMA Office of General Counsel or NIMA office having responsibility for maintenance of the record in question shall release the record, or refer it to an Initial Denial Authority, who shall:</P>
        <P>(i) Determine whether such request shall be granted.</P>
        <P>(ii) Make such determination and provide notification within 30 working days after receipt of such request.</P>

        <P>(iii) Notify the individual that fees for reproducing copies of records will be assessed and should be remitted before the copies may be delivered. Fee schedule and rules for assessing fees are contained in § 320.9.<PRTPAGE P="905"/>
        </P>
        <P>(iv) Requests for access to personal records may be denied only by an agency official authorized to act as an Initial Denial Authority or Final Denial Authority, after coordination with the Office of General Counsel.</P>
        <P>(2) If access to a record is denied because such information has been compiled by NIMA in reasonable anticipation of a civil or criminal action or proceeding, the individual will be notified of such determination and his right to judicial appeal under 5 U.S.C. 552a(g).</P>
        <P>(d) Manner of providing access.</P>
        <P>(1) If access is granted, the individual making the request shall notify NIMA whether the records requested are to be copied and mailed.</P>
        <P>(2) If the records are to be made available for personal inspection the individual shall arrange for a mutually agreeable time and place for inspection of the record. NIMA reserves the right to require the presence of a NIMA officer or employee during personal inspection of any record pursuant to this section and to request of the individual that a signed acknowledgment of the fact be provided that access to the record in question was granted by NIMA.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 320.6</SECTNO>
        <SUBJECT>Request for correction or amendment to record.</SUBJECT>
        <P>(a) Any individual may request amendment of a record pertaining to said individual.</P>
        <P>(b) After inspection of a pertinent record, the individual may file a request in writing with the NIMA Office of General Counsel for amendment. Such requests shall specify the particular portions of the record to be amended, the desired amendments and the reasons, supported by documentary proof, if available.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 320.7</SECTNO>
        <SUBJECT>Agency review of request for correction or amendment of record.</SUBJECT>
        <P>(a) Not later than 10 working days after receipt of a request to amend a record, in whole or in part, the NIMA Office of General Counsel, or NIMA office having responsibility for maintenance of the record in question, shall correct any portion of the record which the individual demonstrates is not accurate, relevant, timely or complete, and thereafter either inform the individual of such correction or process the request for denial.</P>
        <P>(b) Denials of requests for amendment of a record will be made only by an agency official authorized to act as an Initial Denial Authority, after coordination with the Office of General Counsel. The denial letter will inform the individual of the denial to amend the record setting forth the reasons therefor and notifying the individual of his right to appeal the decision to NIMA.</P>
        <P>(c) Any person or other agency to whom the record has been previously disclosed shall be informed of any correction or notation of dispute with respect to such records.</P>
        <P>(d) These provisions for amending records are not intended to permit the alteration of evidence previously presented during any administrative or quasi-judicial proceeding, such as an employee grievance case. Any changes in such records should be made only through the established procedures for such cases. Further, these provisions are not designed to permit collateral attack upon what has already been the subject of an administrative or quasi-judicial action. For example, an individual may not use this procedure to challenge the final decision on a grievance, but the individual would be able to challenge the fact that such action has been incorrectly recorded in his file.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 320.8</SECTNO>
        <SUBJECT>Appeal of initial adverse agency determination on correction or amendment.</SUBJECT>
        <P>(a) An individual whose request for amendment of a record pertaining to him may further request a review of such determination in accordance with this section.</P>

        <P>(b) Not later than 30 working days following receipt of notification of denial to amend, an individual may file an appeal of such decision with NIMA. The appeal shall be in writing, mailed or delivered to NIMA, ATTN: Mail Stop D-10, 4600 Sangamore Road, Bethesda, MD 20816-5003. The appeal must identify the records involved, indicate the dates of the request and adverse determination, and indicate the express <PRTPAGE P="906"/>basis for that determination. In addition, the letter of appeal shall state briefly and succinctly the reasons why the adverse determination should be reversed.</P>
        <P>(c) Upon appeal from a denial to amend a record the NIMA Appellate Authority or designee shall make a determination whether to amend the record and must notify the individual of that determination by mail, not later than 10 working days after receipt of such appeal, unless extended pursuant to paragraph (d) of this section.</P>
        <P>(1) The Appellate Authority or designee shall also notify the individual of the provisions of the Privacy Act of 1974 regarding judicial review of the NIMA Appellate Authority's determination.</P>
        <P>(2) If on appeal the denial to amend the record is upheld, the individual shall be permitted to file a statement setting forth the reasons for disagreement with the Appellate Authority's determination and such statement shall be appended to the record in question.</P>
        <P>(d) The Appellate Authority or designee may extend up to 30 days the time period in which to make a determination on an appeal from denial to amend a record for the reason that a fair and equitable review cannot be completed within the prescribed time period.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 320.9</SECTNO>
        <SUBJECT>Disclosure of record to person other than the individual to whom it pertains.</SUBJECT>
        <P>(a) No officer or employee of NIMA will disclose any record which is contained in a system of records, by any means of communication to any person or agency within or outside the Department of Defense without the request or consent of the individual to whom the record pertains, except as described in to 32 CFR 310.41; Appendix C to part 310 of this chapter; and/or a NIMA Privacy Act system of records notice.</P>
        <P>(b) Any such record may be disclosed to any person or other agency only upon written request, of the individual to whom the record pertains.</P>
        <P>(c) In the absence of a written consent from the individual to whom the record pertains, such record may be disclosed only provided such disclosure is:</P>
        <P>(1) To those officers and employees of the DoD who have a need for the record in the performance of their duties.</P>
        <P>(2) Required under the Freedom of Information Act (32 CFR part 286).</P>
        <P>(3) For a routine use established within the system of records notice.</P>
        <P>(4) To the Bureau of Census for purposes of planning or carrying out a census or survey or related activity pursuant to the provisions of title 13.</P>
        <P>(5) To a recipient who has provided the NIMA with adequate advance written assurance that the record will be used solely as a statistical research or reporting record and the record is transferred in a form that is not individually identifiable and will not be used to make any decisions about the rights, benefits or entitlements of an individual.</P>
        <P>(6) To the National Archives of the United States as a record which has sufficient historical or other value to warrant its continued preservation by the U.S. Government or for evaluation by the Administrator of the General Services Administration or his designee to determine whether the record has such value.</P>
        <P>(7) To another agency or to an instrumentality of any governmental jurisdiction within or under the control of the U.S. for a civil or criminal law enforcement activity authorized by law, provided the head of the agency or instrumentality has made a prior written request to the Director, NIMA specifying the particular record and the law enforcement activity for which it is sought.</P>
        <P>(8) To a person pursuant to a showing of compelling circumstances affecting the health or safety of an individual, if upon such disclosure notification is transmitted to the last known address of such individual.</P>
        <P>(9) To either house of Congress, and, to the extent of the matter within its jurisdiction, any committee or subcommittee or joint committee of Congress.</P>

        <P>(10) To the Comptroller General or any of his authorized representatives in the course of the performance of the duties of the GAO.<PRTPAGE P="907"/>
        </P>
        <P>(11) Under an order of a court of competent jurisdiction.</P>
        <P>(12) To a consumer reporting agency in accordance with section 3711(f) of title 31.</P>
        <P>(d) Except for disclosures made pursuant to paragraphs (c)(1) and (2) of this section, an accurate accounting will be kept of the data, nature and purpose of each disclosure of a record to any person or agency, and the name and address of the person or agency to whom the disclosure was made. The accounting of disclosures will be made available for review by the subject of a record at his request except for disclosures made pursuant to paragraph (c)(7) of this section. If an accounting of disclosure has been made, any person or agency contained therein will be informed of any correction or notation of dispute made pursuant to section 320.6 of this part.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 320.10</SECTNO>
        <SUBJECT>Fees.</SUBJECT>
        <P>Individuals may request copies for retention of any documents to which they are granted access to NIMA records pertaining to them. Requesters will not be charged for the first copy of any records provided; however, duplicate copies will require a charge to cover costs of reproduction. Such charges will be computed in accordance with 32 CFR part 310.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 320.11</SECTNO>
        <SUBJECT>Penalties.</SUBJECT>
        <P>The Privacy Act of 1974 (5 U.S.C. 552a(i)(3)) makes it a misdemeanor subject to a maximum fine of $5,000, to knowingly and willfully request or obtain any record concerning an individual under false pretenses. The Act also establishes similar penalties for violations by NIMA employees of the Act or regulations established thereunder.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 320.12</SECTNO>
        <SUBJECT>Exemptions.</SUBJECT>
        <P>(a) <E T="03">Exempt systems of record.</E> All systems of records maintained by the NIMA and its components shall be exempt from the requirements of 5 U.S.C. 552a(d) pursuant to 5 U.S.C. 552a(k)(1) to the extent that the system contains any information properly classified under Executive Order 12958 and that is required by Executive Order to be withheld in the interest of national defense or foreign policy. This exemption is applicable to parts of all systems of records, including those not otherwise specifically designated for exemptions herein, which contain isolated items of properly classified information.</P>
        <P>(b) [Reserved]</P>
      </SECTION>
    </PART>
    <PART>
      <EAR>Pt. 321</EAR>
      <HD SOURCE="HED">PART 321—DEFENSE SECURITY SERVICE PRIVACY PROGRAM</HD>
      <CONTENTS>
        <SECHD>Sec.</SECHD>
        <SECTNO>321.1</SECTNO>
        <SUBJECT>Purpose and applicability.</SUBJECT>
        <SECTNO>321.2</SECTNO>
        <SUBJECT>Definitions.</SUBJECT>
        <SECTNO>321.3</SECTNO>
        <SUBJECT>Information and procedures for requesting notification.</SUBJECT>
        <SECTNO>321.4</SECTNO>
        <SUBJECT>Requirements for identification.</SUBJECT>
        <SECTNO>321.5</SECTNO>
        <SUBJECT>Access by subject individuals.</SUBJECT>
        <SECTNO>321.6</SECTNO>
        <SUBJECT>Medical records.</SUBJECT>
        <SECTNO>321.7</SECTNO>
        <SUBJECT>Request for correction or amendment.</SUBJECT>
        <SECTNO>321.8</SECTNO>
        <SUBJECT>DSS review of request for amendment.</SUBJECT>
        <SECTNO>321.9</SECTNO>
        <SUBJECT>Appeal of initial amendment decision.</SUBJECT>
        <SECTNO>321.10</SECTNO>
        <SUBJECT>Disclosure to other than subject.</SUBJECT>
        <SECTNO>321.11</SECTNO>
        <SUBJECT>Fees.</SUBJECT>
        <SECTNO>321.12</SECTNO>
        <SUBJECT>Penalties.</SUBJECT>
        <SECTNO>321.13</SECTNO>
        <SUBJECT>Exemptions.</SUBJECT>
        <SECTNO>321.14</SECTNO>
        <SUBJECT>DSS implementation policies.</SUBJECT>
      </CONTENTS>
      <AUTH>
        <HD SOURCE="HED">Authority:</HD>
        <P>Pub. L. 93-579, 88 Stat 1896 (5 U.S.C. 552a).</P>
      </AUTH>
      <SOURCE>
        <HD SOURCE="HED">Source:</HD>
        <P>64 FR 49660, Sept. 14, 1999, unless otherwise noted.</P>
      </SOURCE>
      <SECTION>
        <SECTNO>§ 321.1</SECTNO>
        <SUBJECT>Purpose and applicability.</SUBJECT>
        <P>(a) This part establishes rules, policies and procedures for the disclosure of personal records in the custody of the Defense Security Service (DSS) to the individual subjects, the handling of requests for amendment or correction of such records, appeal and review of DSS decisions on these matters, and the application of general and specific exemptions, under the provisions of the Privacy Act of 1974. It also prescribes other policies and procedures to effect compliance with the Privacy Act of 1974 and DoD Directive 5400.11 <SU>1</SU>
          <FTREF/>.</P>
        <FTNT>
          <P>
            <SU>1</SU> Copies may be obtained via internet at http://web7.whs.osd.mil/corres.htm</P>
        </FTNT>

        <P>(b) The procedures set forth in this part do not apply to DSS personnel seeking access to records pertaining to themselves which previously have been available. DSS personnel will continue to be granted ready access to their personnel, security, and other records by making arrangements directly with the  maintaining office. DSS personnel should contact the Office of Freedom of <PRTPAGE P="908"/>Information and Privacy, DSSHQ, for access to investigatory records pertaining to themselves or any assistance in obtaining access to other records pertaining to themselves, and may follow the procedures outlined in these rules in any  case.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 321.2</SECTNO>
        <SUBJECT>Definitions.</SUBJECT>
        <P>(a) All terms used in this part which are defined in 5 U.S.C. 552a shall have the same meaning herein.</P>
        <P>(b) As used in this part, the term agency means the Defense Security Service.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 321.3</SECTNO>
        <SUBJECT>Information and procedures for requesting notification.</SUBJECT>
        <P>(a) <E T="03">General.</E> Any individual may request and receive notification of whether he is the subject of a record in any system of records maintained by DSS using the information and procedures described in this section.</P>
        <P>(1) Paragraphs (b) and (c) of this section give information that will assist an individual in determining in what systems of DSS records (if any) he may be the subject. This information is presented as a convenience to the individual in that he may avoid consulting the lengthy systems notices elsewhere in the Federal Register.</P>
        <P>(2) Paragraph (d) of this section details the procedure an individual should use to contact DSS and request notification. It will be helpful if the individual states what his connection with  DSS has or may have been, and about what record system(s) he is inquiring. Such information is not required, but its absence may cause some delay.</P>
        <P>(b) <E T="03">DSS Records Systems.</E> A list of DSS records systems is available by contacting Defense Security Service, Office of FOI and Privacy, 1340 Braddock Place, Alexandria, VA, 22314-1551.</P>
        <P>(c) <E T="03">Categories of individuals in DSS Record Systems.</E> (1) Any  person who is the subject or co-subject of an ongoing or completed investigation by DSS should have an investigative case file/record in system V5-01, if the record meets retention criteria. An index to such files should be in V5-02.</P>
        <P>(2) If an individual has ever made a formal request to DSS under the Freedom of Information Act or the Privacy Act of 1974, a record pertaining to that request under the name of the requester, or subject matter, will be in system V1-01.</P>
        <P>(3) Persons of Counterintelligence interest who have solicited from industrial contractors/DoD installations information which may appear to be sensitive in nature may have a record in system V5-04.</P>
        <P>(4) Individuals who have been applicants for employment with DSS, or nominees for assignment to DSS, but who have not completed their DSS affiliation, may be subjects in systems  V4-04, V5-01, V5-02, V5-03, or V6-01.</P>
        <P>(5) Any individual who is a subject, victim or cross-referenced personally in an investigation by an investigative element of any DoD component, may be referenced in the Defense Clearance and Investigations Index, system V5-02, in an index to the location, file number, and custodian of the case record.</P>
        <P>(6) Individuals who have ever presented a complaint to or have been connected with a DSS Inspector General inquiry may be subjects of records in system V2-01.</P>
        <P>(7) If an individual has ever attended the Defense Industrial Security Institute or completed training with the DSS Training Office he should be subject of a record in V7-01.</P>
        <P>(8) If an individual has ever been a guest speaker or instructor at the Defense Industrial Security Institute, he should be the subject of a record in V7-01.</P>
        <P>(9) If an individual is an employee or major stockholder of a government contractor or other DoD-affiliated company or agency and has been issued, now possesses or has been processed for a security clearance, he may be subject to a record in V5-03.</P>
        <P>(d) <E T="03">Procedures.</E> The following procedures should be followed to determine if an individual is a subject of records maintained by DSS, and to request notification and access.</P>

        <P>(1) Individuals should submit inquiries in person or by mail to the Defense Security Service, Office of FOI and Privacy, 1340 Braddock Place, Alexandria, VA 22314-1651. Inquiries by personal appearance should be made Monday through Friday from 8:30 to 11:30 a.m. and 1:00 to 4:00 p.m. The information <PRTPAGE P="909"/>requested in Sec. 321.4 must be provided if records are to be accurately identified. Telephonic requests for records will not be honored. In a case where the system of records is not specified in the  request, only systems that would reasonably contain records of the individual will be checked, as described in  paragraph (b) of this section.</P>
        <P>(2) Only the Director or Chief, Office of FOI and Privacy  may authorize exemptions to notification of individuals in accordance with § 321.13.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 321.4</SECTNO>
        <SUBJECT>Requirements for identification.</SUBJECT>
        <P>(a) <E T="03">General.</E> Only upon proper identification, made in accordance with the provisions of this section, will any individual be granted notification concerning and access to all releasable records pertaining to him which are maintained in a DSS system.</P>
        <P>(b) <E T="03">Identification.</E> Identification of individuals is required both for accurate record identification and to verify identity in order to avoid disclosing records to unauthorized persons. Individuals who request notification of, access to, or amendment of records pertaining to themselves, must provide their full name (and additional names such as aliases, maiden names, alternate spellings, etc., if a check of these variants is desired), date and place of birth, and social security number (SSN).</P>
        <P>(1) Where reply by mail is requested, a mailing address is required, and a telephone number is recommended to expedite certain matters. For military requesters residing in the United States, home address or P.O. Box number is preferred in lieu of duty assignment address.</P>
        <P>(2) Signatures must be notarized on requests received by  mail. Exceptions may be made when the requester is well known to releasing officials. For requests made in person, a photo identification card,  such as military ID, driver's license or building pass, must be presented.</P>
        <P>(3) While it is not required as a condition of receiving notification, in many cases the SSN may be necessary to obtain an accurate search of DCII (V5-02) records.</P>
        <P>(c) A DSS Form 30 (Request for Notification of/Access to Personal Records) will be provided to any individual inquiring about records pertaining to himself whose mailed request was not notarized. This form is also available at the DSS Office of FOI and Privacy, 1340 Braddock Place, Alexandria, VA 22314-1651, for those who make their requests in person.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 321.5</SECTNO>
        <SUBJECT>Access by subject individuals.</SUBJECT>
        <P>(a) <E T="03">General.</E> (1) Individuals may request access to records pertaining to themselves in person or by mail in accordance with this section. However, nothing in this section shall allow an individual access to any information compiled or maintained by DSS in reasonable anticipation of a civil or criminal action or proceeding, or otherwise exempted under the provisions of § 321.13.</P>
        <P>(2) A request for a pending personnel security investigation  will be held in abeyance until completion of the investigation and the requester will be so notified.</P>
        <P>(b) <E T="03">Manner of access.</E> (1) Requests by mail or in person for access to DSS records should be made to the DSS Office of FOI and Privacy, 1340 Braddock Place, Alexandria, VA 22314-1651.</P>
        <P>(2) Any individual who makes a request for access in person shall:</P>
        <P>(i) Provide identification as specified in Sec. 321.4.</P>
        <P>(ii) Complete and sign a request form.</P>
        <P>(3) Any individual making a request for access to records by mail shall include a signed and notarized statement to verify his identity, which may be the DSS request form if he has received one.</P>
        <P>(4) Any individual requesting access to records in person may be accompanied by an identified person of his own choosing while reviewing the record. If the individual elects to be accompanied, he shall make this known in his written request, and include a statement authorizing disclosure of the record contents to the accompanying person. Without written authorization of the subject individual, records will not be disclosed to third parties accompanying the subject.</P>

        <P>(5) During the course of official business, members of DSS field elements <PRTPAGE P="910"/>may be given access to records maintained by the field elements/Operations Center without referral to the Office of FOI and Privacy.  An account of such access will be kept for reporting purposes.</P>
        <P>(6) In all requests for access, the requester must state whether he or she desires access in person or mailed copies of  records. During personal access, where copies are made for retention, a fee for reproduction and postage may be assessed as provided in Sec. 321.11. Where copies are mailed because personal appearance is impractical, there will be no fee.</P>
        <P>(7) All individuals who are not affiliates of DSS will be given  access to records, if authorized, in the Office of FOI and Privacy, or by means of mailed copies.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 321.6</SECTNO>
        <SUBJECT>Medical records.</SUBJECT>
        <P>
          <E T="03">General.</E> Medical records that are part of DSS records systems will generally be included with those records when access is granted to the subject to which they pertain. However, if it is determined that such access could have an adverse effect upon the individual's physical or mental health, the medical record in question will be released only to a physician named by the requesting individual.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 321.7</SECTNO>
        <SUBJECT>Request for correction or amendment.</SUBJECT>
        <P>(a) <E T="03">General.</E> Upon request and proper identification by any individual who has been granted access to DSS records pertaining to himself or herself, that individual may request,  either in person or through the mail, that the record be amended. Such a request must be made in writing and addressed to the Defense Security Service, Office of FOI and Privacy, 1340 Braddock Place, Alexandria, VA 22314-1651.</P>
        <P>(b) <E T="03">Content.</E> The following information must be included to insure effective action on the request:</P>
        <P>(1) Description of the record. Requesters should specify the number of pages and documents, the titles of the documents, form numbers if there are any, dates on the documents and names of individuals who signed them. Any reasonable description of the document is acceptable.</P>
        <P>(2) Description of the items to be amended. The description of the passages, pages or documents to be amended should be as clear and specific as possible.</P>
        <P>(i) Page, line and paragraph numbers should be cited where they exist.</P>
        <P>(ii) A direct quotation of all or a portion of the passage may be made if it isn’t otherwise easily identifiable. If the passage is long, a quotation of its beginning and end will suffice.</P>
        <P>(iii) In appropriate cases, a simple substantive request may be appropriate, e.g., ‘delete all references to my alleged arrest in July 1970.’</P>
        <P>(iv) If the requester has received a copy of the record, he may submit an annotated copy of documents he wishes amended.</P>
        <P>(3) Type of amendment. The requester must clearly state the type of amendment he is requesting.</P>
        <P>(i) Deletion or expungement, i.e., a complete removal from the record of data, sentences, passages, paragraphs or documents.</P>
        <P>(ii) Correction of the information in the record to make it more accurate, e.g., rectify mistaken identities, dates, data pertaining to the individual, etc.</P>
        <P>(iii) Additions to make the record more relevant, accurate or timely may be requested.</P>
        <P>(iv) Other changes may be requested; they must be specifically and clearly described.</P>
        <P>(4) Reason for amendment. Requests for amendment must be based on specific reasons, included in writing. Categories of reasons are as follows:</P>
        <P>(i) Accuracy. Amendment may be requested where matters of fact are believed incorrectly recorded, e.g., dates, names, addresses, identification numbers, or any other information concerning the individual. The request, whenever possible, should contain the accurate information, copies of verifying documents, or indication of how the information can be verified.</P>
        <P>(ii) Relevance. Amendment may be requested when information in a record is believed not to be relevant or necessary to the purposes of the record system.</P>

        <P>(iii) Timeliness. Amendment may be requested when information is thought <PRTPAGE P="911"/>to be so old as to no longer be pertinent to the stated purposes of the records system. It may also be requested when there is recent information of a pertinent type that is not included in the record.</P>
        <P>(iv) Completeness. Amendment may be requested where  information in a record is incomplete with respect to its purpose. The data thought to have been omitted should be included or identified with the request.</P>
        <P>(v) Fairness. Amendment may be requested when a record is thought to be unfair concerning the subject, in terms of the stated purposes of the record. In such cases, a source of additional information to increase the fairness of the record should be identified where possible.</P>
        <P>(vi) Other reasons. Reasons for requesting amendment are not limited to those cited above. The content of the records is authorized in terms of their stated purposes which should be the basis for evaluating them. However, any matter believed appropriate may be submitted as a basis of an amendment request.</P>
        <P>(vii) Court orders and statutes may require amendment of a file. While they do not require a Privacy Act request for execution, such may be brought to the attention of DSS by these procedures.</P>
        <P>(c)<E T="03"> Assistance.</E> Individuals seeking to request amendment of records pertaining to themselves that are maintained by DSS will be assisted as necessary by DSS officials. Where a request is incomplete, it will not be denied, but the requester will be contacted for the additional information necessary to his request.</P>
        <P>(d) This section does not permit the alteration of evidence presented to courts, boards and other official proceedings.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 321.8</SECTNO>
        <SUBJECT>DSS review of request for amendment.</SUBJECT>
        <P>(a) <E T="03">General.</E> Upon receipt from any individual of a request to amend a record pertaining to himself and maintained by the Defense Security Service, Office of FOI and Privacy will handle the request as follows:</P>
        <P>(1) A written acknowledgment of the receipt of a request for amendment of a record will be provided to the individual within 10 working days, unless final action regarding approval or denial can be accomplished within that time. In that case, the notification of approval or denial will constitute adequate acknowledgment.</P>
        <P>(2) Where there is a determination to grant all or a portion of a request to amend a record, the record shall be promptly amended and the requesting individual notified. Individuals, agencies or components shown by accounting records to have received copies of the record, or to whom disclosure has been made, will be notified, if necessary, of the amendment by the responsible official. Where a DoD recipient of an investigative record cannot be located, the notification, if necessary, will be sent to the personnel security element of the parent Component.</P>
        <P>(3) Where there is a determination to deny all or a portion of a request to amend a record, the office will promptly:</P>
        <P>(i) Advise the requesting individual of the specifics of the refusal and the reasons;</P>
        <P>(ii) Inform the individual that he may request a review of the denial(s) from ‘Director, Defense Security Service, 1340  Braddock Place, Alexandria, VA 22314-1651.’ The request should be brief, in writing, and enclose a copy of the denial correspondence.</P>
        <P>(b) DSS determination to approve or deny. Determination to approve or deny and request to amend a record or portion thereof may necessitate additional investigation or inquiry be made to verify assertions of individuals requesting amendment. Coordination will be made with the Director for Investigations and the Director of the Personnel Investigations Center in such instances.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 321.9</SECTNO>
        <SUBJECT>Appeal of initial amendment decision.</SUBJECT>
        <P>(a) <E T="03">General.</E> Upon receipt from any individual of an appeal to review a DSS refusal to amend a record, the Defense Security Service, Office of FOI and Privacy will assure that such appeal is handled in compliance with the Privacy Act of 1974 and DoD Directive 5400.11 and accomplish the following:<PRTPAGE P="912"/>
        </P>
        <P>(1) Review the record, request for amendment, DSS action on the request and the denial, and direct such additional inquiry or investigation as is deemed necessary to make a fair and equitable determination.</P>
        <P>(2) Recommend to the Director whether to approve or deny the appeal.</P>
        <P>(3) If the determination is made to amend a record, advise the individual and previous recipients (or an appropriate office) where an accounting of disclosures has been made.</P>
        <P>(4) Where the decision has been made to deny the individual's appeal to amend a record, notify the individual:</P>
        <P>(i) Of the denial and the reason;</P>
        <P>(ii) Of his right to file a concise statement of reasons for disagreeing with the decision not to amend the record;</P>
        <P>(iii) That such statement may be sent to the Defense Security Service, Office of FOI and Privacy, (GCF), 1340 Braddock Place, Alexandria, VA 22314-1651, and that it will be disclosed to users of the disputed record;</P>
        <P>(iv) That prior recipients of the disputed record will be provided a copy of the statement of disagreement, or if they cannot be reached (e.g., through deactivation) the personnel security element of their DoD component;</P>
        <P>(v) And, that he may file a suit in a Federal District Court to contest DSS's decision not to amend the disputed record.</P>
        <P>(b) <E T="03">Time limit for review of appeal.</E> If the review of an appeal of a refusal to amend a record cannot be accomplished within 30 days, the Office of FOI and Privacy will notify the individual and advise him of the reasons, and inform him of when he may expect the review to be completed.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 321.10</SECTNO>
        <SUBJECT>Disclosure to other than subject.</SUBJECT>
        <P>(a) <E T="03">General.</E> No record contained in a system of records maintained by DSS shall be disclosed by any means to any person  or agency outside the Department of Defense, except with the written consent or request of the individual subject of the record, except as provided in this section. Disclosures that may be made without the request or consent of the subject of the record are as follows:</P>
        <P>(1) To those officials and employees of the Department of Defense who have a need for the record in the performance of their duties, when the use is compatible with the stated purposes for which the record is maintained.</P>
        <P>(2) Required to be disclosed by the Freedom of Information Act.</P>
        <P>(3) For a routine use as described in DoD Directive 5400.11.</P>
        <P>(4) To the Census Bureau, National Archives, the U.S. Congress, the Comptroller General or General Accounting Office under the conditions specified in DoD Directive 5400.11.</P>
        <P>(5) At the written request of the head of an agency outside DoD for a law enforcement activity as authorized by DoD Directive  5400.11.</P>
        <P>(6) For statistical purposes, in response to a court order, or for compelling circumstances affecting the health or safety of an individual as described in DoD Directive 5400.11.</P>
        <P>(7) Legal guardians recognized by the Act.</P>
        <P>(b) <E T="03">Accounting of disclosures.</E> Except for disclosures made to members of the DoD in connection with their routine duties, and disclosures required by the Freedom of Information  Act, an accounting will be kept of all disclosures of records maintained in DSS systems.</P>
        <P>(1) Accounting entries will normally be kept on a DSS form, which will be maintained in the record file jacket, or in a document that is part of the record.</P>
        <P>(2) Accounting entries will record the date, nature and purpose of each disclosure, and the name and address of the person or agency to whom the disclosure is made.</P>
        <P>(3) An accounting of disclosures made to agencies outside the DoD of records in the Defense Clearance and Investigations Index (V5-02) will be kept as prescribed by the Director of Systems, DSS.</P>
        <P>(4) Accounting records will be maintained for at least 5 years after the last disclosure, or for the life of the record, whichever is longer.</P>
        <P>(5) Subjects of DSS records will be given access to associated accounting records upon request, except as exempted under § 321.13.</P>
      </SECTION>
      <SECTION>
        <PRTPAGE P="913"/>
        <SECTNO>§ 321.11</SECTNO>
        <SUBJECT>Fees.</SUBJECT>
        <P>Individuals may request copies for retention of any documents to which they are granted access in DSS records pertaining to them. Requestors will not be charged for the first copy of any records provided; however, duplicate copies will require a charge to cover costs of reproduction. Such charges will be computed in accordance with DoD Directive 5400.11.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 321.12</SECTNO>
        <SUBJECT>Penalties.</SUBJECT>
        <P>(a) An individual may bring a civil action against the DSS to correct or amend the record, or where there is a refusal to comply with an individual request or failure to maintain any record with accuracy, relevance, timeliness and completeness, so as to guarantee fairness, or failure to comply with any other provision of 5 U.S.C. 552a. The court may order correction or amendment. It may assess against the United States reasonable attorney fees and other costs, or may enjoin the DSS from withholding the records and order the production to the complainant.</P>
        <P>(b) Where it is determined that the action was willful or intentional with respect to 5 U.S.C. 552a(g)(1) (C) or (D), the United States shall be liable for the actual damages sustained, but in no case less than the sum of $1,000 and the costs of the  action with attorney fees.</P>
        <P>(c) Criminal penalties may be imposed against an officer or employee of the DSS who fully discloses material, which he knows is prohibited from disclosure, or who willfully maintains a system of records without the notice requirements; or against any person who knowingly and willfully requests or obtains any record concerning an individual from an agency under false pretenses. These offenses shall be misdemeanors with a fine not to exceed $5,000.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 321.13</SECTNO>
        <SUBJECT>Exemptions.</SUBJECT>
        <P>(a) <E T="03">General.</E> The Director of the Defense Security Service establishes the following exemptions of records systems (or portions thereof) from the provisions of these rules, and other indicated portions of Pub. L. 93-579, in this section. They may be exercised only by the Director, Defense Security Service and the Chief of the Office of FOI and Privacy. Exemptions will be exercised only when necessary for a specific, significant and legitimate reason connected with the purpose of a records system, and not simply because they are authorized by statute. Personal records releasable under the provisions of 5 U.S.C. 552 will not be withheld from subject individuals based on these exemptions.
        </P>

        <P>(b) All systems of records maintained by DSS shall be exempt from the requirements of 5 U.S.C. 552a(d) pursuant to 5 U.S.C. 552a(k)(1) to the extent that the system contains any information properly classified under Executive Order 12958 and which is required by the Executive Order to be withheld in the interest of national defense of foreign policy. This exemption, which may be applicable to parts of all systems of records, is necessary because certain record systems not otherwise specifically designated for exemptions herein may contain items of information that have been properly classified.
        </P>
        <P>(c) <E T="03">System identifier:</E> V1-01.</P>
        <P>(1) System name: Privacy and Freedom of Information Request Records.</P>

        <P>(2) Exemptions: (i) Investigatory material compiled for law enforcement purposes may be exempt pursuant to 5 U.S.C. 552a(k)(2).  However, if an individual is denied any right, privilege, or benefit for which he would otherwise be entitled by Federal law or for which he would otherwise be eligible, as a result of the maintenance of such information, the individual will be provided access to such information except to the extent that disclosure would reveal the identity of a confidential source.
        </P>

        <P>(ii) Records maintained in connection with providing protective services to the President and other individuals under 18 U.S.C. 3506, may be exempt pursuant to 5 U.S.C. 552a(k)(3).
        </P>

        <P>(iii) Investigatory material compiled solely for the purpose of determining suitability, eligibility, or qualifications for federal civilian employment, military service, federal contracts, or access to classified information may be exempt pursuant to 5  U.S.C. 552a(k)(5), but only to the extent that such material would reveal the identity of a confidential source.<PRTPAGE P="914"/>
        </P>
        <P>(iv) Any portion of this system that falls under the provisions of 5 U.S.C. 552a(k)(2), (k)(3), (k)(5) may be exempt from the following subsections of 5 U.S.C. 552a(c)(3); (d); (e)(1); (e)(4)(G), (H) and (I); and (f).</P>
        <P>(3) Authority: 5 U.S.C. 552a(k)(2), (k)(3), (k)(5).</P>
        <P>(4) Reasons: (i) From subsection (c)(3) because it will enable DSS  to conduct certain investigations and relay law enforcement information without compromise of the information, protection of investigative techniques and efforts employed, and identities of confidential sources who might not otherwise come forward and who furnished information under an express promise that the sources’ identity would be held in confidence (or prior to the effective date of the Act, under an implied promise);</P>
        <P>(ii) From subsections (e)(1), (e)(4)(G), (H), and (I) because it will provide protection against notification of investigatory material including certain reciprocal investigations and counterintelligence information, which might alert a subject to the fact that an investigation of that individual is taking place, and the disclosure of which would weaken the on-going investigation, reveal investigatory techniques, and place confidential informants in jeopardy who furnished information under an express promise that the sources’ identity would be held in confidence (or prior to the effective date of the Act, under an implied promise);</P>

        <P>(iii) From subsections (d) and (f) because requiring DSS to grant access to records and agency rules for access and amendment of records would unfairly impede the agency's investigation of allegations of unlawful activities. To require DSS to confirm or deny the existence of a record pertaining to a requesting individual may in itself provide an answer to that individual relating to an on-going investigation. The investigation of possible unlawful activities would be jeopardized by agency rules requiring verification of record, disclosure of the record to the subject, and record amendment procedures.
        </P>
        <P>(d) <E T="03">System identifier:</E> V5-01.</P>
        <P>(1) System name: Investigative Files System</P>

        <P>(2) Exemption:  (i)  Investigatory material compiled for law enforcement purposes may be exempt pursuant to 5 U.S.C. 552a(k)(2).  However, if an individual is denied any right, privilege, or benefit for which he would otherwise be entitled by Federal law or for which he would otherwise be eligible, as a result of the maintenance of such information, the individual will be provided access to such information except to the extent that disclosure would reveal the identity of a confidential source.
        </P>

        <P>(ii) Records maintained in connection with providing protective services to the President and other individuals under  18 U.S.C. 3506, may be exempt pursuant to 5 U.S.C. 552a(k)(3).
        </P>
        <P>(iii) Investigatory material compiled solely for the purpose of determining suitability, eligibility, or qualifications for federal civilian employment, military service, federal contracts, or access to classified information may be exempt pursuant to 5 U.S.C. 552a(k)(5), but only to the extent that such material would reveal the identity of a confidential source.</P>
        <P>(iv) Any portion of this system that falls under the provisions of 5 U.S.C. 552a(k)(2), (k)(3), or (k)(5) may be exempt from the following subsections of 5 U.S.C. 552a(c)(3); (d); (e)(1); (e)(4)(G), (H), and (I); and (f).</P>
        <P>(3) Authority:  5 U.S.C. 552a(k)(2), (k)(3), or (k)(5).</P>
        <P>(4) Reasons: (i) From subsection (c)(3) because it will enable DSS to conduct certain investigations and relay law enforcement information without compromise of the information, protection of investigative techniques and efforts employed, and identities of confidential sources who might not otherwise come forward and who furnished information under an express promise that the sources’ identity would be held in confidence (or prior to the effective date of the Act, under an implied promise).</P>

        <P>(ii) From subsections (e)(1), (e)(4)(G), (H), and (I) because it will provide protection against notification of investigatory material including certain reciprocal investigations and counterintelligence information, which might alert a subject to the fact that an investigation of that individual is taking place, and the disclosure of which <PRTPAGE P="915"/>would weaken the on-going investigation, reveal investigatory techniques, and place confidential informants in jeopardy who furnished information under an express promise that the sources’ identity would be held in confidence (or prior to the effective date of the Act, under an implied promise).</P>

        <P>(iii) From subsections (d) and (f) because requiring DSS to grant access to records and agency rules for access and amendment of records would unfairly impede the agency's investigation of allegations of unlawful activities. To require DSS to confirm or deny the existence of a record pertaining to a requesting individual may in itself provide an answer to that individual relating to an on-going  investigation. The investigation of possible unlawful activities would be jeopardized by agency rules requiring verification of record, disclosure of the record to the subject, and record amendment procedures.
        </P>
        <P>(e) <E T="03">System identifier:</E> V5-02.</P>
        <P>(1) System name: Defense Clearance and Investigations Index (DCII).</P>
        <P>(2) Exemption: Investigatory material compiled for law enforcement purposes may be exempt pursuant to 5 U.S.C. 552a(k)(2).  However, if an individual is denied any right, privilege, or benefit for which he would otherwise be entitled by  Federal law or for which he would otherwise be eligible, as a result of the maintenance of such information, the individual will be provided access to such information except to the extent that disclosure would reveal the identity of a confidential source.  Any portion of this system that falls under the provisions of 5 U.S.C. 552a(k)(2) may be exempt from the following subsections of 5 U.S.C. 552a(c)(3); (d); (e)(1); (e)(4)(G), (H), and (I), and (f).</P>
        <P>(3) Authority: 5 U.S.C. 552a(k)(2).</P>
        <P>(4) Reasons: (i) From subsection (c)(3) because it will enable DSS to conduct certain investigations and relay law enforcement information without compromise of the information, protection of investigative techniques and efforts employed, and identities of confidential sources who might not otherwise come forward and who furnished information under an express promise that the sources’ identity would be held in confidence (or prior to the effective date of the Act, under an implied promise).</P>
        <P>(ii) From subsections (e)(1), (e)(4)(G), (H), and (I) because it will provide protection against notification of investigatory material including certain reciprocal investigations and counterintelligence information, which might alert a subject to the fact that an investigation of that individual is taking place, and the disclosure of which would weaken the on-going investigation, reveal investigatory techniques, and place confidential informants in jeopardy who furnished information under an express promise that the sources’ identity would be held in confidence (or prior to the effective date of the Act, under an implied promise).</P>

        <P>(iii) From subsections (d) and (f) because requiring DSS to grant access to records and agency rules for access and amendment of records would unfairly impede the agency's investigation of allegations of unlawful activities. To require DSS to confirm or deny the existence of a record pertaining to a requesting individual may in itself provide an answer to that individual relating to an on-going investigation. The investigation of possible unlawful activities would be jeopardized by agency rules requiring verification of record, disclosure of the record to the subject, and record amendment procedures.
        </P>
        <P>(f) <E T="03">System identifier:</E> V5-03.</P>
        <P>(1) System name: Case Control Management System (CCMS).</P>
        <P>(2) Exemption:  (i) Investigatory material compiled for law enforcement purposes may be exempt pursuant to 5 U.S.C. 552a(k)(2).  However, if an individual is denied any right, privilege, or benefit for which he would otherwise be entitled by Federal law or for which he would otherwise be eligible, as a result of the maintenance of such information, the individual will be provided access to such information except to the extent that disclosure would reveal the identity of a confidential source.</P>

        <P>(ii) Investigatory material compiled solely for the purpose of determining suitability, eligibility, or qualifications for  federal civilian employment, military service, federal contracts, or access to classified information may be exempt pursuant to 5 U.S.C. 552a(k)(5), <PRTPAGE P="916"/>but only to the extent that such material would reveal the identity of a confidential source.  Any portion of this system that falls under the provisions of 5 U.S.C. 552a(k)(2) or (k)(5) may be exempt from the following subsections of 5 U.S.C. 552a: (c)(3); (d); (e)(1); (e)(4)(G), (H), and (I); and (f).</P>
        <P>(3) Authority. 5 U.S.C. 552a(k)(2) and (k)(5).</P>
        <P>(4) Reasons. (i) From subsection (c)(3) because it will enable DSS to conduct certain investigations and relay law enforcement information without compromise of the information, protection of investigative techniques and efforts employed, and identities of confidential sources who might not otherwise come forward and who furnished information under an express promise that the sources’ identity would be held in confidence (or prior to the effective date of the Act, under an implied promise).</P>
        <P>(ii) From subsections (e)(1), (e)(4)(G), (H), and (I) because it will provide protection against notification of investigatory material including certain reciprocal investigations and counterintelligence information, which might alert a subject to the fact that an investigation of that individual is taking place, and the disclosure of which would weaken the on-going investigation, reveal investigatory techniques, and place confidential informants in jeopardy who furnished information under an express promise that the sources’ identity would be held in confidence (or prior to the effective date of the Act, under an implied promise).</P>

        <P>(iii) From subsections (d) and (f) because requiring DSS to grant access to records and agency rules for access and amendment of records would unfairly impede the agency's investigation of allegations of unlawful activities. To require DSS to confirm or deny the existence of a record pertaining to a requesting individual may in itself provide an answer to that individual relating to an on-going investigation. The investigation of possible unlawful activities would be jeopardized by agency rules requiring verification of record, disclosure of the record to the subject, and record amendment procedures.
        </P>
        <P>(g) <E T="03">System identifier:</E> V5-04.</P>
        <P>(1) System name: Counterintelligence Issues Database (CII-DB).</P>

        <P>(2) Exemption: (i) Information specifically authorized to be classified under E.O. 12958, as implemented by DoD 5200.1-R, may be exempt pursuant to 5 U.S.C. 552a(k)(1).
        </P>

        <P>(ii) Investigatory material compiled for law enforcement purposes may be exempt pursuant to 5 U.S.C. 552a(k)(2).  However, if an individual is denied any right, privilege, or benefit for which he would otherwise be entitled by Federal law or for which he would otherwise be eligible, as a result of the maintenance of such information, the individual will be provided access to such  information except to the extent that disclosure would reveal the identity of a confidential source.
        </P>

        <P>(iii) Records maintained in connection with providing protective services to the President and other individuals under 18 U.S.C. 3506, may be exempt pursuant to 5 U.S.C. 552a(k)(3).
        </P>
        <P>(iv) Investigatory material compiled solely for the purpose of determining suitability, eligibility, or qualifications for  federal civilian employment, military service, federal contracts, or access to classified information may be exempt pursuant to 5 U.S.C. 552a(k)(5), but only to the extent that such material would reveal the identity of a confidential source.</P>
        <P>(v) Any portion of this system that falls within the provisions of 5 U.S.C. 552a(k)(1), (k)(2), (k)(3) and (k)(5) may be exempt from the following subsections (c)(3); (d)(1) through (d)(5); (e)(1); (e)(4)(G), (H), and (I); and (f).</P>
        <P>(3) Authority. 5 U.S.C. 552a(k)(1), (k)(2), (k)(3) and (k)(5).</P>

        <P>(4) Reasons. (i) From subsection (c)(3) because giving the individual access to the disclosure accounting could alert the subject of an investigation to the existence and nature of the investigation and reveal investigative or prosecutive interest by other agencies, particularly in a joint-investigation situation. This would seriously impede or compromise the investigation and case preparation by prematurely revealing its existence and nature; compromise or interfere with witnesses or make witnesses reluctant to cooperate with the investigators; lead to suppression, alteration, fabrication, or destruction <PRTPAGE P="917"/>of evidence; and endanger the physical safety of confidential sources, witnesses, law enforcement personnel and their families.</P>
        <P>(ii) From subsection (d) because the application of these provisions could impede or compromise an investigation or prosecution if the subject of an investigation had access to the records or were able to use such rules to learn of the existence of an investigation before it would be completed. In addition, the mere notice of the fact of an investigation could inform the subject and others that their activities are under or may become the subject of an investigation and could enable the subjects to avoid detection or apprehension, to influence witnesses improperly, to destroy evidence, or to fabricate testimony.</P>
        <P>(iii) From subsection (e)(1) because during an investigation it is  not always possible to detect the relevance or necessity of each piece of information in the early stages of an investigation. In some cases, it is only after the information is evaluated in light of other evidence that its relevance and necessity will be clear. In other cases, what may appear to be a relevant and necessary piece of information may become irrelevant in light of further investigation. In addition, during the course of an investigation, the investigator may obtain information that related primarily to matters under the investigative jurisdiction  of another agency, and that information may not be reasonably segregated. In the interest of effective law enforcement, DSS investigators should retain this information, since it can aid in establishing patterns of criminal activity and can provide valuable leads for Federal and other law enforcement agencies.</P>
        <P>(iv) From subsections (e)(4)(G), (e)(4)(H), (e)(4)(I) and (f) because this system is exempt from subsection (d) of the Act, concerning access to records. These requirements are inapplicable to the extent that these records will be exempt from these  subsections. However, DSS has published information concerning its notification and access procedures, and the records source categories because under certain circumstances, DSS could decide it is appropriate for an individual to have access to all or a portion of his/her records in this system of records.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 321.14</SECTNO>
        <SUBJECT>DSS implementation policies.</SUBJECT>
        <P>(a) <E T="03">General.</E> The implementation of the Privacy Act of 1974 within DSS is as prescribed by DoD Directive 5400.11. This section provides special rules and information that extend or amplify DoD policies with respect to matters of particular concern to the Defense Security Service.</P>
        <P>(b) <E T="03">Privacy Act rules application.</E> Any request which cites neither Act, concerning personal record information in a system or records, by the individual to whom such information pertains, for access, amendment, correction, accounting of disclosures, etc., will be governed by the Privacy Act of 1974, DoD Directive 5400.11 and these rules exclusively. Requests for like information which cite only the Freedom of Information Act will be governed by the Freedom of Information Act, DoD Regulation 5400.7R <SU>2</SU>
          <FTREF/>. Any denial or exemption of all or part of a record from notification, access, disclosure, amendment or other provision, will also be processed under these rules, unless court order or other competent authority directs otherwise.</P>
        <FTNT>
          <P>
            <SU>2</SU> See footnote 1 to 321.1.</P>
        </FTNT>
        <P>(c) <E T="03">First amendment rights.</E> No DSS official or element may maintain any information pertaining to the exercise by an individual of his rights under the First Amendment without the permission of that individual unless such collection is specifically authorized by statute or necessary to and within the scope of an authorized law enforcement activity.</P>
        <P>(d) <E T="03">Standards of accuracy and validation of records.</E> (1) All individuals or elements within DSS which create or maintain records pertaining to individuals will insure that they are reasonably accurate, relevant, timely and complete to serve the purpose for which they are maintained and to assure fairness to the individual to whom they pertain. Information that is not pertinent to a stated purpose of a system of records will not be maintained within those records. Officials compiling investigatory records will make every reasonable effort to assure that <PRTPAGE P="918"/>only reports that are impartial, clear, accurate, complete, fair and relevant with respect to the authorized purpose of such records are included, and that reports not meeting these standards or serving such purposes are not included in such  records.</P>
        <P>(2) Prior to dissemination to an individual or agency outside DoD of any record about an individual (except for a Freedom of Information Act action or access by a subject individual under these rules) the disclosing DSS official will by review, make a reasonable effort to assure that such record is accurate, complete, timely, fair and relevant to the purpose for which they  are maintained.</P>
        <P>(e) <E T="03">The Defense Clearance and Investigations Index (DCII).</E> It is the policy of DSS, as custodian, that each DoD component or element that has direct access to or contributes records to the DCII (V5-02), is individually responsible for compliance with the Privacy Act of 1974 and DoD Directive 5400.11 with respect to requests for notification, requests for access by subject individuals, granting of such access, request for amendment and corrections by subjects, making amendments or corrections, other disclosures, accounting for disclosures and the exercise of exemptions, insofar as they pertain to any record placed in the DCII by that component or element. Any  component or element of the DoD that makes a disclosure of any record whatsoever to an individual or agency outside the DoD, from the DCII, is individually responsible to maintain an accounting of that disclosure as prescribed by the Privacy Act of 1974 and DoD Directive 5400.11 and to notify the element placing the record in the DCII of the disclosure. Use of and compliance with the procedures of the DCII Disclosure Accounting System will meet these requirements. Any component or element of DoD with access to the DCII that, in response to a request concerning an individual, discovers a record pertaining to that individual placed in the DCII by another component or element, may refer the requester to the DoD component that placed the record into the DCII without making an accounting of such referral, although it involves the divulging of the existence of that record. Generally, consultation with, and referral to, the component or element placing a record in the DCII should be effected by any component receiving a request pertaining to that record to insure appropriate exercise of amendment or exemption procedures.</P>
        <P>(f) <E T="03">Investigative operations.</E> (1) DSS agents must be thoroughly familiar with and understand these rules and the authorities, purposes and routine uses of DSS investigative records, and be prepared to explain them and the effect of refusing information to all sources of investigative information, including subjects, during interview, in response to questions that go beyond the required printed and oral notices. Agents shall be guided by DSS Handbook for Personnel Security Investigations in this respect.</P>
        <P>(2) All sources may be advised that the subject of an investigative record may be given access to it, but that the identities of sources may be withheld under certain conditions. Such advisement will be made as prescribed in DSS Handbook for Personnel Security Investigations, and the interviewing agent may not urge a source to request a grant of confidentiality. Such pledges of confidence will be given sparingly and then only when required to obtain information relevant and necessary to the stated purpose of the investigative information being collected.</P>
        <P>(g) <E T="03">Non-system information on individuals.</E> The following information is not considered part of personal records systems reportable under the Privacy Act of 1974 and may be  maintained by DSS members for ready identification, contact, and property control purposes only. If at any time the information described in this paragraph is to be used for other than these purposes, that information must become part of a reported, authorized record system. No other information concerning individuals except that described in the records systems notice and this paragraph may be maintained within DSS.</P>
        <P>(1) Identification information at doorways, building directories, desks, lockers, name tags, etc.</P>
        <P>(2) Identification in telephone directories, locator cards and rosters.</P>
        <P>(3) Geographical or agency contact cards.<PRTPAGE P="919"/>
        </P>
        <P>(4) Property receipts and control logs for building passes, credentials, vehicles, weapons, etc.</P>
        <P>(5) Temporary personal working notes kept solely by and at the initiative of individual members of DSS to facilitate their duties.</P>
        <P>(h)<E T="03"> Notification of prior recipients.</E> Whenever a decision is made  to amend a record, or a statement contesting a DSS decision not to amend a record is received from the subject individual, prior recipients of the record identified in disclosure accountings will be notified to the extent possible. In some cases, prior recipients cannot be located due to reorganization or deactivations. In these cases, the personnel security element of the receiving Defense Component will be sent the notification or statement for appropriate action.</P>
        <P>(i) <E T="03">Ownership of DSS Investigative Records.</E> Personnel security investigative reports shall not be retained by DoD recipient organizations. Such reports are considered to be the property of the investigating organization and are on loan to the recipient organization for the purpose for which requested. All copies of such reports shall be destroyed within 120 days after the completion of the final personnel security determination and the completion of all personnel action necessary to implement the determination. Reports that are required for longer periods may be retained only with the specific written approval of the investigative organization.</P>
        <P>(j) <E T="03">Consultation and referral.</E> DSS system of records may contain records originated by other components or agencies which may have claimed exemptions for them under the Privacy Act of 1974. When any action that may be exempted is initiated concerning such a record, consultation with the originating agency or component will be effected. Where appropriate such records will be referred to the originating component or agency for approval or disapproval of the action.</P>
      </SECTION>
    </PART>
    <PART>
      <EAR>Pt. 322</EAR>
      <HD SOURCE="HED">PART 322—PRIVACY ACT SYSTEMS OF RECORDS—DISCLOSURES AND AMENDMENT PROCEDURES—SPECIFIC EXEMPTIONS, NATIONAL SECURITY AGENCY</HD>
      <CONTENTS>
        <SECHD>Sec.</SECHD>
        <SECTNO>322.1</SECTNO>
        <SUBJECT>Purpose and scope.</SUBJECT>
        <SECTNO>322.2</SECTNO>
        <SUBJECT>Definitions.</SUBJECT>
        <SECTNO>322.3</SECTNO>
        <SUBJECT>Procedures for requests concerning individual records in a system of records.</SUBJECT>
        <SECTNO>322.4</SECTNO>
        <SUBJECT>Times, places and procedures for disclosures.</SUBJECT>
        <SECTNO>322.5</SECTNO>
        <SUBJECT>Medical or psychological records.</SUBJECT>
        <SECTNO>322.6</SECTNO>
        <SUBJECT>Parents or legal guardians acting on behalf of minor applicants and employees.</SUBJECT>
        <SECTNO>322.7</SECTNO>
        <SUBJECT>Procedures for amendment.</SUBJECT>
        <SECTNO>322.8</SECTNO>
        <SUBJECT>Appeal determination.</SUBJECT>
        <SECTNO>322.9</SECTNO>
        <SUBJECT>Fees.</SUBJECT>
        <SECTNO>322.10</SECTNO>
        <SUBJECT>Specific exemptions.</SUBJECT>
      </CONTENTS>
      <AUTH>
        <HD SOURCE="HED">Authority:</HD>
        <P>Pub. L. 93-579; 88 Stat. 1896 (5 U.S.C. 552a).</P>
      </AUTH>
      <SOURCE>
        <HD SOURCE="HED">Source:</HD>
        <P>40 FR 44294, Sept. 25, 1975, unless otherwise noted. Redesignated at 56 FR 55631, Oct. 29, 1991.</P>
      </SOURCE>
      <SECTION>
        <SECTNO>§ 322.1</SECTNO>
        <SUBJECT>Purpose and scope.</SUBJECT>
        <P>(a) The purpose of this rule is to comply with and implement title 5 U.S.C. 552a, sections (f) and (k), hereinafter identified as the Privacy Act. It establishes the procedures by which an individual may be notified whether a system of records contains information pertaining to the individual; defines times, places and requirements for identification of the individual requesting records, for disclosure of requested records where appropriate; special handling for medical and psychological records; for amendment of records; appeal of denials of requests for amendment; and provides a schedule of fees to be charged for making copies of requested records. In addition, this rule contains the exemptions promulgated by the Director, NSA, pursuant to 5 U.S.C. 552a(k), to exempt Agency systems of records from subsections (c)(3); (d); (e)(1); (e)(4)(G), (H), (I); and (f) of section 552a.</P>

        <P>(b) The procedures established and exemptions claimed apply to systems of records for which notice has been published in the <E T="04">Federal Register</E>
          <PRTPAGE P="920"/>pursuant to the Privacy Act. Requests from individuals for records pertaining to themselves will be processed in accordance with these procedures and consistent with the exemptions claimed. Requests for records which do not specify the statute pursuant to which they are made but which may be reasonably construed to be requests by an individual for records pertaining to that individual will also be processed in accordance with these procedures and consistent with exemptions claimed. To the extent appropriate, these procedures apply to records maintained by this Agency pursuant to system of records notices published by the Civil Service Commission. The primary category of records affected by a Commission notice is that maintained in conjunction with the CSC system identified as “CSC-Retirement Life Insurance and Health Benefits Records System.” Authority pursuant to 44 U.S.C. 3101 to maintain each system of records for which notice has been published is implied in each “authority for maintenance of a system” of each systems notice.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 322.2</SECTNO>
        <SUBJECT>Definitions.</SUBJECT>
        <P>(a) <E T="03">Access to the NSA headquarters:</E> means current and continuing daily access to those facilities making up the NSA headquarters.</P>
        <P>(b) <E T="03">Individual:</E> means a natural person who is a citizen of the United States or an alien lawfully admitted for permanent residence.</P>
        <P>(c) <E T="03">Request:</E> means a request in writing for records pertaining to the requester contained in a system of rec- -ords and made pursuant to the Privacy Act or if no statute is identified considered by the Agency to be made pursuant to that Act.</P>
        <P>(d) <E T="03">System of Records:</E> means a grouping of records maintained by the Agency for which notice has been published in the <E T="04">Federal Register</E> pursuant to section 552a(e)(4) of Title 5 U.S.C.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 322.3</SECTNO>
        <SUBJECT>Procedures for requests concerning individual records in a system of records.</SUBJECT>
        <P>(a)(1) <E T="03">Notification.</E> Any individual may be notified in response to a request if any system of records contains a record pertaining to the requester by sending a request addressed to: Information Officer, National Security Agency, Fort George G. Meade, Maryland 20755. Such request shall be in writing, shall be identified on the envelope and the request as a “Privacy Act Request,” shall designate the system or systems of records using the names of the systems as published in the system notices, shall contain the full name, present address, date of birth, social security number and dates of affiliation or contact with NSA/CSS of the requester and shall be signed in full by the requester.</P>
        <P>(2) A request pertaining to records concerning the requester which does not specify the Act pursuant to which the request is made shall be processed as a Privacy Act request. A request which does not designate the system or systems of records to be searched shall be processed by checking the following systems of records: Applicants; Personnel; Health, Medical and Safety.</P>
        <P>(b)(1) <E T="03">Identification.</E> Any individual currently not authorized access to the National Security Agency headquarters who requests disclosure of records shall provide the following information with the written request for disclosure: full name, present address, date of birth, social security number, and date of first affiliation or contact with NSA/CSS and date of last affiliation or contact with NSA/CSS.</P>
        <P>(2) Any individual currently authorized access to the National Security Agency headquarters shall provide the following information with the request for notification: full name, present organizational assignment, date of birth, social security number.</P>
        <P>(3) Such request shall be treated as a certification of the requester that the requester is the individual named. Individuals should be aware that the Privacy Act provides criminal penalties for any person who knowingly and willfully requests or obtains any rec- -ords concerning an individual under false pretenses.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 322.4</SECTNO>
        <SUBJECT>Times, places and procedures for disclosures.</SUBJECT>
        <P>(a) Individual not currently affiliated with NSA:</P>
        <P>(1) <E T="03">Request procedure.</E> Any individual currently not authorized access to the <PRTPAGE P="921"/>National Security Agency headquarters shall make the request for notification in writing and shall include the required identifying data. Upon verification of the existence in systems of records pertaining to the requester, a copy of the records located shall be mailed to the requester subject to appropriate specific exemptions, applicable Public Laws, special procedures pertaining to medical rec- -ords, including psychological records, and the exclusion for information compiled in reasonable anticipation of a civil action or proceeding. If the request cannot be processed within ten working days from the time of receipt of the request, an acknowledgment of receipt of the request will be sent to the requester.</P>
        <P>(2) <E T="03">Appointment of other individual.</E> If a requester wishes another individual to obtain the requested records on his behalf, the requester shall provide a written, signed, notarized statement appointing that individual as his representative, certifying that the individual appointed may have access to the records of the requester and that such access shall not constitute an invasion of the privacy of the requester nor a violation of his rights under the Privacy Act of 1974.</P>
        <P>(b) <E T="03">Individual currently affiliated with NSA—</E>(1) <E T="03">Request procedure.</E> Any individual currently authorized access to the National Security Agency headquarters may make the request for notification to the appropriate official delegated responsibility for a system of records pursuant to internal agency regulations pertaining to the Privacy Act of 1974. In the alternative, such individual may direct the request to the NSA Information Officer in writing in the same form and including the data required in § 322.4(a)(1) above. In the case of any denial of notification by officials delegated responsibility for a system the request shall be referred to the NSA Information Officer for review.</P>
        <P>(2) <E T="03">Appointment of other individual.</E> If the requester makes a request pursuant to this paragraph and wishes to designate another individual to accompany him, the same procedures as provided in paragraph (a)(2) of this section apply. If the individual appointed is currently authorized access to the National Security Agency headquarters, he may accompany the requester. If the individual appointed is not currently authorized access, a copy of the records located may be mailed to the appointed individual subject to appropriate specific exemptions, applicable Public Laws, special procedures pertaining to medical records including psychological records, and the exclusion for information compiled in reasonable anticipation of a civil action or proceeding.</P>
        <CITA>[40 FR 44294, Sept. 25, 1975. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57803, Nov. 14, 1991]</CITA>
      </SECTION>
      <SECTION>
        <SECTNO>§ 322.5</SECTNO>
        <SUBJECT>Medical or psychological records.</SUBJECT>
        <P>If the request includes records of a medical or psychological nature, and if an Agency doctor makes the determination that the records requested contain information which would have an adverse effect upon the requester, the requester will be advised to appoint a medical doctor in the appropriate discipline to receive the information. The appointment of the doctor shall be in the same form as that indicated in § 322.4(a)(2) and shall include a certification that the doctor appointed is authorized to practice the appropriate specialty by virtue of a license to practice same in the state which granted the license.</P>
        <CITA>[40 FR 44294, Sept. 25, 1975. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57803, Nov. 14, 1991]</CITA>
      </SECTION>
      <SECTION>
        <SECTNO>§ 322.6</SECTNO>
        <SUBJECT>Parents or legal guardians acting on behalf of minor applicants and employees.</SUBJECT>

        <P>Parents or legal guardians acting on behalf of minors who request rec-ords concerning NSA/CSS applicants or employees who are minors shall be subject to the same requirements contained in § 322.4(a)(1) appointment of other individuals, including the requirement for written authorization. Requests by parents or legal guardians acting on behalf of minors will be processed in the same manner and in accordance with the procedures established herein <PRTPAGE P="922"/>for individuals not currently authorized access to the NSA headquarters.</P>
        <CITA>[40 FR 44294, Sept. 25, 1975. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57803, Nov. 14, 1991]</CITA>
      </SECTION>
      <SECTION>
        <SECTNO>§ 322.7</SECTNO>
        <SUBJECT>Procedures for amendment.</SUBJECT>
        <P>(a) <E T="03">Request procedure.</E> Any request for amendment of a record or records contained in a system of records shall be in writing addressed to the Information Officer, National Security Agency, Fort George G. Meade, Md. 20755, Attention: Privacy Act Amendment, and shall contain sufficient details concerning the requested amendment, justification for the amendment, and a copy of the record(s) to be amended or sufficient identifying data concerning the affected record(s) to permit its timely retrieval. Such requests may not be used to accomplish actions for which other procedures have been established such as grievances, performance appraisal protests, etc. In such cases the requester will be advised of the appropriate procedures for such actions.</P>
        <P>(b) <E T="03">Initial determination:</E> The NSA Information Officer may make an initial determination concerning the requested amendment within ten working days or shall acknowledge receipt of the amendment request within that period if a determination cannot be completed. The determination shall advise the requester of action taken to make the requested amendment or inform the requester of the rejection of the request, the reason(s) for the rejection and the procedures established by the Agency for review of rejected amendment requests.</P>
        <P>(c) <E T="03">Request on appeal:</E> A requester may appeal the rejection by the NSA Information Officer of a request for amendment to the Executive for Staff Services. Such appeal shall be in writing, addressed to the Executive for Staff Services, National Security Agency, Fort George G. Meade, Md. 20755, Attention: Privacy Act Amendment Appeal.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 322.8</SECTNO>
        <SUBJECT>Appeal determination.</SUBJECT>
        <P>The Executive for Staff Services shall acknowledge receipt of the appeal within ten working days. A determination concerning the appeal shall be provided to the requester within 30 working days, unless the Director, National Security Agency, extends the period for good cause. The Executive for Staff Services shall advise the requester of the action taken to make the requested amendment or inform the requester of the rejection of the appeal, the right to submit for incorporation in the file containing the disputed record(s) a concise statement of disagreement, and notify the requester of the right of judicial review of the denial pursuant to subsection (g)(1)(A) of 5 U.S.C. 552a.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 322.9</SECTNO>
        <SUBJECT>Fees.</SUBJECT>
        <P>A fee may be charged for the reproduction of copies of any requested rec- -ords, provided one copy is made available without charge where access is limited to mail service only. Fees shall be charged in accordance with The Uniform Schedule of Fees established by the Department of Defense pursuant to Pub. L. 93-502.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 322.10</SECTNO>
        <SUBJECT>Specific exemptions.</SUBJECT>

        <P>(a)(1) The following National Security Agency systems of records, published in the <E T="04">Federal Register</E>, are specifically exempted from the provisions of 5 U.S.C. 552a, subsections (c)(3), (d), (e)(1), (e)(4)(G), (e)(4)(H), (e)(4)(I) and (f) pursuant to subsection (k) of section 552a to the extent that each system contains individual rec-ords or files within the category or categories provided by subsection (k). Notice is hereby given that individual records and files within each NSA system of records may be subject to specific provisions of Pub. L. 86-36, Pub. L. 88-290 and Title 18 U.S.C. 798 and other laws limiting access to certain types of information or application of laws to certain categories of information.</P>
        <P>(2) In addition, those records maintained pursuant to notice of systems of records published by the CSC are exempted pursuant to Title 5 U.S.C. 552a(k)(1) to the extent that they contain classified information in order to protect such information from unauthorized disclosure. Such records may also be subject to other specific exemptions pursuant to rules promulgated by the CSC.</P>
        <P>(b) Systems of records subject to specific exemptions:
        </P>
        <EXTRACT>
          <PRTPAGE P="923"/>
          <P>(1) <E T="03">System name:</E> NSA/CSS Access, Authority and Release of Information File.</P>
          <P>
            <E T="03">Exemption:</E> This system of records is exempted from the sections of title 5 U.S.C. 552a cited in paragraph 322.10(a) and is subject to the limitations noted in that paragraph.</P>
          <P>
            <E T="03">Authority:</E> 5 U.S.C. 552a(k)(1), (k)(5)</P>
          <P>
            <E T="03">Reasons:</E> This system of records is exempted from all subsections cited pursuant to exemption (k)(1) to protect from unauthorized disclosure classified information which may be contained in records and files making up the system. The exemption does not limit access to that portion of the rec- -ords in the system which are not classified or otherwise protected from unauthorized disclosure.</P>
          <P>This system of records is also exempted from all subsections cited pursuant to exemption (k)(5) to protect the identity of confidential sources of information constituting investigatory material compiled solely for the purpose of determining access to classified information. The exemption does not limit access to that portion of the records in the system which are not exempted, not otherwise protected from unauthorized disclosure, and which would not undermine the integrity of the controlled access system.</P>
          <P>(2) <E T="03">System name:</E> NSA/CSS Applicants</P>
          <P>
            <E T="03">Exemption:</E> This system of records is exempted from the sections of Title 5 U.S.C. 552a cited in paragraph 322.10(a) and is subject to the limitations noted in that paragraph.</P>
          <P>
            <E T="03">Authority:</E> 5 U.S.C. 552a(k)(1), (k)(5)</P>
          <P>
            <E T="03">Reasons:</E> This system of records is exempted from all subsections cited pursuant to exemption (k)(1) to protect from unauthorized disclosure classified information which may be contained in records and files making up the system. The exemption does not limit access to that portion of the rec- -ords in the system which are not classified or otherwise protected from unauthorized disclosure.</P>
          <P>This system of records is also exempted from all subsections cited pursuant to exemption (k)(5) to protect the identity of confidential sources of information constituting investigatory material compiled solely for the purposes of determining suitability; eligibility; qualifications for Federal civilian employment; Federal contracts; or access to classified information which may be contained in records and files making up the system. The exemption does not limit access to that portion of the records in the system which are not subject to this exemption, nor otherwise protected from unauthorized disclosure.</P>
          <P>(3) <E T="03">System name:</E> NSA/CSS Correspondence, Cases, Complaints, Visitors, Requests</P>
          <P>
            <E T="03">Exemption:</E> This system of records is exempted from the sections of Title 5 U.S.C. 552a cited in § 322.10(a) and is subject to the limitations noted in that paragraph.</P>
          <P>
            <E T="03">Authority:</E> 5 U.S.C. 552a(k)(1), (k)(2), (k)(4), (k)(5)</P>
          <P>
            <E T="03">Reasons:</E> This system of records is exempted from all subsections cited pursuant to exemption (k)(1) to protect from unauthorized disclosure classified information which may be contained in records and files making up the system. The exemption does not limit access to that portion of the rec- -ords in the system which are not classified or otherwise protected from unauthorized disclosure.</P>
          <P>This system of records is exempted from all subsections cited pursuant to exemption (k)(2) to protect from unauthorized disclosure individual records and files which constitute investigatory material compiled for law enforcement purposes pursuant to a lawful national security intelligence investigation and maintain the integrity of the personnel security system required by Pub. L. 88-290. The exemption does not limit access to that portion of the records in the system which are not investigatory material which are not exempted or otherwise protected from unauthorized disclosure.</P>
          <P>This system is exempted from all subsections cited pursuant to exemption (k)(4) where individual records and files are maintained and used solely for statistical records in accordance with statutory requirements to insure compliance with those requirements with a minimum of administrative burden and expense.</P>
          <P>This system is exempted from all subsections cited pursuant to exemption (k)(5) to protect the identity of confidential sources of information constituting investigatory material compiled solely for the purpose of determining suitability; eligibility; qualifications for Federal civilian employment, Federal contracts; or access to classified information which may be contained in records and files making up the system. The exemption does not limit access to that portion of the records in the system which are not subject to this exemption or otherwise protected from unauthorized disclosure.</P>
          <P>(4) <E T="03">System name:</E> NSA/CSS Cryptologic Reserve Mobilization Designee List</P>
          <P>
            <E T="03">Exemption:</E> This system of records is exempted from the sections of Title 5 U.S.C. 552a cited in § 322.10(a) and is subject to the limitations noted in that paragraph.</P>
          <P>
            <E T="03">Authority:</E> 5 U.S.C. 552a (k) (1), (k) (5)</P>
          <P>
            <E T="03">Reasons:</E> This system of records is exempted from all subsections cited pursuant to exemption (k)(1) to prevent the unauthorized disclosure of classified information concerning anticipated personnel assignments to sensitive cryptologic positions during periods of national emergency or war requiring reserve mobilization.</P>

          <P>This system of records is also exempted from all subsections cited pursuant to exemption (k)(5) to protect the identity of confidential sources of information constituting <PRTPAGE P="924"/>investigatory material compiled solely for the purpose of determining suitability, eligibility or qualifications for designation for mobilization to fill a sensitive cryptologic position or access to classified material as a result of designation for mobilization.</P>
          <P>(5) <E T="03">System name:</E> NSA/CSS Equal Employment Opportunity Data</P>
          <P>
            <E T="03">Exemption:</E> This system of records is exempted from the sections of Title 5 U.S.C. 552a cited in § 322.10(a) and is subject to the limitations noted in that paragraph.</P>
          <P>
            <E T="03">Authority:</E> 5 U.S.C. 552a(k) (1), (k) (2), (4)</P>
          <P>
            <E T="03">Reasons:</E> This system of records is exempted from all subsections cited pursuant to exemption (k)(1) to protect from unauthorized disclosure classified information which may be contained in records and files making up the system. The exemption does not limit access to that portion of the rec- -ords in the system which are not classified or otherwise protected from unauthorized disclosure.</P>
          <P>This system of records is exempted from all subsections cited pursuant to exemption (k)(4) to protect the integrity of those statistical records compiled for Equal Employment Opportunity purposes.</P>
          <P>This system of records is also exempted from all subsections cited pursuant to exemption (k)(2) to the extent that individual records and files are related to investigations to enforce the provisions of Pub. L. 92-261 and consistent with the provisions of that statute with respect to individual access to such records. The purpose of the exemption is to protect the integrity of investigations conducted pursuant to Pub. L. 92-261.</P>
          <P>(6) <E T="03">System name:</E> NSA/CSS Health, Medical and Safety Files</P>
          <P>
            <E T="03">Exemption:</E> This system of records is exempted from sections of Title 5 U.S.C. 552a cited in § 322.10(a) and is subject to the statutory limitations noted in that paragraph.</P>
          <P>
            <E T="03">Authority:</E> 5 U.S.C. 552a(k) (1), (k) (5), (k) (6).</P>
          <P>
            <E T="03">Reasons:</E> This system of records is exempted from all subsections cited pursuant to exemption (k)(1) to protect from unauthorized disclosure classified information which may be contained in records and files making up the system. The exemption does not limit access to that portion of the rec- -ords in the system which are not classified or otherwise protected from unauthorized disclosure.</P>
          <P>This system of records is exempted from all subsections cited pursuant to exemption (k)(5) to protect the identity of confidential sources of information constituting investigatory material compiled solely for the purpose of determining suitability, eligibility, or qualifications for Federal civilian employment, Federal contracts or access to classified information. The exemption does not limit access to that portion of the records in the system which are not exempted or otherwise protected from unauthorized disclosure.</P>
          <P>This system of records is also exempted from all subsections cited pursuant to exemption (k)(6) to protect those testing or examination materials used solely to determine individual qualifications for employment in the Federal service the disclosure of which would compromise the objectivity or fairness of the testing or examination process.</P>
          <P>(7) <E T="03">System name:</E> NSA/CSS Motor Vehicles and Carpools</P>
          <P>
            <E T="03">Exemption:</E> This system of records is exempted from the sections of Title 5 U.S.C. 552a cited in § 322.10(a) and is subject to the statutory limitations noted in that paragraph.</P>
          <P>
            <E T="03">Authority:</E> 5 U.S.C. 552a(k)(1)</P>
          <P>
            <E T="03">Reasons:</E> This system of records is exempted from all subsections cited pursuant to exemption (k)(1) to protect from unauthorized disclosure any and all classified information which may be contained in rec-ords and files making up the system. The exemption does not limit access to that portion of the of the records in the system which are not classified or otherwise protected from unauthorized disclosure.</P>
          <P>(8) <E T="03">System name:</E> NSA/CSS Payroll and Claims</P>
          <P>
            <E T="03">Exemption:</E> This system of records is exempted from the sections of Title 5 U.S.C. 552a cited in § 322.10(a) and is subject to the statutory limitations noted in that paragraph.</P>
          <P>
            <E T="03">Authority:</E> 5 U.S.C. 552a(k) (1), (k) (2)</P>
          <P>
            <E T="03">Reasons:</E> This system of records is exempted from all subsections cited pursuant to exemption (k)(1) to protect from unauthorized disclosure classified information which may be contained in records and files making up this system. The exemption does not limit access to that portion of the records in the system which are not classified or otherwise protected from unauthorized disclosure.</P>
          <P>This system of records is also exempted from all subsections cited pursuant to exemption (k)(2) to protect investigatory materials related to the enforcement of laws with respect to claims against the Government. The exemption does not limit access to that portion of the records in the system not related to investigations of claims or otherwise protected from unauthorized disclosure.</P>
          <P>(9) <E T="03">System name:</E> NSA/CSS Personnel File</P>
          <P>
            <E T="03">Exemption:</E> This system of records is exempted from the sections of Title 5 U.S.C. 552a cited in § 322.10(a) and is subject to the statutory limitations noted in that paragraph.</P>
          <P>
            <E T="03">Authority:</E> 5 U.S.C. 552a(k) (1), (k) (5), (k) (6)</P>
          <P>
            <E T="03">Reasons:</E> This system of records is exempted from all subsections cited pursuant to exemption (k)(1) to protect from unauthorized disclosure classified information which may be contained in records and files making up <PRTPAGE P="925"/>the system. The exemption does not limit access to that portion of the rec- -ords in the system which are not classified or otherwise protected from unauthorized disclosure.</P>
          <P>This system of records is exempted from all subsections cited pursuant to exemption (k)(5) to protect the identity of confidential sources of information constituting investigatory material compiled solely for the purpose of determining suitability, eligibility, or qualifications for Federal civilian employment, Federal contracts or access to classified information. The exemption does not limit access to that portion of the records in the system which are not exempted or otherwise protected from unauthorized disclosure.</P>
          <P>This system of records is also exempted from all subsections cited pursuant to exemption (k)(6) to protect those testing or examination materials used solely to determine individual qualifications for employment in the Federal service the disclosure of which would compromise the objectivity or fairness of the testing or examination process.</P>
          <P>(10) <E T="03">System name:</E> NSA/CSS Personnel Security File</P>
          <P>
            <E T="03">Exemption:</E> This system of records is exempted from the sections of Title 5 U.S.C. 552a cited in § 322.10(a) and is subject to the limitations noted in that paragraph.</P>
          <P>
            <E T="04">Authority:</E> 5 U.S.C. 552a (k)(1), (k)(2), (k)(5), and (k)(6)</P>
          <P>
            <E T="03">Reasons:</E> This system of records is exempted from all subsections cited pursuant to exemption (k)(1) to protect from unauthorized disclosure classified information which may be contained in records and files making up the system. The exemption does not limit access to that portion of the rec- -ords in the system which are not classified or otherwise protected from unauthorized disclosure.</P>
          <P>This system of records is exempted from all subsections cited pursuant to exemption (k)(2) to protect investigatory materials compiled for purposes of enforcement of Pub. L. 88-290 and title 18 U.S.C. 798 as well as other appropriate criminal and civil laws related to the protection of sensitive cryptologic information. Both statutes cited require the Director, NSA, to observe special procedures and standards in permitting access to sensitive cryptologic information and provide statutory authority to act when those standards are breached. The materials contained in this system are of an investigatory nature, are maintained on a continuing basis and are used to insure compliance with and enforcement of the cited statutes.</P>
          <P>This system of records is exempted from all subsections cited pursuant to exemption (k)(5) to protect the identity of confidential sources of information constituting investigatory material compiled solely for the purpose of determining suitability, eligibility, or qualifications for Federal civilian employment, Federal contracts or access to classified information. The exemption does not limit access to that portion of the records in the system which are not exempted or otherwise protected from unauthorized disclosure.</P>
          <P>This system of records is exempted from all subsections cited pursuant to exemption (k)(6) to protect testing or examination materials and procedures, the disclosure of which would compromise the objectivity or fairness of the testing or examination process.</P>
          <P>(11) <E T="03">System name:</E> NSA/CSS Time, Attendance, and Absence</P>
          <P>
            <E T="03">Exemption:</E> This system of records is exempted from the sections of Title 5 U.S.C. 552a cited in § 322.10(a) and is subject to the limitations noted in that paragraph.</P>
          <P>
            <E T="03">Authority:</E> 5 U.S.C. 552a(k)(1)</P>
          <P>
            <E T="03">Reasons:</E> This system of records is exempted from all subsections cited pursuant to exemption (k)(1) to protect from unauthorized disclosure classified information which may be contained in records and files making up the system. The exemption does not limit access to that portion of the rec- -ords in the system which are not classified or otherwise protected from unauthorized disclosure.</P>
          <P>(12) <E T="03">System name:</E> NSA/CSS Training</P>
          <P>
            <E T="03">Exemption:</E> This system of records is exempted from the sections of Title 5 U.S.C. 552a cited in § 322.10(a) and is subject to the limitations noted in that paragraph.</P>
          <P>
            <E T="03">Authority:</E> 5 U.S.C. 552a (k)(1), (k)(5), (k)(6).</P>
          <P>
            <E T="03">Reasons:</E> This system of records is exempted from all subsections cited pursuant to exemption (k)(1) to protect from unauthorized disclosure classified information which may be contained in records and files making up the system. The exemption does not limit access to that portion of the rec-ords in the system which are not classified or otherwise protected from unauthorized disclosure.</P>
          <P>This system of records is exempted from all subsections cited pursuant to exemption (k)(5) to protect the identity of confidential sources of information constituting investigatory material compiled solely for the purpose of determining suitability, eligibility, or qualifications for Federal civilian employment, Federal contracts or access to classified information. The exemption does not limit access to that portion of the records in the system which are not exempted or otherwise protected from unauthorized disclosure.</P>

          <P>This system of records is also exempted from all subsections cited pursuant to exemption (k)(6) to protect those testing or examination materials used solely to determine individual qualifications for employment in the Federal service the disclosure of which would compromise the objectivity or fairness of the testing or examination process.<PRTPAGE P="926"/>
          </P>
          <P>(13) <E T="03">System name:</E> NSA/CSS Archival Rec-ords.</P>
          <P>
            <E T="03">Exemption:</E> This system is exempted from the sections of Title 5 U.S.C. 552a cited in § 322.10(a) and is subject to the statutory limitations noted in that paragraph.</P>
          <P>
            <E T="03">Authority:</E> 5 U.S.C. 552a(k)(1) and (k)(4).</P>
          <P>
            <E T="03">Reasons:</E> This system of records is exempted from all subsections cited pursuant to exemption (k)(1) to protect from unauthorized disclosure classified information which may be contained in records and files making up the system. The exemption does not limit access to that portion of the rec- -ords in the system which are not classified or otherwise protected from unauthorized disclosure.</P>
          <P>This system is exempted from all subsections cited pursuant to exemption (k)(4) where individual records and files are maintained and used solely for statistical compliance with those requirements with a minimum of administrative burden and expense.</P>
          <P>(14) <E T="03">System Identification and Name—</E> GNSA14, entitled “NSA/CSS Library Patron File Control System”.</P>
          <P>
            <E T="03">Exemption</E>—Portions of this system which fall within 5 U.S.C. 552a (k)(1) and (k)(4) are exempt from the following provisions of 5 U.S.C. 552a, sections (c)(3), (d) (1)-(5), (e)(1), (e)(4) (G)-(I), and (f) (1)-(5).</P>
          <P>
            <E T="03">Authority</E>—5 U.S.C. 552a (k)(1) and (k)(4).</P>
          <P>
            <E T="03">Reasons</E>—This record system is exempted from all subsections pursuant to exemption (k)(1) to protect from unauthorized disclosure classified information which may be contained in records and files making up the system. The exemption does not limit access to that portion of the records in the system which are not classified or otherwise protected from unauthorized disclosure.</P>
          <P>This record system is exempted from all subsections pursuant to exemption (k)(4) to protect from unauthorized disclosure records maintained for statistical research or program evaluation. The exemption does not limit access to that portion of the records in the system which are not classified or otherwise protected from unauthorized disclosure.</P>
          <P>(15) <E T="03">System Identification and Name</E>—GNSA15, entitled “NSA/CSS Computer Users Control System”.</P>
          <P>
            <E T="03">Exemption</E>—Portions of this system which fall within 5 U.S.C. 552a (k)(1) and (k)(2) are exempt from the following provisions of 5 U.S.C. 552a, sections (c)(3), (d) (1)-(5), (e)(1), (e)(4) (G)-(I), and (f) (1)-(5).</P>
          <P>
            <E T="03">Authority</E>—5 U.S.C. 552a (k)(1) and (k)(2).</P>
          <P>
            <E T="03">Reasons</E>—This system of records is exempted from all subsections pursuant to exemption (k)(1) to protect from unauthorized disclosure classified information which may be contained in records and files making up the system. The exemption does not limit access to that portion of the records in the system which are not classified or otherwise protected from unauthorized disclosure.</P>
          <P>This system of records is exempted from all subsections cited pursuant to exemption (k)(2) to the extent that individual records and files are related to investigations to enforce the provisions of Pub. L. 88-290 and consistent with the provisions of that statute with respect to individual access to such records. The purpose of the exemption is to protect the integrity of investigations conducted pursuant to Pub. L. 88-290.</P>
          <P>(16) <E T="03">System Identification and Name</E>—GNSA16, entitled “NSA/CSS Drug Testing Program”.</P>
          <P>
            <E T="03">Exemption</E>—Portions of this system which fall within 5 U.S.C. 552a(k)(1) are exempt from the following provisions of 5 U.S.C. 552a, sections (c)(3), (d) (1)-(5), (e)(1), (e)(4) (G)-(I), and (f) (1)-(5).</P>
          <P>
            <E T="03">Authority</E>—5 U.S.C. 552a(k)(1).</P>
          <P>
            <E T="03">Reasons</E>—This system of records is exempted from all subsections cited pursuant to exemption (k)(1) to protect from unauthorized disclosure classified information which may be contained in records and files making up the system.</P>
          <P>(17) <E T="03">System Identification and Name</E>—GNSA17, entitled “Employee Assistance Service (EAS) Case Record System”.</P>
          <P>
            <E T="03">Exemption</E>—Portions of this system which fall within 5 U.S.C. 552a (k)(1), (k)(2), (k)(4) and (k)(5) are exempt from the following provisions of 5 U.S.C. 552a, sections (c)(3), (d) (1)-(5), (e)(1), (e)(4) (G)-(I), and (f) (1)-(5).</P>
          <P>
            <E T="03">Authority</E>—5 U.S.C. 552a (k)(1), (k)(2), (k)(4), and (k)(5).</P>
          <P>
            <E T="03">Reasons</E>—This system of records is exempted from all subsections cited pursuant to exemption (k)(1) to protect from unauthorized disclosure classified information which may be contained in records and files making up the system.</P>
          <P>This system of records is exempted from all subsections cited pursuant to exemption (k)(2) to the extent that individual records and files are related to investigations to enforce the provisions of Public Law 92-261 and consistent with the provisions of that statute with respect to individual access to such records. The purpose of the exemption is to protect the integrity of investigations conducted pursuant to Public Law 92-261.</P>
          <P>This record system is exempted from all subsections pursuant to exemption (k)(4) to protect from unauthorized disclosure records maintained for statistical research or program evaluation. The exemption does not limit access to that portion of the records in the system which are not classified or otherwise protected from unauthorized disclosure.</P>

          <P>This system of records is also exempted from all subsections cited pursuant to exemption (k)(5) to protect the identity of confidential sources of information constituting investigatory material compiled solely for the purpose of determining suitability, eligibility, or qualifications for federal civilian employment, federal contracts, or access to <PRTPAGE P="927"/>classified information. The exemption does not limit access to that portion of the records in the system which are not exempted or otherwise protected from unauthorized disclosure.</P>
          <P>(18) <E T="03">System identification and name</E>—GNSA18, NSA/CSS Operations Files.</P>
          <P>
            <E T="03">Exemption</E>—Portions of this record system may be exempted from subsections of 5 U.S.C. 552a (c)(3), (d)(1)—(5), (e)(4)(G)—(I), and (f)(1)—(5).</P>
          <P>
            <E T="03">Authority</E>—5 U.S.C. 552a(k) (1), (2) and (5).</P>
          <P>
            <E T="03">Reasons</E>—Subsection (c)(3) because there may be occasions when making an accounting available to the individual named in the record at his or her request, would reveal classified information. The release of accounting of disclosure would inform a subject that he or she is under investigation. This information would provide considerable advantage to the subject in providing him or her with knowledge concerning the nature of the investigation and the coordinated investigative efforts and techniques employed by the cooperating agencies.</P>
          <P>Subsection (d) because granting access and/or subsequent amendment to the record would reveal classified information. It may also alert a subject to the fact that an investigation of that individual is taking place, and might weaken the on-going investigation, reveal investigatory techniques, and place confidential informants in jeopardy. NSA/CSS may refuse to confirm or deny the existence of a particular record because to do so would reveal classified information.</P>
          <P>Subsection (e)(4)(G), (e)(4)(H), and (e)(4)(I). Although NSA/CSS has published procedures whereby an individual can be notified if a particular record system contains information about themselves; how to gain access to that information; and the source of the information, there may be occasions when confirming that a record exists, granting access, or giving out the source of the information would reveal classified information.</P>
          <P>Subsection (f) because the agency's rules are inapplicable to those portions of the system that are exempt and would place the burden on the agency of either confirming or denying the existence of a record pertaining to a requesting individual. The confirming or denying might, in itself, provide an answer to that individual relating to an on-going criminal investigation. The conduct of a successful investigation leading to the indictment of a criminal offender precludes the applicability of established agency rules relating to verification of record, disclosure of the record to that individual, and record amendment procedures for this record system. Also, because this record system is exempt from the individual access provisions of subsection (d).</P>
        </EXTRACT>
        <CITA>[40 FR 44294, Sept. 25, 1975, as amended at 45 FR 80106, Dec. 3, 1980; 52 FR 41711, Oct. 30, 1987; 55 FR 34907, Aug. 27, 1990; 56 FR 16007, Apr. 19, 1991. Redesignated at 56 FR 55631, Oct. 29, 1991, as amended at 56 FR 57803, Nov. 14, 1991]</CITA>
      </SECTION>
    </PART>
    <PART>
      <EAR>Pt. 323</EAR>
      <HD SOURCE="HED">PART 323—DEFENSE LOGISTICS AGENCY PRIVACY PROGRAM</HD>
      <CONTENTS>
        <SECHD>Sec.</SECHD>
        <SECTNO>323.1</SECTNO>
        <SUBJECT>Purpose and scope.</SUBJECT>
        <SECTNO>323.2</SECTNO>
        <SUBJECT>Policy.</SUBJECT>
        <SECTNO>323.3</SECTNO>
        <SUBJECT>Definitions.</SUBJECT>
        <SECTNO>323.4</SECTNO>
        <SUBJECT>Responsibilities.</SUBJECT>
        <SECTNO>323.5</SECTNO>
        <SUBJECT>Procedures.</SUBJECT>
        <SECTNO>323.6</SECTNO>
        <SUBJECT>Forms and reports.</SUBJECT>
        <APP>Appendix A to Part 323—Instructions for Preparation of System Notices</APP>
        <APP>Appendix B to Part 323—Criteria for New and Altered Record Systems</APP>
        <APP>Appendix C to Part 323—Instructions for Preparation of Reports to New or Altered Systems</APP>
        <APP>Appendix D to Part 323—Word Processing Center (WPC) Safeguards</APP>
        <APP>Appendix E to Part 323—OMB Guidelines for Matching Programs</APP>
        <APP>Appendix F to Part 323—Litigation Status Sheet</APP>
        <APP>Appendix G to Part 323—Privacy Act Enforcement Actions</APP>
        <APP>Appendix H to Part 323—DLA Exemption Rules</APP>
      </CONTENTS>
      <AUTH>
        <HD SOURCE="HED">Authority:</HD>
        <P>Privacy Act of 1974, Pub. L. 93-579, Stat. 1896 (5 U.S.C. 552a).</P>
      </AUTH>
      <SOURCE>
        <HD SOURCE="HED">Source:</HD>
        <P>DLAR 5400.21, 51 FR 33595, Sept. 22, 1986, unless otherwise noted. Redesignated at 56 FR 57803, Nov. 14, 1991.</P>
      </SOURCE>
      <SECTION>
        <SECTNO>§ 323.1</SECTNO>
        <SUBJECT>Purpose and scope.</SUBJECT>
        <P>This part 323 implements the Privacy Act of 1974 (5 U.S.C. 552a) and DoD Directive and DoD Regulation 5400.11, Department of Defense Privacy Program (32 CFR part 286a). It applies to Headquarters, Defense Logistics Agency (HQ DLA) and all DLA field activities.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 323.2</SECTNO>
        <SUBJECT>Policy.</SUBJECT>

        <P>It is the policy of DLA to safeguard personal information contained in any system of records maintained by DLA activities and to make that information available to the individual to whom it pertains to the maximum extent practicable. DLA policy specifically requires that DLA activities:<PRTPAGE P="928"/>
        </P>
        <P>(a) Collect, maintain, use, and disseminate personal information only when it is relevant and necessary to achieve a purpose required by statute or Executive Order.</P>
        <P>(b) Collect personal information directly from the individuals to whom it pertains to the greatest extent practical.</P>
        <P>(c) Inform individuals who are asked to supply personal information for inclusion in any system of records:</P>
        <P>(1) The authority for the solicitation.</P>
        <P>(2) Whether furnishing the information is mandatory or voluntary.</P>
        <P>(3) The intended uses of the information.</P>
        <P>(4) The routine disclosures of the information that may be made outside DoD.</P>
        <P>(5) The effect on the individual of not providing all of any part of the requested information.</P>
        <P>(d) Ensure that all records used in making determinations about individuals are accurate, relevant, timely, and complete.</P>
        <P>(e) Make reasonable efforts to ensure that records containing personal information are accurate, relevant, timely, and complete for the purposes for which they are being maintained before making them available to any recipients outside DoD, other than a Federal agency, unless the disclosure is made under DLAR 5400.14, DLA Freedom of Information Act Program (32 CFR part 1285).</P>
        <P>(f) Keep no record that describes how individuals exercise their rights guaranteed by the First Amendment of the U.S. Constitution, unless expressly authorized by statute or by the individual to whom the records pertain or is pertinent to and within the scope of an authorized law enforcement activity.</P>
        <P>(g) Make reasonable efforts, when appropriate, to notify individuals whenever records pertaining to them are made available under compulsory legal process, if such process is a matter of public record.</P>
        <P>(h) Establish safeguards to ensure the security of personal information and to protect this information from threats or hazards that might result in substantial harm, embarrassment, inconvenience, or unfairness to the individual.</P>
        <P>(i) Establish rules of conduct for DoD personnel involved in the design, development, operation, or maintenance of any system of records and train them in these rules of conduct.</P>
        <P>(j) Assist individuals in determining what records pertaining to them are being collected, maintained, used, or disseminated.</P>
        <P>(k) Permit individual access to the information pertaining to them maintained in any system of records, and to correct or amend that information, unless an exemption for the system has been properly established for an important public purpose.</P>
        <P>(l) Provide, on request, an accounting of all disclosures of the information pertaining to them except when disclosures are made:</P>
        <P>(1) To DoD personnel in the course of their official duties.</P>
        <P>(2) Under 32 CFR part 1285 (DLAR 5400.14).</P>
        <P>(m) Advise individuals on their rights to appeal any refusal to grant access to or amend any record pertaining to them, and to file a statement of disagreement with the record in the event amendment is refused.</P>
        <CITA>[DLAR 5400.21, 51 FR 33595, Sept. 22, 1986, unless otherwise noted. Redesignated at 56 FR 57803, Nov. 14, 1991, as amended at 66 FR 41781, Aug. 9, 2001]</CITA>
      </SECTION>
      <SECTION>
        <SECTNO>§ 323.3</SECTNO>
        <SUBJECT>Definitions.</SUBJECT>
        <P>(a) <E T="03">Access.</E> The review of a record or a copy of a record or parts thereof in a system of records by any individual.</P>
        <P>(b) <E T="03">Agency.</E> For the purpose of disclosing records subject to the Privacy Act among DoD Components, the Department of Defense is considered a single agency. For all other purposes including applications for access and amendment, denial of access or amendment, appeals from denials, and recordkeeping as regards release to non-DoD agencies, DLA is considered an agency within the meaning of the Privacy Act.</P>
        <P>(c) <E T="03">Confidential source.</E> A person or organization who has furnished information to the Federal Government under an express promise that the person's or the organization's identity will be held in confidence or under an implied promise of such confidentiality if this implied promise was made before September 27, 1975.<PRTPAGE P="929"/>
        </P>
        <P>(d) <E T="03">Disclosure.</E> The transfer of any personal information from a system of records by any means of communication to any person, private entity, or Government agency, other than the subject of the record, the subject's designated agent or the subject's legal guardian.</P>
        <P>(e) <E T="03">Individual.</E> A living citizen of the United States or an alien lawfully admitted to the United States for permanent residence. The legal guardian of an individual has the same rights as the individual and may act on his or her behalf.</P>
        <P>(f) <E T="03">Individual access.</E> Access to information pertaining to the individual by the individual or his or her designated agent or legal guardian.</P>
        <P>(g) <E T="03">Maintain.</E> Includes maintain, collect, use, or disseminate.</P>
        <P>(h) <E T="03">Member of the public.</E> Any individual or party acting in a private capacity to include Federal employees or military personnel.</P>
        <P>(i) <E T="03">Official use.</E> Within the context of this part, this term is used when officials and employees of a DLA activity have a demonstrated need for the use of any record or the information contained therein in the performance of their official duties.</P>
        <P>(j) <E T="03">Personal information</E>. Information about an individual that is intimate or private to the individual, as distinguished from information related solely to the individual's official functions or public life.</P>
        <P>(k) <E T="03">Privacy Act.</E> The Privacy Act of 1974, as amended, 5 U.S.C. 552a.</P>
        <P>(l) <E T="03">Privacy Act request.</E> A request from an individual for notification as to the existence of, access to, or amendment of records pertaining to that individual. These records must be maintained in a system of records. The request must indicate that it is being made under the Privacy Act to be considered a Privacy Act request.</P>
        <P>(m) <E T="03">Record.</E> Any item, collection, or grouping of information about an individual that is maintained by DLA, including, but not limited to, the individual's education, financial transactions, medical history, and criminal or employment history, and that contains the individual's name, or the identifying number, symbol, or other identifying particular assigned to the individual, such as a finger or voice print or a photograph.</P>
        <P>(n) <E T="03">Risk assessment.</E> An analysis considering information sensitivity, vulnerabilities, and the cost to a computer facility or word processing activity in safeguarding personal information processed or stored in the facility or activity.</P>
        <P>(o) <E T="03">Routine use</E>. The disclosure of a record outside DoD for a use that is compatible with the purpose for which the information was collected and maintained by DoD. The routine use must be included in the published system notice for the system of records involved.</P>
        <P>(p) <E T="03">Statistical record.</E> A record maintained only for statistical research or reporting purposes and not used in whole or in part in making determinations about specific individuals.</P>
        <P>(q) <E T="03">System of Records.</E> A group of records under the control of a DLA activity from which information is retrieved by the individual's name or by some identifying number, symbol, or other identifying particular assigned to the individual. System notices for all Privacy Act systems of records must be published in the <E T="04">Federal Register.</E>
        </P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 323.4</SECTNO>
        <SUBJECT>Responsibilities.</SUBJECT>
        <P>(a) Headquarters Defense Logistics Agency.</P>
        <P>(1) The Staff Director, Corporate Communications, DLA Support Services (DSS-C) will:</P>
        <P>(i) Formulate policies, procedures, and standards necessary for uniform compliance with the Privacy Act by DLA activities.</P>
        <P>(ii) Serve as the DLA Privacy Act Officer and DLA representative on the Defense Privacy Board.</P>
        <P>(iii) Maintain a master registry of system notices published by DLA.</P>
        <P>(iv) Develop or compile the rules, notices, and reports required under this part.</P>

        <P>(v) Establish training programs for all individuals with public affairs duties, and all other personnel whose duties require access to or contact with systems of records affected by the Privacy Act. Initial training will be given <PRTPAGE P="930"/>to new employees and military members upon assignment. Refresher training will be provided annually or more frequently if conditions warrant.</P>
        <P>(2) The General Counsel, DLA (DLA-GC) will:</P>
        <P>(i) Serve as the appellate authority for denials of individual access and amendment of records.</P>
        <P>(ii) Provide representation to the Defense Privacy Board Legal Committee.</P>
        <P>(iii) Advise the Defense Privacy Office on the status of DLA privacy litigation.</P>
        <P>(3) The DLA Chief Information Office (J-6) will formulate and implement protective standards for personal information maintained in automated data processing systems and facilities.</P>
        <P>(b) The Heads of DLA Primary Level Field Activities (PLFAs) will:</P>
        <P>(1) Ensure that the collection, maintenance, use, or dissemination of records of identifiable personal information is in a manner that assures that such action is for a necessary and lawful purpose; that the information is timely and accurate for its intended use; and that adequate safeguards are provided to prevent misuse of such information.</P>
        <P>(2) Designate a Privacy Act Officer to serve as the principal point of contact on privacy matters.</P>
        <P>(3) Ensure the internal operating procedures provide for effective compliance with the Privacy Act.</P>
        <P>(4) Establish training programs for all individuals with public affairs duties, and all other personnel whose duties require access to or contact with systems of records affected by the Privacy Act. Initial training will be given to new employees and military members upon assignment. Refresher training will be provided annually or more frequently if conditions warrant.</P>
        <CITA>[DLAR 5400.21, 51 FR 33595, Sept. 22, 1986, unless otherwise noted. Redesignated at 56 FR 57803, Nov. 14, 1991, as amended at 66 FR 41781, Aug. 9, 2001]</CITA>
      </SECTION>
      <SECTION>
        <SECTNO>§ 323.5</SECTNO>
        <SUBJECT>Procedures.</SUBJECT>
        <P>(a) <E T="03">Individual access.</E> (1) The access provisions of this part are intended for use by individuals whose records are maintained in systems of records. Release of personal information to individuals under this part is not considered public release of information.</P>
        <P>(2) Individuals will address requests for access to personal information about themselves in a system of records to the system manager or to the office designated in the system notice. Before being granted access to personal data, an individual may be required to provide reasonable verification of his or her identity. Identity verification procedures will be simple so as not to discourage individuals from seeking access to information about themselves; or be required of an individual seeking access to records which normally would be available under 32 CFR part 1285 (DLAR 5400.14).</P>
        <P>(i) Normally, when individuals seek personal access to records pertaining to themselves, identification will be made from documents that normally are readily available, such as employee and military identification cards, driver's license, other licenses, permits, or passes used for routine identification purposes.</P>
        <P>(ii) When access is requested by mail, identity verification may consist of the individual providing certain minimum identifying data, such as full name, date and place of birth, or such other personal information necessary to locate the record sought. If the information sought is sensitive, additional identifying data may be required. If notarization of requests is required, procedures will be established for an alternate method of verification for individuals who do not have access to notary services, such as military members overseas.</P>

        <P>(3) If an individual wishes to be accompanied by a third party when seeking access to his or her records or to have the records released directly to a third party, the individual may be required to furnish a signed access authorization granting the third party access. An individual will not be refused access to his or her record solely for failure to divulge his or her social security number (SSN) unless it is the only method by which retrieval can be made. The individual is not required to explain or justify his or her need for access to any record under this part.<PRTPAGE P="931"/>
        </P>
        <P>(4) Disclose medical records to the individual to whom they pertain, even if a minor, unless a judgment is made that access to such records could have an adverse effect on the mental or physical health of the individual. Normally, this determination will be made in consultation with a medical doctor. If it is determined that the release of the medical information may be harmful to the mental or physical health of the individual, send the record to a physician named by the individual and in the transmittal letter to the physician, explain why access by the individual without proper professional supervision could be harmful (unless it is obvious from the record). Do not require the physician to request the records for the individual. If the individual refuses or fails to designate a physician, the record will not be provided. Such refusal of access is not considered a denial for reporting purposes.</P>
        <P>(5) Requests by individuals for access to investigatory records pertaining to themselves and compiled for law enforcement purposes are processed under this part or 32 CFR part 1285 depending on which part gives them the greatest degree of access.</P>
        <P>(6) Certain documents under the physical control of DoD personnel and used to assist them in performing official functions, are not considered “agency records” within the meaning of this part. Uncirculated personal notes and records that are not disseminated or circulated to any person or organization (for example, personal telephone lists or memory aids) that are retained or discarded at the author's discretion and over which DLA exercises no direct control, are not considered agency records. However, if personnel are officially directed or encouraged, either in writing or orally, to maintain such records, they may become “agency records,” and may be subject to the Privacy Act of 1974 (5 U.S.C. 552a) and this part.</P>
        <P>(7) Acknowledge requests for access within 10 working days after receipt and provide access within 30 working days.</P>
        <P>(b) <E T="03">Denial of individual access.</E> (1) Individuals may be formally denied access to a record pertaining to them only if the record was compiled in reasonable anticipation of civil action; is in a system of records that has been exempted from the access provisions of this part under one of the permitted exemptions; contains classified information that has been exempted from the access provision of this part under the blanket exemption for such material claimed for all DoD records systems; or is contained in a system of records for which access may be denied under some other Federal statute. Only deny the individual access to those portions of the records from which the denial of access serves some legitimate Governmental purpose.</P>
        <P>(2) An individual may be refused access if the record is not described well enough to enable it to be located with a reasonable amount of effort on the part of an employee familiar with the file; or access is sought by an individual who fails or refuses to comply with the established procedural requirements, including refusing to name a physician to receive medical records when required or to pay fees. Always explain to the individual the specific reason access has been refused and how he or she may obtain access.</P>
        <P>(3) Formal denials of access must be in writing and include as a minimum:</P>
        <P>(i) The name, title or position, and signature of the appropriate Head of the HQ DLA principal staff element or primary level field activity.</P>
        <P>(ii) The date of the denial.</P>
        <P>(iii) The specific reason for the denial, including specific citation to the appropriate sections of the Privacy Act of 1974 (5 U.S.C. 552a) or other statutes, this part, or DLAR 5400.21 authorizing the denial.</P>
        <P>(iv) Notice to the individual of his or her right to appeal the denial within 60 calendar days of the date of the denial letter and to file any such appeal with the HQ DLA Privacy Act Officer, Defense Logistics Agency (DSS-CA), 8725 John J. Kingman Road, Suite 2533, Fort Belvoir, VA 22060-6221.</P>
        <P>(4) DLA will process all appeals within 30 days of receipt unless a fair an equitable review cannot be made within that period. The written appeal notification granting or denying access is the final DLA action on access.</P>

        <P>(5) The records in all systems of records maintained in accordance with <PRTPAGE P="932"/>the Office of Personnel Management (OPM) Government-wide system notices are technically only in the temporary custody of DLA. All requests for access to these records must be processed in accordance with the Federal Personnel Manual (5 CFR parts 293, 294, 297 and 735) as well as this part. DLA-GC is responsible for the appellate review of denial of access to such records.</P>
        <P>(c) <E T="03">Amendment of records.</E> (1) Individuals are encouraged to review the personal information being maintained about them by DLA and to avail themselves of the procedures established by this part to update their records. An individual may request the amendment of any record contained in a system of records pertaining to him or her unless the system of record has been exempted specifically from the amendment procedures of this part. Normally, amendments under this part are limited to correcting factual matters and not matters of official judgment, such as performance ratings promotion potential, and job performance appraisals.</P>
        <P>(2) The applicant must adequately support his or her claim and may be required to provide identification to ensure that they are indeed seeking to amend a record pertaining to themselves and not, inadvertently or intentionally, the record of others. Consider the following factors when evaluating the sufficiency of a request to amend:</P>
        <P>(i) The accuracy of the information itself.</P>
        <P>(ii) The relevancy, timeliness, completeness, and necessity of the recorded information for accomplishing an assigned mission or purpose.</P>
        <P>(3) Provide written acknowledgement of a request to amend within 10 working days of its receipt by the appropriate systems manager. There is no need to acknowledge a request if the action is completed within 10 working days and the individual is so informed. The letter of acknowledgement shall clearly identify the request and advise the individual when he or she may expect to be notified of the completed action. Only under the most exceptional circumstances will more than 30 days be required to reach a decision on a request to amend.</P>
        <P>(4) If the decision is made to grant all or part of the request for amendment, amend the record accordingly and notify the requester. Notify all previous recipients of the information, as reflected in the disclosure accounting records, that an amendment has been made and the substance of the amendment. Recipients who are known to be no longer retaining the information need not be advised of the amendment. All DoD Components and Federal agencies known to be retaining the record or information, even if not reflected in disclosure records, will be notified of the amendment. Advise the requester of these notifications, and honor all requests by the requester to notify specific Federal agencies of the amendment action.</P>
        <P>(5) If the request for amendment is denied in whole or in part, promptly advise the individual in writing of the decision to include:</P>
        <P>(i) The specific reason and authority for not amending.</P>
        <P>(ii) Notification that he or she may seek further independent review of the decision by filing an appeal with the HQ DLA Privacy Act Officer, Defense Logistics Agency (DSS-CA), 8725 John J. Kingman Road, Suite 2533, Fort Belvoir, VA 22060-6221, and including all supporting materials.</P>
        <P>(6) DLA will process all appeals within 30 days unless a fair review cannot be made within this time limit.</P>
        <P>(i) If the appeal is granted, DLA will promptly notify the requester and system manager of the decision. The system manager will amend the record(s) as directed and ensure that all prior known recipients of the records who are known to be retaining the record are notified of the decision and the specific nature of the amendment and that the requester is notified as to which DoD Components and Federal agencies have been told of the amendment.</P>
        <P>(ii) If the appeal is denied completely or in part, the individual is notified in writing by the reviewing official that:</P>
        <P>(A) The appeal has been denied and the specific reason and authority for the denial.</P>

        <P>(B) The individual may file a statement of disagreement with the appropriate authority and the procedures for filing this statement.<PRTPAGE P="933"/>
        </P>
        <P>(C) If filed properly, the statement of disagreement shall be included in the records, furnished to all future recipients of the records, and provided to all prior recipients of the disputed records who are known to hold the record.</P>
        <P>(D) The individual may seek a judicial review of the decision not to amend.</P>
        <P>(7) The records in all systems of records controlled by the Office of Personnel Management (OPM) Government-wide system notices are technically only temporarily in the custody of DLA. All requests for amendment of these records must be processed in accordance with the Federal Personnel Manual (FPM). A DLA denial authority may deny a request. However, the appeal process for all such denials must include a review by the Assistant Director for Agency Compliance and Evaluation, Office of Personnel Management, 1900 E Street, NW., Washington, DC 20415. When an appeal is received from a DLA denial of amendment of the OPM controlled record, process the appeal in accordance with the FPM and notify the OPM appeal authority listed above. The individual may appeal any DLA decision not to amend the OPM records directly to OPM. OPM is the final review authority for any appeal from a denial to amend the OPM records.</P>
        <P>(8) If the reviewing authority refuses to amend the record as requested, the individual may submit a concise statement of disagreement setting forth his or her reasons for disagreeing with the decision not to amend.</P>
        <P>(i) If an individual chooses to file a statement of disagreement, annotate the record to indicate that the statement has been filed. Furnish copies of the statement of disagreement to all DoD Components and Federal agencies that have been provided copies of the disputed information and who may be maintaining the information.</P>
        <P>(ii) When possible, incorporate the statement of disagreement into the record. If the statement cannot be made a part of the record, establish procedures to ensure that it is apparent from the records that a statement of disagreement has been filed and maintain the statement so that it can be obtained readily when the disputed information is used or disclosed. Automated record systems that are not programmed to accept statements of disagreement shall be annotated or coded so that they clearly indicate that a statement of disagreement is on file, and clearly identify the statement with the disputed information in the system. Provide a copy of the statement of disagreement whenever the disputed information is disclosed for any purpose.</P>
        <P>(9) A summary of reasons for refusing to amend may be included with any record for which a statement of disagreement is filed. Include in this summary only the reasons furnished to the individual for not amending the record. Do not include comments on the statement of disagreement. Normally, the summary and statement of disagreement are filed together. When disclosing information for which a summary has been filed, a copy of the summary may be included in the release, if desired.</P>
        <P>(d) <E T="03">Documentation.</E> Establish a separate Privacy Case File to retain the documentation received and generated during the amendment or access process. There is no need to establish a Privacy Case File if the individual has not cited the Privacy Act or this part. Privacy Case Files shall not be furnished or disclosed to anyone for use in making any determination about the individual other than determinations made under this part. Only the items listed below may be included in the system of records challenged for amendment or for which access is sought. Do not retain copies of unamended records in the basis record system if the request for amendment is granted.</P>
        <P>(1) The following items relating to an amendment request may be included in the disputed record system:</P>
        <P>(i) Copies of the amended record.</P>
        <P>(ii) Copies of the individual's statement of disagreement.</P>
        <P>(iii) Copies of activity summaries.</P>
        <P>(iv) Supporting documentation submitted by the individual.</P>
        <P>(2) The following items relating to an access request may be included in the basic records system:</P>
        <P>(i) Copies of the request.<PRTPAGE P="934"/>
        </P>
        <P>(ii) Copies of the activity action granting total access. (Note: A separate Privacy Case File need not be created in such cases.)</P>
        <P>(iii) Copies of the activity action denying access.</P>
        <P>(iv) Copies of any appeals filed.</P>
        <P>(v) Copies of the reply to the appeal.</P>
        <P>(e) <E T="03">Fees.</E> An individual may be charged only for the direct cost of copying and reproduction, computed using the appropriate portions of the fee schedule in DLAR 5400.14 (32 CFR part 1285) under the provisions of this part. Normally, fees are waived automatically if the direct costs of a given request is less than $30. This fee waiver provision does not apply when a waiver has been granted to the individual before, and later requests appear to be an extension or duplication of that original request. DLA activities may, however, set aside this automatic fee waiver provision when on the basis of good evidence it determines that the waiver of fees is not in the public interest. Decisions to waive or reduce fees that exceed the automatic waiver threshold will be made on a case-by-case basis. Fees may not be charged when:</P>
        <P>(1) Copying is performed for the convenience of the Government or is the only means to make the record available to the individual.</P>
        <P>(2) The record may be obtained without charge under any other part, directive, or statute.</P>
        <P>(3) Providing documents to members of Congress for copying records furnished even when the records are requested under the Privacy Act on behalf of a constituent.</P>
        <P>(f) <E T="03">Disclosures of personal information.</E> (1) For the purposes of disclosure and disclosure accounting, the Department of Defense is considered a single agency. Records pertaining to an individual may be disclosed without the consent of the individual to any DoD official who has need for the record in the performance of his or her assigned duties. Do not disclose personnel information from a system of records outside the Department of Defense unless the record has been requested by the individual to whom it pertains; the written consent of the individual to whom the record pertains has been obtained for release of the record to the requesting agency, activity, or individual; or the release is for one of the specific nonconsensual purposes set forth in this part or DLAR 5400.14, (32 CFR part 1285).</P>
        <P>(2) Except for releases made in accordance with DLAR 5400.14, (32 CFR part 1285) before disclosing any personal information to any recipient outside DoD other than a Federal agency or the individual to whom it pertains;</P>
        <P>(i) Ensure that the records are accurate, timely, complete, and relevant for agency purposes.</P>
        <P>(ii) Contact the individual, if reasonably available, to verify the accuracy, timeliness, completeness, and relevancy of the information, if this cannot be determined from the record.</P>
        <P>(iii) If the information is not current and the individual is not reasonably available, advise the recipient that the information is believed accurate as of a specific date and any other known factors bearing on its accuracy and relevancy.</P>
        <P>(3) All records must be disclosed if their release is required by the Freedom of Information Act. DLAR 5400.14, (32 CFR part 1285) requires that records be made available to the public unless exempted from disclosure by one of the nine exemptions found in the Freedom of Information Act. The standard for exempting most personal records, such as personnel records, medical records, and similar records, is found in DLAR 5400.14 (32 CFR part 1285). Under the exemption, release of personal information can only be denied when its release would be a ‘clearly unwarranted invasion of personal privacy.'</P>
        <P>(i) All disclosures of personal information regarding Federal civilian employees will be made in accordance with the Federal Personnel Manual. Some examples of personal information regarding DoD civilian employees that normally may be released without a clearly unwarranted invasion of personal privacy include:</P>
        <P>(A) Name.</P>
        <P>(B) Present and past position titles.</P>
        <P>(C) Present and past grades.</P>
        <P>(D) Present and past salaries.</P>
        <P>(E) Present and past duty stations.</P>
        <P>(F) Office and duty telephone numbers.<PRTPAGE P="935"/>
        </P>
        <P>(ii) All release of personal information regarding military members shall be made in accordance with the standards established by DLAR 5400.14, (32 CFR part 1285). While it is not possible to identify categorically information that must be released or withheld from military personnel records in every instance, the following items of personal information regarding military members normally may be disclosed without a clearly unwarranted invasion of their personal privacy:</P>
        <P>(A) Full name.</P>
        <P>(B) Rank.</P>
        <P>(C) Date of rank.</P>
        <P>(D) Gross salary.</P>
        <P>(E) Past duty assignments.</P>
        <P>(F) Present duty assignment.</P>
        <P>(G) Future assignments that are officially established.</P>
        <P>(H) Office or duty telephone numbers.</P>
        <P>(I) Source of commission.</P>
        <P>(J) Promotion sequence number.</P>
        <P>(K) Awards and decorations.</P>
        <P>(L) Attendance at professional military schools.</P>
        <P>(M) Duty status at any given time.</P>
        <P>(iii) All releases of personal information regarding civilian personnel not subject to the FPM shall be made in accordance with the standards established by DLAR 5400.14 (32 CFR part 1285). While it is not possible to identify categorically those items of personal information that must be released regarding civilian employees not subject to the FPM, such as nonappropriated fund employees, normally the following items may be released without a clearly unwarranted invasion of personal privacy:</P>
        <P>(A) Full name.</P>
        <P>(B) Grade or position.</P>
        <P>(C) Date of grade.</P>
        <P>(D) Gross salary.</P>
        <P>(E) Present and past assignments.</P>
        <P>(F) Future assignments, if officially established.</P>
        <P>(G) Office or duty telephone numbers.</P>
        <P>(4) A request for a home address or telephone number may be referred to the last known address of the individual for a direct reply by him or her to the requester. In such cases the requester will be notified of the referral. The release of home addresses and home telephone numbers normally is considered a clearly unwarranted invasion of personal privacy and is prohibited. However, these may be released without prior specific consent of the individual if:</P>
        <P>(i) The individual has indicated previously that he or she has no objection to their release.</P>
        <P>(ii) The source of the information to be released is a public document such as commercial telephone directory or other public listing.</P>
        <P>(iii) The release is required by Federal statute (for example, pursuant to Federally-funded state programs to locate parents who have defaulted on child support payments (42 U.S.C. section 653).)</P>
        <P>(iv) The releasing official releases the information under the provisions of DLAR 5400.14, (32 CFR part 1285).</P>

        <P>(5) Records may be disclosed outside DoD without consent of the individual to whom they pertain for an established routine use. Routine uses may be established, discontinued, or amended without the consent of the individuals involved. However, new or changed routine uses must be published in the <E T="04">Federal Register</E> at least 30 days before actually disclosing any records under their provisions. In addition to the routine uses established by the individual system notices, common blanket routine uses for all DLA-maintained systems of records have been established. These blanket routine uses are published in DLAH 5400.1,<SU>1</SU>
          <FTREF/> DLA Systems of Records Handbook. Unless a system notice specifically excludes a system from a given blanket routine use, all blanket routine uses apply.</P>
        <FTNT>
          <P>
            <SU>1</SU> Copies may be obtained from the Defense Logistics Agency, ATTN: DSS-CV, 8725 John J. Kingman Road, Suite 2533, Fort Belvoir, VA 22060-6221.</P>
        </FTNT>
        <P>(6) Records in DLA systems of records may be disclosed without the consent of the individuals to whom they pertain to the Bureau of the Census for purposes of planning or carrying out a census survey or related activities.</P>

        <P>(7) Records may be disclosed for statistical research and reporting without the consent of the individuals to whom they pertain. Before such disclosures, the recipient must provide advance written assurance that the records will <PRTPAGE P="936"/>be used as statistical research or reporting records; the records will only be transferred in a form that is not individually identifiable; and the records will not be used, in whole or in part, to make any determination about the rights, benefits, or entitlements of specific individuals. A disclosure accounting is not required.</P>
        <P>(8) Records may be disclosed without the consent of the individual to whom they pertain to the National Archives and Records Administration (NARA) if they have historical or other value to warrant continued preservation; or for evaluation by NARA to determine if a record has such historical or other value. Records transferred to a Federal Record Center (FRC) for safekeeping and storage do not fall within this category. These remain under the control of the transferring activity, and the FRC personnel are considered agents of the activity which retain control over the records. No disclosure accounting is required for the transfer of records to FRCs.</P>
        <P>(9) Records may be disclosed without the consent of the individual to whom they pertain to another agency or an instrumentality of any governmental jurisdiction within or under the control of the United States for a civil or criminal law enforcement activity, provided the civil or criminal law enforcement activity is authorized by law; the head of the law enforcement acitivity or a designee has made a written request specifying the particular records desired and the law enforcement purpose (such as criminal investigations, enforcement of civil law, or a similar propose) for which the record is sought; and there is no Federal statute that prohibits the disclosure of the records. Normally, blanket requests for access to any and all records pertaining to an individual are not honored. When a record is released to a law enforcement activity, maintain a disclosure accounting. This disclosure accounting will not be made available to the individual to whom the record pertains if the law enforcement activity requests that the disclosure not be released.</P>
        <P>(10) Records may be disclosed without the consent of the individual to whom they pertain if disclosure is made under compelling circumstances affecting the health or safety of any individual. The affected individual need not be the subject of the record disclosed. When such a disclosure is made, notify the individual who is the subject of the record. Notification sent to the last known address of the individual as reflected in the records is sufficient.</P>
        <P>(11) Records may be disclosed without the consent of the individual to whom they pertain to either House of the Congress or to any committee, joint committee or subcommittee of Congress if the release pertains to a matter within the jurisdiction of the committee. Records may also be disclosed to the General Accounting Office (GAO) in the course of the activities of GAO.</P>
        <P>(12) Records may be disclosed without the consent of the person to whom they pertain under a court order signed by a judge of a court of competent jurisdiction. Releases may also be made under the compulsory legal process of Federal or state bodies having authority to issue such process.</P>
        <P>(i) When a record is disclosed under this provision, make reasonable efforts to notify the individual to whom the record pertains, if the legal process is a matter of public record.</P>
        <P>(ii) If the process is not a matter of public record at the time it is issued, seek to be advised when the process is made public and make reasonable efforts to notify the individual at that time.</P>
        <P>(iii) Notification sent to the last known address of the individual as reflected in the records is considered reasonable effort to notify. Make a disclosure accounting each time a record is disclosed under a court order or compulsory legal process.</P>
        <P>(13) Certain personal information may be disclosed to consumer reporting agencies as defined by the Federal Claims Collection Act. Information which may be disclosed to a consumer reporting agency includes:</P>
        <P>(i) Name, address, taxpayer identification number (SSN), and other information necessary to establish the identity of the individual.</P>
        <P>(ii) The amount, status, and history of the claim.<PRTPAGE P="937"/>
        </P>
        <P>(iii) The agency or program under which the claim arose.</P>
        <P>(g) <E T="03">Disclosure accounting.</E> (1) Keep an accurate record of all disclosures made from any system of records except disclosures to DoD personnel for use in the performance of their official duties or under DLAR 5400.14 (32 CFR part 1285). In all other cases a disclosure accounting is required even if the individual has consented to the disclosure of the information pertaining to him or her.</P>
        <P>(2) Use any system of disclosure accounting that will provide the necessary disclosure information. As a minimum, disclosure accounting will contain the date of the disclosure, a description of the information released, the purpose of the disclosure, the name and address of the person or agency to whom the disclosure was made. When numerous similar records are released (such as transmittal of payroll checks to a bank), identify the category of records disclosed and include the data required in some form that can be used to construct an accounting disclosure record for individual records if required. Retain disclosure accounting records for 5 years after the disclosure or the life of the record, whichever is longer.</P>
        <P>(3) Make available to the individual to whom the record pertains all disclosure accountings except when the disclosure has been made to a law enforcement activity and the law enforcement activity has requested that disclosure not be made, or the system of records has been exempted from the requirement to furnish the disclosure accounting. If disclosure accountings are not maintained with the record and the individual requests access to the accounting, prepare a listing of all disclosures and provide this to the individual upon request.</P>
        <P>(h) <E T="03">Collecting personal information.</E> (1) Collect to the greatest extent practicable personal information directly from the individual to whom it pertains if the information may be used in making any determination about the rights, privileges, or benefits of the individual under any Federal program.</P>
        <P>(2) When an individual is requested to furnish personal information about himself or herself for inclusion in a system of records, a Privacy Act Statement is required regardless of the medium used to collect the information (forms, personal interviews, stylized formats, telephonic interviews, or other methods). The statement enables the individual to make an informed decision whether to provide the information requested. If the personal information solicited is not to be incorporated into a system of records, the statement need not be given. The Privacy Act Statement shall be concise, current, and easily understood. It must include:</P>
        <P>(i) The specific Federal statute or Executive Order that authorizes collection of the requested information.</P>
        <P>(ii) The principal purpose or purposes for which the information is to be used.</P>
        <P>(iii) The routine uses that will be made of the information.</P>
        <P>(iv) Whether providing the information is voluntary or mandatory.</P>
        <P>(v) The effects on the individual if he or she chooses not to provide the requested information.</P>
        <P>(3) The Privacy Act Statement may appear as a public notice (sign or poster), conspicuously displayed in the area where the information is collected, such as at check-cashing facilities or identification photograph facilities. The individual normally is not required to sign the Privacy Act Statement. Provide the individual a written copy of the Privacy Act Statement upon request. This must be done regardless of the method chosen to furnish the initial advisement.</P>

        <P>(4) Include in the Privacy Act Statement specifically whether furnishing the requested personal data is mandatory or voluntary. A requirement to furnish personal data is mandatory only when a Federal statute, Executive order, regulation, or other lawful order specifically imposes a duty on the individual to provide the information sought, and the individual is subject to a penalty if he or she fails to provide the requested information. If providing the information is only a condition of a prerequisite to granting a benefit or privilege and the individual has the option of requesting the benefit or privilege, providing the information is always voluntary. However, the loss or <PRTPAGE P="938"/>denial of the privilege, benefit, or entitlement sought may be listed as a consequence of not furnishing the requested information.</P>
        <P>(5) It is unlawful for any Federal, state, or local government agency to deny an individual any right, benefit, or privilege provided by law because the individual refuses to provide his or her social security number (SSN). However, if a Federal statute requires that the SSN be furnished or if the SSN is required to verify the identity of the individual in a system of records that was established and in use before January 1, 1975, and the SSN was required as an identifier by a statute or regulation adopted before that date, this restriction does not apply.</P>
        <P>(i) When an individual is requested to provide his or her SSN, he or she must be told:</P>
        <P>(A) The uses that will be made of the SSN.</P>
        <P>(B) The statute, regulation, or rule authorizing the solicitation of the SSN.</P>
        <P>(C) Whether providing the SSN is voluntary or mandatory.</P>
        <P>(ii) Include in any systems notice for any system of records that contains SSNs a statement indicating the authority for maintaining the SSN and the source of the SSNs in the system. If the SSN is obtained directly from the individual indicate whether this is voluntary or mandatory.</P>
        <P>(iii) Upon entrance into Military Service of civilian employment with DoD, individuals are asked to provide their SSNs. The SSN becomes the service or employment number for the individual and is used to establish personnel, financial, medical, and other official records. After an individual has provided his or her SSN for the purpose of establishing a record, a Privacy Act Statement is not required if the individual is only requested to furnish or verify the SSNs for identification purposes in connection with the normal use of his or her records. However, if the SSN is to be written down and retained for any purpose by the requesting official, the individual must be provided a Privacy Act Statement.</P>
        <P>(6) DLAI 5530.1, Publications, Forms, Printing, Duplicating, Micropublishing, Office Copying, and Automated Information Management Programs,<SU>2</SU>
          <FTREF/> provides guidance on administrative requirements for Privacy Act Statements used with DLA forms. Forms subject to the Privacy Act issued by other Federal agencies have a Privacy Act Statement attached or included. Always ensure that the statement prepared by the originating agency is adequate for the purpose for which the form will be used by the DoD activity. If the Privacy Act Statement provided is inadequate, the activity concerned will prepare a new statement of a supplement to the existing statement before using the form. Forms issued by agencies not subject to the Privacy Act (state, municipal, and other local agencies) do not contain Privacy Act Statements. Before using a form prepared by such agencies to collect personal data subject to this part, an appropriate Privacy Act Statement must be added.</P>
        <FTNT>
          <P>
            <SU>2</SU> Copies may be obtained from the Defense Logistics Agency, ATTN: DSS-CV, 8725 John J. Kingman Road, Suite 2533, Fort Belvoir, VA 22060-6221.</P>
        </FTNT>
        <P>(i) <E T="03">Systems of records.</E> (1) To be subject to this part, a “system of records” must consist of records retrieved by the name of an individual or some other personal identifier and be under the control of a DLA activity. Records in a group of records that <E T="03">may be</E> retrieved by a name or personal identifier are not covered by this part. The records <E T="03">must be,</E> in fact, retrieved by name or other personal identifier to become a system of records for the purpose of this part.</P>
        <P>(2) Retain in a system of records only that personal information which is relevant and necessary to accomplish a purpose required by a Federal statute or an Executive Order. The existence of a statute or Executive order mandating that maintenance of a system of records does not abrogate the responsibility to ensure that the information in the system of records is relevant and necessary.</P>

        <P>(3) Do not maintain any records describing how an individual exercises his or her rights guaranteed by the First Amendment of the U.S. Constitution unless expressly authorized by Federal <PRTPAGE P="939"/>statute or the individual. First Amendment rights include, but are not limited to, freedom of religion, freedom of political beliefs, freedom of speech, freedom of the press, the right to assemble, and the right to petition.</P>
        <P>(4) Maintain all personal information used to make any determination about an individual with such accuracy, relevance, timeliness, and completeness as is reasonably necessary to ensure fairness to the individual in making any such determination. Before disseminating any personal information from a system of records to any person outside DoD, other than a Federal agency, make reasonable efforts to ensure that the information to be disclosed is accurate, relevant, timely, and complete for the purpose it is being maintained.</P>
        <P>(5) Establish appropriate administrative, technical and physical safeguards to ensure that the records in every system of records are protected from unauthorized alteration or disclosure and that their confidentiality is protected. Protect the records against reasonably anticipated threats or hazards. Tailor safeguards specifically to the vulnerabilities of the system and the type of records in the system, the sensitivity of the personal information stored, the storage medium used and, to a degree, the number of records maintained.</P>
        <P>(i) Treat all unclassified records that contain personal information that normally would be withheld from the public as if they were designated “For Official Use Only” and safeguard them in accordance with the standards established by DLAR 5400.14 (32 CFR part 1285) even if they are not marked “For Official Use Only.”</P>
        <P>(ii) Special administrative, physical, and technical procedures are required to protect data that are stored or being processed temporarily in an automated data processing (ADP) system or in a word processing activity to protect it against threats unique to those environments (see DLAR 5200.17, Security Requirements for Automated Information and Telecommunications Systems,<SU>3</SU>
          <FTREF/> and appendix D to this part).</P>
        <FTNT>
          <P>
            <SU>3</SU> Copies may be obtained from the Defense Logistics Agency, ATTN: DSS-CV, 8725 John J. Kingman Road, Suite 2533, Fort Belvoir, VA 22060-6221.</P>
        </FTNT>
        <P>(6) Dispose of records containing personal data so as to prevent inadvertent compromise. Disposal methods such as tearing, burning, melting, chemical decomposition, pulping, pulverizing, shredding, or mutilation are considered adequate if the personal data is rendered unrecognizable or beyond reconstruction.</P>
        <P>(i) The transfer of large quantities of records containing personal data (for example, computer cards and printouts) in bulk to a disposal activity, such as the Defense Property Disposal Office, is not a release of personal information under this part. The sheer volume of such transfers makes it difficult or impossible to identify readily specific individual records.</P>
        <P>(ii) When disposing of or destroying large quantities of records containing personal information, care must be exercised to ensure that the bulk of the records is maintained so as prevent specific records from being readily identified. If bulk is maintained, no special procedures are required.</P>
        <P>(7) When DLA contracts for the operation or maintenance of a system of records or a portion of a system of records by a contractor, the record system or the portion of the record system affected are considered to be maintained by DLA and are subject to this part. The activity concerned is responsible for applying the requirements of this part to the contractor. The contractor and its employees are to be considered employees of DLA for purposes of the sanction provisions of the Privacy Act during the performance of the contract. See the Federal Acquisition Regulation (FAR), section 24.000 (48 CFR chapter 1).</P>
        <P>(j) <E T="03">System Notices.</E> (1) A notice of the existence of each system of records must be published in the <E T="04">Federal Register.</E> While system notices are not subject to formal rulemaking procedures, advance public notice must be given before an activity may begin to collect personal information or use a new system of records. The notice procedures require that:</P>

        <P>(i) The system notice describes the contents of the record system and the <PRTPAGE P="940"/>routine uses for which the information in the system may be released.</P>
        <P>(ii) The public be given 30 days to comment on any proposed routine uses before implementation.</P>
        <P>(iii) The notice contains the date on which the system will become effective.</P>
        <P>(2) Appendix A of this part discusses the specific elements required in a system notice. DLAH 5400.1 <SU>4</SU>
          <FTREF/> contains systems notices published by DLA.</P>
        <FTNT>
          <P>
            <SU>4</SU> Copies may be obtained from the Defense Logistics Agency, ATTN: DSS-CV, 8725 John J. Kingman Road, Suite 2533, Fort Belvoir, VA 22060-6221.</P>
        </FTNT>
        <P>(3) In addition to system notices, reports are required for new and altered systems of records. The criteria of these reports are outlined in appendixes B and C of this part. No report is required for amendments to existing systems which do not meet the criteria for altered record systems.</P>
        <P>(4) System managers shall evaluate the information to be included in each new system before establishing the system and evaluate periodically the information contained in each existing system of records for relevancy and necessity. Such a review will also occur when a system notice amendment or alteration is prepared. Consider the following:</P>
        <P>(i) The relationship of each item of information retained and collected to the purpose for which the system is maintained.</P>
        <P>(ii) The specific impact on the purpose or mission of not collecting each category of information contained in the system.</P>
        <P>(iii) The possibility of meeting the informational requirements through use of information not individually identifiable or through other techniques, such as sampling.</P>
        <P>(iv) The length of time each item of personal information must be retained.</P>
        <P>(v) The cost of maintaining the information.</P>
        <P>(vi) The necessity and relevancy of the information to the purpose for which it was collected.</P>
        <P>(5) Systems notices and reports of new and altered systems will be submitted to DLA Support Services (DSS-CA) as required.</P>
        <P>(k) <E T="03">Exemptions.</E> The Director, DLA will designate the DLA records which are to be exempted from certain provisions of the Privacy Act. DLA Support Services (DSS-CA) will publish in the <E T="04">Federal Register</E> information specifying the name of each designated system, the specific provisions of the Privacy Act from which each system is to be exempted, the reasons for each exemption, and the reason for each exemption of the record system.</P>
        <P>(1) <E T="03">General Exemptions.</E> To qualify for a general exemption, as defined in the Privacy Act, the system of records must be maintained by a system manager who performs as his/her principal function any activity pertaining to the enforcement of criminal laws, including police efforts to prevent, control, or reduce crime or to apprehend criminals, and the activities or prosecutors, courts, correctional, probation, pardon, or parole authorities. Such system of records must consist of:</P>
        <P>(i) Information compiled for the purpose of identifying individual criminal offenders and alleged offenders and containing only identifying data and notations or arrests, the nature and disposition of criminal charges, sentencing, confinement, release, and parole, and probation status.</P>
        <P>(ii) Information compiled for the purpose of a criminal investigation, including reports of informants and investigators, and associated with an identifiable individual.</P>
        <P>(iii) Reports identifiable to an individual compiled at any stage of the process of enforcement of the criminal laws from arrest or indictment through release from supervision.</P>
        <P>(2) <E T="03">Specific exemption.</E> To qualify for a specfic exemption, as defined by the Privacy Act, the systems of records must be:</P>
        <P>(i) Specifically authorized under criteria established by an Executive Order to be kept classified in the interest of national defense or foreign policy and are in fact properly classified pursuant to such Executive Order.</P>

        <P>(ii) Investigatory material compiled for law enforcement purposes other than material covered under a general exemption. However, an individual will not be denied access to information which has been used to deny him/her a <PRTPAGE P="941"/>right or privilege unless disclosure would reveal a source who furnished information to the Government under a promise that the identity of the source would be held in confidence. For investigations made after September 27, 1975, the identity of the source may be treated as confidential only if based on the expressed guarantee that the identity would not be revealed.</P>
        <P>(iii) Maintained in connection with providing protective services to the President of the United States or other individuals protected pursuant to 18 U.S.C. 3056.</P>
        <P>(iv) Used only to generate aggregate statistical data or for other similarly evaluative or analytic purposes, and which are not used to make decisions on the rights, benefits, or entitlements of individuals except for the disclosure of a census record permitted by 13 U.S.C. 8.</P>
        <P>(v) Investigatory material compiled solely for the purpose of determining suitability, eligibility, or qualifications for Federal civilian employment, Military Service, Federal contracts, or access to classified information, but only to the extent that the disclosure of such material would reveal the identity of a source who furnished information to the Government under an express promise that the source would be held in confidence, or prior to September 27 1975, under an implied promise that the identity of the source would be held in confidence.</P>
        <P>(vi) Testing or examination material used solely to determine individual qualifications for appointment or promotion in the Federal service, the disclosure of which would compromise the objectivity or fairness of the testing or elimination process.</P>
        <P>(vii) Evaluation material used to determine potential for promotion in the Military Services, but only the extent that the disclosure of such material would reveal the identity of a source who furnished information to the Government under an express promise that the identity of the source would be held in confidence or prior to September 27, 1975, under an implied promise that the identity of the source would be held in confidence. System managers will specify those categories of individuals for whom pledges of confidentiality may be made when obtaining information on an individual's suitability for promotion.</P>
        <P>(viii) Exemption rules for DLA systems of records are published in appendix H of this part.</P>
        <P>(l) <E T="03">Matching Program Procedures.</E> The OMB has issued special guidelines to be followed in programs that match the personal records in the computerized data bases of two or more Federal agencies by computer (see appendix E). These guidelines are intended to strike a balance between the interest of the Government in maintaining the integrity of Federal programs and the need to protect individual privacy expectations. They do not authorize matching programs as such and each matching program must be justified individually in accordance with the OMB guidelines.</P>
        <P>(1) Forward all requests for matching programs to include necessary routine use amendments and analysis and proposed matching program reports to DLA Support Services. Changes to existing matching programs shall be processed in the same manner as a new matching program report.</P>

        <P>(2) No time limits are set by the OMB guidelines. However, in order to establish a new routine use for a matching program, the amended system notice must have been published in the <E T="04">Federal Register</E> at least 30 days before implementation. Submit the documentation required above to DLA Support Services (DSS-CA) at least 60 days before the proposed initiation date of the matching program. Waivers to the 60 days' deadline may be granted for good cause shown. Requests for waivers will be in writing a fully justified.</P>
        <P>(3) For the purpose of the OMB guidelines, DoD and all DoD Components are considered a single agency. Before initiating a matching program using only the records of two or more DoD activities, notify DLA Support Services (DSS-CA) that the match is to occur. Further information may be requested from the activity proposing the match.</P>

        <P>(4) System managers shall review annually each system of records to determine if records from the system are being used in matching programs and <PRTPAGE P="942"/>whether the OMB Guidelines have been complied with.</P>
        <CITA>[DLAR 5400.21, 51 FR 33595, Sept. 22, 1986, unless otherwise noted. Redesignated at 56 FR 57803, Nov. 14, 1991, as amended at 66 FR 41781, Aug. 9, 2001.</CITA>
      </SECTION>
      <SECTION>
        <SECTNO>§ 323.6</SECTNO>
        <SUBJECT>Forms and reports.</SUBJECT>
        <P>DLA activities may be required to provide data under reporting requirements established by the Defense Privacy Office and DLA Support Services (DSS-CA). Any report established shall be assigned Report Control Symbol DD-DA&amp;M(A)1379.</P>
        <CITA>[66 FR 41782, Aug. 9, 2001]</CITA>
      </SECTION>
      <APPENDIX>
        <EAR>Pt. 323, App. A</EAR>
        <HD SOURCE="HED">Appendix A to Part 323—Instructions for Preparation of System Notices</HD>
        <P>A. <E T="03">System identification.</E> See DLAH 5400.1.<SU>1</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>1</SU> Copies may be obtained from the Defense Logistics Agency, ATTN: DSS-CV, 8725 John J. Kingman Road, Suite 2533, Fort Belvoir, VA 22060-6221.</P>
        </FTNT>
        <P>B. <E T="03">System name.</E> The name of the system reasonably identifies the general purpose of the system and, if possible, the general categories of individuals involved. Use acronyms only parenthetically following the title or any portion thereof, such as, “Joint Uniform Military Pay System (JUMPS).” Do not use acronyms that are not commonly known unless they are preceded by an explanation. The system name may not exceed 55 character positions including punctuation and spacing.</P>
        <P>C. <E T="03">System location</E> 1. For systems maintained in a single location provided the exact office name, organizational identity, and address or routing symbol. For geographically or organizationally decentralized systems, specify each level of organization or element that maintains a segment of the system. For automated data systems with a central computer facility and input/output terminals at several geographically separated location, list each location by category.<FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>2</SU> [Reserved]</P>
        </FTNT>
        <P>2. When multiple locations are identified by type of organization, the system location may indicate that official mailing addresses are contained in an address directory published as an appendix to DLAH 5400.1.</P>
        <P>3. If no address directory is used or the addresses in the directory are incomplete, the address of each location where a segment of the record system is maintained must appear under the “System Location” caption. Classified addresses are not listed, but the fact that they are classified is indicated. Use the standard U.S. Postal Service two letter state abbreviation symbols and zip codes for all domestic addresses.</P>
        <P>D. <E T="03">Categories of individuals covered by the system.</E> Set forth the specific categories of individuals to whom records in the system pertain in clear, easily understood, nontechnical terms. Avoid the use of broad over-general descriptions, such as “all DLA personnel” or “all civilian personnel” unless this actually reflects the category of individuals involved.</P>
        <P>E. <E T="03">Categories of records in the system.</E> Describe in clear, nontechnical terms the types of records maintained in the system. Only documents actually retained in the system of records will be described, not source documents that are used only to collect data and the destroyed.</P>
        <P>F. <E T="03">Authority for maintenance of the system.</E> 1. Cite the specific provisions of the Federal statute or Executive Order that authorizes the maintenance of the system. Include with citations for statutes the popular names, when appropriate (for example, title 51, United States Code, section 2103, “Tea-Tasters Licensing Act”), and for Executive Orders, the official title (for example, Executive Order 9397, “Numbering System for Federal Accounts Relative to Individual Persons”).</P>
        <P>2. For administrative housekeeping records, cite the directive establishing DLA as well as the Secretary of Defense authority to issue the directive. For example, ‘Pursuant to the authority contained in the National Security Act of 1947, as amended (10 U.S.C. 133d), the Secretary of Defense has issued DoD Directive 5105.22 (32 CFR part 398), Defense Logistics Agency (DLA), the charter of the Defense Logistics Agency (DLA) as a separate agency of the Department of Defense under this control. Therein, the Director, DLA, is charged with the responsibility of maintaining all necessary and appropriate records.'</P>
        <P>G. <E T="03">Purpose or purposes.</E> List the specific purposes for maintaining the system of records by the activity. Include the use made of the information within DLA and the Department of Defense (so-called “internal routine uses”).</P>
        <P>H. <E T="03">Routine uses.</E> 1. The blanket routine uses that appear in DLAH 5400.1 <SU>3</SU>

          <FTREF/> apply to all systems notices unless the individual system notice specifically states that one or more of them do not apply to the system. For all other routine uses, when practical, list the specific activity to which the record may be released, to include any routine automated <PRTPAGE P="943"/>system interface (for example, “to the Department of Justice, Civil Rights Compliance Division,” “to the Veterans Administration, Office of Disability Benefits,” or “to state and local health agencies”).</P>
        <FTNT>
          <P>
            <SU>3</SU> Copies may be obtained from the Defense Logistics Agency, ATTN: DSS-CV, 8725 John J. Kingman Road, Suite 2533, Fort Belvoir, VA 22060-6221.</P>
        </FTNT>
        <P>2. For each routine use identified, include a statement as to the purpose or purposes for which the record is to be released to the activity. Do not use general statements, such as, “to other Federal agencies as required” and “to any other appropriate Federal agency.”</P>
        <P>I. <E T="03">Policies and practices for storing, retiring, accessing, retaining, and disposing of records.</E> This caption is subdivided into four parts:</P>
        <P>1. <E T="03">Storage.</E> Indicate the medium in which the records are maintained. (For example, a system may be “automated, maintained on magnetic tapes or disks,” “manual, maintained in paper files,” or “hybrid, maintained in a combination of paper and automated form.”) Storage does not refer to the container or facility in which the records are kept.</P>
        <P>2. <E T="03">Retrievability.</E> Specify how the records are retrieved (for example, name and SSN, name, SSN) and indicate whether a manual or computerized index is required to retrieve individual records.</P>
        <P>3. <E T="03">Safeguards.</E> List the categories of DLA personnel having immediate access and these responsible for safeguards (such as storage in safes, vaults, locked cabinets or rooms, use of guards, visitors registers, personnel screening, or computer “fail-safe” systems software). Do not describe safeguards in such detail as to compromise system security.</P>
        <P>4. Retention and disposal. Indicate how long the record is retained. When appropriate, state the length of time the records are maintained by the activity, when they are transferred to a Federal Records Center, length of retention at the Records Center and when they are transferred to the National Archives or are destroyed. A reference to DLAI 5015.1,<SU>4</SU>
          <FTREF/> DLA Records Management Procedures and Records Schedules, or other issuances without further detailed information is insufficient.</P>
        <FTNT>
          <P>
            <SU>4</SU> Copies may be obtained from the Defense Logistics Agency, ATTN: DSS-CV, 8725 John J. Kingman Road, Suite 2533, Fort Belvoir, VA 22060-6221.</P>
        </FTNT>
        <P>J. <E T="03">System manager or managers and address.</E> 1. List the title and address of the official responsible for the management of the system. If the title of the specific official is unknown, such as for a local system, specify the local commander or office head as the systems manager.</P>
        <P>2. For geographically separated or ogranizationally decentralized activities for which individuals may deal directly with officials at each location in exercising their rights, list the position or duty title of each category of officials responsible for the system or a segment thereof.</P>
        <P>3. Do not include business or duty addresses if they are listed in DLAH 5400.1.</P>
        <P>K. <E T="03">Notification procedures.</E> 1. If the record system has been exempted from subsection (e)(4)(G) the Privacy Act, so indicate.</P>
        <P>2. For all nonexempt systems, describe how an individual may determine if there are records pertaining to him or her in the system. The procedural rules may be cited, but include a brief procedural description of the needed data. Provide sufficient information in the notice to allow an individual to exercise his or her rights without referrals to this part.</P>
        <P>3. As a minimum, the caption will include:</P>
        <P>a. The official title (normally the system manager) and official address to which request is to be directed.</P>
        <P>b. The specific information required to determine if there is a record of the individual in the system.</P>
        <P>c. Identification of the offices through which the individual may obtain access.</P>
        <P>d. A description of any proof of identity required.</P>
        <P>4. When appropriate, the individual may be referred to an activity official who shall provide this data to him or her.</P>
        <P>L. <E T="03">Record access procedures.</E> 1. If the record system has been exempted from subsection (e)(4)(H) of the Privacy Act, so indicate.</P>
        <P>2. For all nonexempt record systems, describe the procedures under which individuals may obtain access to the record pertaining to them in the system. When appropriate, the individual may be referred to the system manager or activity official to obtain access procedures. Do not repeat the addresses listed in DLAH 5400.1, but refer the individual to that directory.</P>
        <P>M. <E T="03">Contesting record procedures.</E> 1. If the record system has been exempted from subsection (e)(4)(H) of the Privacy Act, so indicate.</P>
        <P>2. For all nonexempt systems of records, state briefly how an individual may contest the content of a record pertaining to him or her in the system. The detailed procedures for contesting record accuracy, refusal of access or amendment, or initial review and appeal need not be included if they are readily available elsewhere and can be referred to by the public. (For example, “The Defense Logistics Agency rules for contesting contents and for appealing initial determinations are contained in 32 CFR part.”) (DLAR 5400.21).</P>
        <P>3. The individual may also be referred to the system manager to determine these procedures.</P>
        <P>N. <E T="03">Record source categories.</E> 1. If the record system has been exempted from subsection (e)(4)(I) of the Privacy Act, so indicate.</P>

        <P>2. For all nonexempt systems of records, list the sources of the information in the system. Specific individuals or institutions <PRTPAGE P="944"/>need not be identified by name, particularly if these sources have been granted confidentiality.</P>
        <P>O. <E T="03">System exempted from certain provisions of the Privacy Act.</E> 1. If no exemption has been claimed for the system, indicate “None.”</P>
        <P>2. If there is an exemption claimed, indicate specifically under which subsection of the Privacy Act is is claimed. Cite the regulation and CFR section containing the exemption rule for the system. (For example, “Parts of this record system may be exempt under title 5, United States Code, sections 552a(k)2. and (5), as applicable. See exemption rules contained in 32 CFR part 323.”) (DLAR 5400.21).</P>
        <CITA>[DLAR 5400.21, 51 FR 33595, Sept. 22, 1986. Redesignated and amended at 56 FR 57803, Nov. 14, 1991; 66 FR 41781, Aug. 9, 2001]</CITA>
      </APPENDIX>
      <APPENDIX>
        <EAR>Pt. 323, App. B</EAR>
        <HD SOURCE="HED">Appendix B to Part 323—Criteria for New and Altered Record Systems</HD>
        <P>A. <E T="03">Criteria for a new record system.</E> A new system of records is one for which there has been no system notice published in the <E T="04">Federal Register.</E> If a notice for a system, of records has been canceled or deleted, before reinstating or reusing the system, a new system notice must be published in the <E T="04">Federal Register.</E>
        </P>
        <P>B. <E T="03">Criteria for an altered record system.</E> A system is considered altered whenever one of the following actions occurs or is proposed:</P>
        <P>1. A significant increase or change in the number or type of indiviudals about whom records are maintained.</P>
        <P>a. Only changes that alter significantly the character and purpose of the records system are considered alterations.</P>
        <P>b. Increases in numbers of individuals due to normal growth are not considered alterations unless they truly alter the character and purpose of the system.</P>
        <P>c. Increases that change significantly the scope of population covered (for example, expansion of a system of records covering a single PLFA's enlisted personnel to include all of DLA enlisted personnel would be considered an alteration).</P>
        <P>d. A reduction in the number of individual covered is not an alteration, but only an amendment.</P>
        <P>e. All changes that add new categories of individuals to system coverage require a change to the “Categories of individuals covered by the system” caption of the notice and may require changes to the “Purpose(s)” caption.</P>
        <P>2. An expansion in the types or categories of information maintained.</P>
        <P>a. The addition of any new category of records not described under the “Categories of Records in System” caption is considered an alteration.</P>
        <P>b. Adding a new data element which is clearly within the scope of the categories of records described in the existing notice is an amendment.</P>
        <P>c. All changes under this criterion require a change to the “Categories of Records in System” caption of the notice.</P>
        <P>3. An alteration in the manner in which the records are organized or the manner in which the records are indexed and retrieved.</P>
        <P>a. The change must alter the nature of use or scope of the records involved (for example, combining records systems in a reorganization).</P>
        <P>b. Any change under this critera requires a change in the “Retrievability” caption of the system notice.</P>
        <P>c. If the records are no longer retrieved by name or personal identifier, cancel the system notice.</P>
        <P>4. A change in the purpose for which the information in the system is used.</P>
        <P>a. The new purpose must not be compatible with the existing purposes for which the system is maintained or a use that would not reasonably be expected to be an alteration.</P>
        <P>b. If the use is compatible and reasonably expected, there is no change in purpose and no alteration occurs.</P>
        <P>c. Any change under this criterion requires a change in the “Purpose(s)” caption and may require a change in the “Authority for maintenance of the system” caption.</P>
        <P>5. Changes that alter the computer environment (such as changes to equipment configuration, software, or procedures) so as to create the potential for greater or easier access.</P>
        <P>a. Increasing the number of offices with direct access is an alteration.</P>
        <P>b. Software releases, such as operating systems and system utilities that provide for easier access are considered alterations.</P>
        <P>c. The addition of an on-line capability to a previously batch-oriented system is an alteration.</P>
        <P>d. The addition of peripheral devices such as tape devices, disk devices, card readers, printers, and similar devices to an existing ADP system constitute an amendment if system security is preserved.</P>
        <P>e. Changes to existing equipment configuration with on-line capability need not be considered alterations to the system if:</P>
        <P>(1) The change does not alter the present security posture.</P>
        <P>(2) The addition of terminals does not extend the capacity of the current operating system and existing security is preserved.</P>
        <P>f. The connecting of two or more formerly independent automated systems or networks together creating a potential for greater access is an alteration.</P>

        <P>g. Any change under this caption requires a change to the “Storage” caption element of the systems notice.<PRTPAGE P="945"/>
        </P>
        <P>C. Reports of new and altered systems. Submit a report of a new or altered system to DLA Support Services (DSS-CA) before collecting information and for using a new system or altering an existing system.</P>
        <P>D. <E T="03">Time restrictions on the operation of a new or altered system.</E> 1. All time periods begin from the date OSD signs the transmittal letters on the reports to OMB and Congress. The specific time limits are:</P>
        <P>a. Sixty days must elapse before collection forms or fomal instructions pertaining to the system may be issued.</P>
        <P>b. Sixty days must elapse before the system may become operational.</P>
        <P>c. Sixty days must elapse before any public issuance of a Request for Proposal or Invitation to Bid for a new ADP or telecommunication system.</P>
        <NOTE>
          <HD SOURCE="HED">Note:</HD>
          <P>Requests for delegation of procurement authority may be submitted to the General Services Administration during the 60 days’ waiting period, but these will include language that the Privacy Act reporting criteria have been reviewed and that a system report is required for such procurement.</P>
        </NOTE>
        <P>d. Normally 30 days must elapse before publication in the <E T="04">Federal Register</E> of the notice of a new or altered system and the preamble to the <E T="04">Federal Register</E> notice must reflect the date the transmittal letters to OMB and Congress were signed by OSD.</P>
        <P>2. Do not operate a system of records until the waiting periods have expired.</P>
        <P>E. <E T="03">Outside review of new and altered systems reports.</E> If no objections are received within 30 days of a submission to the President of the Senate, Speaker of the House of Representatives, and the Director, OMB, of a new or altered system report, it is presumed that the new or altered systems have been approved as submitted.</P>
        <P>F. <E T="03">Waiver of time restrictions.</E> 1. The OMB may authorize a Federal agency to begin operation of a system of records before the expiration of time limits described above. When seeking such a waiver, include in the letter of transmittal to DLA Support Services (CA) an explanation why a delay of 60 days in establishing the system of records would not be in the public interest. The transmittal must include:</P>
        <P>a. How the public interest will be affected adversely if the established time limits are followed.</P>
        <P>b. Why earlier notice was not provided.</P>

        <P>2. Under no circumstances will the routine uses for a new or altered system be implemented before 30 days have elapsed after publication of the system notice containing the routine uses in the <E T="04">Federal Register.</E> This period cannot be waived.</P>
        <CITA>[DLAR 5400.21, 51 FR 33595, Sept. 22, 1986. Redesignated and amended at 56 FR 57803, Nov. 14, 1991; 66 FR 41782, Aug. 9, 2001]</CITA>
      </APPENDIX>
      <APPENDIX>
        <EAR>Pt. 323, App. C</EAR>
        <HD SOURCE="HED">Appendix C to Part 323—Instructions for Preparation of Reports to New or Altered Systems</HD>
        <P>The report on a new or altered system will consist of a transmittal letter, a narrative statement, and include supporting documentation.</P>
        <P>A. <E T="03">Transmittal Letter.</E> The transmittal letter shall include any request for waivers. The narrative statement will be attached.</P>
        <P>B. <E T="03">Narrative Statement.</E> The narrative statement is typed in double space on standard bond paper. The statement includes:</P>
        <P>1. <E T="03">System identification and name.</E> This caption sets forth the identification and name of the system.</P>
        <P>2. <E T="03">Responsible official.</E> The name, title, address, and telephone number of the official responsible for the report and to whom inquiries and comments about the report may be directed by Congress, the Office of Management and Budget, or Defense Privacy Office.</P>
        <P>3. <E T="03">Purpose of the system or nature of the change proposed.</E> Describe the purpose of the new system. For an altered system, describe the nature of the change being proposed.</P>
        <P>4. <E T="03">Authority for the system.</E> See enclosure 1 of this part.</P>
        <P>5. <E T="03">Number of individuals.</E> The approximate number of individuals about whom records are to be maintained.</P>
        <P>6. <E T="03">Information on First Amendment activities.</E> Describe any information to be kept on the exercise of the individual's First Amendment rights and the basis for maintaining it.</P>
        <P>7. <E T="03">Measures to ensure information accuracy.</E> If the system is to be used to make determinations about the rights, benefits, or entitlements of individuals, describe the measures being established to ensure the accuracy, currency, relevance, and completeness of the information used for these purposes.</P>
        <P>8. <E T="03">Other measures to ensure system security.</E> Describe the steps taken to minimize the risk of unauthorized access to the system. A more detailed assessment of security risks and specific administrative, technical, and physical safeguards will be available for review upon request.</P>
        <P>9. <E T="03">Relationship to state and local government activities.</E> Describe the relationship of the system to state or local government activities that are the sources, recipients, or users of the information in the system.</P>
        <P>C. <E T="03">Supporting Documentation.</E> Item 10 of the narrative is captioned <E T="03">Supporting Documents.</E> A positive statement for this caption is essential for those enclosures that are not required to be enclosed. For example, “No changes to the existing DLA procedural or exemption rules (32 CFR part 323) are required for this proposed system.” List in numerical sequence only those enclosures that are actually furnished. The following are typical enclosures that may be required:<PRTPAGE P="946"/>
        </P>
        <P>1. For a new system, an advance copy of the system notice which is proposed for publication; for an altered system an advance copy of the notice reflecting the specific changes proposed.</P>
        <P>2. An advance copy of any proposed exemption rule if the new or altered system is to be exempted. If there is no exemption, so state in the narrative.</P>
        <P>3. Any other supporting documentation that may be pertinent or helpful in understanding the need for the system or clarifying its intended use. While not required, such documentation, when available, is helpful in evaluating the new or altered system.</P>
        <CITA>[DLAR 5400.21, 51 FR 33595, Sept. 22, 1986. Redesignated and amended at 56 FR 57803, Nov. 14, 1991]</CITA>
      </APPENDIX>
      <APPENDIX>
        <EAR>Pt. 323, App. D</EAR>
        <HD SOURCE="HED">Appendix D to Part 323—Word Processing Center (WPC) Safeguards</HD>
        <P>A. <E T="03">Minimum Standards of Protection.</E> All personal data processed using word processing equipment will be afforded the standards of protection required by this regulation. The special considerations discussed in this enclosure are primarily for Word Processing Centers (WPCs) operating independent of the customer's function. However, managers of word processing systems are encouraged to consider and adopt, when appropriate, the special considerations described. WPCs that are not independent of a customer's function are not required to prepare formal written risk assessments.</P>
        <P>B. <E T="03">WPC Information Flow.</E> In analyzing procedures required to safeguard adequately personal information in a WPC, the basic elements of WPC information flow and control must be considered. These are: Information receipt, information processing, information return, information storage and filing. WPCs do not control information acquisition or its ultimate use by the customers and, therefore, these are not addressed.</P>
        <P>C. <E T="03">Safeguarding Information During Receipt.</E> 1. The word processing manager will establish procedures:</P>
        <P>a. That require each customer who requests that information subject to this DLAR be processed to identify specifically that information to the WPC personnel. This may be done by:</P>
        <P>(1) Providing a check-off type entry on the WPC work requests.</P>
        <P>(2) Requiring that the WPC work requests be stamped with a special legend, or that a special notation be made on the work requests.</P>
        <P>(3) Predesignating specifically a class of documents as coming within the provisions of this DLAR (such as, all officer effectiveness reports, all recall rosters, and all medical protocols).</P>
        <P>(4) Using a special cover sheet both to alert the WPC personnel as to the type information, and to protect the document during transmittal.</P>
        <P>(5) Requiring an oral warning on all dictation.</P>
        <P>(6) Any other procedures that ensure the WPC personnel are alerted to the fact that personal data subject to this DLAR is to be processed.</P>
        <P>b. To ensure that the operators or other WPC personnel who receive data for processing not identified as being under the provisions of this DLAR, but that appear to be personal, promptly call the information to the attention of the WPC supervisor or the customer.</P>
        <P>c. To ensure that any request for the processing of personal data which the customer has not identified as being in a system of record, and that appears to meet the criteria set forth in this regulation, is called to the attention of the appropriate supervisory personnel and system manager.</P>
        <P>2. The WPC supervisor will ensure that personal information is not inadvertently compromised within the WPC.</P>
        <P>D. <E T="03">Safeguarding Information During Processing.</E> 1. Each WPC supervisor will establish internal safeguards that will protect personal data from compromise while it is being processed.</P>
        <P>2. Physical safeguards may include:</P>
        <P>a. Controls on individual access to the center.</P>
        <P>b. Machine configurations that reduce external access to the information being processed, or arrangements that alert the operator to the presence of others.</P>
        <P>c. Using certain specific machines to process personnal data.</P>
        <P>d. Any other physical safeguards, to include special technical arrangements that will protect the data during processing.</P>
        <P>3. Other safeguards may include:</P>
        <P>a. Using only certain selected operators to process personal data.</P>
        <P>b. Processing personal data only at certain times during the day without the WPC manager's specific authorization.</P>
        <P>c. Using only certain tapes or diskettes to process and store personal data.</P>
        <P>d. Using continuous tapes for dictation of personal data.</P>
        <P>e. Requiring all WPC copies of documents to be marked specifically so as to prevent inadvertent compromise.</P>
        <P>f. Returing extra copies and mistakes to the customer with the product.</P>
        <P>g. Disposing of waste containing personal data in a special manner.</P>
        <P>h. Any other local procedures that provide adequate protection to the data being processed.</P>
        <P>E. <E T="03">Safeguarding Information During Return.</E> The WPC shall protect the data until it is returned to the customer or is placed into a <PRTPAGE P="947"/>formal distribution channel. In conjunction with the appropriate administrative support personnel and the WPC customers, the WPC manager will establish procedures that protect the information from the time word processing is completed until it is returned to the customer. Safeguarding procedures may include:</P>
        <P>1. Releasing products only to specifically identified individuals.</P>
        <P>2. Using sealed envelopes to transmit products to the customer.</P>
        <P>3. Using special cover sheets to protect products similar to the one discussed in above.</P>
        <P>4. Hand-carrying products to the customers.</P>
        <P>5. Using special messengers to return the products.</P>
        <P>6. Any other procedures that adequately protect products from compromise while they are awaiting return or being returned to the customer.</P>
        <P>F. <E T="03">Safeguards During Storage.</E> The WPC manager shall ensure that all personal data retained in the center for any purpose (including samples) are protected properly. Safeguarding procedures may include:</P>
        <P>1. Marking will hard copies retained with special legends or designators.</P>
        <P>2. Storing media containing personal data in separate files or areas.</P>
        <P>3. Marking the storage containers for media containing personal data with special legends or notations.</P>
        <P>4. Restricting the reuse of media used to process personal data or erasing the media before reuse.</P>
        <P>5. Establishing special criteria for the WPC retention of media used to store and process personal data.</P>
        <P>6. Returning the media to the customer for retention with the file copies of the finished products.</P>
        <P>7. Discouraging, when practical, the long-term storage of personnal data in any form within the WPC.</P>
        <P>8. Any other filing or storage procedures that safeguard adequately any personal information retained or filed within the WPC.</P>
        <P>G. <E T="03">Risk Assessment for WPCs.</E> 1. Each WPC manager will ensure that a formal, written risk assessment is prepared for each WPC that processes personal information subject to this regulation. The assessment will address the areas discussed in this enclosure, as well as any special risks that the WPC location, configuration, or organization may present to the compromise or alteration of personal data being processed or stored.</P>
        <P>2. A risk assessment will be conducted at least every 5 years or whenever there is a change of equipment, equipment configuration, WPC location, WPC configuration or modification of the WPC facilities that either increases or decreases the likelihood or compromise of personal data.</P>
        <P>3. Copies of the risk assessment will be retained by the WPC manager and made available to appropriate inspectors, as well as to personnel studying equipment for facility upgrading of personal data.</P>
        <P>H. <E T="03">Special Considerations in WPC Design and Modification.</E> Procedures will be established to ensure that all personnel involved in the design of WPCs or the acquisition of word processing equipment are aware of the special considerations required when processing personal data subject to this DLAR.</P>
      </APPENDIX>
      <APPENDIX>
        <EAR>Pt. 323, App. E</EAR>
        <HD SOURCE="HED">Appendix E to Part 323—OMB Guidelines for Matching Programs</HD>
        <P>A. <E T="03">Purpose.</E> These guidelines supplement and will be used in conjunction with OMB Guidelines on the Administration of the Privacy Act of 1974, issued on July 1, 1975, and supplemented on November 21, 1975. They replace earlier guidance on conducting computerized matching programs issued on March 30, 1979. They are intended to help agencies relate the procedural requirements of the Privacy Act to the operational requirements of computerized matching. They are designed to address the concern expressed by the Congress in the Privacy Act of 1974 that “the increasing use of computers and sophisticated information technology, while essential to the efficient operation of the Government, has greatly magnified the harm to individual privacy that can occur from any collection, maintenance, use, or dissemination of personal information.” These guidelines do not authorize activities that are not permitted by law, nor do they prohibit activities expressly required to be performed by law. Complying with these guidelines, however, does not relieve a Federal agency of the obligation to comply with the provisions of the Privacy Act, including any provisions not cited in these guidelines.</P>
        <P>B. <E T="03">Scope.</E> These guidelines apply to all agencies subject to the Privacy Act of 1974 (5 U.S.C. 552a) and to all matching programs:</P>
        <P>1. Performed by a Federal agency, whether the personal records used in the match are Federal or nonfederal.</P>
        <P>2. For which a Federal agency discloses any personal records for use in a matching program performed by any other Federal agency or any nonfederal organization.</P>
        <P>C. <E T="03">Effective Date.</E> These guidelines were effective on May 11, 1982.</P>
        <P>D. <E T="03">Definitions.</E> For the purpose of the Guidelines, all the terms defined in the Privacy Act of 1974 apply.</P>
        <P>1. <E T="03">Personal Record.</E> Any information pertaining to an individual that is stored in an automated system of records; for example, a data base which contains information about individuals that is retrieved by name or some other personal identifier.</P>
        <P>2. <E T="03">Matching Program.</E> A procedure in which a computer is used to compare two or more <PRTPAGE P="948"/>automated systems of records or a system of records with a set of nonfederal records to find individuals who are common to more than one system or set. The procedure includes all of the steps associated with the match, including obtaining the records to be matched, actual use of the computer, administrative and investigative action on the hits, and disposition of the personal records maintained in connection with the match. It should be noted that a single matching program may involve several matches among a number of participants. Watching programs do not include the following:</P>
        <P>a. Matches which compare a substantial number of records, such as, comparison of the Department of Education's defaulted student loan data base with the Office of Personnel Management's Federal employee data base would be covered; comparison of six individual student loan defaultees with the OPM file would not be covered.</P>
        <P>b. Checks on specific individuals to verify data in an application for benefits done reasonably soon after the application is received.</P>
        <P>c. Checks on specific individuals based on information which raises questions about an individual's eligibility for benefits or payments done reasonably soon after the information is received.</P>
        <P>d. Matches done to produce aggregate statistical data without any personal identifiers.</P>
        <P>e. Matches done to support any research or statistical project when the specfic data are not to be used to make decisions about the rights, benefits, or privileges of specific individuals.</P>
        <P>f. Matches done by an agency using its own records.</P>
        <P>3. <E T="03">Matching Agency.</E> The Federal agency which actually performs the match.</P>
        <P>4. <E T="03">Source Agency.</E> The Federal agency which discloses records from a system of records to be used in the match. Note that in some circumstances a source agency may be the instigator and ultimate beneficiary of the matching program, as when an agency lacking computer resources uses another agency to perform the match. The disclosure of records to the matching agency and any later disclosure of “hits” (by either the matching or the source agencies) must be done in accordance with the provisions of paragraph (b) of the Privacy Act.</P>
        <P>5. <E T="03">Hit.</E> The identification, through a matching program, of a specific individual.</P>
        <P>E. <E T="03">Guidelines for Agencies Participating in Matching Programs.</E> Agencies should acquire and disclose matching records and conduct matching programs in accordance with the provisions of this section and the Privacy Act.</P>
        <P>1. <E T="03">Disclosing Personal Records for Matching Programs—</E>
        </P>
        <P>a. <E T="03">To another Federal agency.</E> Source agencies are responsible for determining whether or not to disclose personal records from their systems and for making sure they meet the necessary Privacy Act disclosure provisions when they do. Among the factors source agencies should consider are:</P>
        <P>(1) Legal authority for the match.</P>
        <P>(2) Purpose and description of the match.</P>
        <P>(3) Description of the records to be matched.</P>
        <P>(4) Whether the record subjects have consented to the match; or whether disclosure of records for the match would be compatible with the purpose for which the records were originally collected; that is, whether disclosure under a “routine use” would be appropriate; whether the soliciting agency is seeking the records for a legitimate law enforcement activity—whichever is appropriate; or any other provision of the Privacy Act under which disclosure may be made.</P>
        <P>(5) Description of additional information which may be subsequently disclosed in relation to “hits.”</P>
        <P>(6) Subsequent actions expected of the source (for example, verification of the identity of the “hits” or followup with individuals who are “hits”).</P>
        <P>(7) Safeguards to be afforded the records involved, including disposition.</P>

        <P>b. If the agency is satisfied that disclosure of the records would not violate its responsibilities under the Privacy Act, it may proceed to make the disclosure to the matching agency. It should ensure that only the minimum information necessary to conduct the match is provided. If disclosure is to be made pursuant to a “routine use” (Section b.3. of the Privacy Act), it should ensure that the system of records contains such a use, or it should publish a routine use notice in the <E T="04">Federal Register</E>. The agency should also be sure to maintain an accounting of the disclosure pursuant to Section (c) of the Privacy Act.</P>
        <P>c. <E T="03">To a nonfederal entity.</E> Before disclosing records to a nonfederal entity for a matching program to be carried out by that entity, a source agency should, in addition to all of the consideration in subparagraph a, above, also make reasonable efforts, pursuant to Section (e)(6) of the Privacy Act, to “assure that such records are accurate, complete, timely, and relevant for agency purposes.”</P>
        <P>2. <E T="03">Written Agreements.</E> Before disclosing to either a Federal or non-Federal entity, the source agency should require the matching entity to agree in writing to certain conditions governing the use of the matching file; for example, that the matching file will remain the property of the source agency and be returned at the end of the matching program (or destroyed as appropriate); that the file will be used and accessed only to match the file or files previously agreed to; that it <PRTPAGE P="949"/>will not be used to extract information concerning “non-hit” individuals for any purpose, and that it will not be duplicated or disseminated within or outside the matching agency unless authorized in writing by the source agency.</P>
        <P>3. <E T="03">Performing Matching Programs—</E>
        </P>
        <P>a. Matching agencies should maintain reasonable administrative, technical, and physical security safeguards on all files involved in the matching program.</P>

        <P>b. Matching agencies should ensure that they have appropriate systems of records including those containing “hits,” and that such systems and any routine uses have been appropriately notices in the <E T="04">Federal Register</E> and reported to OMB and the Congress.</P>
        <P>4. <E T="03">Disposition of Records—</E>
        </P>
        <P>a. Matching agencies will return or destroy source matching files (by mutual agreement) immediately after the match.</P>
        <P>b. Records relating to this will be kept only so long as an investigation, either criminal or administrative, is active, and will be disposed of in accordance with the requirements of the Privacy Act and the Federal Records Act.</P>
        <P>5. <E T="03">Publication Requirements—</E>
        </P>

        <P>a. Agencies, before disclosing records outside the agency, will publish appropriate “routine use” notices in the <E T="04">Federal Register,</E> if necessary.</P>

        <P>b. If the matching program will result in the creation of a new or the substantial alteration of an existing system of records, the agency involved should publish the appropriate <E T="04">Federal Register</E> notice and submit the requisite report to OMB and the Congress pursuant to OMB Circular No. A-108.</P>
        <P>6. <E T="03">Reporting Requirements—</E>
        </P>

        <P>a. As close to the initiation of the matching program as possible, matching agencies will publish in the <E T="04">Federal Register</E> a brief public notice describing the matching program. The notice should include:</P>
        <P>1. The legal authority under which the match is being conducted.</P>
        <P>2. A description of the matching program including whether the program is one time or continuing, the organizations involved, the purpose or purposes for which the program is being conducted, and the procedures to be used in matching and following up on the “hits.”</P>

        <P>3. A complete description of the personal records to be matched, including the source or sources, system of records identifying data, date or dates and page number of the most recent <E T="04">Federal Register</E> full text publication when appropriate.</P>
        <P>4. The projected start and ending dates of the program.</P>
        <P>5. The security safeguards to be used to protect against unauthorized access or disclosure of the personal records.</P>
        <P>6. Plans for disposition of the source records and “hits.”</P>

        <P>7. Agencies should send a copy of this notice to the Congress and to OMB at the same time it is sent to the <E T="04">Federal Register</E>.</P>
        <P>a. Agencies should report new or altered systems of records as described in subparagraph 5b, above, as necessary.</P>
        <P>b. Agencies should also be prepared to report on matching programs pursuant to the reporting requirements of either the Privacy Act or the Paperwork Reduction Act. Reports will be solicited by the Office of Information and Regulatory Affairs and will focus on both the protection of individual privacy and Government's effective use of information technology. Reporting instructions will be disseminated to the agencies as part of either the reports required by paragraph (p) of the Privacy Act, or section 3514 of Pub. L. 96-511.</P>
        <P>8. <E T="03">Use of Contractors.</E> Matching programs should, as far as practicable, be conducted “in-house” by Federal agencies using agency personnel, rather than by contract. When contractors are used:</P>
        <P>a. The matching agency should, consistent with paragraph (m) of the Privacy Act, cause the requirements of that Privacy Act to be applied to the contractor's performance of the matching program. The contract should include the Privacy Act clause required by Federal Personnel Regulation Amendment 155 (41 CFR 1-1.337-5).</P>
        <P>b. The terms of the contract should include appropriate privacy and security provisions consistent with policies, regulations, standards, and guidelines issued by OMB, GSA, and the Department of Commerce.</P>
        <P>c. The terms of the contract should preclude the contractor from using, disclosing, copying, or retaining records associated with the matching program for the contractor's own use.</P>
        <P>d. Contractor personnel involved in the matching program shall be made explicitly aware of their obligations under the Privacy Act and of these guidelines, agency rules, and any special safegurds in relation to each specific match performed.</P>
        <P>e. Any disclosures of records by the agency to the contractor should be made pursuant to a “routine use” (5 U.S.C. 552a(b)(3)).</P>
        <P>F. <E T="03">Implementation and Oversight.</E> OMB will oversee the implementation of these guidelines and will interpret and advise upon agency proposals and actions within their scope, consistent with section 6 of the Privacy Act.</P>
      </APPENDIX>
      <APPENDIX>
        <EAR>Pt. 323, App. F</EAR>
        <HD SOURCE="HED">Appendix F to Part 323—Litigation Status Sheet</HD>
        <P>1. Case Number.<SU>1</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>1</SU> Number used by the Component for reference purposes.</P>
        </FTNT>
        <P>2. Requester.<PRTPAGE P="950"/>
        </P>
        <P>3. Document Title or Description.<SU>2</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>2</SU> Indicate the nature of the case, such as “Denial of access,” “Refusal to amend,” “Incorrect records,” or other violations of the Act (specify).</P>
        </FTNT>
        <P>4. Litigation.</P>
        <P>a. Date Complaint Filed.</P>
        <P>b. Court.</P>
        <P>c. Case File Number.<SU>1</SU>
        </P>
        <P>5. Defendants (DoD Component and individual).</P>
        <P>6. Remarks (brief explanation of what the case is about).</P>
        <P>7. Court Action.</P>
        <P>a. Court's Finding.</P>
        <P>b. Disciplinary Action (as appropriate).</P>
        <P>8. Appeal (as appropriate).</P>
        <P>a. Date Complaint File.</P>
        <P>b. Court.</P>
        <P>c. Case File Number.<SU>1</SU>
        </P>
        <P>d. Court's Finding.</P>
        <P>e. Disciplinary Action (as appropriate).</P>
      </APPENDIX>
      <APPENDIX>
        <EAR>Pt. 323, App. G</EAR>
        <HD SOURCE="HED">Appendix G to Part 323—Privacy Act Enforcement Actions</HD>
        <P>A. <E T="03">Administrative Remedies.</E> Any individual who feels he or she has a legitimate complaint or grievance against the Defense Logistics Agency or any DLA employee concerning any right granted by this DLAR will be permitted to seek relief through appropriate administrative channels.</P>
        <P>B. <E T="03">Civil Actions.</E> An individual may file a civil suit against DLA or its employees if the individual feels certain provisions of the Privacy Act have been violated (see 5 U.S.C. 552a(g), reference (b).)</P>
        <P>C. <E T="03">Civil Remedies.</E> In addition to specific remedial actions, the Privacy Act provides for the payment of damages, court cost, and attorney fees in some cases.</P>
        <P>D. <E T="03">Criminal Penalties—</E>
        </P>

        <P>1. The Privacy Act also provides for criminal penalties (see 5 U.S.C. 552a(1).) Any official or employee may be found guilty of a misdemeanor and fined not more than $5,000 if he or she willfully discloses personal information to anyone not entitled to receive the information, or maintains a system of records without publishing the required public notice in the <E T="04">Federal Register</E>.</P>
        <P>2. A person who requests or obtains access to any record concerning another individual under false pretenses may be found guilty of a misdemeanor and fined up to $5,000.</P>
      </APPENDIX>
      <APPENDIX>
        <EAR>Pt. 323, App. H</EAR>
        <HD SOURCE="HED">Appendix H to Part 323—DLA Exemption Rules</HD>
        <P>
          <E T="03">Exempted Records Systems.</E> All systems of records maintained by the Defense Logistics Agency will be exempt from the requirements of 5 U.S.C. 552a(d) pursuant to 5 U.S.C. 552a(k)(1) to the extent that the system contains any information properly classified under Executive Order 12958 and which is required by the Executive Order to be kept secret in the interest of national defense or foreign policy. This exemption, which may be applicable to parts of all systems of records, is necessary because certain record systems not otherwise specifically designated for exemptions herein may contain isolated items of information which have been properly classified.</P>
        <HD SOURCE="HD2">a. ID: S500.10 DLA-I (Specific exemption).</HD>
        <P>1. <E T="03">System name:</E> Personnel Security Files.</P>
        <P>2. <E T="03">Exemption:</E> This system of records is exempted from the following provisions of title 5, United States Code, section 552a: (c)(3); (d); and (e)(1).</P>
        <P>3. <E T="03">Authority:</E> 5 U.S.C. 552a(k)(2).</P>
        <P>4. <E T="03">Reasons:</E> The investigatory reports are used by appropriate Security Officers and Commanders or other designated officials as a basis for determining a persons's eligibility for access to information classified in the interests of national defense.</P>
        <HD SOURCE="HD2">b. ID: S500.20 DLA-I (Specific exemption).</HD>
        <P>1. <E T="03">System name:</E> Criminal Incident/Investigations File.</P>
        <P>2. <E T="03">Exemption:</E> This system of records is exempted from the following provisions of the Title 5, United States Code, section 552a: (c)(3); (d); and (e)(1).</P>
        <P>3. <E T="03">Authority:</E> 5 U.S.C. 552a(k)(2).</P>
        <P>4. <E T="03">Reasons:</E> Granting individuals access to information collected and maintained by this component relating to the enforcement of criminal laws could interfere with orderly investigations, with the orderly administration of justice, and possibly enable suspects to avoid detection or apprehension. Disclosure of this information could result in the concealment, destruction or fabrication of evidence and jeopardize the safety and well being of informants, witnesses and their families, and law enforcement personnel and their families. Disclosure of this information could also reveal and render ineffectual investigative techniques, sources and methods used by this component and could result in the invasion of privacy of individuals only incidentally related to an investigation. Investigatory material is exempt to the extent that the disclosure of such material would reveal the identity of a source who furnished the information to the Government under an express promise that the identity of the source would be held in confidence, or prior to September 27, 1975 under an implied promise that the identity of the source would be held in confidence. This exemption will protect the identities of certain sources who would be otherwise unwilling to provide information to the Government. The exemption of the individual's right of access to his records and the reasons therefore necessitate the exemptions of this system of records <PRTPAGE P="951"/>from the requirements of the other cited provisions.</P>
        <HD SOURCE="HD2">c. ID: S100.50 DLA-GC (Specific exemption).</HD>
        <P>1. <E T="03">System name:</E> Fraud and Irregularities.</P>
        <P>2. <E T="03">Exemption:</E> This system of records is exempt from the provisions of 5 U.S.C. 552a(c)(3), (d)(1) through (4), (e)(1), (e)(4)(G), (H), and (I), and (f).</P>
        <P>3. <E T="03">Authorities:</E> 5 U.S.C. 552a(k)(2) and (k)(5).</P>
        <P>4. <E T="03">Reasons:</E> From subsection (c)(3) because granting access to the accounting for each disclosure as required by the Privacy Act, including the date, nature, and purpose of each disclosure and the identity of the recipient, could alert the subject to the existence of the investigation or prosecutive interest by DLA or other agencies. This could seriously compromise case preparation by prematurely revealing its existence and nature; compromise or interfere with witnesses or make witnesses reluctant to cooperate; and lead to suppression, alteration, or destruction of evidence.</P>
        <P>From subsections (d)(1) through (d)(4) and (f) because providing access to records of a civil investigation and the right to contest the contents of those records and force changes to be made to the information contained therein would seriously interfere with and thwart the orderly and unbiased conduct of the investigation and impede case preparation. Providing access rights normally afforded under the Privacy Act would provide the subject with valuable information that would allow interference with or compromise of witnesses or render witnesses reluctant to cooperate; lead to suppression, alteration, or destruction of evidence; and result in the secreting of or other disposition of assets that would make them difficult or impossible to reach in order to satisfy any Government claim growing out of the investigation or proceeding.</P>
        <P>From subsection (e)(1) because it is not always possible to detect the relevance or necessity of each piece of information in the early stages of an investigation. In some cases, it is only after the information is evaluated in light of other evidence that its relevance and necessity will be clear.</P>
        <P>From subsections (e)(4)(G) and (H) because there is no necessity for such publication since the system of records will be exempt from the underlying duties to provide notification about and access to information in the system and to make amendments to and corrections of the information in the system.</P>
        <P>From subsection (e)(4)(I) because to the extent that this provision is construed to require more detailed disclosure than the broad, generic information currently published in the system notice, an exemption from this provision is necessary to protect the confidentiality of sources of information and to protect privacy and physical safety of witnesses and informants. DLA will, nevertheless, continue to publish such a notice in broad generic terms as is its current practice.</P>
        <HD SOURCE="HD2">d. ID: S100.10 GC (Specific exemption).</HD>
        <P>1. <E T="03">System name:</E> Whistleblower Complaint and Investigation Files.</P>
        <P>2. <E T="03">Exemption:</E> Portions of this system of records may be exempt under the provisions of 5 U.S.C. 552a(c)(3), (d)(1) through (d)(4), (e)(1), (e)(4)(G), (e)(4)(H), and (e)(4)(I), and (f).</P>
        <P>3. <E T="03">Authority:</E> 5 U.S.C. 552a(k)(2).</P>
        <P>4. <E T="03">Reasons:</E> From subsection (c)(3) because granting access to the accounting for each disclosure as required by the Privacy Act, including the date, nature, and purpose of each disclosure and the identity of the recipient, could alert the subject to the existence of the investigation or prosecutive interest by DLA or other agencies. This could seriously compromise case preparation by prematurely revealing its existence and nature; compromise or interfere with witnesses or make witnesses reluctant to cooperate; and lead to suppression, alteration, or destruction of evidence.</P>
        <P>From subsections (d)(1) through (d)(4), and (f) because providing access to records of a civil investigation and the right to contest the contents of those records and force changes to be made to the information contained therein would seriously interfere with and thwart the orderly and unbiased conduct of the investigation and impede case preparation. Providing access rights normally afforded under the Privacy Act would provide the subject with valuable information that would allow interference with or compromise of witnesses or render witnesses reluctant to cooperate; lead to suppression, alteration, or destruction of evidence; and result in the secreting of or other disposition of assets that would make them difficult or impossible to reach in order to satisfy any Government claim growing out of the investigation or proceeding.</P>
        <P>From subsection (e)(1), because it is not always possible to detect the relevance or necessity of each piece of information in the early stages of an investigation. In some cases, it is only after the information is evaluated in light of other evidence that its relevance and necessity will be clear.</P>
        <P>From subsections (e)(4)(G) and (e)(4)(H) because there is no necessity for such publication since the system of records will be exempt from the underlying duties to provide notification about and access to information in the system and to make amendments to and corrections of the information in the system. However, DLA will continue to publish such a notice in broad generic terms as is its current practice.</P>

        <P>From subsection (e)(4)(I) because to the extent that this provision is construed to require more detailed disclosure than the <PRTPAGE P="952"/>broad, generic information currently published in the system notice, an exemption from this provision is necessary to protect the confidentiality of sources of information and to protect privacy and physical safety of witnesses and informants. DLA will, nevertheless, continue to publish such a notice in broad generic terms as is its current practice.</P>
        <P>e. <E T="03">ID: S500.60 CA (Specific exemption).</E>
        </P>
        <P>1. <E T="03">System name:</E> DLA Complaint Program Records.</P>
        <P>2. <E T="03">Exemption:</E>  (i) Investigatory material compiled for law enforcement purposes may be exempt pursuant to 5 U.S.C. 552a(k)(2).  However, if an individual is denied any right, privilege, or benefit for which he would otherwise be entitled by Federal law or for which he would otherwise be eligible, as a result of the maintenance of the information, the individual will be provided access to the information except to the extent that disclosure would reveal the identity of a confidential source.</P>
        <P>(ii) Investigatory material compiled solely for the purpose of determining suitability, eligibility, or qualifications for federal civilian employment, military service, federal contracts, or access to classified information may be exempt pursuant to 5 U.S.C. 552a(k)(5), but only to the extent that such material would reveal the identity of a confidential source.</P>
        <P>3. <E T="03">Authority:</E> 5 U.S.C. 552a(k)(2) and (k)(5), subsections (c)(3), (d)(1) through (d)(4), (e)(1), (e)(4)(G), (H), and (I), and (f).</P>
        <P>4. <E T="03">Reasons:</E> (i) From subsection (c)(3) because to grant access to an accounting of disclosures as required by the Privacy Act, including the date, nature, and purpose of each disclosure and the identity of the recipient, could alert the subject to the existence of the investigation or prosecutive interest by DLA or other agencies.  This could seriously compromise case preparation by prematurely revealing its existence and nature; compromise or interfere with witnesses or make witnesses reluctant to cooperate; and lead to suppression, alteration, or destruction of evidence.</P>
        <P>(ii) From subsections (d)(1) through (d)(4), and (f) because providing access to records of a civil or administrative investigation and the right to contest the contents of those records and force changes to be made to the information contained therein would seriously interfere with and thwart the orderly and unbiased conduct of the investigation and impede case preparation.  Providing access rights normally afforded under the Privacy Act would provide the subject with valuable information that would allow interference with or compromise of witnesses or render witnesses reluctant to cooperate; lead to suppression, alteration, or destruction of evidence; enable individuals to conceal their wrongdoing or mislead the course of the investigation; and result in the secreting of or other disposition of assets that would make them difficult or impossible to reach in order to satisfy any Government claim growing out of the investigation or proceeding.</P>
        <P>(iii) From subsection (e)(1) because it is not always possible to detect the relevance or necessity of each piece of information in the early stages of an investigation. In some cases, it is only after the information is evaluated in light of other evidence that its relevance and necessity will be clear.</P>
        <P>(iv) From subsections (e)(4)(G) and (H) because this system of records is compiled for law enforcement purposes and is exempt from the access provisions of subsections (d) and (f).</P>
        <P>(v) From subsection (e)(4)(I) because to the extent that this provision is construed to require more detailed disclosure than the broad, generic information currently published in the system notice, an exemption from this provision is necessary to protect the confidentiality of sources of information and to protect privacy and physical safety of witnesses and informants.  DLA will, nevertheless, continue to publish such a notice in broad generic terms as is its current practice.</P>
        <P>f. <E T="03">ID: S500.30 CAAS (Specific exemption).</E>
        </P>
        <P>1. <E T="03">System name:</E> Incident Investigation/Police Inquiry Files.</P>
        <P>2. <E T="03">Exemption:</E> (i) Investigatory material compiled for law enforcement purposes may be exempt pursuant to 5 U.S.C. 552a(k)(2). However, if an individual is denied any right, privilege, or benefit for which he would otherwise be entitled by Federal law or for which he would otherwise be eligible, as a result of the maintenance of the information, the individual will be provided access to the information except to the extent that disclosure would reveal the identity of a confidential source.</P>
        <P>(ii) Investigatory material compiled solely for the purpose of determining suitability, eligibility, or qualifications for federal civilian employment, military service, federal contracts, or access to classified information may be exempt pursuant to 5 U.S.C. 552a(k)(5), but only to the extent that such material would reveal the identity of a confidential source.</P>
        <P>3. <E T="03">Authority:</E> 5 U.S.C. 552a(k)(2) and (k)(5), subsections (c)(3), (d)(1) through (d)(4), (e)(1), (e)(4)(G), (H), and (I), and (f).</P>
        <P>4. <E T="03">Reasons:</E> (i) From subsection (c)(3) because to grant access to the accounting for each disclosure as required by the Privacy Act, including the date, nature, and purpose of each disclosure and the identity of the recipient, could alert the subject to the existence of the investigation or prosecutive interest by DLA or other agencies. This could seriously compromise case preparation by prematurely revealing its existence and nature; compromise or interfere with witnesses <PRTPAGE P="953"/>or make witnesses reluctant to cooperate; and lead to suppression, alteration, or destruction of evidence.</P>
        <P>(ii) From subsections (d)(1) through (d)(4), and (f) because providing access to records of a civil or administrative investigation and the right to contest the contents of those records and force changes to be made to the information contained therein would seriously interfere with and thwart the orderly and unbiased conduct of the investigation and impede case preparation. Providing access rights normally afforded under the Privacy Act would provide the subject with valuable information that would allow interference with or compromise of witnesses or render witnesses reluctant to cooperate; lead to suppression, alteration, or destruction of evidence; enable individuals to conceal their wrongdoing or mislead the course of the investigation; and result in the secreting of or other disposition of assets that would make them difficult or impossible to reach in order to satisfy any Government claim growing out of the investigation or proceeding.</P>
        <P>(iii) From subsection (e)(1) because it is not always possible to detect the relevance or necessity of each piece of information in the early stages of an investigation. In some cases, it is only after the information is evaluated in light of other evidence that its relevance and necessity will be clear.</P>
        <P>(iv) From subsections (e)(4)(G) and (H) because this system of records is compiled for law enforcement purposes and is exempt from the access provisions of subsections (d) and (f).</P>
        <P>(v) From subsection (e)(4)(I) because to the extent that this provision is construed to require more detailed disclosure than the broad, generic information currently published in the system notice, an exemption from this provision is necessary to protect the confidentiality of sources of information and to protect privacy and physical safety of witnesses and informants. DLA will, nevertheless, continue to publish such a notice in broad generic terms as is its current practice.</P>
        <CITA>[DLAR 5400.21, 51 FR 33595, Sept. 22, 1986. Redesignated at 56 FR 57803, Nov. 14, 1991, as amended at 55 FR 32913, Aug. 13, 1990; 57 FR 40609, Sept. 4, 1992; 59 FR 9668, Mar. 1, 1994; 60 FR 3088, Jan. 13, 1995; 61 FR 2916, Jan. 30, 1996; 63 FR 25772, May 11, 1998; 65 FR 18900, Apr. 10, 2000]</CITA>
      </APPENDIX>
    </PART>
    <PART>
      <EAR>Pt. 324</EAR>
      <HD SOURCE="HED">PART 324—DFAS PRIVACY ACT PROGRAM</HD>
      <CONTENTS>
        <SUBPART>
          <HD SOURCE="HED">Subpart A—General Information</HD>
          <SECHD>Sec.</SECHD>
          <SECTNO>324.1</SECTNO>
          <SUBJECT> Issuance and purpose.</SUBJECT>
          <SECTNO>324.2</SECTNO>
          <SUBJECT> Applicability and scope.</SUBJECT>
          <SECTNO>324.3</SECTNO>
          <SUBJECT> Policy.</SUBJECT>
          <SECTNO>324.4</SECTNO>
          <SUBJECT> Responsibilities.</SUBJECT>
        </SUBPART>
        <SUBPART>
          <HD SOURCE="HED">Subpart B—Systems of Records</HD>
          <SECTNO>324.5</SECTNO>
          <SUBJECT> General information.</SUBJECT>
          <SECTNO>324.6</SECTNO>
          <SUBJECT> Procedural rules.</SUBJECT>
          <SECTNO>324.7</SECTNO>
          <SUBJECT> Exemption rules.</SUBJECT>
        </SUBPART>
        <SUBPART>
          <HD SOURCE="HED">Subpart C—Individual Access to Records</HD>
          <SECTNO>324.8</SECTNO>
          <SUBJECT> Right of access.</SUBJECT>
          <SECTNO>324.9</SECTNO>
          <SUBJECT> Notification of record's existence.</SUBJECT>
          <SECTNO>324.10</SECTNO>
          <SUBJECT>Individual requests for access.</SUBJECT>
          <SECTNO>324.11</SECTNO>
          <SUBJECT>Denials.</SUBJECT>
          <SECTNO>324.12</SECTNO>
          <SUBJECT>Granting individual access to records.</SUBJECT>
          <SECTNO>324.13</SECTNO>
          <SUBJECT>Access to medical and psychological records.</SUBJECT>
          <SECTNO>324.14</SECTNO>
          <SUBJECT>Relationship between the Privacy Act and the Freedom of Information Act.</SUBJECT>
          <APP>Appendix A to Part 324—DFAS Reporting Requirements</APP>
          <APP>Appendix B to Part 324—System of Records Notice</APP>
        </SUBPART>
      </CONTENTS>
      <AUTH>
        <HD SOURCE="HED">Authority:</HD>
        <P>Pub. L. 93-579, 88 Stat 1896 (5 U.S.C. 552a).</P>
      </AUTH>
      <SOURCE>
        <HD SOURCE="HED">Source:</HD>
        <P>61 FR 25561, May 22, 1996, unless otherwise noted.</P>
      </SOURCE>
      <SUBPART>
        <HD SOURCE="HED">Subpart A—General information</HD>
        <SECTION>
          <SECTNO>§ 324.1</SECTNO>
          <SUBJECT>Issuance and purpose.</SUBJECT>
          <P>The Defense Finance and Accounting Service fully implements the policy and procedures of the Privacy Act and the DoD 5400.11-R <SU>1</SU>
            <FTREF/>, ‘Department of Defense Privacy Program’ (see 32 CFR part 310). This regulation supplements the DoD Privacy Program only to establish policy for the Defense Finance and Accounting Service (DFAS) and provide DFAS unique procedures.</P>
          <FTNT>
            <P>
              <SU>1</SU> Copies may be obtained at cost from the National Technical Information Service, 5285 Port Royal Road, Springfield, VA 22161.</P>
          </FTNT>
        </SECTION>
        <SECTION>
          <SECTNO>§ 324.2</SECTNO>
          <SUBJECT>Applicability and scope.</SUBJECT>
          <P>This regulation applies to all DFAS, Headquarters, DFAS Centers, the Financial System Organization (FSO), and other organizational components. It applies to contractor personnel who have entered a contractual agreement with DFAS. Prospective contractors will be advised of their responsibilities under the Privacy Act Program.</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 324.3</SECTNO>
          <SUBJECT>Policy.</SUBJECT>

          <P>DFAS personnel will comply with the Privacy Act of 1974, the DoD Privacy Program and the DFAS Privacy Act <PRTPAGE P="954"/>Program. Strict adherence is required to ensure uniformity in the implementation of the DFAS Privacy Act Program and to create conditions that will foster public trust. Personal information maintained by DFAS organizational elements will be safeguarded. Information will be made available to the individual to whom it pertains to the maximum extent practicable. Specific DFAS policy is provided for Privacy Act training, responsibilities, reporting procedures and implementation requirements. DFAS Components will not define policy for the Privacy Act Program.</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 324.4</SECTNO>
          <SUBJECT>Responsibilities.</SUBJECT>
          <P>(a) <E T="03">Director, DFAS.</E> (1) Ensures the DFAS Privacy Act Program is implemented at all DFAS locations.</P>
          <P>(2) The Director, DFAS, will be the Final Denial Appellate Authority. This authority may be delegated to the Director for Resource Management.</P>
          <P>(3) Appoints the Director for External Affairs and Administrative Support, or a designated replacement, as the DFAS Headquarters Privacy Act Officer.</P>
          <P>(b) <E T="03">DFAS Headquarters General Counsel.</E> (1) Ensures uniformity is maintained in legal rulings and interpretation of the Privacy Act.</P>
          <P>(2) Consults with DoD General Counsel on final denials that are inconsistent with other final decisions within DoD. Responsible to raise new legal issues of potential significance to other Government agencies.</P>
          <P>(3) Provides advice and assistance to the DFAS Director, Center Directors, and the FSO as required, in the discharge of their responsibilities pertaining to the Privacy Act.</P>
          <P>(4) Acts as the DFAS focal point on Privacy Act litigation with the Department of Justice.</P>
          <P>(5) Reviews Headquarters’ denials of initial requests and appeals.</P>
          <P>(c) <E T="03">DFAS Center Directors.</E> (1) Ensures that all DFAS Center personnel, all personnel at subordinate levels, and contractor personnel working with personal data comply with the DFAS Privacy Act Program.</P>
          <P>(2) Serves as the DFAS Center Initial Denial Authority for requests made as a result of denying release of requested information at locations within DFAS Center authority. Initial denial authority may not be redelegated. Initial denial appeals will be forwarded to the appropriate DFAS Center marked to the attention of the DFAS Center Initial Denial Authority.</P>
          <P>(d) <E T="03">Director, FSO.</E> (1) Ensures that FSO and subordinate personnel and contractors working with personal data comply with the Privacy Act Program.</P>
          <P>(2) Serves as the FSO Initial Denial Authority for requests made as a result of denying release of requested information at locations within FSO authority. FSO Initial denial authority may not be redelegated.</P>
          <P>(3) Appoints a Privacy Act Officer for the FSO and each Financial System Activity (FSA).</P>
          <P>(e) <E T="03">DFAS Headquarters Privacy Act Officer.</E> (1) Establishes, issues and updates policy for the DFAS Privacy Act Program and monitors compliance. Serves as the DFAS single point of contact on all matters concerning Privacy Act policy. Resolves any conflicts resulting from implementation of the DFAS Privacy Act Program policy.</P>
          <P>(2) Serves as the DFAS single point of contact with the Department of Defense Privacy Office. This duty may be delegated.</P>
          <P>(3) Ensures that the collection, maintenance, use and/or dissemination of records of identifiable personal information is for a necessary and lawful purpose, that the information is current and accurate for the intended use and that adequate security safeguards are provided.</P>

          <P>(4) Monitors system notices for agency systems of records. Ensures that new, amended, or altered notices are promptly prepared and published. Reviews all notices submitted by the DFAS Privacy Act Officers for correctness and submits same to the Department of Defense Privacy Office for publication in the <E T="04">Federal Register.</E> Maintains and publishes a listing of DFAS Privacy Act system notices.</P>

          <P>(5) Establishes DFAS Privacy Act reporting requirement due dates. Compiles all Agency reports and submits the completed annual report to the Defense Privacy Office. DFAS reporting <PRTPAGE P="955"/>requirements are provided in appendix A to this part.</P>
          <P>(6) Conducts annual Privacy Act Program training for DFAS Headquarters (HQ) personnel. Ensures that subordinate DFAS Center and FSO Privacy Act Officers fulfill annual training requirements.</P>
          <P>(f) <E T="03">FSO and Financial System Activities (FSAs) Legal Support.</E> The FSO and subordinate FSA organizational elements will be supported by the appropriate DFAS-HQ or DFAS Center General Counsel office.</P>
          <P>(g) <E T="03">DFAS Center(s) Assistant General Counsel.</E> (1) Ensures uniformity is maintained in legal rulings and interpretation of the Privacy Act and this regulation. Consults with the DFAS-HQ General Counsel as required.</P>
          <P>(2) Provides advice and assistance to the DFAS Center Director and the FSA in the discharge of his/her responsibilities pertaining to the Privacy Act.</P>
          <P>(3) Coordinates on DFAS Center and the FSA denials of initial requests.</P>
          <P>(h) <E T="03">DFAS Center Privacy Act Officer.</E> (1) Implements and administers the DFAS Privacy Act Program for all personnel, to include contractor personnel, within the Center, Operating Locations (OpLocs) and Defense Accounting Offices (DAOs).</P>

          <P>(2) Ensures that the collection, maintenance, use, or dissemination of records of identifiable personal information is in a manner that assures that such action is for a necessary and lawful purpose; the information is timely and accurate for its intended use; and that adequate safeguards are provided to prevent misuse of such information. Advises the Program Manager that systems notices must be published in the <E T="04">Federal Register</E> prior to collecting or maintenance of the information. Submits system notices to the DFAS-HQ Privacy Act Officer for review and subsequent submission to the Department of Defense Privacy Office.</P>
          <P>(3) Administratively controls and processes Privacy Act requests. Ensures that the provisions of this regulation and the DoD Privacy Act Program are followed in processing requests for records. Ensures all Privacy Act requests are promptly reviewed. Coordinates the reply with other organizational elements as required.</P>
          <P>(4) Prepares denials and partial denials for the Center Director's signature and obtain required coordination with the assistant General Counsel. Responses will include written justification citing a specific exemption or exemptions.</P>
          <P>(5) Prepares input for the annual Privacy Act Report as required using the guidelines provided in appendix A to this part.</P>
          <P>(6) Conducts training on the DFAS Privacy Act Program for Center personnel.</P>
          <P>(i) <E T="03">FSO Privacy Act Officer.</E> (1) Implements and administers the DFAS Privacy Act Program for all personnel, to include contractor personnel, within the FSO.</P>

          <P>(2) Ensures that the collection, maintenance, use, or dissemination of records of identifiable personal information is in a manner that assures that such action is for a necessary and lawful purpose; the information is timely and accurate for its intended use; and that adequate safeguards are provided to prevent misuse of such information. Advises the Program Manager that systems notices must be published in the <E T="04">Federal Register</E> prior to collecting or maintenance of the information. Submits system notices to the DFAS-HQ Privacy Act Officer for review and subsequent submission to the Department of Defense Privacy Office.</P>
          <P>(3) Administratively controls and processes Privacy Act requests. Ensures that the provisions of this regulation and the DoD Privacy Act Program are followed in processing requests for records. Ensure all Privacy Act requests are promptly reviewed. Coordinate the reply with other organizational elements as required.</P>
          <P>(4) Prepares denials and partial denials for signature by the Director, FSO and obtains required coordination with the assistant General Counsel. Responses will include written justification citing a specific exemption or exemptions.</P>

          <P>(5) Prepares input for the annual Privacy Act Report (RCS: DD DA&amp;M(A)1379) as required using the <PRTPAGE P="956"/>guidelines provided in appendix A to this part.</P>
          <P>(6) Conducts training on the DFAS Privacy Act Program for FSO personnel.</P>
          <P>(j) <E T="03">DFAS employees.</E> (1) Will not disclose any personal information contained in any system of records, except as authorized by this regulation.</P>

          <P>(2) Will not maintain any official files which are retrieved by name or other personal identifier without first ensuring that a system notice has been published in the <E T="04">Federal Register.</E>
          </P>
          <P>(3) Reports any disclosures of personal information from a system of records or the maintenance of any system of records not authorized by this regulation to the appropriate Privacy Act Officer for action.</P>
          <P>(k) <E T="03">DFAS system managers (SM).</E> (1) Ensures adequate safeguards have been established and are enforced to prevent the misuse, unauthorized disclosure, alteration, or destruction of personal information contained in system records.</P>
          <P>(2) Ensures that all personnel who have access to the system of records or are engaged in developing or supervising procedures for handling records are totally aware of their responsibilities to protect personal information established by the DFAS Privacy Act Program.</P>
          <P>(3) Evaluates each new proposed system of records during the planning stage. The following factors should be considered:</P>
          <P>(i) Relationship of data to be collected and retained to the purpose for which the system is maintained. All information must be relevant to the purpose.</P>
          <P>(ii) The impact on the purpose or mission if categories of information are not collected. All data fields must be necessary to accomplish a lawful purpose or mission.</P>
          <P>(iii) Whether informational needs can be met without using personal identifiers.</P>
          <P>(iv) The disposition schedule for information.</P>
          <P>(v) The method of disposal.</P>
          <P>(vi) Cost of maintaining the information.</P>
          <P>(4) Complies with the publication requirements of DoD 5400.11-R, ‘Department of Defense Privacy Program’ (see 32 CFR part 310). Submits final publication requirements to the appropriate DFAS Privacy Act Officer.</P>
          <P>(l) <E T="03">DFAS program manager(s).</E> Reviews system alterations or amendments to evaluate for relevancy and necessity. Reviews will be conducted annually and reports prepared outlining the results and corrective actions taken to resolve problems. Reports will be forwarded to the appropriate Privacy Act Officer.</P>
          <P>(m) <E T="03">Federal government contractors.</E> When a DFAS organizational element contracts to accomplish an agency function and performance of the contract requires the operation of a system of records or a portion thereof, DoD 5400.11-R, ‘Department of Defense Privacy Program’ (see 32 CFR part 310) and this part apply. For purposes of criminal penalties, the contractor and its employees shall be considered employees of DFAS during the performance of the contract.</P>
          <P>(1) <E T="03">Contracting involving operation of systems of records.</E> Consistent with Federal Acquisition Regulation (FAR) <SU>2</SU>
            <FTREF/> and the DoD Supplement to the Federal Acquisition Regulation (DFAR) <SU>3</SU>
            <FTREF/>, Part 224.1, contracts involving the operation of a system of records or portion thereof shall specifically identify the record system, the work to be performed and shall include in the solicitations and resulting contract such terms specifically prescribed by the FAR and DFAR.</P>
          <FTNT>
            <P>
              <SU>2</SU> Copies may be obtained at cost from the Superintendent of Documents, P.O. Box 37195, Pittsburgh, PA 15250-7954.</P>
          </FTNT>
          <FTNT>
            <P>
              <SU>3</SU> See footnote 2 to § 324.4(m)(1)</P>
          </FTNT>
          <P>(2) <E T="03">Contracting.</E> For contracting subject to this part, the Agency shall:</P>
          <P>(i) Informs prospective contractors of their responsibilities under the DFAS Privacy Act Program.</P>
          <P>(ii) Establishes an internal system for reviewing contractor performance to ensure compliance with the DFAS Privacy Act Program.</P>
          <P>(3) <E T="03">Exceptions.</E> This rule does not apply to contractor records that are:</P>

          <P>(i) Established and maintained solely to assist the contractor in making internal contractor management decisions, such as records maintained by <PRTPAGE P="957"/>the contractor for use in managing the contract.</P>
          <P>(ii) Maintained as internal contractor employee records, even when used in conjunction with providing goods or services to the agency.</P>
          <P>(4) <E T="03">Contracting procedures.</E> The Defense Acquisition Regulatory Council is responsible for developing the specific policies and procedures for soliciting, awarding, and administering contracts.</P>
          <P>(5) <E T="03">Disclosing records to contractors.</E> Disclosing records to a contractor for use in performing a DFAS contract is considered a disclosure within DFAS. The contractor is considered the agent of DFAS when receiving and maintaining the records for the agency.</P>
        </SECTION>
      </SUBPART>
      <SUBPART>
        <HD SOURCE="HED">Subpart B—Systems of Records</HD>
        <SECTION>
          <SECTNO>§ 324.5</SECTNO>
          <SUBJECT>General information.</SUBJECT>

          <P>(a) The provisions of DoD 5400.11-R, ‘Department of Defense Privacy Program’ (see 32 CFR part 310) apply to all DFAS systems of records. DFAS Privacy Act Program Procedural Rules, DFAS Exemption Rules and System of Record Notices are the three types of documents relating to the Privacy Act Program that must be published in the <E T="04">Federal Register.</E>
          </P>

          <P>(b) A system of records used to retrieve records by a name or some other personal identifier of an individual must be under DFAS control for consideration under this regulation. DFAS will maintain only those Systems of Records that have been described through notices published in the <E T="04">Federal Register.</E>
          </P>
          <P>(1) <E T="03">First amendment guarantee.</E> No records will be maintained that describe how individuals exercise their rights guaranteed by the First Amendment unless maintenance of the record is expressly authorized by Statute, the individual or for an authorized law enforcement purpose.</P>
          <P>(2) <E T="03">Conflicts.</E> In case of conflict, the provisions of DoD 5400.11-R take precedence over this supplement or any DFAS directive or procedure concerning the collection, maintenance, use or disclosure of information from individual records.</P>
          <P>(3) <E T="03">Record system notices.</E> Record system notices are published in the <E T="04">Federal Register</E> as notices and are not subject to the rule making procedures. The public must be given 30 days to comment on any proposed routine uses prior to implementing the system of record.</P>
          <P>(4) <E T="03">Amendments.</E> Amendments to system notices are submitted in the same manner as the original notices.</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 324.6</SECTNO>
          <SUBJECT>Procedural rules.</SUBJECT>

          <P>DFAS procedural rules (regulations having a substantial and direct impact on the public) must be published in the <E T="04">Federal Register</E> first as a proposed rule to allow for public comment and then as a final rule. Procedural rules will be submitted through the appropriate DFAS Privacy Act Officer to the Department of Defense Privacy Office. Appendix B to this part provides the correct format. Guidance may be obtained from the DFAS-HQ and DFAS Center Records Managers on the preparation of procedural rules for publication.</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 324.7</SECTNO>
          <SUBJECT>Exemption rules.</SUBJECT>
          <P>(a) <E T="03">Submitting proposed exemption rules.</E> Each proposed exemption rule submitted for publication in the <E T="04">Federal Register</E> must contain: The agency identification and name of the record system for which an exemption will be established; The subsection(s) of the Privacy Act which grants the agency authority to claim an exemption for the system; The particular subsection(s) of the Privacy Act from which the system will be exempt; and the reasons why an exemption from the particular subsection identified in the preceding subparagraph is being claimed. No exemption to all provisions of the Privacy Act for any System of records will be granted. Only the Director, DFAS may make a determination that an exemption should be established for a system of record.</P>
          <P>(b) <E T="03">Submitting exemption rules for publication.</E> Exemption rules must be published in the <E T="04">Federal Register</E> first as proposed rules to allow for public comment, then as final rules. No system of records shall be exempt from any provision of the Privacy Act until the exemption rule has been published in the <E T="04">Federal Register</E> as a final rule. The DFAS Privacy Act Officer will submit <PRTPAGE P="958"/>proposed exemption rules, in proper format, to the Defense Privacy Office, for review and submission to the <E T="04">Federal Register</E> for publication. Amendments to exemption rules are submitted in the same manner as the original exemption rules.</P>
          <P>(c) <E T="03">Exemption for classified records.</E> Any record in a system of records maintained by the Defense Finance and Accounting Service which falls within the provisions of 5 U.S.C. 552a(k)(1) may be exempt from the following subsections of 5 U.S.C. 552a: (c)(3), (d), (e)(1), (e)(4)(G)-(e)(4)(I) and (f) to the extent that a record system contains any record properly classified under Executive Order 12589 and that the record is required to be kept classified in the interest of national defense or foreign policy. This specific exemption rule, claimed by the Defense Finance and Accounting Service under authority of 5 U.S.C. 552a(k)(1), is applicable to all systems of records maintained, including those individually designated for an exemption herein as well as those not otherwise specifically designated for an exemption, which may contain isolated items of properly classified information</P>
          <P>(1) <E T="03">General exemptions.</E> [Reserved]</P>
          <P>(2) <E T="03">Specific exemptions.</E> [Reserved]</P>
        </SECTION>
      </SUBPART>
      <SUBPART>
        <HD SOURCE="HED">Subpart C—Individual Access to Records</HD>
        <SECTION>
          <SECTNO>§ 324.8</SECTNO>
          <SUBJECT>Right of access.</SUBJECT>
          <P>The provisions of DoD 5400.11-R, ‘Department of Defense Privacy Program’ (see 32 CFR part 310) apply to all DFAS personnel about whom records are maintained in systems of records. All information that can be released consistent with applicable laws and regulations should be made available to the subject of record.</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 324.9</SECTNO>
          <SUBJECT>Notification of record's existence.</SUBJECT>
          <P>All DFAS Privacy Act Officers shall establish procedures for notifying an individual, in response to a request, if the system of records contains a record pertaining to him/her.</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 324.10</SECTNO>
          <SUBJECT>Individual requests for access.</SUBJECT>
          <P>Individuals shall address requests for access to records to the appropriate Privacy Act Officer by mail or in person. Requests for access should be acknowledged within 10 working days after receipt and provided access within 30 working days. Every effort will be made to provide access rapidly; however, records cannot usually be made available for review on the day of request. Requests must provide information needed to locate and identify the record, such as individual identifiers required by a particular system, to include the requester's full name and social security number.</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 324.11</SECTNO>
          <SUBJECT>Denials.</SUBJECT>
          <P>Only a designated denial authority may deny access. The denial must be in writing.</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 324.12</SECTNO>
          <SUBJECT>Granting individual access to records.</SUBJECT>
          <P>(a) The individual should be granted access to the original record (or exact copy) without any changes or deletions. A record that has been amended is considered the original.</P>
          <P>(b) The DFAS component that maintains control of the records will provide an area where the records can be reviewed. The hours for review will be set by each DFAS location.</P>
          <P>(c) The custodian will require presentation of identification prior to providing access to records. Acceptable identification forms include military or government civilian identification cards, driver's license, or other similar photo identification documents.</P>
          <P>(d) Individuals may be accompanied by a person of their own choosing when reviewing the record; however, the custodian will not discuss the record in the presence of the third person without written authorization.</P>
          <P>(e) On request, copies of the record will be provided at a cost of $.15 per page. Fees will not be assessed if the cost is less that $30.00. Individuals requesting copies of their official personnel records are entitled to one free copy and then a charge will be assessed for additional copies.</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 324.13</SECTNO>
          <SUBJECT>Access to medical and psychological records.</SUBJECT>

          <P>Individual access to medical and psychological records should be provided, even if the individual is a minor, unless <PRTPAGE P="959"/>it is determined that access could have an adverse effect on the mental or physical health of the individual. In this instance, the individual will be asked to provide the name of a personal physician, and the record will be provided to that physician in accordance with guidance in Department of Defense 5400.11-R, ‘Department of Defense Privacy Program’ (see 32 CFR part 310).</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 324.14</SECTNO>
          <SUBJECT>Relationship between the Privacy Act and the Freedom of Information Act.</SUBJECT>
          <P>Access requests that specifically state or reasonably imply that they are made under FOIA, are processed pursuant to the DFAS Freedom of Information Act Regulation. Access requests that specifically state or reasonably imply that they are made under the PA are processed pursuant to this regulation. Access requests that cite both the FOIA and the PA are processed under the Act that provides the greater degree of access. Individual access should not be denied to records otherwise releasable under the PA or the FOIA solely because the request does not cite the appropriate statute. The requester should be informed which Act was used in granting or denying access.</P>
        </SECTION>
        <APPENDIX>
          <EAR>Pt. 324, App. A</EAR>
          <HD SOURCE="HED">Appendix A to Part 324—DFAS Reporting Requirements</HD>
          <P>By February 1, of each calendar year, DFAS Centers and Financial Systems Organizations will provide the DFAS Headquarters Privacy Act Officer with the following information:</P>
          <P>1. Total Number of Requests for Access:</P>
          <P>a. Number granted in whole:</P>
          <P>b. Number granted in part:</P>
          <P>c. Number wholly denied:</P>
          <P>d. Number for which no record was found:</P>
          <P>2. Total Number of Requests to Amend Records in the System:</P>
          <P>a. Number granted in whole:</P>
          <P>b. Number granted in part:</P>
          <P>c. Number wholly denied:</P>
          <P>3. The results of reviews undertaken in response to paragraph 3a of Appendix I to OMB Circular A-130 <SU>4</SU>
            <FTREF/>.</P>
          <FTNT>
            <P>
              <SU>4</SU> Copies available from the Office of Personnel Management, 1900 E. Street, Washington, DC 20415.</P>
          </FTNT>
        </APPENDIX>
        <APPENDIX>
          <EAR>Pt. 324, App. B</EAR>
          <HD SOURCE="HED">Appendix B to Part 324—System of Records Notice</HD>

          <P>The following data captions are required for each system of records notice published in the <E T="04">Federal Register</E>. An explanation for each caption is provided.</P>
          <P>1. <E T="03">System identifier.</E> The system identifier must appear in all system notices. It is limited to 21 positions, including agency code, file number, symbols, punctuation, and spaces.</P>
          <P>2. <E T="03">Security classification.</E> Self explanatory. (DoD does not publish this caption. However, each agency is responsible for maintaining the information.)</P>
          <P>3. <E T="03">System name.</E> The system name must indicate the general nature of the system of records and, if possible, the general category of individuals to whom it pertains. Acronyms should be established parenthetically following the first use of the name (e.g., ‘Field Audit Office Management Information System (FMIS)’). Acronyms shall not be used unless preceded by such an explanation. The system name may not exceed 55 character positions, including punctuation and spaces.</P>
          <P>4. <E T="03">Security classification.</E> This category is not published in the <E T="04">Federal Register</E> but is required to be kept by the Headquarters Privacy Act Officer.</P>
          <P>5. <E T="03">System location.</E> a. For a system maintained in a single location, provide the exact office name, organizational identity, routing symbol, and full mailing address. Do not use acronyms in the location address.</P>
          <P>b. For a geographically or organizationally decentralized system, describe each level of organization or element that maintains a portion of the system of records.</P>
          <P>c. For an automated data system with a central computer facility and input or output terminals at geographically separate locations, list each location by category.</P>

          <P>d. If multiple locations are identified by type of organization, the system location may indicate that official mailing addresses are published as an appendix to the agency's compilation of systems of records notices in the <E T="04">Federal Register</E>. If no address directory is used, or if the addresses in the directory are incomplete, the address of each location where a portion of the record system is maintained must appear under the ‘system location’ caption.</P>
          <P>e. Classified addresses shall not be listed but the fact that they are classified shall be indicated.</P>
          <P>f. The U.S. Postal Service two-letter state abbreviation and the nine-digit zip code shall be used for all domestic addresses.</P>
          <P>6. <E T="03">Categories of individuals covered by the system.</E> Use clear, non technical terms which show the specific categories of individuals to whom records in the system pertain. Broad descriptions such as ‘all DFAS personnel’ or ‘all employees’ should be avoided unless the <PRTPAGE P="960"/>term actually reflects the category of individuals involved.</P>
          <P>7. <E T="03">Categories of records in the system.</E> Use clear, non technical terms to describe the types of records maintained in the system. The description of documents should be limited to those actually retained in the system of records. Source documents used only to collect data and then destroyed should not be described.</P>
          <P>8. <E T="03">Authority for maintenance of the system.</E> The system of records must be authorized by a Federal law or Executive Order of the President, and the specific provision must be cited. When citing federal laws, include the popular names (e.g., ‘5 U.S.C. 552a, The Privacy Act of 1974’) and for Executive Orders, the official titles (e.g., ‘Executive Order 9397, Numbering System for Federal Accounts Relating to Individual Persons’).</P>
          <P>9. <E T="03">Purpose(s).</E> The specific purpose(s) for which the system of records was created and maintained; that is, the uses of the records within DFAS and the rest of the Department of Defense should be listed.</P>
          <P>10. <E T="03">Routine uses of records maintained in the system, including categories of users and purposes of the uses.</E> All disclosures of the records outside DoD, including the recipient of the disclosed information and the uses the recipient will make of it should be listed. If possible, the specific activity or element to which the record may be disclosed (e.g., ‘to the Department of Veterans Affairs, Office of Disability Benefits’) should be listed. General statements such as ‘to other Federal Agencies as required’ or ‘to any other appropriate Federal Agency’ should not be used. The blanket routine uses, published at the beginning of the agency's compilation, applies to all system notices, unless the individual system notice states otherwise.</P>
          <P>11. <E T="03">Disclosure to consumer reporting agencies.</E> This entry is optional for certain debt collection systems of records.</P>
          <P>12. <E T="03">Policies and practices for storing, retrieving, accessing, retaining, and disposing of records in the system.</E> This section is divided into four parts.</P>
          <P>13. <E T="03">Storage.</E> The method(s) used to store the information in the system (e.g., ‘automated, maintained in computers and computer output products’ or ‘manual, maintained in paper files’ or ‘hybrid, maintained in paper files and in computers’) should be stated. Storage does not refer to the container or facility in which the records are kept.</P>
          <P>14. <E T="03">Retrievability.</E> How records are retrieved from the system (e.g., ‘by name,’ ‘by SSN,’ or ‘by name and SSN’) should be indicated.</P>
          <P>15. <E T="03">Safeguards.</E> The categories of agency personnel who use the records and those responsible for protecting the records from unauthorized access should be stated. Generally the methods used to protect the records, such as safes, vaults, locked cabinets or rooms, guards, visitor registers, personnel screening, or computer ‘fail-safe’ systems software should be identified. Safeguards should not be described in such detail as to compromise system security.</P>
          <P>16. <E T="03">Retention and disposal.</E> Describe how long records are maintained. When appropriate, the length of time records are maintained by the agency in an active status, when they are transferred to a Federal Records Center, how long they are kept at the Federal Records Center, and when they are transferred to the National Archives or destroyed should be stated. If records eventually are destroyed, the method of destruction (e.g., shredding, burning, pulping, etc.) should be stated. If the agency rule is cited, the applicable disposition schedule shall also be identified.</P>
          <P>17. <E T="03">System manager(s) and address.</E> The title (not the name) and address of the official or officials responsible for managing the system of records should be listed. If the title of the specific official is unknown, such as with a local system, the local director or office head as the system manager should be indicated. For geographically separated or organizationally decentralized activities with which individuals may correspond directly when exercising their rights, the position or title of each category of officials responsible for the system or portion thereof should be listed. Addresses that already are listed in the agency address directory or simply refer to the directory should not be included.</P>
          <P>18. <E T="03">Notification procedures.</E> Notification procedures describe how an individual can determine if a record in the system pertains to him/her. If the record system has been exempted from the notification requirements of subsection (f)(l) or subsection (e)(4)(G) of the Privacy Act, it should be so stated. If the system has not been exempted, the notice must provide sufficient information to enable an individual to request notification of whether a record in the system pertains to him/her. Merely referring to a DFAS regulation is not sufficient. This section should also include the title (not the name) and address of the official (usually the Program Manager) to whom the request must be directed; any specific information the individual must provide in order for DFAS to respond to the request (e.g., name, SSN, date of birth, etc.); and any description of proof of identity for verification purposes required for personal visits by the requester.</P>
          <P>19. <E T="03">Record access procedures.</E> This section describes how an individual can review the record and obtain a copy of it. If the system has been exempted from access and publishing access procedures under subsections (d)(1) and (e)(4)(H), respectively, of the Privacy Act, it should be so indicated. If the system has not been exempted, describe the procedures an individual must follow in order to review the record and obtain a copy of it, including any requirements for identity <PRTPAGE P="961"/>verification. If appropriate, the individual may be referred to the system manager or another DFAS official who shall provide a detailed description of the access procedures. Any addresses already listed in the address directory should not be repeated.</P>
          <P>20. <E T="03">Contesting records procedures.</E> This section describes how an individual may challenge the denial of access or the contents of a record that pertains to him or her. If the system of record has been exempted from allowing amendments to records or publishing amendment procedures under subsections (d)(1) and (e)(4)(H), respectively, of the Privacy Act, it should be so stated. If the system has not been exempted, this caption describes the procedures an individual must follow in order to challenge the content of a record pertaining to him/her, or explain how he/she can obtain a copy of the procedures (e.g., by contacting the Program Manager or the appropriate DFAS Privacy Act Officer).</P>
          <P>21. <E T="03">Record source categories.</E> If the system has been exempted from publishing record source categories under subsection (e)(4)(I) of the Privacy Act, it should be so stated. If the system has not been exempted, this caption must describe where DFAS obtained the information maintained in the system. Describing the record sources in general terms is sufficient; specific individuals, organizations, or institutions need not be identified.</P>
          <P>22. <E T="03">Exemptions claimed for the system.</E> If no exemption has been established for the sys-tem, indicate ‘None.’ If an exemption has been established, state under which provision of the Privacy Act it is established (e.g., ‘Portions of this system of records may be exempt under the provisions of 5 U.S.C. 552a(k)(2).’)</P>
        </APPENDIX>
      </SUBPART>
    </PART>
    <PART>
      <EAR>Pt. 326</EAR>
      <HD SOURCE="HED">PART 326—-NATIONAL RECONNAISSANCE OFFICE PRIVACY ACT PROGRAM</HD>
      <CONTENTS>
        <SECHD>Sec.</SECHD>
        <SECTNO>326.1</SECTNO>
        <SUBJECT>Purpose.</SUBJECT>
        <SECTNO>326.2</SECTNO>
        <SUBJECT>Application.</SUBJECT>
        <SECTNO>326.3</SECTNO>
        <SUBJECT>Definitions.</SUBJECT>
        <SECTNO>326.4</SECTNO>
        <SUBJECT>Policy.</SUBJECT>
        <SECTNO>326.5</SECTNO>
        <SUBJECT>Responsibilities.</SUBJECT>
        <SECTNO>326.6</SECTNO>
        <SUBJECT>Policies for processing requests for records.</SUBJECT>
        <SECTNO>326.7</SECTNO>
        <SUBJECT>Procedures for collection.</SUBJECT>
        <SECTNO>326.8</SECTNO>
        <SUBJECT>Procedures for requesting access.</SUBJECT>
        <SECTNO>326.9</SECTNO>
        <SUBJECT>Procedures for disclosure of requested records.</SUBJECT>
        <SECTNO>326.10</SECTNO>
        <SUBJECT>Procedures to appeal denial of access to requested record.</SUBJECT>
        <SECTNO>326.11</SECTNO>
        <SUBJECT>Special procedures for disclosure of medical and psychological records.</SUBJECT>
        <SECTNO>326.12</SECTNO>
        <SUBJECT>Procedures to request amendment or correction of record.</SUBJECT>
        <SECTNO>326.13</SECTNO>
        <SUBJECT>Procedures to appeal denial of amendment.</SUBJECT>
        <SECTNO>326.14</SECTNO>
        <SUBJECT>Disclosure of record to person other than subject.</SUBJECT>
        <SECTNO>326.15</SECTNO>
        <SUBJECT>Fees.</SUBJECT>
        <SECTNO>326.16</SECTNO>
        <SUBJECT>Penalties.</SUBJECT>
        <SECTNO>326.17</SECTNO>
        <SUBJECT>Exemptions.</SUBJECT>
      </CONTENTS>
      <AUTH>
        <HD SOURCE="HED">Authority:</HD>
        <P>Pub. L. 93-579, 88 Stat 1896 (5 U.S.C. 552a).</P>
      </AUTH>
      <SOURCE>
        <HD SOURCE="HED">Source:</HD>
        <P>65 FR 20372, Apr. 17, 2000, unless otherwise noted.</P>
      </SOURCE>
      <SECTION>
        <SECTNO>§ 326.1</SECTNO>
        <SUBJECT>Purpose.</SUBJECT>
        <P>This part implements the basic policies and procedures outlined in the Privacy Act of 1974, as amended (5 U.S.C. 552a), and 32 CFR part 310; and establishes the National Reconnaissance Office Privacy Program (NRO) by setting policies and procedures for the collection and disclosure of information maintained in records on individuals, the handling of requests for amendment or correction of such records, appeal and review of NRO decisions on these matters, and the application of exemptions.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 326.2</SECTNO>
        <SUBJECT>Application.</SUBJECT>
        <P>Obligations under this part apply to all employees detailed, attached, or assigned to or authorized to act as agents of the National Reconnaissance Office. The provisions of this part shall be made applicable by contract or other legally binding action to government contractors whenever a contract is let for the operation of a system of records or a portion of a system of records.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 326.3</SECTNO>
        <SUBJECT>Definitions.</SUBJECT>
        <P>
          <E T="03">Access.</E> The review or copying of a record or its parts contained in a system of records by a requester.</P>
        <P>
          <E T="03">Agency.</E>  Any executive or military department, other establishment, or entity included in the definition of agency in 5 U.S.C. 522(f).</P>
        <P>
          <E T="03">Control.</E>  Ownership or authority of the NRO pursuant to federal statute or privilege to regulate official or public access to records.</P>
        <P>
          <E T="03">Disclosure.</E>  The authorized transfer of any personal information from a system of records by any means of communication (such as oral, written, electronic, mechanical, or actual review) to any person, private entity, or government agency other than the subject of the record, the subject's designated agent, or the subject's legal guardian.<PRTPAGE P="962"/>
        </P>
        <P>
          <E T="03">He, him, and himself.</E>  Generically used in this part to refer to both males and females.</P>
        <P>
          <E T="03">Individual or requester.</E>  A living citizen of the U.S. or an alien lawfully admitted to the U.S. for permanent residence and to whom a record might pertain. The legal guardian or legally authorized agent of an individual has the same rights as the individual and may act on his behalf. No rights are vested in the representative of a dead person or in persons acting in an entrepreneurial (for example, sole proprietorship or partnership) capacity under this part.</P>
        <P>
          <E T="03">Interested party.</E>  Any official in the executive (including military), legislative, or judicial branches of government, U.S. or foreign, or U.S. Government contractor who, in the sole discretion of the NRO, has a subject matter or physical interest in the documents or information at issue.</P>
        <P>
          <E T="03">Maintain.</E> To collect, use, store, disclose, retain, or disseminate when used in connection with records.</P>
        <P>
          <E T="03">Originator.</E> The NRO employee or contractor who created the document at issue or his successor in office or any official who has been delegated release or declassification authority pursuant to law.</P>
        <P>
          <E T="03">Personal information.</E> Information about any individual that is intimate or private to the individual, as distinguished from ‘corporate information’ which is in the public domain and related solely to the individual's official functions or public life (i.e., employee's name, job title, work phone, grade/rank, job location).</P>
        <P>
          <E T="03">Privacy Act Coordinator.</E> The NRO Information and Access Release Center Chief who serves as the NRO manager ofthe information review and release program instituted under the Privacy Act.</P>
        <P>
          <E T="03">Record.</E>  Any item, collection, or grouping of information about an individual that is maintained by the NRO, including, but not limited to, the individual's education, financial transactions, medical history, and criminal or employment history, and that contains the individual's name or identifying number (such as Social Security or employee number), symbol, or other identifying particular assigned to the individual, such as fingerprint, voice print, or photograph. Records include data about individuals which is stored in computers.</P>
        <P>
          <E T="03">Responsive record.</E>  Documents or records that the NRO has determined to be within the scope of a Privacy Act request.</P>
        <P>
          <E T="03">Routine use.</E> The disclosure of a record outside the Department of Defense (DoD) for a use that is compatible with the purpose for which the information was collected and maintained by NRO. Routine use encompasses not only common or ordinary use, but also all the proper and necessary uses of the record even if such uses occur infrequently. All routine uses must be published in the <E T="04">Federal Register</E>.</P>
        <P>
          <E T="03">System managers.</E>  Officials who have overall responsibility for a Privacy Act system of records.</P>
        <P>
          <E T="03">System notice.</E> The official public notice published in the Federal Register of the existence and general content of the system of records.</P>
        <P>
          <E T="03">System of records.</E>  A group of any records under the control of the NRO from which information is retrieved by the name of an individual or by some identifying number, symbol, or other identifying particular assigned to that individual.</P>
        <P>
          <E T="03">Working days.</E>  Days when the NRO is operating and specifically excludes Saturdays, Sundays, and legal public holidays.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 326.4</SECTNO>
        <SUBJECT>Policy.</SUBJECT>
        <P>(a) <E T="03">Records about individuals—</E>
        </P>
        <P>(1) <E T="03">Collection.</E>  The NRO will safeguard the privacy of individuals identified in its records. Information about an individual will, to the greatest extent practicable, be collected directly from the individual, and personal information will be protected from unintentional or unauthorized disclosure by treating it as marked ‘For Official Use Only.’ Access to personal information will be restricted to those employees whose official duties require it during the regular course of business.</P>
        <P>(i) <E T="03">Privacy Act Statement.</E> When an individual is requested to furnish personal information about himself for inclusion in a system of records, a Privacy Act Statement is required to enable him to make an informed decision <PRTPAGE P="963"/>whether to provide the information requested. A Privacy Act Statement may appear, in order of preference, at the top or bottom of a form, on the reverse side of a form, or attached to the form as a tear-off sheet.</P>
        <P>(ii) <E T="03">Social Security Numbers (SSNs).</E> It is unlawful for any governmental agency to deny an individual any right, benefit, or privilege provided by law because the individual refuses to provide his SSN. However, if a federal statute requires that the SSN be furnished or if the SSN is required to verify the identity of an individual in a system of records that was established and in use before January 1, 1975, this restriction does not apply. When collecting the SSN, a ‘qualified’ Privacy Act Statement must be provided even if the SSN will not be maintained in a system of records. The 'qualified' Privacy Act Statement shall inform the individual whether the disclosure is mandatory or voluntary, by what statutory or other authority such number is solicited, and what uses will be made of it.</P>
        <P>(2) <E T="03">Maintenance.</E>  The NRO will maintain in its records only such information about an individual which is accurate, relevant, timely, and necessary to accomplish a purpose which is required by statute or Executive Order. All records used by the NRO to make determinations about individuals will be maintained with such accuracy and completeness as is reasonably necessary to assure fairness to the individual.</P>
        <P>(3) <E T="03">Existence.</E>  The applicability of the Privacy Act depends on the existence of an identifiable record. The procedures described in NRO regulations do not require that a record be created or that an individual be given access to records that are not retrieved by name or other individual identifier. Nor do these procedures entitle an individual to have access to any information compiled in reasonable anticipation of a civil action or proceeding. NRO will maintain only those systems of records that have been described through notices published in the <E T="04">Federal Register</E>. A system of records from which records may be retrieved by a name or some other personal identifier must be under NRO control for consideration under this part.</P>
        <P>(4) <E T="03">Disposal.</E>  The NRO will archive, dispose of, or destroy records containing personal data in a manner to prevent specific records from being readily identified or inadvertently compromised.</P>
        <P>(b) <E T="03">Evaluation of records.</E>  Statutory authority to establish and maintain a system of records does not grant unlimited authority to collect and maintain all information which may be useful or convenient. Directorates and offices maintaining records will evaluate each category of information in records systems for necessity and relevance prior to republication of all system notices in the <E T="04">Federal Register</E> and during the design phase or change of a system of records. The following will be considered in the evaluation:</P>
        <P>(1) Relationship of each item of information to the statutory purpose for which the system is maintained;</P>
        <P>(2) Specific adverse consequences of not collecting each category of information; and</P>
        <P>(3) Techniques for purging parts of the records.</P>
        <P>(c) <E T="03">Disclosure of records.</E>  The NRO will provide the fullest access practicable by individuals to NRO records concerning them. Release of personal information to such individuals is not considered public release of information. Upon receipt of a written request, the NRO will release to individuals those records that are releasable and applicable to the individual making the request. Generally, information, other than that exempted by law and this part, will be provided to the individual. NRO personnel will comply with the Privacy Act of 1974, as amended, the DoD Privacy Act Program (32 CFR part 310), and the NRO Privacy Act Program. No NRO records shall be disclosed by any means of communication to any person or to any agency except pursuant to a written request by or the prior written consent of the individual to whom it pertains, unless disclosure of the record will be:</P>

        <P>(1) To those employees of the NRO who have an official need for the record in the performance of their duties.<PRTPAGE P="964"/>
        </P>
        <P>(2) Required to be disclosed to a member of the public under the Freedom of Information Act, as amended.</P>
        <P>(3) For a routine use as defined in the Privacy Act.</P>
        <P>(4) To the Census Bureau for the purpose of conducting a census or survey or related activity authorized by law.</P>
        <P>(5) To a recipient who has provided the NRO with advance, adequate written assurance that the record will be used solely as statistical research and that the record is to be transferred in a form in which the individual is not identifiable.</P>
        <P>(6) To the National Archives of the United States as a record which has sufficient historical or other value to warrant its continued preservation by the U. S. Government.</P>
        <P>(7) To another agency or to an instrumentality of any governmental jurisdiction within or under the control of the U.S. for a civil or criminal law enforcement activity if such activity is authorized by law and if the head of the agency or governmental entity has made a written request to the NRO specifying the particular portion of the record and the law enforcement activity for which the record is sought (blanket requests will not be accepted); a record may also be disclosed to a law enforcement agency at the initiative of the NRO pursuant to the blanket routine use for law enforcement when criminal conduct is indicated in the record.</P>
        <P>(8) To a person showing compelling circumstances affecting the health or safety of an individual if, upon such disclosure, notification is sent to the last known address of the individual to whom the record pertains (emergency medical information may be released by telephone).</P>
        <P>(9) To Congress or any committee, joint committee, or subcommittee of Congress with respect to a matter under its jurisdiction. This provision does not authorize the disclosure of a record to members of Congress acting in their individual capacities or on behalf of their constituents making third party requests. However, such releases may be made pursuant to the blanket routine use for Congressional inquiries when a constituent has sought the assistance of his Congressman forthe constituent's individual record(s).</P>
        <P>(10) To the Comptroller General or any of his authorized representatives in the course of the performance of the duties of the General Accounting Office.</P>
        <P>(11) Pursuant to an order of a court of competent jurisdiction. When the record is disclosed under compulsory legal process and when the issuance of that order or subpoena is made public by the court which issued it, the NRO will make reasonable efforts to notify the individual to whom the record pertains by mail at the most recent address contained in NRO records.</P>
        <P>(12) To a consumer reporting agency in accordance with 31 U.S.C. 3711(f).</P>
        <P>(d) <E T="03">Allocation of resources.</E>  NRO components shall exercise due diligence in their responsibilities under the Privacy Act and must devote a reasonable level of personnel to respond to requests on a ‘first-in, first-out’ basis. In allocating Privacy Act resources, the component shall consider its imposed business demands, the totality of resources available to it, the information review and release demands imposed by Congress and other governmental authorities, and the rights of the public under various disclosure laws. The PA Coordinator will establish priorities for cases consistent with established law to ensure that smaller as well as larger ‘project’ cases receive equitable attention.</P>
        <P>(e) <E T="03">Written permission for disclosure.</E> Disclosures made under circumstances not delineated in this part shall be made only if the written permission of the individual involved has been obtained. Written permission shall be recorded on or appended to the document transmitting the personal information to the other agency, in which case no separate accounting of the disclosure need be made. Written permission is required in each case; that is, once obtained, written permission for one case does not constitute blanket permission for other disclosures.</P>
        <P>(f) <E T="03">Coordination with other government agencies.</E> Records systems of the NRO may contain records originated by other agencies that may have claimed exemptions for them under the Privacy Act. Where appropriate, coordination <PRTPAGE P="965"/>will be effected with the originating agency. The NRO will comply with the instructions issued by another agency responsible for a system of records (e.g., Office of Personnel Management) in granting access to such records. Records containing information or interests of another government agency will not be released until coordination with the other agency involved. A request for information pertaining to the individual in an NRO record system received from another federal agency will be coordinated with the originating agency.</P>
        <P>(g) <E T="03">Accounting for disclosure.</E> Except for disclosures made under paragraphs (c)(1) and (c)(2) of this section, an accurate account of the disclosures shall be kept by the record holder in consultation with the Privacy Act Coordinator (PA Coordinator). There need not be a notation on a single document of every disclosure of a particular record. The record holder should be able to construct from its system of records the accounting information:</P>
        <P>(1) When required by the individual to whom the record pertains, or</P>
        <P>(2) When necessary to inform previous recipients of any amended records. The accounting shall be retained for at least five years or for the life of the record, whichever is longer, to be available for review by the subject of the record at his request except for disclosures made under paragraph (c)(7) of this section.</P>
        <P>(h) <E T="03">Application of rules.</E> Any request for access, amendment, correction, etc., of personal record information in a system of records by an individual to whom such information pertains will be governed by the Privacy Act of 1974, as amended, DoD regulatory authority, and this part, exclusively. Any denial or exemption of all or part of a record from access, disclosure, amendment, correction, etc., will be processed under DoD regulatory authority and this part, unless court order or other competent authority directs otherwise.</P>
        <P>(i) <E T="03">First Amendment rights.</E>  No NRO official or component may maintain any information pertaining to the exercise by an individual of his rights under the First Amendment without the permission of that individual unless such collection is specifically authorized by statute or pertains to an authorized law enforcement activity.</P>
        <P>(j) <E T="03">Non-system information on individuals.</E> The following information is not considered part of personal records systems reportable under this part and may be maintained by NRO for ready identification, contact, and property control purposes only, provided it is not maintained in a system of records. If at any time the information described in this paragraph is being maintained in a system of records, the information is subject to the Privacy Act.</P>
        <P>(1) Identification information at doorways, building directories, desks, lockers, name tags, etc.</P>
        <P>(2) Geographical or agency contact cards.</P>
        <P>(3) Property receipts and control logs for building passes, credentials, vehicles, etc.</P>
        <P>(4) Personal working notes of employees that are merely an extension of the author's memory, if maintained properly, do not come under the Privacy Act. Personal notes are not considered official NRO records if they meet the following requirements:</P>
        <P>(i) Keeping or discarding notes must be at the sole discretion of the author. Any requirement by supervising authority, whether by oral or written directive, regulation, policy, or memo to maintain such notes, likely would cause the notes to become official agency records.</P>
        <P>(ii) Such notes must be restricted to the author's personal use as memory aids, and only the author may have access to them. Passing them to a successor or showing them to other personnel (including supporting staff such as secretaries) would likely cause them to become agency records.</P>
        <P>(5) Rosters. The NRO has no restriction against rosters that contain only corporate information such as name, work telephone number, and position. Good recordkeeping practices dictate that only rosters that are relevant and necessary to the NRO's operations may be maintained, and therefore convenience rosters, which by definition do not satisfy the test, may not be maintained.</P>
      </SECTION>
      <SECTION>
        <PRTPAGE P="966"/>
        <SECTNO>§ 326.5</SECTNO>
        <SUBJECT>Responsibilities.</SUBJECT>
        <P>(a) The Director, NRO (DNRO):</P>
        <P>(1) Supervises the execution of the Privacy Act and this part within the NRO.</P>
        <P>(2) Appoints:</P>
        <P>(i) The Chief, Information Access and Release Center as the NRO Privacy Act Coordinator.</P>
        <P>(ii) The Director of Security, the Director of Policy, and the NRO General Counsel as the NRO Appeals Panel; and</P>
        <P>(iii) The Chief of Staff as the Senior Official for Privacy Policy and the Privacy Act Appeal Authority.</P>
        <P>(b) The Privacy Act Coordinator, NRO:</P>
        <P>(1) Establishes, issues, and updates policy for the NRO Privacy Act Program, monitors compliance, and serves as the principal NRO point of contact on all Privacy Act matters.</P>
        <P>(2) Receives, processes, and responds to all PrivacyAct requests received by the NRO, including:</P>
        <P>(i) Granting, granting in part, or denying an initial Privacy Act request for access or amendment to a record, and notifying a requester of such actions taken in regard to that request.</P>
        <P>(ii) Granting a requester access to all or part ofa record under dispute when, after a review, a decision is made in favor of a requester.</P>
        <P>(iii) Directing the appropriate NRO component to amend a record and advising other record holders to amend a record when a decision is made in favor of a requester.</P>
        <P>(iv) Notifying a requester, if a request is denied, of the reasons for denial and the procedures for appeal to the Privacy Act Appeal Authority.</P>
        <P>(v) Notifying a requester of his right to file a concise statement of his reasons for disagreement with the NRO's refusal to amend a record.</P>
        <P>(vi) Directing that a requester's statement of reasons for the request to amend, his concise statement of disagreement with the NRO's refusal to amend a record, and the NRO's letter of denial be included in the file containing the disputed record.</P>
        <P>(vii) Referring all appeals to the Privacy Act Appeals Panel and Appeal Authority.</P>
        <P>(viii) Notifying a requester of any required fees and delivering such collected fees to the Comptroller.</P>
        <P>(ix) Obtaining supplemental information from the requester when required.</P>
        <P>(3) Serves as the NRO point of contact with the Defense Privacy Office.</P>

        <P>(4) Reviews NRO use of records, and at least 40 calendar days prior to establishing a new agency system of records, ensures that new or amended notices are prepared and published in the <E T="04">Federal Register</E> consistent with the requirements of 32 CFR part 310;</P>
        <P>(5) Coordinates with forms managers to ensure that a Privacy Act Statement is on all forms or in all other methods used to collect personal information for inclusion in any NRO records system;</P>
        <P>(6) Prepares the NRO Privacy Act report for submission to the DoD Privacy Office and to other authorities, as required by 32 CFR part 310.</P>
        <P>(7) Reviews all procedures, including forms, which require an individual to furnish information for conformity with the Privacy Act.</P>
        <P>(8) Retains the accounting of disclosures for at least five years or for the life of the record, whichever is longer, to be available for review by the subject of the record at his request except for disclosures made under paragraph (c)(7) of § 326.4; and</P>
        <P>(9) Develops and oversees Privacy Act Program training for NRO personnel.</P>
        <P>(c) The Privacy Act Appeals Panel, NRO:</P>
        <P>(1) Meets and reviews all denials appealed by means of the NRO internal appeals process; and</P>
        <P>(2) Recommends a finding to the Privacy Act Appeal Authority by a majority vote of those present at the meeting and based on the written record and the panel's deliberations.</P>
        <P>(d) The Privacy Act Appeal Authority, NRO:</P>
        <P>(1) Determines all NRO Privacy Act appeals.</P>
        <P>(2) Reports the determination to the PA Coordinator.</P>
        <P>(3) Signs the final appeal letter to the requester.</P>
        <P>(e) General Counsel, NRO:</P>

        <P>(1) Ensures uniformity in NRO legal positions concerning the Privacy Act <PRTPAGE P="967"/>and reviews proposed responses to Privacy Act requests to ensure legal sufficiency, as appropriate.</P>
        <P>(2) Consults with DoD General Counsel on final denials that may be inconsistent with other final decisions within DoD; raises new legal issues of potential significance to other government agencies.</P>
        <P>(3) Provides advice and assistance to the DNRO, the PA Coordinator, and component Directors, as required, in the discharge of their responsibilities pertaining to the Privacy Act.</P>
        <P>(4) Advises on all legal matters concerning the Privacy Act, including legal decisions, rulings by the Department of Justice, and actions by DoD and other commissions on the Privacy Act.</P>
        <P>(5) Approves all Privacy Act Statements prior to their reproduction and distribution.</P>
        <P>(6) Acts as the NRO focal point for Privacy Act litigation with the Department of Justice.</P>
        <P>(7) Provides a status report to the Defense Privacy Office, consistent with the requirements of 32 CFR part 310, whenever an individual brings suit under subsection (g) of the Privacy Act against NRO.</P>
        <P>(f) Chief Information Officer (CIO), NRO:</P>
        <P>(1) Ensures that NRO systems of records databases have procedures to protect the confidentiality of personal records maintained or processed by means of automatic data processing (ADP) systems and ensures that ADP systems contain appropriate safeguards for the privacy of personnel.</P>
        <P>(2) Coordinates with the PA Coordinator before developing or modifying CIO-sponsored ADP supported files subject to the provisions of this part.</P>
        <P>(g) Directorate and Office Managers, NRO:</P>
        <P>(1) Ensure that records contained in their directorate or office systems of records are disclosed only to those NRO officials or employees who require the records for official purposes.</P>

        <P>(2) Review their own directorate and office systems of records to ensure and certify that no systems of records other than those listed in the <E T="04">Federal Register</E> System Notices are maintained; notify the CIO and the PA Coordinator promptly whenever there are changes to processing equipment, hardware, software, or database that may require an amended system notice.</P>
        <P>(3) Maintain only such information about an individual as is relevant and necessary to accomplish a purpose which is required by statute or Executive Order and identify the specific provision of law or Executive Order which provides authority for the maintenance of information in each system of records.</P>
        <P>(h) System Managers, NRO:</P>
        <P>(1) Ensure that adequate safeguards have been established and are enforced to prevent the misuse, unauthorized disclosure, alteration, or destruction of personal information contained in system records.</P>
        <P>(2) Ensure that all personnel who have access tothe system of records, or are engaged in developing or supervising procedures for handling records, are aware of their responsibilities established by the NRO Privacy Act Program.</P>
        <P>(3) Evaluate each system of records during the planning stage and at regular intervals. The following factors should be considered:</P>
        <P>(i) Relationship of data to be collected and retained to the purposes for which the system is maintained (all information must be relevant and necessary to the purpose for which it is collected).</P>
        <P>(ii) The specific impact on the purpose or mission if categories of information are not collected (all data fields must be necessary to accomplish a lawful purpose or mission).</P>
        <P>(iii) Whether informational needs can be met without using personal identifiers.</P>
        <P>(iv) The cost of maintaining and disposing of records within the systems of records and the length of time each item of information must be retained according to the NRO Records Control Schedule as approved by the National Archives and Records Administration.</P>
        <P>(4) Review system alterations or amendments to evaluate for relevancy and necessity.</P>

        <P>(i) Forms and Information Managers. All NRO individualsresponsible for <PRTPAGE P="968"/>forms or methods used to collect personal information from individuals will:</P>
        <P>(1) Ensure that Privacy Act Statements are on appropriate forms and that new forms have the required Privacy Act Statement.</P>
        <P>(2) Determine, with General Counsel's concurrence, which forms require Privacy Act Statements and will prepare such statements.</P>
        <P>(3) Assist the initiators in determining whether a form, format, questionnaire, or report requires a Privacy Act Statement. Privacy Act Statements must be complete, specific, written in plain English, and approved by the Office of General Counsel.</P>
        <P>(j) Employees, NRO:</P>
        <P>(1) Will be familiar with the provisions of this part regarding the maintenance of systems of records, authorized access, and authorized disclosure;</P>
        <P>(2) Will collect, maintain, use, and/or disseminate records containing identifiable personal information only for lawful purposes; will keep the information current, complete, relevant, and accurate for its intended use; and will safeguard the records in a system and keep them the minimum time required;</P>
        <P>(3) Will not disclose any personal information contained in any system of records, except as authorized by the Privacy Act and this part;</P>
        <P>(4) Will maintain no system of records concerning individuals except those authorized, and will maintain no other information concerning individuals except as necessary for the conduct of business at the NRO;</P>
        <P>(5) Will provide individuals a Privacy Act Statement when asking them to provide information about themselves. The Privacy Act Statement will include the authority under which the information is being requested, whether disclosure of the information is mandatory or voluntary, the purposes for which it is being requested, the uses to which it will be put, and the consequences of not providing the information;</P>
        <P>(6) May not deny an individual any right or privilege provided by law because of that individual's failure to disclose his SSN unless such information is required by federal statute or disclosure was required by statute or regulations adopted prior to January 1, 1975. If disclosure of the SSN is not required, NRO directorates and offices are not precluded from requesting it from individuals; however, the Privacy Act Statement must make clear that the disclosure of the SSN is voluntary and, if the individual refuses to disclose it, must be prepared to identify him by alternate means.</P>
        <P>(7) Will collect personal information directly from the subject whenever possible; employees may collect information from third parties when that information must be verified, opinions or evaluations are required, the subject cannot be contacted, or the subject requests it.</P>
        <P>(8) Will keep paper and electronic records which contain personal information and are retrieved by name or personal identifier only in approved systems published in the Federal Register.</P>
        <P>(9) Will amend and correct records when directed by the PA Coordinator.</P>
        <P>(10) Will report to the PA Coordinator any disclosures of personal information from a system of records, or the maintenance of any system of records, not authorized by this part.</P>
        <P>(11) Will participate in specialized Privacy Act training should their duties require dealing with special investigators, the news media, or the public.</P>
        <CITA>[65 FR 20372, Apr. 17, 2000, as amended at 66 FR 41783, Aug. 9, 2001]</CITA>
      </SECTION>
      <SECTION>
        <SECTNO>§ 326.6</SECTNO>
        <SUBJECT>Policies for processing requests for records.</SUBJECT>
        <P>(a) An individual's written request for access to records about himself which does not specify the Act under which the request is made will be processed under both the Freedom of Information Act (FOIA) and the Privacy Act and the applicable regulations. Such requests will be processed under both Acts regardless of whether the requester cites one Act, both, or neither in the request in order to ensure the maximum possible disclosure to the requester. Individuals may not be denied access to a record pertaining to themselves merely because those records are exempt from disclosure under the FOIA.</P>

        <P>(b) A Privacy Act request that neither specifies the system(s) of records <PRTPAGE P="969"/>to be searched nor identifies the substantive nature of the information sought will be processed by searching the systems of records categorized as Environmental Health, Safety and Fitness, FOIA/Privacy, General, and Security.</P>
        <P>(c) A Privacy Act request that does not designate the system(s) of records to be searched but does identify the substantive nature of the information sought will be processed by searching those systems of records likely to have information similar to that sought by the requester.</P>
        <P>(d) The NRO will not disclose any record to any person or government agency except by written request or prior written consent of the subject of the record unless the disclosure is required by law or is within the exceptions of the Privacy Act. If a requester authorizes another individual to obtain the requested records on his behalf, the requester shall provide a written, signed, notarized statement appointing that individual as his representative and certifying that the individual appointed may have access to the requester's records and that such access shall not constitute an invasion of his privacy nor a violation of his rights under the Privacy Act. In lieu of a notarized statement, the NRO will accept a declaration in accordance with 28 U.S.C. 1746.</P>
        <P>(e) Upon receipt of a written request, the Privacy Act Coordinator (PA Coordinator) will release to the requester those records which are releasable and applicable to the individual making the request. Records about individuals include data stored electronically or in electronic media. Documentary material qualifies as a record if the record is maintained in a system of records.</P>
        <P>(f) Initial availability, potential for release, and cost determination will usually be made within ten working days of the date on which a written request for any identifiable record is received by the NRO (and acknowledgement is sent to the individual). If additional time is needed due to unusual circumstances, a written notification of the delay will be forwarded to the requester within the ten working day period. This notification will briefly explain the circumstances for the delay and indicate the anticipated date for a substantive response.</P>
        <P>(g) All requests will be handled in the order received on a ‘first-in, first-out’ basis. Requests will be considered for expedited processing only if the NRO determines that there is a genuine health, humanitarian, or due process reason involving possible deprivation of life or liberty which creates an exceptional and urgent need, that there is no alternative forum for the records sought, and that substantive records relevantto the stated needs may exist and be releasable.</P>
        <P>(h) Records provided or originated by another agency or containing other agency information will not be released prior to coordination with the other agency involved.</P>
        <P>(i) Requesting or obtaining access to records under false pretenses is a violation of the Privacy Act and is subject to criminal penalties.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 326.7</SECTNO>
        <SUBJECT>Procedures for collection.</SUBJECT>
        <P>(a) To the maximum extent practical, personal information about an individual will be obtained directly from that individual.</P>
        <P>(b) Whenever an individual is asked to provide personal information, including Social Security Number (SSN) or a personal identifier, about himself, a Privacy Act Statement will be furnished that will advise him of the authority (whether by statute or by Executive Order) under which the information is requested, whether disclosure of the information is voluntaryor mandatory, the purposes for which it is requested, the uses to which it will be put, and the consequences of not providing the information.</P>
        <P>(c) When asking third parties to provide information about other individuals, NRO employees will advise them:</P>
        <P>(1) Of the purpose of the request, and</P>
        <P>(2) That their identities and the information they are furnishing may be released to the individual unless they expressly request confidentiality. All persons interviewed must be informed of their rights and offered confidentiality.</P>
      </SECTION>
      <SECTION>
        <PRTPAGE P="970"/>
        <SECTNO>§ 326.8</SECTNO>
        <SUBJECT>Procedures for requesting access.</SUBJECT>
        <P>(a) <E T="03">Request in writing.</E>  An individual seeking notification of whether a system of records contains a record pertaining to him, or an individual seeking access to records pertaining to him which are available under the Privacy Act, shall address the request in writing to the Privacy Act Coordinator, National Reconnaissance Office, 14675 Lee Road, Chantilly, VA 20151-1715. The request should contain at least the following information:</P>
        <P>(1) <E T="03">Identification.</E>  Reasonable identification, including first name, middle name or initial, surname, any aliases or nicknames, Social Security Number, and return address of the individual concerned, accompanied by a signed notarized statement that such information is true under penalty of perjury and swearing to or affirming his identity. An unsworn declaration, under 28 U.S.C. 1746, also is acceptable. In the case of a request for records of a sensitive nature if the PA Coordinator determines that this information does not sufficiently identify the individual, the PA Coordinator may requests additional identification or clarification of information submitted by the individual.</P>
        <P>(i) In addition, an alien lawfully admitted for permanent residence shall provide his Alien Registration Number and the date that status was acquired.</P>
        <P>(ii) The parent or guardian of a minor or of a person judicially determined to be incompetent, or an attorney retained to represent an individual, in addition to establishing the identity of the minor or person represented as required in this part, shall provide evidence of his own identity as required in this part and evidence of such parentage, guardianship, or representation by submitting a certified copyof the minor's birth certificate, the court order establishing such guardianship, or the representation agreement which establishes the relationship.</P>
        <P>(2) <E T="03">Cost.</E>  A statement of willingness to pay reproduction costs. Processing of requests and administrative appeals from individuals who owe outstanding fees will be held in abeyance until such fees are paid.</P>
        <P>(3) <E T="03">Record sought.</E> A description, to the best of his ability, of the nature of the record sought and the system in which it is thought to be included. In lieu of this, a requester may simply describe why and under what circumstances he believes that the NRO maintains responsive records; the NRO will undertake the appropriate searches.</P>
        <P>(b) <E T="03">Access on behalf of the individual.</E> If the requester wishes another person to obtain the records on his behalf, the requester will furnish a notarized statement or unsworn declaration appointing that person as his representative, authorizing him access to the record, and affirming that access will not constitute an invasion of the requester's privacy or a violation of his rights under the Privacy Act. The NRO requires a written statement to authorize discussion of the individual's record in the presence of a third person.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 326.9</SECTNO>
        <SUBJECT>Procedures for disclosure of requested information.</SUBJECT>
        <P>(a) The PA Coordinator shall acknowledge receipt of the request in writing within ten working days.</P>
        <P>(b) Upon receipt of a request, the PA Coordinator shall refer the request to those components most likely to possess responsive records. The components shall search all relevant record systems within their cognizance and shall:</P>
        <P>(1) Determine whether a responsive record exists in a system of records.</P>
        <P>(2) Determine whether access must be denied and on what legal basis. An individual may be denied access to his records under the Privacy Act only if an exemption has been properly claimed for all or part of the records or information requested; or if the information was compiled in reasonable anticipation of a civil action or proceeding.</P>
        <P>(3) Approve the disclosure of records for which they are the originator.</P>
        <P>(4) Forward to the PA Coordinator all records approved for release or necessary for coordination with or referral to another originator or interested party as well as notification of the specific determination for any denial.</P>

        <P>(c) When all records have been collected, the PA Coordinator shall notify <PRTPAGE P="971"/>the individual of the determination and shall provide an exact copy of records deemed to be accessible if a copy has been requested.</P>
        <P>(d) When an original record is illegible, incomplete, or partially exempt from release, the PA Coordinator shall explain in terms understood by the requester the portions of a record that are unclear.</P>
        <P>(e) If access to requested records, or any portion thereof, is denied, the PA Coordinator shall inform the requester in writing of the specific reason(s) for denial, including the specific citation to appropriate sections of the Privacy Act or other statutes, this and other NRO regulations, or the Code of Federal Regulations authorizing denial, and the right to appeal this determination through the NRO appeal procedure within 60 calendar days. The denial shall include the date of denial, the name and title/position of the denial authority, and the address of the NRO Appeal Authority. Access may be refused when the records are exempt by the Privacy Act. Usually an individual will not be denied access to the entire record, but only to those portions to which the denial of access furthers the purpose for which an exemption was claimed.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 326.10</SECTNO>
        <SUBJECT>Procedures to appeal denial of access to requested record.</SUBJECT>
        <P>(a) Any individual whose request for access is denied may request a review of the initial decision within 60 calendar days of the date of the notification of denial of access by appealing within the NRO internal appeals process. If a requester elects to request NRO review, the request shall be sent in writing to the Privacy Act Coordinator, National Reconnaissance Office, 14675 Lee Road, Chantilly, VA 20151-1715, briefly identifying the particular record which is the subject of the request and setting forth the reasons for the appeal. The request should enclose a copy of the denial correspondence. The following procedures apply to appeals within the NRO:</P>
        <P>(1) The PA Coordinator, after acknowledging receipt of the appeal, shall promptly refer the appeal to the record-holding components, informing them of the date of receipt of the appeal and requesting that the component head or his designee review the appeal.</P>
        <P>(2) The record-holding components shall review the initial denial of access to the requested records and shall inform the PA Coordinator of their review determination.</P>
        <P>(3) The PA Coordinator shall consolidate the component responses, review the record, direct such additional inquiry or investigation as is deemed necessary to make a fair and equitable determination, and make a recommendation to the NRO Appeals Panel, which makes a recommendation to the Appeal Authority.</P>
        <P>(4) The Appeal Authority shall notify the PA Coordinator of the result of the determination on the appeal, who shall notify the individual of the determination in writing.</P>
        <P>(5) If the determination reverses the initial denial, the PA Coordinator shall provide a copy of the records requested. If the determination upholds the initial denial, the PA Coordinator shall inform the requester of his right to judicial review in U.S. District Court and shall include the exact reasons for denial with specific citations to the provisions of the Privacy Act, other statutes, NRO regulations, or the Code of Federal Regulations upon which the determination is based.</P>
        <P>(b) The Appeal Authority shall act on the appeal or provide a notice of extension within 30 working days.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 326.11</SECTNO>
        <SUBJECT>Special procedures for disclosure of medical and psychological records.</SUBJECT>

        <P>When requested medical and psychological records are not exempt from disclosure, the PA Coordinator may determine which non-exempt medical or psychological records should not be sent directly to the requester because of possible harm or adverse impact to the requester or another person. In that event, the information may be disclosed to a physician named by the requester. The appointment of the physician will be in the same notarized form or declaration as described in § 326.8 and will certify that the physician is licensed to practice in the appropriate specialty (medicine, psychology, or psychiatry). Upon designation, <PRTPAGE P="972"/>verification of the physician's identity, and agreement by the physician to review the documents with the requester to explain the meaning of the documents and to offer counseling designed to mitigate any adverse reaction, the NRO will forward such records to the designated physician. If the requester refuses or fails to designate a physician, the record shall not be provided. Under such circumstances refusal of access is not considered a denial for Privacy Act reporting purposes. However, if the designated physician declines to furnish the records to the individual, the PA Coordinator will take action to ensure that the records are provided to the individual.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 326.12</SECTNO>
        <SUBJECT>Procedures to request amendment or correction of record.</SUBJECT>
        <P>(a) An individual may request amendment or correction of a record pertaining to him/her by addressing such request in writing, to the Privacy Act Coordinator, National Reconnaissance Office, 14675 Lee Road, Chantilly, VA 20151-1715. Incomplete or inaccurate requests will not be rejected categorically; instead, the requester will be asked to clarify the request as needed. A request will not be rejected or require resubmission unless additional information is essential to process the request. Usually, amendments under this part are limited to correcting factual errors and not matters of official judgment, such as promotion ratings and job performance appraisals. The requester must adequately support his claim and must identify:</P>
        <P>(1) The particular record he wishes to amend or correct, specifying the number of pages and documents, the titles of the documents, form numbers if any, dates on documents, and individuals who signed them. Any reasonable description of the documents is acceptable. A clear and specific description of passages, pages, or documents to be amended will expedite processing the request.</P>
        <P>(2) The desired amending language. The requester should specify the type of amendment, including complete removal of data, passages, or documents from record or correction of information to make it accurate, more timely, complete, or relevant.</P>
        <P>(3) A justification for such amendment or correctionto include any documentary evidence supporting the request.</P>
        <P>(b) Individuals will be required to provide verification of identity as in § 326.8. to ensure that the requester is seeking to amend records pertaining to himself and not, inadvertently or intentionally, the records of another individual.</P>
        <P>(c) Minor factual errors in an individual's personal record may be corrected routinely upon request without resort to the Privacy Act or the provisions of this part, if the requester and the record holder agree to that procedure and the requester receives a copy of the corrected record whenever possible. A written request is not required when individuals indicate amendments during routine annual review and updating of records programs conducted by the NRO for civilian personnel and the Services for military personnel. Requests for deletion, removal of records, and amendment of substantive factual information will be processed according to the Privacy Act and the provisions of this part.</P>
        <P>(d) The PA Coordinator shall acknowledge receipt of the request in writing within ten working days. No separate acknowledgement of receipt is necessary if the request can be either approved or denied and the requester advised within the ten-day period. For written requests presented in person, written acknowledgement may be provided at the time the request is presented.</P>
        <P>(e) The PA Coordinator shall refer such request to the record-holder components, shall advise those components of the date of receipt, and shall request that those components make a prompt determination on such request.</P>
        <P>(f) The record-holder components shall promptly:</P>

        <P>(1) Make any amendment or correction to any portion of the record which the individual believes is not accurate, relevant, timely, or complete and notify the PA Coordinator and all holders and recipients of such records and their amendments that the correction was made; or<PRTPAGE P="973"/>
        </P>
        <P>(2) Set forth the reasons for the refusal, if they determine that the requested amendment or correction will not be made or if they decline to make the requested amendment but instead augment the official record, and so inform the PA Coordinator.</P>
        <P>(g) The Privacy Act Coordinator shall:</P>
        <P>(1) Inform the requester of the agency's determination to make the amendment or correction as requested and notify all prior recipients of the change to the disputed records for which an accounting had been required; or</P>
        <P>(2) Inform the requester of the specific reasons and legal authorities for the agency's refusal and the procedures established for him to request a review of that refusal.</P>
        <P>(h) The amendment procedure is not intended to replace other existing procedures such as those for registering grievances or appealing performance appraisal reports. In such cases the requester will be apprised of the appropriate procedures for such actions.</P>
        <P>(i) This part does not permit the alteration of evidence presented to courts, boards, or other official proceedings.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 326.13</SECTNO>
        <SUBJECT>Procedures to appeal denial of amendment.</SUBJECT>
        <P>(a) Any individual whose request for amendment or correction is denied may request a review of the initial decision within 60 calendar days of the date of the notification of denial by appealing within the NRO internal appeals process. If a requester elects to request NRO review, the request shall be sent in writing to the Privacy Act Coordinator, National Reconnaissance Office, 14675 Lee Road, Chantilly, VA 20151-1715, briefly identifying the particular record which is the subject of the request and setting forth the reasons for the appeal. The request should enclose a copy of the denial correspondence. The following procedures apply to appeals within the NRO:</P>
        <P>(1) The PA Coordinator, after acknowledging receipt of the appeal, shall promptly refer the appeal to the record-holding components, informing them of the date of receipt of the appeal and requesting that the component head or his designee review the appeal.</P>
        <P>(2) The record-holding components shall review the initial denial of access to the requested records and shall inform the PA Coordinator of their review determination.</P>
        <P>(3) The PA Coordinator shall act as secretary of the Appeals Panel. He shall:</P>
        <P>(i) Consolidate the component responses and reasons for the initial denial.</P>
        <P>(ii) Provide all supporting materials both furnished to and by the requester and the record-holding component.</P>
        <P>(iii) Review the record.</P>
        <P>(iv) Direct such additional inquiry or investigation as is deemed necessary to make a fair and equitable determination.</P>
        <P>(v) Prepare the record and schedule the appeal for the next meeting of the Appeals Panel. The Appeals Panel shall recommend a finding to the Appeal Authority by a majority vote of those present at the meeting based on the written record and the Panel's deliberations. No personal appearances shall be permitted without the express permission of the Panel.</P>
        <P>(4) The Appeal Authority shall notify the PA Coordinator of the result of the determination on the appeal who shall notify the individual of the determination in writing.</P>
        <P>(5) The Appeal Authority will notify the PA Coordinator if the determination is that the record should be amended. The PA Coordinator will promptly advise the requester and the office holding the record to amend the record and to notify all prior recipients of the records for which an accounting was required of the change.</P>
        <P>(6) If the determination upholds the initial denial, in whole or in part, the PA Coordinator shall inform the requester:</P>
        <P>(i) Of the denial and the reason.</P>

        <P>(ii) Of his right to file in NRO records within 60 calendar days a concise statement of the reasons for disputing the information contained in the record. If the requester elects to file a statement of disagreement, the PA Coordinator will be responsible for clearly noting any portion of the record that is disputed and for appending into the file <PRTPAGE P="974"/>the requester's statement as well as a copy of the NRO's letter to the requester denying the disputed information, if appropriate. The requester's statement and the NRO denial letter will be made available to anyone to whom the record is subsequently disclosed, and prior recipients of the disputed record will be provided a copy of both to the extent that an accounting of disclosures is maintained.</P>
        <P>(iii) Of his right to judicial review in U.S. District Court.</P>
        <P>(7) The Appeal Authority shall act on the appeal or provide a notice of extension within 30 working days.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 326.14</SECTNO>
        <SUBJECT>Disclosure of records to person other than subject.</SUBJECT>
        <P>(a) Personal records contained in a Privacy Act system of records maintained by NRO shall not be disclosed by any means to any person or agency outside the NRO except with the written consent of the individual subject of the record, unless as provided in this part.</P>
        <P>(b) Except for disclosure made to members of the NRO in connection with their official duties and disclosures required by the Freedom of Information Act, an accounting will be kept of all disclosures of records maintained in NRO systems of records and of all disclosures of investigative information. Accounting entries will record the date, kind of information, purpose of each disclosure, and the name and address of the person or agency to whom the disclosure is made. Accounting records will be maintained for at least five years after the last disclosure or for the life of the record, whichever is longer. Subjects of NRO records will be given access to associated accounting records upon request except for disclosures made pursuant to § 326.4, or where an exemption has been properly claimed for the system of records.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 326.15</SECTNO>
        <SUBJECT>Fees.</SUBJECT>
        <P>Individuals requesting copies of their official personnel records are entitled to one free copy; a charge will be assessed for additional copies. There is a cost of $.15 per page. Fees will not be assessed if the cost is less than $30.00. Fees should be paid by check or postal money order payable to the Treasurer of the United States and forwarded to the Privacy Act Coordinator, NRO, at the time the copy of the record is delivered. In some instances, fees will be due in advance.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 326.16</SECTNO>
        <SUBJECT>Penalties.</SUBJECT>
        <P>Each request shall be treated as a certification by the requester that he is the individual named in the request. The Privacy Act provides criminal penalties for any person who knowingly and willfully requests or obtains any information concerning an individual under false pretenses.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 326.17</SECTNO>
        <SUBJECT>Exemptions.</SUBJECT>
        <P>(a) All systems of records maintained by the NRO shall be exempt from the requirements of 5 U.S.C. 552a(d) pursuant to 5 U.S.C. 552a(k)(1) to the extent that the system contains any information properly classified under Executive Order 12958 and which is required by the Executive Order to be withheld in the interest of national defense of foreign policy. This exemption, which may be applicable to parts of all systems of records, is necessary because certain record systems not otherwise specifically designated for exemptions herein may contain items of information that have been properly classified.</P>

        <P>(b) No system of records within the NRO shall be considered exempt under subsection (j) or (k) of the Privacy Act until the exemption and the exemption rule for the system of records has been published as a final rule in the <E T="04">Federal Register</E>.</P>
        <P>(c) An individual is not entitled to have access to any information compiled in reasonable anticipation of a civil action or proceeding (5 U.S.C. 552a(d)(5)).</P>
        <P>(d) Proposals to exempt a system of records will be forwarded to the Defense Privacy Office, consistent with the requirements of 32 CFR part 310, for review and action.</P>
        <P>(e) QNRO-23.</P>
        <P>(1) <E T="03">System name:</E> Counterintelligence Issue Files.</P>
        <P>(2) <E T="03">Exemptions:</E> (i) Investigatory material compiled for law enforcement purposes may be exempt pursuant to 5 U.S.C. 552a(k)(2). However, if an individual is denied any right, privilege, or benefit for which he would otherwise be <PRTPAGE P="975"/>entitled by Federal law or for which he would otherwise be eligible, as a result of the maintenance of such information, the individual will be provided access to such information except to the extent that disclosure would reveal the identity of a confidential source.</P>
        <P>(ii) Investigatory material compiled solely for the purpose of determining suitability, eligibility, or qualifications for federal civilian employment, military service, federal contracts, or access to classified information may be exempt pursuant to 5 U.S.C. 552a(k)(5), but only to the extent that such material would reveal the identity of a confidential source.</P>
        <P>(iii) Therefore, portions of this system of records may be exempt pursuant to 5 U.S.C. 552a(k)(2) and/or (k)(5) from the following subsections of 5 U.S.C. 552a(c)(3), (d), (e)(1), (e)(4)(G), (H) and (I), and (f).</P>
        <P>(3) <E T="03">Authority:</E> 5 U.S.C. 552a(k)(2) and (k)(5).</P>
        <P>(4) <E T="03">Reasons:</E> (i) From subsection (c)(3) because to grant access to the accounting for each disclosure as required by the Privacy Act, including the date, nature, and purpose of each disclosure and the identity of the recipient, could alert the subject to the identity of the recipient, could alert the subject to the existence of the investigation or prosecutable interest by NRO or other agencies. This could seriously compromise case preparation by prematurely revealing its existence and nature; compromise or interfere with witnesses or make witnesses reluctant to cooperate; and lead to suppression, alteration, or destruction of evidence.</P>
        <P>(ii) From subsections (d)(1) through (d)(4), and (f) because providing access to records of a civil or administrative investigation and the right to contest the contents of those records and force changes to be made to the information contained therein would seriously interfere with and thwart the orderly and unbiased conduct of the investigation and impede case preparation. Providing access rights normally afforded under the Privacy Act would provide the subject with valuable information that would allow interference with or compromise of witnesses or render witnesses reluctant to cooperate; lead to suppression, alteration, or destruction of evidence; enable individuals to conceal their wrongdoing or mislead the course of the investigation; and result in the secreting of or other disposition of assets that would make them difficult or impossible to reach in order to satisfy any Government claim growing out of the investigation or proceeding.</P>
        <P>(iii) From subsection (e)(1) because it is not always possible to detect the relevance or necessity of each piece of information in the early stages of an investigation. In some cases, it is only after the information is evaluated in light of other evidence that its relevance and necessity will be clear.</P>
        <P>(iv) From subsections (e)(4)(G) and (H) because this system of records is compiled for law enforcement purposes and is exempt from the access provisions of subsections (d) and (f).</P>
        <P>(v) From subsection (e)(4)(I) because to the extent that this provision is construed to require more detailed disclosure than the broad, generic information currently published in the system notice, an exemption from this provision is necessary to protect the confidentiality of sources of information and to protect privacy and physical safety of witnesses and informants. NRO will, nevertheless, continue to publish such a notice in broad generic terms as is its current practice.</P>

        <P>(vi) Consistent with the legislative purpose of the Privacy Act of 1974, the NRO will grant access to nonexempt material in the records being maintained. Disclosure will be governed by NRO's Privacy Regulation, but will be limited to the extent that the identity of confidential sources will not be compromised; subjects of an investigation of an actual or potential criminal violation will not be alerted to the investigation; the physical safety of witnesses, informants and law enforcement personnel will not be endangered, the privacy of third parties will not be violated; and that the disclosure would not otherwise impede effective law enforcement. Whenever possible, information of the above nature will be deleted from the requested documents and the balance made available. The controlling principle behind this limited access is to allow disclosures except those indicated above. The decisions to <PRTPAGE P="976"/>release information from these systems will be made on a case-by-case basis.</P>
        <P>(f) <E T="03">QNRO-10, Inspector General Investigative Files—</E>(1) Exemption: This system may be exempt pursuant to 5 U.S.C. 552a(j)(2) if the information is compiled and maintained by a component of the agency which performs as its principle function any activity pertaining to the enforcement of criminal laws. Any portion of this system which falls within the provisions of 5 U.S.C. 552a(j)(2) may be exempt from the following subsections of 5 U.S.C. 552a (c)(3), (c)(4), (d), (e)(1), (e)(2), (e)(3), (e)(4)(G), (H), and (I), (e)(5), (e)(8), (f), and (g).</P>
        <P>(2) <E T="03">Authority:</E> 5 U.S.C. 552a(j)(2).</P>
        <P>(3) <E T="03">Reasons.</E> (i) From subsection (c)(3) because the release of accounting of disclosure would inform a subject that he or she is under investigation. This information would provide considerable advantage to the subject in providing him or her with knowledge concerning the nature of the investigation and the coordinated investigative efforts and techniques employed by the cooperating agencies. This would greatly impede the NRO IG's criminal law enforcement.</P>
        <P>(ii) From subsection (c)(4) and (d), because notification would alert a subject to the fact that an open investigation on that individual is taking place, and might weaken the on-going investigation, reveal investigative techniques, and place confidential informants in jeopardy.</P>
        <P>(iii) From subsection (e)(1) because the nature of the criminal and/or civil investigative function creates unique problems in prescribing a specific parameter in a particular case with respect to what information is relevant or necessary. Also, due to NRO IG's close liaison and working relationships with other Federal, state, local and foreign country law enforcement agencies, information may be received which may relate to a case under the investigative jurisdiction of another agency. The maintenance of this information may be necessary to provide leads for appropriate law enforcement purposes and to establish patterns of activity, which may relate to the jurisdiction of other cooperating agencies.</P>
        <P>(iv) From subsection (e)(2) because collecting information to the fullest extent possible directly from the subject individual may or may not be practical in a criminal and/or civil investigation.</P>
        <P>(v) From subsection (e)(3) because supplying an individual with a form containing a Privacy Act Statement would tend to inhibit cooperation by many individuals involved in a criminal and/or civil investigation. The effect would be somewhat adverse to established investigative methods and techniques.</P>
        <P>(vi) From subsection (e)(4) (G) through (I) because this system of records is exempt from the access provisions of subsection (d).</P>
        <P>(vii) From subsection (e)(5) because the requirement that records be maintained with attention to accuracy, relevance, timeliness, and completeness would unfairly hamper the investigative process. It is the nature of law enforcement for investigations to uncover the commission of illegal acts at diverse stages. It is frequently impossible to determine initially what information is accurate, relevant, timely, and least of all complete. With the passage of time, seemingly irrelevant or untimely information may acquire new significance as further investigation brings new details to light.</P>
        <P>(viii) From subsection (e)(8) because the notice requirements of this provision could present a serious impediment to law enforcement by revealing investigative techniques, procedures, and existence of confidential investigations.</P>

        <P>(ix) From subsection (f) because the agency's rules are inapplicable to those portions of the system that are exempt and would place the burden on the agency of either confirming or denying the existence of a record pertaining to a requesting individual might in itself provide an answer to that individual relating to an on-going investigation. The conduct of a successful investigation leading to the indictment of a criminal offender precludes the applicability of established agency rules relating to verification of record, disclosure of the record to that individual, and record amendment procedures for this record system.<PRTPAGE P="977"/>
        </P>
        <P>(x) From subsection (g) because this system of records should be exempt to the extent that the civil remedies relate to provisions of 5 U.S.C. 552a from which this rule exempts the system.</P>
        <P>(4) <E T="03">Exemptions.</E> (i) Investigative material compiled for law enforcement purposes, other than material within the scope of subsection (j)(2), may be exempt pursuant to 5 U.S.C. 552a(k)(2). However, if an individual is denied any right, privilege, or benefit for which he would otherwise be entitled by Federal law or for which he would otherwise be eligible, as a result of the maintenance of such information, the individual will be provided access to such information except to the extent that disclosure would reveal the identity of a confidential source.</P>
        <P>(ii) Investigative material compiled solely for the purpose of determining suitability, eligibility, or qualifications for federal civilian employment, military service, federal contracts, or access to classified information may be exempt pursuant to 5 U.S.C. 552a(k)(5), but only to the extent that such material would reveal the identity of a confidential source.</P>
        <P>(iii) Therefore, portions of this system of records may be exempt pursuant to 5 U.S.C. 552a(k)(2) and/or (k)(5) from the following subsections of 5 U.S.C. 552a(c)(3), (d), (e)(1), (e)(4)(G), (H) and (I), and (f).</P>
        <P>(5) <E T="03">Authority.</E> 5 U.S.C. 552a(k)(2) and (k)(5).</P>
        <P>(6) <E T="03">Reasons.</E> (i) From subsection (c)(3) because to grant access to the accounting for each disclosure as required by the Privacy Act, including the date, nature, and purpose of each disclosure and the identity of the recipient, could alert the subject to the existence of the investigation or prosecutable interest by the NRO or other agencies. This could seriously compromise case preparation by prematurely revealing its existence and nature; compromise or interfere with witnesses or make witnesses reluctant to cooperate; and lead to suppression, alteration, or destruction of evidence.</P>
        <P>(ii) From subsections (d) and (f) because providing access to investigative records and the right to contest the contents of those records and force changes to be made to the information contained therein would seriously interfere with and thwart the orderly and unbiased conduct of the investigation and impede case preparation. Providing access rights normally afforded under the Privacy Act would provide the subject with valuable information that would allow interference with or compromise of witnesses or render witnesses reluctant to cooperate; lead to suppression, alteration, or destruction of evidence; enable individuals to conceal their wrongdoing or mislead the course of the investigation; and result in the secreting of or other disposition of assets that would make them difficult or impossible to reach in order to satisfy any Government claim growing out of the investigation or proceeding.</P>
        <P>(iii) From subsection (e)(1) because it is not always possible to detect the relevance or necessity of each piece of information in the early stages of an investigation. In some cases, it is only after the information is evaluated in light of other evidence that its relevance and necessity will be clear.</P>
        <P>(iv) From subsections (e)(4)(G) and (H) because this system of records is compiled for investigative purposes and is exempt from the access provisions of subsections (d) and (f).</P>
        <P>(v) From subsection (e)(4)(I) because to the extent that this provision is construed to require more detailed disclosure than the broad, generic information currently published in the system notice, an exemption from this provision is necessary to protect the confidentiality of sources of information and to protect privacy and physical safety of witnesses and informants. NRO will, nevertheless, continue to publish such a notice in broad generic terms as is its current practice.</P>

        <P>(vi) Consistent with the legislative purpose of the Privacy Act of 1974, the NRO will grant access to nonexempt material in the records being maintained. Disclosure will be governed by NRO's Privacy Regulation, but will be limited to the extent that the identity of confidential sources will not be compromised; subjects of an investigation of an actual or potential criminal or civil violation will not be alerted to the investigation; the physical safety <PRTPAGE P="978"/>of witnesses, informants and law enforcement personnel will not be endangered, the privacy of third parties will not be violated; and that the disclosure would not otherwise impede effective law enforcement. Whenever possible, information of the above nature will be deleted from the requested documents and the balance made available. The controlling principle behind this limited access is to allow disclosures except those indicated above. The decisions to release information from these systems will be made on a case-by-case basis.</P>
        <P>(g) QNRO-15, Facility Security Files.</P>
        <P>(1) <E T="03">Exemptions.</E> (i) Investigative material compiled for law enforcement purposes may be exempt pursuant to 5 U.S.C. 552a(k)(2). However, if an individual is denied any right, privilege, or benefit for which he would otherwise be entitled by Federal law or for which he would otherwise be eligible, as a result of the maintenance of such information, the individual will be provided access to such information except to the extent that disclosure would reveal the identity of a confidential source.</P>
        <P>(ii) Investigative material compiled solely for the purpose of determining suitability, eligibility, or qualifications for federal civilian employment, military service, federal contracts, or access to classified information may be exempt pursuant to 5 U.S.C. 552a(k)(5), but only to the extent that such material would reveal the identity of a confidential source.</P>
        <P>(iii) Therefore, portions of this system of records may be exempt pursuant to 5 U.S.C. 552a(k)(2) and/or (k)(5) from the following subsections of 5 U.S.C. 552a(c)(3), (d), (e)(1), (e)(4)(G), (H) and (I), and (f).</P>
        <P>(2) <E T="03">Authority.</E> 5 U.S.C. 552a(k)(2) and (k)(5).</P>
        <P>(3) <E T="03">Reasons.</E> (i) From subsection (c)(3) because to grant access to the accounting for each disclosure as required by the Privacy Act, including the date, nature, and purpose of each disclosure and the identity of the recipient, could alert the subject to the existence of the investigation or prosecutable interest by the NRO or other agencies. This could seriously compromise case preparation by prematurely revealing its existence and nature; compromise or interfere with witnesses or make witnesses reluctant to cooperate; and lead to suppression, alteration, or destruction of evidence.</P>
        <P>(ii) From subsections (d)(1) through (d)(4), and (f) because providing access to investigative records and the right to contest the contents of those records and force changes to be made to the information contained therein would seriously interfere with and thwart the orderly and unbiased conduct of the investigation and impede case preparation. Providing access rights normally afforded under the Privacy Act would provide the subject with valuable information that would allow interference with or compromise of witnesses or render witnesses reluctant to cooperate; lead to suppression, alteration, or destruction of evidence; enable individuals to conceal their wrongdoing or mislead the course of the investigation; and result in the secreting of or other disposition of assets that would make them difficult or impossible to reach in order to satisfy any Government claim growing out of the investigation or proceeding.</P>
        <P>(iii) From subsection (e)(1) because it is not always possible to detect the relevance or necessity of each piece of information in the early stages of an investigation. In some cases, it is only after the information is evaluated in light of other evidence that its relevance and necessity will be clear.</P>
        <P>(iv) From subsections (e)(4)(G) and (H) because this system of records is compiled for investigative purposes and is exempt from the access provisions of subsections (d) and (f).</P>
        <P>(v) From subsection (e)(4)(I) because to the extent that this provision is construed to require more detailed disclosure than the broad, generic information currently published in the system notice, an exemption from this provision is necessary to protect the confidentiality of sources of information and to protect privacy and physical safety of witnesses and informants. NRO will, nevertheless, continue to publish such a notice in broad generic terms as is its current practice.</P>

        <P>(vi) Consistent with the legislative purpose of the Privacy Act of 1974, the NRO will grant access to nonexempt <PRTPAGE P="979"/>material in the records being maintained. Disclosure will be governed by NRO's Privacy Regulation, but will be limited to the extent that the identity of confidential sources will not be compromised; subjects of an investigation of an actual or potential criminal or civil violation will not be alerted to the investigation; the physical safety of witnesses, informants and law enforcement personnel will not be endangered; the privacy of third parties will not be violated; and that the disclosure would not otherwise impede effective law enforcement. Whenever possible, information of the above nature will be deleted from the requested documents and the balance made available. The controlling principle behind this limited access is to allow disclosures except those indicated above. The decisions to release information from these systems will be made on a case-by-case basis.</P>
        <P>(h) QNRO-19.</P>
        <P>(1) <E T="03">System name:</E> Customer Security Services Personnel Security Files.</P>
        <P>(2) <E T="03">Exemptions:</E> (i) Investigatory material compiled for law enforcement purposes may be exempt pursuant to 5 U.S.C. 552a(k)(2). However, if an individual is denied any right, privilege, or benefit for which he would otherwise be entitled by Federal law or for which he would otherwise be eligible, as a result of the maintenance of such information, the individual will be provided access to such information except to the extent that disclosure would reveal the identity of a confidential source.</P>
        <P>(ii) Investigatory material compiled solely for the purpose of determining suitability, eligibility, or qualifications for federal civilian employment, military service, federal contracts, or access to classified information may be exempt pursuant to 5 U.S.C. 552a(k)(5), but only to the extent that such material would reveal the identity of a confidential source.</P>
        <P>(iii) Therefore, portions of this system of records may be exempt pursuant to 5 U.S.C. 552a(k)(2) and/or (k)(5) from the following subsections of 5 U.S.C. 552a(c)(3), (d), (e)(1), (e)(4)(G), (H) and (I), and (f).</P>
        <P>(3) <E T="03">Authority:</E> 5 U.S.C. 552a(k)(2) and (k)(5).</P>
        <P>(4) <E T="03">Reasons:</E> (i) From subsection (c)(3) because to grant access to the accounting for each disclosure as required by the Privacy Act, including the date, nature, and purpose of each disclosure and the identity of the recipient, could alert the subject to the existence of the investigation or prosecutable interest by the NRO or other agencies. This could seriously compromise case preparation by prematurely revealing its existence and nature; compromise or interfere with witnesses or make witnesses reluctant to cooperate; and lead to suppression, alteration, or destruction of evidence.</P>
        <P>(ii) From subsections (d)(1) through (d)(4), and (f) because providing access to investigatory records and the right to contest the contents of those records and force changes to be made to the information contained therein would seriously interfere with and thwart the orderly and unbiased conduct of the investigation and impede case preparation. Providing access rights normally afforded under the Privacy Act would provide the subject with valuable information that would allow interference with or compromise of witnesses or render witnesses reluctant to cooperate; lead to suppression, alteration, or destruction of evidence; enable individuals to conceal their wrongdoing or mislead the course of the investigation; and result in the secreting of or other disposition of assets that would make them difficult or impossible to reach in order to satisfy any Government claim growing out of the investigation or proceeding.</P>
        <P>(iii) From subsection (e)(1) because it is not always possible to detect the relevance or necessity of each piece of information in the early stages of an investigation. In some cases, it is only after the information is evaluated in light of other evidence that its relevance and necessity will be clear.</P>
        <P>(iv) From subsections (e)(4)(G) and (H) because this system of records is compiled for investigatory purposes and is exempt from the access provisions of subsections (d) and (f).</P>

        <P>(v) From subsection (e)(4)(I) because to the extent that this provision is construed to require more detailed disclosure than the broad, generic information currently published in the system <PRTPAGE P="980"/>notice, an exemption from this provision is necessary to protect the confidentiality of sources of information and to protect privacy and physical safety of witnesses and informants. NRO will, nevertheless, continue to publish such a notice in broad generic terms as is its current practice.</P>
        <P>(vi) Consistent with the legislative purpose of the Privacy Act of 1974, the NRO will grant access to nonexempt material in the records being maintained. Disclosure will be governed by NRO's Privacy Regulation, but will be limited to the extent that the identity of confidential sources will not be compromised; subjects of an investigation of an actual or potential criminal or civil violation will not be alerted to the investigation; the physical safety of witnesses, informants and law enforcement personnel will not be endangered; the privacy of third parties will not be violated; and that the disclosure would not otherwise impede effective law enforcement. Whenever possible, information of the above nature will be deleted from the requested documents and the balance made available. The controlling principle behind this limited access is to allow disclosures except those indicated in this paragraph. The decisions to release information from these systems will be made on a case-by-case basis.</P>
        <P>(i) NRO-21.</P>
        <P>(1) <E T="03">System name:</E> Personnel Security Files.</P>
        <P>(2) <E T="03">Exemptions:</E> (i) Investigatory material compiled for law enforcement purposes may be exempt pursuant to 5 U.S.C. 552a(k)(2). However, if an individual is denied any right, privilege, or benefit for which he would otherwise be entitled by Federal law or for which he would otherwise be eligible, as a result of the maintenance of such information, the individual will be provided access to such information except to the extent that disclosure would reveal the identity of a confidential source.</P>
        <P>(ii) Investigatory material compiled solely for the purpose of determining suitability, eligibility, or qualifications for federal civilian employment, military service, federal contracts, or access to classified information may be exempt pursuant to 5 U.S.C. 552a(k)(5), but only to the extent that such material would reveal the identity of a confidential source.</P>
        <P>(iii) Therefore, portions of this system of records may be exempt pursuant to 5 U.S.C. 552a(k)(2) and/or (k)(5) from the following subsections of 5 U.S.C. 552a(c)(3), (d), (e)(1), (e)(4)(G), (H) and (I), and (f).</P>
        <P>(3) <E T="03">Authority:</E> 5 U.S.C. 552a(k)(2) and (k)(5).</P>
        <P>(4) <E T="03">Reasons:</E> (i) From subsection (c)(3) because to grant access to the accounting for each disclosure as required by the Privacy Act, including the date, nature, and purpose of each disclosure and the identity of the recipient, could alert the subject to the existence of the investigation or prosecutable interest by the NRO or other agencies. This could seriously compromise case preparation by prematurely revealing its existence and nature; compromise or interfere with witnesses or make witnesses reluctant to cooperate; and lead to suppression, alteration, or destruction of evidence.</P>
        <P>(ii) From subsections (d)(1) through (d)(4), and (f) because providing access to records of a civil or administrative investigation and the right to contest the contents of those records and force changes to be made to the information contained therein would seriously interfere with and thwart the orderly and unbiased conduct of the investigation and impede case preparation. Providing access rights normally afforded under the Privacy Act would provide the subject with valuable information that would allow interference with or compromise of witnesses or render witnesses reluctant to cooperate; lead to suppression, alteration, or destruction of evidence; enable individuals to conceal their wrongdoing or mislead the course of the investigation; and result in the secreting of or other disposition of assets that would make them difficult or impossible to reach in order to satisfy any Government claim growing out of the investigation or proceeding.</P>

        <P>(iii) From subsection (e)(1) because it is not always possible to detect the relevance or necessity of each piece of information in the early stages of an investigation. In some cases, it is only after the information is evaluated in light of other evidence that its relevance and necessity will be clear.<PRTPAGE P="981"/>
        </P>
        <P>(iv) From subsections (e)(4)(G) and (H) because this system of records is compiled for law enforcement purposes and is exempt from the access provisions of subsections (d) and (f).</P>
        <P>(v) From subsection (e)(4)(I) because to the extent that this provision is construed to require more detailed disclosure than the broad, generic information currently published in the system notice, an exemption from this provision is necessary to protect the confidentiality of sources of information and to protect privacy and physical safety of witnesses and informants. NRO will, nevertheless, continue to publish such a notice in broad generic terms as is its current practice.</P>
        <P>(vi) Consistent with the legislative purpose of the Privacy Act of 1974, the NRO will grant access to nonexempt material in the records being maintained. Disclosure will be governed by NRO's Privacy Regulation, but will be limited to the extent that the identity of confidential sources will not be compromised; subjects of an investigation of an actual or potential criminal violation will not be alerted to the investigation; the physical safety of witnesses, informants and law enforcement personnel will not be endangered; the privacy of third parties will not be violated; and that the disclosure would not otherwise impede effective law enforcement. Whenever possible, information of the above nature will be deleted from the requested documents and the balance made available. The controlling principle behind this limited access is to allow disclosures except those indicated above. The decisions to release information from these systems will be made on a case-by-case basis.</P>
        <P>(j) QNRO-4.</P>
        <P>(1) <E T="03">System name:</E> Freedom of Information Act and Privacy Act Files.</P>
        <P>(2) <E T="03">Exemption:</E> During the processing of a Freedom of Information Act/Privacy Act request, exempt materials from other systems of records may in turn become part of the case record in this system. To the extent that copies of exempt records from those “other” systems of records are entered into this system, the NRO hereby claims the same exemptions for the records from those “other” systems that are entered into this system, as claimed for the original primary system of which they are a part.</P>
        <P>(3) Authority: 5 U.S.C. 552a(j)(2), (k)(1), (k)(2), (k)(3), (k)(4), (k)(5), (k)(6), and (k)(7).</P>
        <P>(4) Records are only exempt from pertinent provisions of 5 U.S.C. 552a to the extent such provisions have been identified and an exemption claimed for the original record and the purposes underlying the exemption for the original record still pertain to the record which is now contained in this system of records. In general, the exemptions were claimed in order to protect properly classified information relating to national defense and foreign policy, to avoid interference during the conduct of criminal, civil, or administrative actions or investigations, to ensure protective services provided the President and others are not compromised, to protect the identity of confidential sources incident to Federal employment, military service, contract, and security clearance determinations, and to preserve the confidentiality and integrity of Federal evaluation materials. The exemption rule for the original records will identify the specific reasons why the records are exempt from specific provisions of 5 U.S.C. 552a.</P>
        <CITA>[65 FR 20372, Apr. 17, 2000, as amended at 66 FR 41783, Aug. 9, 2001; 66 FR 54926, Oct. 31, 2001; 67 FR 17616, Apr. 11, 2002]</CITA>
      </SECTION>
    </PART>
    <PART>
      <EAR>Pt. 327</EAR>
      <HD SOURCE="HED">PART 327—DEFENSE COMMISSARY AGENCY PRIVACY ACT PROGRAM</HD>
      <CONTENTS>
        <SECHD>Sec.</SECHD>
        <SECTNO>327.1</SECTNO>
        <SUBJECT>Purpose.</SUBJECT>
        <SECTNO>327.2</SECTNO>
        <SUBJECT>Applicability.</SUBJECT>
        <SECTNO>327.3</SECTNO>
        <SUBJECT>Responsibilities.</SUBJECT>
        <SECTNO>327.4</SECTNO>
        <SUBJECT>Definitions.</SUBJECT>
        <SECTNO>327.5</SECTNO>
        <SUBJECT>Systems of records.</SUBJECT>
        <SECTNO>327.6</SECTNO>
        <SUBJECT>Collecting personal information.</SUBJECT>
        <SECTNO>327.7</SECTNO>
        <SUBJECT>Access by individuals.</SUBJECT>
        <SECTNO>327.8</SECTNO>
        <SUBJECT>Disclosure of personal information to other agencies and third parties.</SUBJECT>
        <APP>Appendix A to part 327—Sample DeCA response letter.</APP>
        <APP>Appendix B to part 327—Internal Management Control Review Checklist.</APP>
        <APP>Appendix C to part 327—DeCA Blanket Routine Uses.</APP>
      </CONTENTS>
      <AUTH>
        <HD SOURCE="HED">Authority:</HD>
        <P>Pub. L. 93-579, 88 Stat. 1896 (5 U.S.C. 522a).</P>
      </AUTH>
      <SOURCE>
        <HD SOURCE="HED">Source:</HD>
        <P>65 FR 39806, June 28, 2000, unless otherwise noted.</P>
      </SOURCE>
      <SECTION>
        <PRTPAGE P="982"/>
        <SECTNO>§ 327.1</SECTNO>
        <SUBJECT>Purpose.</SUBJECT>
        <P>This part implements the basic policies and procedures for the implementation of the Privacy Act of 1974, as amended (5 U.S.C. 552a); OMB Circular A-130; <SU>1</SU>
          <FTREF/> and 32 CFR part 310; and to promote uniformity in the DeCA Privacy Act Program.</P>
        <FTNT>
          <P>
            <SU>1</SU> Copies may be obtained: http://www.whitehouse.gov/OMB/circulars.</P>
        </FTNT>
      </SECTION>
      <SECTION>
        <SECTNO>§ 327.2</SECTNO>
        <SUBJECT>Applicability.</SUBJECT>
        <P>This part applies to Headquarters, Field Operating Activities (FOA), Regions, Zones, Central Distribution Centers (CDC), Commissaries of DeCA, and contractors during the performance of a contract with DeCA. All personnel are expected to comply with the procedures established herein.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 327.3</SECTNO>
        <SUBJECT>Responsibilities.</SUBJECT>
        <P>(a) <E T="03">The Director, DeCA.</E> (1) Supervises the execution of the Privacy Act and this part within the DeCA, and serves as the DeCA Privacy Act Appeal Authority.</P>
        <P>(2) Appoints:</P>
        <P>(i) The Executive Director for Support as the DeCA Initial Denial Authority for the DeCA Privacy Act Program.</P>
        <P>(ii) The Records Manager, Office of Safety, Security, and Administration as the DeCA Privacy Act Officer.</P>
        <P>(b) <E T="03">The Privacy Act Officer, DeCA.</E> (1) Establishes and manages the PA program for DeCA.</P>
        <P>(2) Provides guidance, assistance and training.</P>
        <P>(3) Controls and monitors all requests received and prepares documentation to the office of primary responsibility (OPR) for response.</P>
        <P>(4) Prepares response to requester based on information provided by the OPR.</P>
        <P>(5) Signs all response requests for releasable information to the requester after coordination through the General Counsel. Ensures that all denied requests for information are released by the DeCA Initial Denial Authority.</P>
        <P>(6) Publishes instructions to contractors that:</P>
        <P>(i) Provide DeCA Privacy program guidance to their personnel who solicit, award, or administer government contracts;</P>
        <P>(ii) Inform prospective contractors of their responsibilities regarding the DeCA Privacy Program; and</P>
        <P>(iii) Establish an internal system of contractor performance review to ensure compliance with DeCA's Privacy program.</P>

        <P>(iv) Prepare and submit System Notices to the Defense Privacy Office for publication in the <E T="04">Federal Register.</E>
        </P>
        <P>(7) Maintain Privacy Case files and records of disclosure accounting.</P>
        <P>(8) Submit the DeCa Annual Privacy Act Report (RCS: DD-DA&amp;M(A)1379) to the Defense Privacy Office.</P>
        <P>(c) <E T="03">DeCA Directorates/Staff Offices.</E> (1) Provide response and the information requested to the PA Officer for release to the individual.</P>
        <P>(2) In the event the information is to be denied release, the requested information and rationale for denial will be forwarded to the PA Officer for denial determination.</P>
        <P>(d) <E T="03">Regions.</E> Regional Directors will appoint a Regional PA Coordinator who will maintain suspense control of PA actions, prepare documentation to the OPR for response, forward the information to the DeCA PA Officer for release determination, and notify the requester that the response will be received from the DeCA PA Officer using the format in Appendix A to this part.</P>
        <P>(e) <E T="03">DeCA Field Operating Activities (FOAs).</E> (1) Upon receipt of a PA request that has not been received from the DeCA PA Officer, notify the DeCA PA Officer within 2 days.</P>
        <P>(2) Collect all information available and forward to the DeCA PA Officer. If the requested information is not available, provide the DeCA PA Officer the rationale to respond to the requester.</P>
        <P>(f) <E T="03">Central Distribution Centers (CDCs) and Commissaries.</E> (1) Upon receipt of a PA request, not received from the Region Coordinator, notify the Region Coordinator within 2 days.</P>

        <P>(2) Collect all information available and forward it to the Region Coordinator for submission to DeCA PA Officer. If requested information is not available, provide the Region Coordinator the rationale so they can prepare a response to the DeCA PA Officer. If <PRTPAGE P="983"/>the information is available but determined to be exempt, provide the Region Coordinator with the requested information and specific reasons why the request should be denied. The Region Coordinator will formalize a reply to the DeCA PA Officer, forwarding requested information and reasons for denial. The DeCA PA Officer will prepare the response to the requester with coordination by the General Counsel and signature by the IDA.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 327.4</SECTNO>
        <SUBJECT>Definitions.</SUBJECT>
        <P>
          <E T="03">Access.</E> The review of a record of a copy of a record or parts thereof in a system of records by any individual.</P>
        <P>
          <E T="03">Agency.</E> For the purposes of disclosing records subject to the Privacy Act among DoD Components, the Department of Defense is considered a single agency. For all other purposes to include applications for access and amendment, denial of access or amendment, appeals from denials, and record keeping as regards release to non-DoD agencies; each DoD Component is considered an agency within the meaning of the Privacy Act.</P>
        <P>
          <E T="03">Computer room.</E> Any combination of electronic hardware and software integrated in a variety of forms (firmware, programmable software, hard wiring, or similar equipment) that permits the processing of textual data. The equipment contains device to receive information and other processors with various capabilities to manipulate the information, store and provide input.</P>
        <P>
          <E T="03">Confidential source.</E> A person or organization who has furnished information to the federal government under an express promise that the person's or the organization's identity will be held in confidence or under an implied promise of such confidentiality if this implied promise was made before September 27, 1975.</P>
        <P>
          <E T="03">Disclosure.</E> The transfer of any personal information from a system of records by any means of communication (such as oral, written, electronic, mechanical, or actual review) to any person, private entity, or government agency, other than the subject of the record, the subject's designated agent or the subject's legal guardian.</P>
        <P>
          <E T="03">Federal Register system.</E> Established by Congress to inform the public of interim, proposed, and final regulations or rulemaking documents having substantial impact on the public. In this case, DeCA directives have the same meaning as regulations or rulemaking documents. The secondary role of the Federal Register system is to publish notice documents of public interest.</P>
        <P>
          <E T="03">Individual.</E> A living person who is a citizen of the United States or an alien lawfully admitted for permanent residence. The parent of a minor or the legal guardian of any individual also may act on behalf of an individual. Corporations, partnerships, sole proprietorships, professional groups, businesses, whether incorporated or unincorporated, and other commercial entities are not “individuals.”</P>
        <P>
          <E T="03">Individual access.</E> Access to information pertaining to the individual by the individual or his or her designated agent or legal guardian.</P>
        <P>
          <E T="03">Law enforcement activity.</E> Any activity engaged in the enforcement of criminal laws, including efforts to prevent, control, or reduce crime or to apprehend criminals, and the activities of prosecutors, courts, correctional, probation, pardon, or parole authorities.</P>
        <P>
          <E T="03">Maintain.</E> Includes maintain, collect, use or disseminate.</P>
        <P>
          <E T="03">Official use.</E> Within the context of this part, this term is used when officials and employees of a DoD Component have a demonstrated need for the use of any record or the information contained therein in the performance of their official duties, subject to DoD 5200.1-R,<SU>2</SU>
          <FTREF/> “DoD Information Security Program Regulation.”</P>
        <FTNT>
          <P>
            <SU>2</SU> Copies may be obtained: http//www.whs.osd.mil/corres.htm.</P>
        </FTNT>
        <P>
          <E T="03">Personal information.</E> Information about an individual that identifies, relates or is unique to, or describes him or her; <E T="03">e.g.,</E> a social security number, age, military rank, civilian grade, marital status, race, salary, home/office phone numbers, etc.</P>
        <P>
          <E T="03">Privacy Act.</E> The Privacy Act of 1974, as amended, (5 U.S.C. 552a).</P>
        <P>
          <E T="03">Privacy Act request.</E> A request from an individual for notification as to the existence of, access to, or amendment of records pertaining to that individual. These records must be maintained in a system of records.<PRTPAGE P="984"/>
        </P>
        <P>
          <E T="03">Member of the public.</E> Any individual or party acting in a private capacity to include federal employees or military personnel.</P>
        <P>
          <E T="03">Record.</E> Any item, collection, or grouping of information, whatever the storage media (<E T="03">e.g.,</E> paper, electronic, etc.), about an individual that is maintained by a DoD Component, including but not limited to, his or her education, financial transactions, medical history, criminal or employment history and that contains his or her name, or the identifying number, symbol, or other identifying particular assigned to the individual, such as a finger or voice print or a photograph.</P>
        <P>
          <E T="03">Risk assessment.</E> An analysis considering information sensitivity, vulnerabilities, and the cost to a computer facility or word processing activity in safeguarding personal information processed or stored in the facility or activity.</P>
        <P>
          <E T="03">Routine use.</E> The disclosure of a record outside the Department of Defense for a use that is compatible with the purpose for which the information was collected and maintained by the Department of Defense. The routine use must be included in the published system notice for the system of records involved.</P>
        <P>
          <E T="03">Statistical record.</E> A record maintained only for statistical research or reporting purposes and not used in whole or in part in making determinations about specific individuals.</P>
        <P>
          <E T="03">System manager.</E> The DoD Component official who is responsible for the operation and management of a system of records.</P>
        <P>
          <E T="03">System of records.</E> A group of records under the control of a DoD Component from which personal information is retrieved by the individual's name or by some identifying number, symbol, or other identifying particular assigned to an individual.</P>
        <P>
          <E T="03">Word processing system.</E> A combination of equipment employing automated technology, systematic procedures, and trained personnel for the primary purpose of manipulating human thoughts and verbal or written or graphic presentations intended to communicate verbally or visually with another individual.</P>
        <P>
          <E T="03">Word processing equipment.</E> Any combination of electronic hardware and computer software integrated in a variety of forms (firmware, programmable software, hard wiring, or similar equipment) that permits the processing of textual data. Generally, the equipment contains a device to recieve information, a computer-like processor with various capabilities to manipulate the information, a storage medium, and an output device.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 327.5</SECTNO>
        <SUBJECT>Systems of records.</SUBJECT>
        <P>(a)<E T="03"> System of records.</E> To be subject to the provisions of this part, a “system of records” must:</P>
        <P>(1) Consist of “records” that are retrieved by the name of an individual or some other personal identifier, and</P>
        <P>(2) Be under the control of DeCA.</P>
        <P>(b)<E T="03"> Retrieval practices.</E> Records in a group of records that may be retrieved by a name or personal identifier are not covered by this part even if the records contain personal data and are under the control of DeCA. The records MUST BE, in fact, retrieved by name or other personal identifier to become a system of records for DeCA.</P>
        <P>(c)<E T="03"> Relevance and necessity.</E> Only those records that contain personal information which is relevant and necessary to accomplish a purpose required by Federal statute or an Executive Order will be maintained by DeCA.</P>
        <P>(d)<E T="03"> Authority to establish systems of records.</E> Director, DeCA has the authority to establish systems of records; however, each time a system of records is established, the Executive Order or Federal statute that authorizes maintaining the personal information must be identified.</P>
        <P>(1) DeCA will not maintain any records describing how an individual exercises his or her rights guaranteed by the First Amendment of the U.S. Constitution.</P>
        <P>(2) These rights include, but are not limited to, freedom of religion, freedom of political beliefs, freedom of speech, freedom of the press, the right to assemble, and the right to petition.</P>
        <P>(e)<E T="03"> System manager's evaluation.</E> Systems managers, along with the DeCA Privacy Officer, shall evaluate the information to be included in each new system before establishing the system <PRTPAGE P="985"/>and evaluate periodically the information contained in each existing system of records for relevancy and necessity. Such a review will also occur when a system notice amendment or alteration is prepared. Consider the following:</P>
        <P>(1) The relationship of each item of information retained and collected to the purpose for which the system is maintained.</P>
        <P>(2) The specific impact on the purpose or mission of not collecting each category of information contained in the system.</P>
        <P>(3) The possibility of meeting the informational requirements through use of information not individually identifiable or through other techniques, such as sampling.</P>
        <P>(4) The length of time each item of personal information must be retained.</P>
        <P>(5) The cost of maintaining the information.</P>
        <P>(6) The necessity and relevancy of the information to the purpose for which it was collected.</P>
        <P>(f)<E T="03"> Discontinued information requirements.</E> (1) When notification is received to stop collecting any category or item of personal information, the DeCA PA Officer will issue instructions to stop immediately and also excise this information from existing records, when feasible, and amend existing notice.</P>
        <P>(2) Disposition of these records will be provided by the DeCA PA Officer in accordance with the DeCA Filing System.<SU>3</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>3</SU> Copies may be obtained: Defense Commissary Agency, ATTN: FOIA/Privacy Officer, 1300 E. Avenue, Fort Lee, VA 23801-1800.</P>
        </FTNT>
        <P>(g)<E T="03"> Government contractors.</E> (1) When DeCA contracts for the operation or maintenance of a system of records or a portion of a system of records by a contractor, the record system or the portion affected are considered to be maintained by DeCA and are subject to this part. DeCA is responsible for applying the requirements of this part to the contractor. The contractor and its employees are to be considered employees of DeCA for the purposes of the approved provisions of the Privacy Act during the performance of the contract. Consistent with the Defense Acquisition Regulation, contracts requiring the maintenance of a system of records or the portion of a system of records shall identify specifically the record system and the work to be performed and shall include in the solicitation and resulting contract such terms as are prescribed in the Defense Acquisition Regulation (DAR).<SU>4</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>4</SU> See footnote 3 to § 327.5.</P>
        </FTNT>
        <P>(2) If the contractor must use or have access to individually identifiable information subject to this part to perform any part of a contract, and the information would have been collected and maintained by DeCA but for the award of the contract, these contractor activities are subject to this part.</P>
        <P>(3) The restrictions in paragraphs (g)(1) and (g)(2) of this section do not apply to records:</P>
        <P>(i) Established and maintained to assist in making internal contractor management decisions such as those maintained for use in managing the contract.</P>
        <P>(ii) Those maintained as internal contractor employee records even when used in conjunction with providing goods and services to DeCA.</P>
        <P>(4) Disclosure of records to contractors. Disclosure of personal records to a contractor for the use in the performance of any DeCA contract is considered a disclosure within the Department of Defense (DoD). The contractor is considered the agent of DeCA and is to be maintaining and receiving the records for DeCA.</P>
        <P>(h)<E T="03"> Safeguarding personal information.</E> DeCA personnel will protect records in every system of records for confidentiality against alteration, unauthorized disclosure, embarrassment, or unfairness to any individual about when information is kept.</P>
        <P>(1) Supervisor/Manager paper records maintained by DeCA personnel will be treated as ‘For Official Use Only’ (FOUO) documents and secured in locked file cabinets, desks or bookcases during non-duty hours. During normal working hours, these records will be out-of-sight if the working area is accessible to non-government personnel.</P>

        <P>(2) Personnel records maintained by DeCA computer room or stand alone systems, will be safeguarded at all <PRTPAGE P="986"/>times. Printed computer reports containing personal data must carry the markings FOUO. Other media storing personal data such as tapes, reels, disk packs, etc., must be marked with labels which bear FOUO and properly safeguarded.</P>
        <P>(3) Adherence to paragraphs (h)(1) and (h)(2) of this section, fulfills the requirements of 32 CFR part 285.</P>
        <P>(i) <E T="03">Records disposal.</E> (1) DeCA records containing personal data will be shredded or torn to render the record unrecognizable or beyond reconstruction.</P>
        <P>(2) The transfer of large quantities of DeCA records containing personal data to disposal activities is not considered a release of personal information under this part. The volume of such transfers makes it difficult or impossible to identify easily specific individual records. Care must be exercised to ensure that the bulk is maintained so as to prevent specific records from becoming readily identifiable. If the bulk is amintained, no special procedures are required. if the bulk cannot be maintained, dispose of the records by shredding or tearing to render the record unrecognizable or beyond reconstruction.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 327.6</SECTNO>
        <SUBJECT>Collecting personal information</SUBJECT>
        <P>(a) <E T="03">Collect directly from the individual.</E> To the greatest extent practicable, collect personal information directly from the individual to whom it pertains if the information may be used in making any determination about the rights, privileges, or benefits of the individual under any Federal program.</P>
        <P>(b) <E T="03">Collecting personal information from third parties.</E> It may not be practical to collect personal information directly from an individual in all cases. Some examples of this are:</P>
        <P>(1) Verification of information through third party sources for security or employment suitability determinations;</P>
        <P>(2) Seeking third party opinions such as supervisory comments as to job knowledge, duty performance, or other opinion-type evaluations;</P>
        <P>(3) When obtaining the needed information directly from the individual is exceptionally difficult or may result in unreasonable costs; or</P>
        <P>(4) Contacting a third party at the request of the individual to furnish certain information such as exact periods of employment, termination dates, copies of records, or similar information.</P>
        <P>(c) <E T="03">Collecting social security numbers (SSNs).</E> (1) It is unlawful for DeCA to deny an individual any right, benefit, or privilege provided by law because an individual refuses to provide his or her SSN. Executive Order 9397 authorizes solicitation and use of SSNs as numerical identifiers for individuals in most Federal record systems, however, it does not provide mandatory authority for soliciting.</P>
        <P>(2) When an individual is requested to provide their SSN, they must be told:</P>
        <P>(i) the uses that will be made of the SSN;</P>
        <P>(ii) The statute, regulation or rule authorizing the solicitation of the SSN; and</P>
        <P>(iii)  Whether providingthe SSN is voluntary or mandatory.</P>
        <P>(3) Once the SSN has been furnished for the purpose of establishing a record, the notification in paragraph (c)(2) of this section is not required if the individual is only requested to furnish or verify the SSNs for identification purposes in connection with the normal use of his or her records.</P>
        <P>(d) <E T="03">Privacy act statements.</E> When a DeCA individual is requested to furnish personal information about himself or herself for inclusion in a system of records, a Privacy Act Statement is required regardless of the medium used to collect the information, <E T="03">e.g.</E> forms, personal interviews, telephonic interviews. The statement allows the individual to make a decision whether to provide the information requested. The statement will be concise, curent, and easily understood and must state whether providing the information is voluntary or mandatory. if furnishing the data is mandatory, a Federal statute, Executive Order, regulation or other lawful order must be cited. If the personal information solicited is not to be incorporated into a DeCA system of records, a PA statement is not required. This information obtained without the PA statement will not be incorporated into any DeCA systems of records.</P>
        <P>(1) <E T="03">The DeCA Privacy Act Statement will include:</E>
          <PRTPAGE P="987"/>
        </P>
        <P>(i) The specific Federal statute or Executive Order that authorized collection of the requested information;</P>
        <P>(ii) The principal purpose or purposes for which the information is to be used;</P>
        <P>(iii) The routine uses that will be made of the information;</P>
        <P>(iv) Whether providing the information is voluntary or mandatory; and</P>
        <P>(v) The effects on the individual if he or she chooses not to provide the requested information.</P>
        <P>(2) <E T="03">Forms.</E> When DeCA uses forms to collect personal information, placement of the Privacy Act advisory statement should be in the following order of preference:</P>
        <P>(i) Below the title of the form and positioned so the individual will be advised of the requested information,</P>
        <P>(ii) Within the body of the form with a notation of its location below the title of the form,</P>
        <P>(iii) On the reverse of the form with a notation of its location below the title of the form,</P>
        <P>(iv) Attached to the form as a tear-off sheet, or</P>
        <P>(v) Issued as a separate supplement to the form.</P>
        <P>(3) <E T="03">Forms issued by non-DoD Activities.</E> Ensure that the statement prepared by the originating agency on their forms is adequate for the purpose for which DeCA will use the form. If the statement is inadequate, DeCA will prepare a new statement before using the form. Forms issued by other agencies not subject to the Privacy Act but its use requires DeCA to collect personal data, a Privacy Act Statement will be added.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 327.7</SECTNO>
        <SUBJECT>Access by individuals</SUBJECT>
        <P>(a) <E T="03">Individual access to personal information</E>. Release of personal information to individuals whose records are maintained in a systems of records under this part is not considered public release of information. DeCA will release to the individuals all of the personal information, except to the extent the information is contained in an exempt system of records.</P>
        <P>(1) <E T="03">Requests for access.</E> (i) Individuals in DeCA Headquarters and FOAs will address requests for access to their personal information to the DeCA Privacy Act Officers. Individuals in Regions, CDCs, and commissaries, will address requests to their respective Region Privacy Act Coordinator. The individual is not required to explain or justify why access is being sought.</P>
        <P>(ii) If an individual wishes to be accompanied by a third party when seeking access to his or her records or to have the records released directly to the third party, a signed access authorization granting the third party access is required.</P>
        <P>(iii) A DeCA individual will not be denied access to his or her records because he or she refuses to provide his or her SSN unless the SSN is the only way retrieval can be made.</P>
        <P>(2) <E T="03">Granting access.</E> (i) If the record is not part of an exempt system, DeCA personnel will be granted access to the original record or an exact copy of the original record without any changes or deletions. Medical records will be disclosed to the individual to whom they pertain unless an individual fails to comply with the established requirements. This includes refusing to name a physician to receive medical records when required, refusing to pay fees, or when a judgment is made that access to such records may have an adverse effect on the mental or physical health of the individual. Where an adverse effect may result, a release will be made in consultation with a physician.</P>
        <P>(ii) DeCA personnel may be denied access to information compiled in reasonable anticipation of a civil action or proceeding. The term “civil proceeding” is intended to include quasi-judicial and pretrial judicial proceedings. Information prepared in conjunction with the quasi-judicial, pretrial and trial proceedings to include those prepared by DeCA legal and non-legal officials of the possible consequences of a given course of action are protected from access.</P>

        <P>(iii) Requests by DeCA personnel for access to investigatory records pertaining to themselves, compiled for law enforcement purposes, are processed under this part and that of 32 CFR part 310. Those requests by DeCA personnel for investigatory records pertaining to themselves that are in records systems exempt from access provisions shall be processed under this part or 32 CFR part 285, depending upon which provides the greatest degree of access.<PRTPAGE P="988"/>
        </P>
        <P>(3) <E T="03">Non agency records.</E> (i) Uncirculated personal notes and records that are not given or circulated to any person or organization (example, personal telephone list) that are kept or discarded at the author's discretion and over which DeCA exercises no direct control, are not considered DeCA records. However, if personnel are officially directed or encouraged, either in writing or orally, to maintain such records, they may become “agency records” and may be subject  to this part.</P>
        <P>(ii) Personal uncirculate handwritten notes of team leaders, office supervisors, or military supervisory personnel concerning subordinates are not a system of records within the meaning of this part. Such notes are an extension of the individual's memory. These notes, however, must be maintained and discarded at the discretion of the individual supervisor and not circulated to others. Any established requirement to maintain such notes (written or oral directives, regulation or command policy) make these notes “AGENCY RECORDS.” If the notes are circulated, they must be made a part of the system of records. Any action that gives personal notes the appearance of official agency records is prohibited unless they have been incorporated into a DeCA system of records.</P>
        <P>(b) <E T="03">Relationship between the Privacy Act and the Freedom of Information Act (FOIA).</E> (1) Requests from DeCA individuals for access to a record pertaining to themselves made under the FOIA are processed under the provisions of this part, 32 CFR part 310 and DeCA Directive 30-12, Freedom of Information Act (FOIA) Program. <SU>5</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>5</SU> See footnote 3 to § 327.5.</P>
        </FTNT>
        <P>(2) Request from DeCA individuals or access to a record pertaining to themselves are processed under this part and 32 CFR part 310.</P>
        <P>(3) Requests from DeCA individuals for access to records about themselves that cite both Acts or the DeCA implementing directives for both Acts are processed under this part except:</P>
        <P>(i) When the access provisions of the FOIA provide a greater degree of access process under the FOIA, or</P>
        <P>(ii) When access to the information sought is controlled by another Federal statute process access procedures under the controlling statute.</P>
        <P>(4) Requests from DeCA individuals for access to information about themselves in a system of records that do not cite either Act or DeCA implementing directive are processed under the procedures established by this part.</P>
        <P>(5) DeCA requesters will not be denied access to personal information concerning themselves that would be releasable to them under either Act because they fail to cite either Act or the wrong Act. The Act or procedures used in granting or denying access will be explained to requesters.,</P>
        <P>(6) DeCA requesters should receive access to their records within 30 days.</P>
        <P>(7) Records in all DeCA systems maintained in accordance with the Government-wide systems notices are in temporary custody of DeCA, and all requests or amend these records will be processed in accordance with this part.</P>
        <P>(c) <E T="03">Denial of individual access.</E> (1) A DeCA individual may be denied formal access to a record pertaining to him/her only if the record:</P>
        <P>(i) Was compiled in reasonable anticipation of civil action.</P>
        <P>(ii) Is in a system of records that has been exempt from access provisions of this part.</P>
        <P>(iii) All systems of records maintained by the Defense Commissary Agency shall be exempt from the requirements of 5 U.S.C. 552a(d) pursuant to 5 U.S.C. 552a(k)(1) to the extent that the system contains any information properly classified under Executive Order 12958 and which is required by the Executive Order to be withheld in the interest of national defense or foreign policy. This exemption, which may be applicable to parts of all systems of records, is necessary because certain record systems not otherwise specifically designated for exemptions herein may contain items of information that have been properly classified.</P>
        <P>(iv) Is contained in a system of records for which access may be denied under some other Federal statute.</P>

        <P>(v) All systems of records maintained by the DeCA shall be exempt from the requirements of 5 U.S.C. 552a(d) pursuant to 5 U.S.C. 552a(k)(1) to the extent <PRTPAGE P="989"/>that the system contains any information properly classified under Executive Order 12958 and which is required by the Executive Order to be withheld in the interest of national defense of foreign policy. This exemption, which may be applicable to parts of all systems of records, is necessary because certain record systems not otherwise specifically designated for exemptions herein may contain items of information that have been properly classified.</P>
        <P>(2) DeCA individuals will only be denied access to those portions of the records from which the denial of access serves some legitimate governmental purpose.</P>
        <P>(3) Other reasons to refuse DeCA individuals are:</P>
        <P>(i) The request is not described well enough to locate it within a reasonable amount of effort by the PA Officer or PA Coordinator; or</P>
        <P>(ii) An individual fails to comply with the established requirements including refusing to name a physician to receive medical records when required or to pay fees.</P>
        <P>(4) Only the DeCA IDA can deny access. This denial must be in writing and contain:</P>
        <P>(i) The date of the denial, name, title of position, and signature of the DeCA Initial Denial Authority.</P>
        <P>(ii) The specific reasons for the denial, including specific reference to the appropriate sections of the PA, other statutes, this part or the Code of Federal Regulations (CFR);</P>
        <P>(iii) Information providing the right to appeal the denial through the DeCa appeal procedure within 60 days, and the title, position and address of the DeCA PA Appellate Authority.</P>
        <P>(5) <E T="03">DeCA Appeal Procedures.</E> The Director of DeCA, or the designee, will review any appeal by an individual from a denial of access to DeCA records. Formal written notification will be provided to the individual explaining whether the denial is sustained totally or in part. The DeCA PA Officer will:</P>
        <P>(i) Assign a control number and process the appeal to the Director, DeCA or the designee appointed by the Director.</P>
        <P>(ii) Provide formal written notification to the individual by the appeal authority explaining whether the denial is sustained totally or in part and the exact reasons for the denial to include provisions of the Act, other statute, this part or the CFR whichever the determination is based, or</P>
        <P>(iii) Provide the individual access to the material if the appeal is granted.</P>
        <P>(iv) Process all appeals within 30 days of receipt unless the appeal authority determines the review cannot be made within that period and provide notification to the individual the reasons for the delay and when an answer may be expected.</P>
        <P>(d) <E T="03">Amendment of records.</E> (1) DeCA employees are encouraged to review the personal information being maintained abut them periodically. An individual may request amendment of any record contained in a system of records unless the system of records has been exempt specifically from the amendment procedures by the Director, DeCa. A request for amendment must include:</P>
        <P>(i) A  description of the item or items to be amended.</P>
        <P>(ii) The specific reason for the amendment.</P>
        <P>(iii) The type of amendment action such as deletion, correction or addition.</P>
        <P>(iv) Copies of evidence supporting the request.</P>
        <P>(v) DeCA employees may be required to provide identification to make sure that they are indeed seeking to amend a record pertaining to themselves.</P>
        <P>(2) The amendment process is not intended to permit the alteration of evidence presented in the course of judicial or quasi-judicial proceedings. Amendments to these records are made through specific procedures established for the amendment of these records.</P>

        <P>(i) Written notification will be provided to the requester within 10 working days of its receipt by the DeCA PA Officer. No notification will be provided to the requester if the action completed within the 10 days. Only under exceptional circumstances will more than 30 days be required to reach the decision to amend a request. If the decision is to grant all or in part of the request for amendment, the record will be amended and the requester informed and all other offices/personnel known to be keeping the information.<PRTPAGE P="990"/>
        </P>
        <P>(ii) If the request for amendment is denied in whole or in part, The PA Officer will notify the individual in writing and provide the specific reasons and the procedures for appealing the decision.</P>
        <P>(iii) All appeals are to be processed within 30 days. If additional time is required, the requester will be informed and provided when a final decision may be expected.</P>
        <P>(e) <E T="03">Fee assessments.</E> (1) DeCA personnel will only be charged the direct cost of copying and reproduction, computed using the appropriate portions of the fee schedule in DeCA Directive 30-12.<SU>6</SU>
          <FTREF/> Normally, fees are waived automatically if the direct costs of a given request are less than $30. This fee waiver provision does not apply when a waiver has been granted to the individual before, and later requests appear to be an extension or duplication of that original request. Decisions to waive or reduce fees that exceed the automatic waiver threshold will be made on a case-by-case basis. Fees may not be charged when:</P>
        <FTNT>
          <P>
            <SU>6</SU> See footnote 3 to § 327.5.</P>
        </FTNT>
        <P>(i) Copying is performed for the convenience of the Government or is the only means to make the record available for the individual.</P>
        <P>(ii) No reading room is available for the individual to review the record or a copy is made to keep the original in DeCA files.</P>
        <P>(iii) The information may be obtained without charge under any other regulation, directive, or statute.</P>
        <P>(2) No fees will be collected for search, retrieval, and review of records to determine releasability, copying of records when the individual has not requested a copy, transportation of records and personnel, or normal postage.</P>
      </SECTION>
      <SECTION>
        <SECTNO>§ 327.8</SECTNO>
        <SUBJECT>Disclosure of personal information to other agencies and third parties</SUBJECT>
        <P>(a) <E T="03">Disclosures and nonconsensual disclosures.</E> (1) All requests made by DeCA individuals for personal information about other individuals (third parties) will be processed under DeCA Directive 30-12 <SU>7</SU>
          <FTREF/> except when the third party personal information is contained in the Privacy record of the individual making the request.</P>
        <FTNT>
          <P>
            <SU>7</SU> See footnote 3 to § 327.5.</P>
        </FTNT>
        <P>(2) For the purposes of disclosure and disclosure accounting, the Department of Defense is considered a single agency.</P>
        <P>(3) Personal information from DeCA systems of records will not be disclosed outside the DoD unless:</P>
        <P>(i) The record has been requested by the individual to whom it pertains,</P>
        <P>(ii) Written consent has been given by the individual to whom the record pertains for release to the requesting agency, activity, or individual, or</P>
        <P>(iii) The release is pursuant to one of the specific nonconsensual purposes set forth in the Act.</P>
        <P>(4) Records may be disclosed without the consent of a DeCA individual to any DoD official who has need for the record in the performance of their assigned duties. Rank, position, or title alone does not authorize this access. An official need for this information must exist.</P>
        <P>(5) DeCA records must be disclosed if their release is required by 32 CFR part 285, which is implemented by DeCA Directive 30-12.<SU>8</SU>
          <FTREF/> 32 CFR part 285 requires that records be made available to the public unless exempt from disclosure under the FOIA.</P>
        <FTNT>
          <P>
            <SU>8</SU> See footnote 3 to § 327.5.</P>
        </FTNT>
        <P>(b) <E T="03">Normally releasable information.</E> Personal information that is normally releasable without the consent of a DeCA individual that does not imply a clearly unwarranted invasion of personal privacy:</P>
        <P>(1) Civilian employees:</P>
        <P>(i) Name,</P>
        <P>(ii) Present and past position titles,</P>
        <P>(iii) Present and past grades,</P>
        <P>(iv) Present and past salaries,</P>
        <P>(v) Present and past duty stations,</P>
        <P>(vi) Office or duty telephone numbers,</P>
        <P>(2) Military members:</P>
        <P>(i) Full name,</P>
        <P>(ii) Rank,</P>
        <P>(iii) Date of rank,</P>
        <P>(iv) Gross salary,</P>
        <P>(v) Past duty assignments,</P>
        <P>(vi) Present duty assignments,</P>

        <P>(vii) Future assignments that are officially established,<PRTPAGE P="991"/>
        </P>
        <P>(viii) Office or duty telephone numbers,</P>
        <P>(ix) Source of commission,</P>
        <P>(x) Promotion sequence number,</P>
        <P>(xi) Awards and decorations,</P>
        <P>(xii) Attendance at professional military schools,</P>
        <P>(xiii) Duty status at any given time.</P>
        <P>(3) All disclosures of personal information on civilian employees shall be made in accordance with the Office of Personnel Management (OPM) and all disclosures of personal information on military members shall be made in accordance with the standards established by 32 CFR part 285.</P>
        <P>(4) The release of DeCA employees' home addresses and home telephone numbers is considered a clearly unwarranted invasion of personal privacy and is prohibited; however, these may be released without prior consent of the employee if:</P>
        <P>(i) The employee has indicated previously that he or she consents to their release,</P>
        <P>(ii) The releasing official was requested to release the information under the provisions of 32 CFR part 285.</P>
        <P>(5) Before listing home addresses and home telephone numbers in any DeCA telephone directory, give the individuals the opportunity to refuse such a listing.</P>
        <P>(c) <E T="03">Disclosures for established routine uses.</E> (1) Records may be disclosed outside of DeCA without consent of the individual to whom they pertain for an established routine use.</P>
        <P>(2) A routine use shall:</P>
        <P>(i) Be compatible with the purpose for which the record was collected;</P>
        <P>(ii) Indicate to whom the record may be released;</P>
        <P>(iii) Indicate the uses to which the information may be put by the receiving agency; and</P>
        <P>(iv) Have been published previously in the <E T="04">Federal Register</E>.</P>

        <P>(3) A routine use will be established for each user of the information outside DeCA who need official access to the records. This use may be discontinued or amended without the consent of the individual/s involved. Any routine use that is new or changed is published in the <E T="04">Federal Register</E> 30 days before actually disclosing the record. In addition to routine uses established by DeCA individual system notices, blanket routine uses have been established. See Appendix C to this part.</P>
        <P>(d) <E T="03">Disclosure without consent.</E> DeCA records may be disclosed without the consent of the individual to whom they pertain to another agency within or under the control of the U.S. for a civil or criminal law enforcement activity if:</P>
        <P>(1) The civil or criminal law enforcement activity is authorized by law (Federal, State, or local); and</P>
        <P>(2) The head of the agency or instrumentality (or designee) has made a written request to the Component specifying the particular record or portion desired and the law enforcement activity for which it is sought.</P>
        <P>(3) Blanket requests for any and all records pertaining to an individual shall not be honored. The requesting agency or instrumentality must specify each record or portion desired and how each relates to the authorized law enforcement activity.</P>
        <P>(4) This disclosure provision applies when the law enforcement agency or instrumentality request the record, If the DoD Component discloses a record outside the DoD for law enforcement purposes without the individual's consent and without an adequate written request, the disclosure must be pursuant to an established routine use, such as the blanket routine use for law enforcement.</P>
        <P>(e) <E T="03">Disclosures to the public from health care records.</E> (1) The following general information may be released to the news media or public concerning a DeCA employee treated or hospitalized in DoD medical facilities and non-Federal facilities for whom the cost of the care is paid by DoD:</P>
        <P>(i) Personal information concerning the patient that is provided in § 327.8 and under provisions of 32 CFR part 285.</P>
        <P>(ii) The medical condition such as the date of admission or disposition and the present medical assessment of the individual's condition in the following terms if the medical doctor has volunteered the information:</P>

        <P>(A) The individual's condition is presently (stable) (good) (fair) (serious) or (critical), and<PRTPAGE P="992"/>
        </P>
        <P>(B) Whether the patient is conscious, semi-conscious or unconscious.</P>
        <P>(2) Detailed medical and other personal information may be released on a DeCA employee only if the employee has given consent to the release. If the employee is not conscious or competent, no personal information, except that required by 32 CFR part 285, will be released until there has been enough improvement in the patient's condition for them to give informed consent.</P>
        <P>(3) Any item of personal information may be released on a DeCA patient if the patient has given consent to its release.</P>
        <P>(4) This part does not limit the disclosure of personal medical information for other government agencies' use in determining eligibility for special assistance or other benefits provided disclosure in pursuant to a routine use.</P>
      </SECTION>
      <APPENDIX>
        <EAR>Pt. 327, App. A</EAR>
        <HD SOURCE="HED">Appendix A to Part 327—Sample DeCA Response Letter</HD>
        <FP>Mrs. Floria Employee</FP>
        <FP>551 Florida Avenue</FP>
        <FP>Oakland, CA 94618 </FP>
        
        <P>Dear Mrs. Employee: This responds to your Privacy Act request dated (enter date of request), in which you requested (describe requested records).</P>
        <P>Your request has been referred to our headquarters for further processing. They will respond directly to you. Any questions concerning your request may be made telephonically (enter Privacy Officer's telephone number) or in writing to the following address:</P>
        <P>Defense Commissary Agency, Safety, Security, and Administration, Attention: FOIA/PA Officer, Fort Lee, VA 23801-1800.</P>
        <P>I trust this information is responsive to your needs.
        </P>
        <FP>(Signature block)</FP>
      </APPENDIX>
      <APPENDIX>
        <EAR>Pt. 327, App. B</EAR>
        <HD SOURCE="HED">Appendix B to Part 327—Internal Management Control Review Checklist</HD>
        <P>(a) <E T="03">Task:</E> Personnel and/or Organization Management.</P>
        <P>(b) <E T="03">Subtask:</E> Privacy Act (PA) Program.</P>
        <P>(c) <E T="03">Organization:</E>
        </P>
        <P>(d) <E T="03">Action officer:</E>
        </P>
        <P>(e) <E T="03">Reviewer:</E>
        </P>
        <P>(f) <E T="03">Date completed:</E>
        </P>
        <P>(g) <E T="03">Assessable unit:</E> The assessable units are HQ, DeCA, Regions, Central Distribution Centers, Field Operating Activities, and commissaries. Each test question is annotated to indicate which organization(s) is (are) responsible for responding to the question(s). Assessable unit managers responsible for completing this checklist are shown in the DeCA, MCP, DeCA Directive 70-2.<SU>1</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>1</SU> Copies may be obtained: Defense Commissary Agency, ATTN: FOIA/Privacy Officer, 1300 E. Avenue, Fort Lee, VA 23801-1800.</P>
        </FTNT>
        <P>(h) <E T="03">Event cycle 1:</E> Establish and implement a Privacy Act Program.</P>
        <P>(1) Risk: If prescribed policies, procedures and responsibilities of the Privacy Act Program are not adhered to, sensitive private information on individuals can be given out to individuals.</P>
        <P>(2) Control Objectives: The prescribed policies, procedures and responsibilities contained in 5 U.S.C. 552a are followed to protect individual privacy and information release.</P>
        <P>(3) Control Techniques: 32 CFR part 310 and DeCA Directive 30-13,<SU>2</SU>
          <FTREF/> Privacy Act Program.</P>
        <FTNT>
          <P>
            <SU>2</SU> See footnote 1 to this Appendix B.</P>
        </FTNT>
        <P>(i) Ensure that a PA program is established and implemented.</P>
        <P>(ii) Appoint an individual with PA responsibilities and ensure the designation of appropriate staff to assist.</P>
        <P>(4) Test Questions: Explain rationale for YES responses or provide cross-references where rationale can be found. For NO responses, cross-reference to where corrective action plans can be found. If response is NA, explain rationale.</P>
        <P>(i) Is a PA program established and implemented in DeCA to encompass procedures for subordinate activities? (DeCA HQ/SA, Region IM). Response: Yes / No / NA. Remarks:</P>
        <P>(ii) Is an individual appointed PA responsibilities? (DeCA HQ/SA, Region IM). Response: Yes / No / NA. Remarks:</P>
        <P>(iii) Are the current names and office telephone numbers furnished OSD, Private Act Office of the PA Officer and the IDA? (DeCA HQ/SA). Response: Yes / No / NA. Remarks:</P>
        <P>(iv) Is the annual PA report prepared and forwarded to OSD, Defense Privacy Office? (DeCA HQ/SA). Response: Yes / No / NA. Remarks:</P>
        <P>(v) Is PA awareness training/orientation provided? Is in-depth training provided for personnel involved in the establishment, development, custody, maintenance and use of a system of records? (DeCA HQ/SA, Region). Response: Yes / No / NA. Remarks:</P>
        <P>(vi) Is the PA Officer consulted by information systems developers for privacy requirements which need to be included as part of the life cycle management of information consideration in information systems design? (DeCA HQ/SA, Region). Response: Yes / No / NA. Remarks:</P>

        <P>(vii) Is each system of records maintained by DeCA supported by a Privacy Act System Notice and has the systems notice been published in the <E T="04">Federal Register</E>? (DeCA HQ/SA). Response: Yes / No / NA. Remarks:<PRTPAGE P="993"/>
        </P>
        <P>(i) <E T="03">Event cycle 2:</E> Processing PA Requests.</P>
        <P>(1) Risk: Failure to process PA requests correctly could result in privacy information being released which subjects the Department of Defense, DeCA or individuals to criminal penalties.</P>
        <P>(2) Control Objective: PA requests are processed correctly.</P>
        <P>(3) Control Technique:</P>
        <P>(i) Ensure PA requests are logged into a formal control system.</P>
        <P>(ii) Ensure PA requests are answered promptly and correctly.</P>
        <P>(iii) Ensure DeCA records are only withheld when they fall under the general and specific exemptions of 5 U.S.C. 552a and one or more of the nine exemptions under DeCA Directive 30-12,<SU>3</SU>
          <FTREF/> Freedom of Information Act (FOIA) Program.</P>
        <FTNT>
          <P>
            <SU>3</SU> See footnote 1 to this Appendix B.</P>
        </FTNT>
        <P>(iv) Ensure all requests are coordinated through the General Counsel.</P>
        <P>(v) Ensure all requests are denied by the DeCA IDA.</P>
        <P>(vi) Ensure all appeals are forwarded to the Director DeCA or his designee.</P>
        <P>(4) Test Questions:</P>
        <P>(i) Are PA requests logged into a formal control system? (DeCA HQ/SA, Region IM). Response: Yes / No / NA. Remarks:</P>
        <P>(ii) Are individual requests for access acknowledged within 10 working days after receipt? (DeCA HQ/SA, Region IM). Response: Yes / No / NA. Remarks:</P>
        <P>(iii) when more than 10 working days are required to respond to a PA request, is the requester informed, explaining the circumstances for the delay and provided an approximate date for completion? (DeCA HQ/SA, Region IM). Response: Yes / No / NA. Remarks:</P>
        <P>(iv) Are DeCA records withheld only when they fall under one or more of the general or specific exemptions of the PA or one or more of the nine exemptions of the FOIA? (DeCA HQ/SA, Region IM). Response: Yes / No / NA. Remarks:</P>
        <P>(v) Do denial letters contain the name and title or position of the official who made the determination, cite the exemption(s) on which the denial is based and advise the PA requester of their right to appeal the denial to the Director DeCA or designee? (DeCA HQ/SA). Response: Yes / No / NA. Remarks:</P>
        <P>(vi) Are PA requests denied only by the HQ DeCA IDA? (All). Response: Yes / No / NA. Remarks:</P>
        <P>(vii) Is coordination met with the General Counsel prior to forwarding a PA request to the IDA? (DeCA HQ/SA). Response: Yes / No / NA. Remarks:</P>
        <P>(j) <E T="03">Event cycle 3:</E> Requesting PA Information.</P>
        <P>(1) Risk: Obtaining personal information resulting in a violation of the PA.</P>
        <P>(2) Control Objective: Establish a system before data collection and storage to ensure no violation of the privacy of individuals.</P>
        <P>(3) Control Technique: Ensure Privacy Act Statement to obtain personal information is furnished to individuals before data collection.</P>
        <P>(4) Test Questions:</P>
        <P>(i) Are all forms used to collect information about individuals which will be part of a system of records staffed with the PA Officer for correctness of the Privacy Act Statement? (DeCA HQ/SA, Region). Response: Yes / No / NA. Remarks:</P>
        <P>(ii) Are Privacy Statements prepared and issued for all forms, formats and questionnaires that are subject to the PA, coordinated with the DeCA forms manager? (DeCA HQ/SA, Region). Response: Yes / No / NA. Remarks:</P>
        <P>(iii) Do Privacy Act Statements furnished to individuals provide the following:</P>
        <P>(A) The authority for the request.</P>
        <P>(B) The principal purpose for which the information will be used.</P>
        <P>(C) Any routine uses.</P>
        <P>(D) The consequences of failing to provide the requested information. Yes / No / NA. Remarks:</P>
        <P>(k) <E T="03">Event cycle 4:</E> Records Maintenance.</P>
        <P>(1) Risk: Unprotected records allowing individuals without a need to know access to privacy information.</P>
        <P>(2) Control Objective: PA records are properly maintained throughout their life cycle.</P>
        <P>(3) Control Technique: Ensure the prescribed policies and procedures are followed during the life cycle of information.</P>
        <P>(4) Test Questions:</P>
        <P>(i) Are file cabinets/containers that house PA records locked at all times to prevent unauthorized access? (All). Response: Yes / No / NA. Remarks:</P>
        <P>(ii) Are personnel with job requirement (need to know) only allowed access to PA information? (All). Response: Yes / No / NA. Remarks:</P>
        <P>(iii) Are privacy act records treated as unclassified records and designated ‘For Official Use Only’? (All). Response: Yes / No / NA. Remarks:</P>
        <P>(iv) Are computer printouts that contain privacy act information as well as disks, tapes and other media marked ‘For Official Use Only’? (All). Response: Yes / No / NA. Remarks:</P>
        <P>(v) Is a Systems Manager appointed for each automated/manual PA systems of records? (DeCA HQ/SA, Region). Response: Yes / No / NA. Remarks:</P>

        <P>(vi) Are PA records maintained and disposed of in accordance with DeCA Directive <PRTPAGE P="994"/>30-2,<SU>4</SU>
          <FTREF/> The Defense Commissary Agency Filing System? (All). Response: Yes / No / NA. Remarks:</P>
        <FTNT>
          <P>
            <SU>4</SU> See footnote 2 to this Appendix B.</P>
        </FTNT>
        <P>(1) I attest that the above listed internal controls provide reasonable assurance that DeCA resources are adequately safeguarded. I am satisfied that if the above controls are fully operational, the internal controls for this sub-task throughout DeCA are adequate.</P>
        <P>Safety, Security and Administration.</P>
        <P>FUNCTIONAL PROPONENT.</P>
        <P>I have reviewed this sub-task within my organization and have supplemented the prescribed internal control review checklist when warranted by unique environmental circumstances. The controls prescribed in this checklist, as amended, are in place and operational for my organization (except for the weaknesses described in the attached plan, which includes schedules for correcting the weaknesses).</P>
        <P>ASSESSABLE UNIT MANAGER (Signature).</P>
      </APPENDIX>
      <APPENDIX>
        <EAR>Pt. 327, App. C.</EAR>
        <HD SOURCE="HED">Appendix C to Part 327-DeCA Blanket Routine Uses</HD>
        <P>(a) <E T="03">Routine Use—Law Enforcement.</E> If a system of records maintained by a DoD Component, to carry out its functions, indicates a violation or potential violation of law, whether civil, criminal, or regulatory in nature, and whether arising by general statute or by regulation, rule, or order issued pursuant thereto, the relevant records in the system of records may be referred, as a routine use, the agency concerned, whether Federal, State, local, or foreign, charged with the responsibility of investigating or prosecuting such violation or charged with enforcing or implementing the statute, rule, regulation, or order issued pursuant thereto.</P>
        <P>(b) <E T="03">Routine Use—Disclosure when Requesting Information.</E> A record from a system of records maintained by a Component may be disclosed as a routine use to a Federal, State, or local agency maintaining civil, criminal, or other relevant enforcement information or other pertinent information, such as current licenses, if necessary to obtain information relevant to a Component decision concerning the hiring or retention of an employee, the issuance of a security clearance, the letting of a contract, or the issuance of a license, grant, or other benefit.</P>
        <P>(c) <E T="03">Routine Use—Disclosure of Requested Information.</E> A record from a system of records maintained by a Component may be disclosed to a Federal agency, in response to its request, in connection with the hiring or retention of an employee, the issuance of a security clearance, the reporting of an investigation of an employee, the letting of a contract, or the issuance of a license, grant, or other benefit by the requesting agency, to the extent that the information is relevant and necessary to the requesting agency's decision on the matter.</P>
        <P>(d) <E T="03">Routine Use—Congressional Inquiries.</E> Disclosure from a system of records maintained by a Component may be made to a congressional office from the record of an individual in response to an inquiry from the congressional office made at the request of that individual.</P>
        <P>(e) <E T="03">Routine Use—Private Relief Legislation.</E> Relevant information contained in all systems of records of the Department of Defense published on or before August 22, 1975, will be disclosed to the OMB in connection with the review of private relief legislation as set forth in OMB Circular A-19 at any stage of the legislative coordination and clearance process as set forth in that Circular.</P>
        <P>(f) <E T="03">Routine Use—Disclosures Required by International Agreements.</E> A record from a system of records maintained by a Component may be disclosed to foreign law enforcement, security, investigatory, or administrative authorities to comply with requirements imposed by, or to claim rights conferred in, international agreements and arrangements including those regulating the stationing and status in foreign countries of DoD military and civilian personnel.</P>
        <P>(g) <E T="03">Routine Use—Disclosure to State and Local Taxing Authorities.</E> Any information normally contained in Internal Revenue Service (IRS) Form W-2 which is maintained in a record from a system of records maintained by a Component may be disclosed to State and local taxing authorities with which the Secretary of the Treasury has entered into agreements under 5 U.S.C., 5516, 5517, and 5520 and only to those State and local taxing authorities for which an employee or military member is or was subject to tax regardless of whether tax is or was withheld.  This routine use is in accordance with Treasury Fiscal Requirements Manual Bulletin No. 76-07.</P>
        <P>(h) <E T="03">Routine Use—Disclosure to the Office of Personnel Management.</E> A record from a system of records subject to the Privacy Act and maintained by a Component may be disclosed to the Office of Personnel Management (OPM) concerning information on pay and leave, benefits, retirement deduction, and any other information necessary for the OPM to carry out its legally authorized government-wide personnel management functions and studies.</P>
        <P>(i) <E T="03">Routine Use—Disclosure to the Department of Justice for Litigation.</E> A record from a system of records maintained by this component may be disclosed as a routine use to any component of the Department of Justice for the purpose of representing the Department of Defense, or any officer, employee or member of the Department in pending or potential litigation to which the record is pertinent.<PRTPAGE P="995"/>
        </P>
        <P>(j) <E T="03">Routine Use—Disclosure to Military Banking Facilities Overseas.</E> Information as to current military addresses and assignments may be provided to military banking facilities who provide banking services overseas and who are reimbursed by the Government for certain checking and loan losses.  For personnel separated, discharged, or retired from the Armed Forces, information as to last known residential or home of record address may be provided to the military banking facility upon certification by a banking facility officer that the facility has a returned or dishonored check negotiated by the individual or the individual has defaulted on a loan and that if restitution is not made by the individual, the U.S. Government will be liable for the losses the facility may incur.</P>
        <P>(k) <E T="03">Routine Use—Disclosure of Information to the General Services Administration (GSA).</E> A record from a system of records maintained by this component may be disclosed as a routine use to the General Services Administration (GSA) for the purpose of records management inspections conducted under authority of 44 U.S.C. 2904 and 2906.</P>
        <P>(l) <E T="03">Routine Use—Disclosure of Information to the National Archives and Records Administration (NARA).</E> A record from a system of records maintained by this component may be disclosed as a routine use to the National Archives and Records Administration (NARA) for the purpose of records management inspections conducted under authority of 44 U.S.C. 2904 and 2906.</P>
        <P>(m) <E T="03">Routine Use—Disclosure to the Merit Systems Protection Board.</E> A record from a system of records maintained by this component may be disclosed as a routine use to the Merit Systems Protection Board, including the Office of the Special Counsel for the purpose of litigation, including administrative proceedings, appeals, special studies of the civil service and other merit systems, review of OPM or component rules and regulations, investigation of alleged or possible prohibited personnel practices; including administrative proceedings involving any individual subject of a DoD investigation, and such other functions, promulgated in 5 U.S.C. 1205 and 1206, or as may be authorized by law.</P>
        <P>(n) <E T="03">Routine Use—Counterintelligence Purpose.</E> A record from a system of records maintained by this component may be disclosed as a routine use outside the DoD or the U.S. Government for the purpose of counterintelligence activities authorized by U.S. Law or Executive Order or for the purpose of enforcing laws which protect the national security of the United States.</P>
      </APPENDIX>
    </PART>
  </SUBCHAP>
</CFRGRANULE>
