# Sharing Safely: OPSEC and Privacy Guidance for Contributors

**Air Force EOD History Project**  
**Status:** Guidance for people sharing a story. This is not an official Department of Defense publication and does not replace official prepublication, security, or public-affairs review when that review is required.  
**Audience:** Contributors and interview guests. A shorter public summary appears on the website's Guidelines page.

---

## 1. Purpose and responsibility

This project collects personal stories from Air Force Explosive Ordnance Disposal technicians and veterans (AFSC 3E8X1 and related EOD-qualified officers). Every kind of Air Force EOD story is welcome — school and training, stateside duty, deployments and combat, family, humor, losses, and life after service — told as personal experience.

You are solely responsible for making sure that what you share is unclassified, contains no controlled unclassified information (CUI), and complies with operations security (OPSEC) and personnel security and privacy (PERSEC). The Air Force EOD History Project does not review submissions for security.

Operations security (OPSEC) protects information that, by itself or when combined with other public information, could reveal sensitive activities, capabilities, or plans. Personnel security and privacy (PERSEC, used here in the practical sense of protecting people) covers the names, images, and private details of living teammates, family members, and other identifiable individuals.

When in doubt, generalize or leave a sensitive detail unsaid. Silence is better than a clever workaround.

The project may decline or later remove content at its discretion. That decision is not a security review and does not certify that material is unclassified or approved for public release. You may request that a published story be removed from the website going forward.

## 2. Public sources this guidance is based on

