When a service member is charged with a speech-based offense, the intuitive response is often that the words were never meant to go anywhere, that they were a private remark, a vent to a friend, or an off-the-record comment. The instinct is understandable, but as a legal matter the privacy of the speaker’s intent is rarely a defense by itself. What matters under most speech-related provisions of the Uniform Code of Military Justice (UCMJ) is whether the words reached someone else and what effect they had, not whether the speaker hoped they would stay private. Privacy can be relevant, but usually as evidence bearing on an element or as mitigation, not as a freestanding defense.
Start with the elements of the charged offense
Whether “I meant it privately” helps depends entirely on what the government must prove. Speech offenses in the military do not all share the same elements, so the private-communication argument has to be tested against the specific charge.
Take contempt toward officials under Article 88. One element is that the contemptuous words came, by an act of the accused, to the knowledge of a person other than the accused. If the words truly never left the speaker, that element fails and there is no offense, but that is a failure of proof, not a “private communication” defense. Once the words are spoken to even one other person, the element is satisfied. The fact that the speaker considered the conversation private does not undo the communication. The Manual for Courts-Martial recognizes that opinions expressed in a purely private conversation ordinarily should not be charged, but that is prosecutorial guidance about discretion, not a legal immunity. If such a statement is charged and the communication element is met, privacy does not negate it.
Consider provoking speeches or gestures, or disrespect offenses. These typically require that the words be used in the presence of or toward another person. Again, if the statement was genuinely never communicated, an element is missing. But if it was heard, the private intent behind it does not erase that it was used in another’s presence.
Consider the general article, Article 134, used for some speech that is prejudicial to good order and discipline or service discrediting. The focus is on the effect of the conduct. A statement made in a setting the speaker thought was private can still be prejudicial to good order and discipline if it in fact circulated and harmed discipline, and it can be service discrediting if it reached the public. The speaker’s expectation of privacy does not control whether the effect occurred.
Privacy as evidence, not as a shield
The recurring theme is that the asserted privacy of a statement is best understood as evidence that may bear on an element, rather than as an independent defense.
It can negate the communication element when the proof shows the words never actually reached anyone else. That is a genuine and complete answer to a charge like Article 88, but it is really an argument that the government cannot prove its case.
It can bear on intent where the offense requires a particular mental state. If a charge requires that the accused intended to communicate, to provoke, or to disrespect, evidence that the remark was a private aside not meant for the target’s ears can undercut that intent. Here privacy is doing evidentiary work on a specific element.
It can bear on whether words were contemptuous, disrespectful, or service discrediting in context. The setting of a remark is part of the totality the factfinder weighs. A muttered comment among close friends may read differently than a public broadside, and counsel can argue that context to defeat the characterization element.
Where privacy does little or nothing
For offenses that turn on effect or on the mere fact of communication, the private-intent argument tends to fall flat once the statement is out. If a service member transmits a statement to others, posts it where it can be seen, or speaks it where it is overheard and then spreads, the speaker’s hope that it would remain confidential does not reverse the consequences. Electronic messages are a frequent trap: a text or chat the sender treats as private is a written communication to another person, and forwarding or screenshotting by the recipient puts the words exactly where the sender did not want them, with the communication element already satisfied at the moment of sending.
There is also no general First Amendment safe harbor that converts a private label into immunity. Service members retain free-expression protections, but those protections are applied against the military’s recognized interest in good order and discipline, and the privacy of a statement is only one factor in that balance, not a categorical exemption.
The role of mitigation
When privacy does not defeat an element, it still matters at sentencing. That a statement was an isolated private remark, not a deliberate public attack, is classic extenuation and mitigation. It speaks to the seriousness of the misconduct and the appropriate punishment even where guilt is established.
Bottom line
Claiming that a statement was meant as private communication is generally not a standalone defense. It can be decisive only when it shows the government cannot prove an element, most clearly the requirement in offenses like Article 88 that the words came to the knowledge of another person, or when it undercuts a required intent or the characterization of the words. Once a statement has in fact reached someone else, the speaker’s private intent ordinarily goes to mitigation rather than to guilt.
Disclaimer
This article is provided strictly for general educational and informational purposes. It is intended to explain how the Uniform Code of Military Justice (UCMJ), the Rules for Courts-Martial, the Military Rules of Evidence, and related military administrative processes work as a matter of public legal education. It does not constitute legal advice, a legal opinion, or a recommendation about any particular case, and it is not a substitute for advice from a qualified military defense attorney who can evaluate the specific facts and command, service, and jurisdictional circumstances involved.
Reading this article, or contacting any website on which it appears, does not create an attorney-client relationship between the reader and any law firm, attorney, or author. Every court-martial, nonjudicial punishment action, administrative separation, and security-clearance matter turns on its own facts, the charged articles, the convening authority, the service branch, and the evidence, and outcomes vary widely from one case to another.
Military law also changes over time. The Military Justice Act of 2016 (effective January 1, 2019) and subsequent National Defense Authorization Acts renumbered and rewrote many punitive articles, revised the Article 32 preliminary hearing, and altered sentencing, clemency, and appellate procedures. Statutes, regulations, executive orders, the Manual for Courts-Martial, and decisions of the service Courts of Criminal Appeals and the Court of Appeals for the Armed Forces may have been amended, superseded, or reinterpreted after this article was written, and article numbers or procedures cited here may have changed.
For these reasons, no reader should act or decline to act based on this content without first consulting a licensed attorney experienced in military justice about their own situation. The author and publisher make no warranty, express or implied, as to the accuracy, completeness, timeliness, or current applicability of the information provided, and disclaim any liability for any action taken or not taken in reliance on it. If you are facing investigation, charges, or an adverse administrative action, time limits may apply, and you should seek qualified counsel promptly.