The following public sources informed this document. Issuances are updated. If you have an official prepublication duty, use the version in force and seek guidance from an appropriate reviewing office. Official texts are posted by the DoD Directives Division at [https://www.esd.whs.mil/DD/](https://www.esd.whs.mil/DD/).

1. **DoD Directive 5205.02E**, *DoD Operations Security (OPSEC) Program* (June 20, 2012, incorporating Change 2, August 20, 2020). Establishes that DoD missions and activities are to be protected by an OPSEC program; DoD personnel must safeguard information useful to adversaries; and the OPSEC process is used to identify and mitigate indicators of U.S. intentions, capabilities, operations, and activities. The directive is marked cleared for public release and is issued from the Directives Division website. A publicly accessible copy is also available from the Federation of American Scientists intelligence-doctrine collection: [https://irp.fas.org/doddir/dod/d5205_02.pdf](https://irp.fas.org/doddir/dod/d5205_02.pdf).

2. **DoD Manual 5205.02**, *DoD Operations Security (OPSEC) Program Manual* (November 3, 2008, incorporating Change 2, October 29, 2020). The official file is posted by Washington Headquarters Services at [https://www.esd.whs.mil/portals/54/documents/dd/issuances/dodm/520502m.pdf](https://www.esd.whs.mil/portals/54/documents/dd/issuances/dodm/520502m.pdf). The manual's public-release discussion emphasizes content review of information intended for release outside the organization, including release to the public, and states that OPSEC focuses on identifying and protecting unclassified information that may, individually or in the aggregate, lead to the compromise of classified information or sensitive activities.

3. **DoD Instruction 5230.09**, *Clearance of DoD Information for Public Release* (January 25, 2019, Change 1 effective February 9, 2022). Official DoD information intended for public release that pertains to military matters, national security issues, or subjects of significant concern to the DoD is to undergo prepublication review before release. The instruction is cleared for public release and is issued from the Directives Division website. A publicly accessible copy is posted by DARPA at [https://www.darpa.mil/sites/default/files/DoDInstructionforPublicReleasea.pdf](https://www.darpa.mil/sites/default/files/DoDInstructionforPublicReleasea.pdf).

4. **DoD Instruction 5230.29**, *Security and Policy Review of DoD Information for Public Release* (August 13, 2014, incorporating Change 2, February 8, 2022). Official file: [https://www.esd.whs.mil/portals/54/documents/dd/issuances/dodi/523029p.pdf](https://www.esd.whs.mil/portals/54/documents/dd/issuances/dodi/523029p.pdf). The instruction describes security review as protecting classified information, controlled unclassified information, or unclassified information that may individually or in the aggregate lead to the compromise of classified information or disclosure of operations security.

5. **DoD Instruction 5200.48**, *Controlled Unclassified Information (CUI)* (effective March 6, 2020). Official file: [https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520048p.PDF](https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520048p.PDF). CUI is unclassified information that still requires safeguarding or dissemination controls. It is not automatically releasable to the public.

6. **Department of Defense, *Memorandum on Reinforcing Operations Security***, posted on defense.gov at [https://www.defense.gov/News/Releases/Release/Article/2281405/memorandum-on-reinforcing-operations-security/](https://www.defense.gov/News/Releases/Release/Article/2281405/memorandum-on-reinforcing-operations-security/). The public memorandum emphasizes that **unclassified information is not publicly releasable until it is approved for release by an appropriate authorizing official**, and that prepublication-review obligations can continue after a person retires, resigns, or otherwise leaves government service or a contract.

**Note on retrieval:** Some `.mil` and `defense.gov` hosts may filter automated or datacenter requests. If a link fails in one environment, open it in a regular browser or download the current issuance from [https://www.esd.whs.mil/DD/](https://www.esd.whs.mil/DD/).

This project document is a practical aid for contributors to an independent history archive. It is not a substitute for a Component OPSEC program, a Public Affairs release, or a formal prepublication review. The project does not perform that review for you.

## 3. Who this applies to

- **Every contributor** is solely responsible for the content they share, including written stories, interviews, photographs, audio, and video.
- **Contributors who are current DoD personnel** (active duty, Guard, Reserve, DoD civilians, and contractors, as applicable) may have a separate legal or policy duty to seek official prepublication or Public Affairs review before discussing official DoD information. This project does not fulfill that duty.
- **Veterans and retirees** may still have prepublication obligations for classified, CUI, or other protected information they learned in service, and for some official materials. When you are unsure, the safe path is to stay with personal, non-technical memories and to consult an appropriate reviewing office.
- **Family members** should not be asked to describe a veteran's operational details.

## 4. What not to include

Leave the detail out, or replace it with a general phrase, in the categories below. Do not try to "hint around" a restricted subject. If the interesting part of a story is the restricted part, choose a different story.

### 4.1 Classified information and CUI

Do not include anything that is classified, was classified when you learned it, or is marked or known to be CUI. That includes documents, slides, maps, chat logs, mission products, and photographs of those materials. "It was later declassified" is not enough unless you can point to a genuine public release. If a classification or CUI marking appears in a file or on a screen in a photo, do not send that item until that content is removed.

### 4.2 Render-safe procedures and tactics, techniques, and procedures (TTPs)

Do not describe how a task was done in a way that would teach a method. That includes render-safe procedures, diagnostic sequences, tool-selection logic, timing, standoff or positioning practices, communications practices used on a call, and other techniques unique to EOD or to a unit's way of working.

Safe alternative: speak to the human experience — fatigue, trust, humor, fear, relief, what a mentor said afterward — without describing the procedure itself.

This document does not list or illustrate those procedures, even as examples of what to leave out.

### 4.3 Specific device or IED construction details

Do not include construction, components, wiring, concealment methods, firing-system details, or other design information about explosive devices, hoax devices, or related hazards, whether foreign, homemade, conventional, or otherwise. Do not send photographs that show those details clearly.

Safe alternative: "We responded to a hazardous device call" or "the work that day was technically demanding." Do not add the interesting particulars.

### 4.4 Capability gaps and sensitive capabilities

Do not include statements about what a unit, platform, tool, or procedure could not do, could not detect, or could not reach, or about shortages, work-arounds, or "what we wished we had." Do not include sensitive descriptions of current special equipment, unique access, or unpublished capabilities, even if you are proud of them.

Safe alternative: stay with personal growth, teamwork, and the general difficulty of the work.

### 4.5 Current or recent unit locations and sensitive operating locations

Do not include the exact location of current or recent sensitive operations, named current deployments, unpublished facility locations, home addresses of service members, or the current station of a specific team if that information is not already appropriately public and non-sensitive.

Historical, widely known facts may be acceptable at a general level (for example, "tech school at NAVSCOLEOD / Eglin," or "a deployment to a widely known theater in the mid-2000s"). Prefer era and theater over base, camp, compound, grid, or route. When a location is still sensitive, drop it.

### 4.6 Names of living teammates and other third parties without consent

Do not include the name, nickname, call sign, recognizable photograph, or other identifying detail of a living teammate, interpreter, partner-force member, or other third party unless that person has given informed consent to be identified in this story. Your consent is not a substitute for the other person's consent.

Fallen teammates may be honored, with care. Prefer information that is already appropriately public (for example, a name on the EOD Memorial). Do not add unpublished operational details, graphic descriptions, or private family information. When a family has asked for privacy, follow that request.

### 4.7 Identifying details of family members

Do not include a family member's full name, workplace, school, medical information, home address, or other details that would make that person easy to find or that they have not agreed to share. A first name or a general role ("my spouse," "our kids") is often enough if you want to talk about home life. Children's identities deserve particular care; default to no photos and no names of minors unless a parent or guardian has consented.

### 4.8 Other common problem areas

Leave out or generalize:

- Unpublished unit rosters, manning, or alert-posture information.
- Exact dates and times combined with specific places for recent or sensitive activity.
- Non-public telephone numbers, official email addresses, network names, or internal system details.
- Badge, credential, or access-control details.
- Screenshots or photos that include badges, documents, maps, or user interfaces.
- Information that looks harmless alone but becomes revealing when combined with your public social-media presence, other stories in this archive, or news reporting.

## 5. What to tell us about

Please do tell us about:

- Why you joined and what you hoped to do.
- EOD school and early training as a culture and a test, not as a manual.
- Stateside and range work, base response calls, and VIP or presidential support.
- First assignments, mentors, shop humor, and the feel of the career field.
- The weight of responsibility and how it shaped you.
- Deployments and combat, including IED and UXO missions and close calls, told as personal experience rather than a technical walk-through.
- Leadership and mentorship.
- Teammates, in ways that protect the living and honor the fallen.
- Family and spouse perspectives, homecomings, and the cost and joy of the life around the job.
- Losses and memorials, handled with care.
- Life after service, civilian work, and advice for the next generation.

War stories are welcome, alongside stateside and career stories. Humor belongs in this archive. So do hard days. Neither requires a technical explanation. The restrictions in this document are how to share those memories safely, not a request to leave them out.

## 6. Wording examples

These examples are generic. They are not real stories, and they do not describe real people, units, or events. They show the *kind* of wording that is usually safer, needs to be generalized, or should be left out.

### Usually safer

> "I entered the career field in the 1990s. Tech school was harder than I expected, not only because of the material, but because of the standard the instructors expected us to meet. My first shop taught me that reputation is built in ordinary workdays. I still think about a mentor who made time to explain things twice."

> "During a deployment to a widely known theater in the mid-2000s, the days were long. What has stayed with me is how the team looked after one another, and how quiet it could feel after a difficult call. I do not need to describe the work itself to remember what it asked of us."

> "My family carried a lot while I was gone. I will not name them here, but coming home and learning how to be present again was its own job. Humor in the shop helped. So did people who checked in after I left the service."

These passages are personal, historically general, and free of procedures, devices, current locations, and third-party identifiers.

### Pause and generalize

> "Last year my flight at [named current installation] supported [a named current operation]. I cannot get into everything, but the way we handled one call made a real difference."

Problems: a current unit location, a current or recent operation, and a hint that a specific method will follow.  
Safer direction: move the story back to a general era and theater, drop the current installation and operation name, and keep the memory at a human level without describing how the call was handled.

> "A teammate, SSgt [full name], and I were inseparable on that rotation. His kids went to [named school] off base."

Problems: a living teammate is identified without documented consent, and a family member's school is an identifying detail.  
Safer direction: "A teammate I trust" or, if that teammate has consented to be named, name only what they agreed to share, and leave out the school and children's identities.

> "This photo is from inside the work area. You can see the board and a couple of our tools in the background."

Problems: images may reveal layouts, equipment, or documents even when the caption is mild.  
Safer direction: use a portrait or a non-sensitive public photo; crop or withhold anything that shows work areas, tools in context, screens, or papers.

### Do not include

The following are categories of content that should not be sent. This list describes the problem; it does not provide a worked example of restricted technical detail.

- Any passage, file, or image that is classified or CUI, or that you think "probably should not be out there."
- A description of how a device was constructed, concealed, or defeated, or how a render-safe or diagnostic procedure was performed, including sequences, tools used for a specific purpose, measurements, or decision logic.
- Statements about current capability gaps, what a unit could not do, or unpublished equipment performance.
- Exact locations of current or recent sensitive operations, or details that would let a reader find a current team, facility, or family residence.
- Names, images, or unique identifiers of living teammates or family members without consent, especially minors.
- Graphic accounts of a teammate's wounds or death that go beyond what is needed to honor them and that the family has not approved.

If the interesting part of a memory falls in this list, tell a different, personal story instead of sending a lightly edited version that still implies the same facts.

## 7. Photographs, audio, and video

You are responsible for the media you send, not only the words.

- Watch or listen all the way through, including asides, off-camera voices, and the last few seconds, before you send it.
- Check stills and video frames for ID cards, nametapes you do not have consent to share, maps, screens, documents, license plates, house numbers, and work-area layouts.
- Prefer portraits, public ceremonies that were already cleared, and images you took in a non-sensitive setting.
- Do not send official imagery unless its public-release status is clear.
- Do not send recordings of official briefings, nets, or internal meetings.

## 8. If you realize something should not have been shared

Tell the project as soon as you can at stories@afeodhistory.com. The project can take an item down or replace it on its own website going forward. It cannot recall copies already downloaded, shared, quoted, or archived by others.

If classified or CUI material may have been sent, do not spread the file further. The project lead should seek appropriate official guidance without delay.

## 9. Crisis and dignity reminder

Interviewers and project volunteers are not therapists. If you are in crisis, pause the work and get help: the Veterans Crisis Line, 24/7 and confidential — dial 988, then press 1; text 838255; or chat at [https://www.veteranscrisisline.net/get-help-now/chat/](https://www.veteranscrisisline.net/get-help-now/chat/). See also [https://www.veteranscrisisline.net/](https://www.veteranscrisisline.net/). Enrollment in VA care is not required.
