Boundaries change when private information is shared

By Koffi |

July 14, 2026 |

Sena had been thinking about leaving his job, but he was not ready for anyone at work to know. During lunch, he told a trusted colleague, Julian, that he had quietly started looking at other opportunities. Before returning to the office, Sena added, “Please keep this between us.”

Two days later, another coworker asked Sena whether he was planning to resign.

Julian had mentioned the conversation to one person because he believed that person could be trusted. He had not announced it to the team. In his mind, the information had remained mostly private.

Sena saw it differently. Once he shared the information, he believed Julian had agreed to protect it. Julian believed he could use discretion. Their friendship was damaged not because the information was false, but because they understood its ownership differently.

That is the heart of communication privacy management theory. Sandra Petronio developed the theory to explain how people decide what to reveal, what to protect, and how private information should be handled once another person knows it. Privacy, in this view, is managed through communication.

Private information still feels like ours

When Sena told Julian about the job search, he opened a privacy boundary. He allowed another person into a part of his life that had previously been closed.

But disclosure did not make the information feel public. Sena still believed the story belonged to him. Communication privacy management theory explains that people often continue to feel ownership over private information after sharing it.

The receiver becomes a co-owner. That does not mean equal freedom to repeat the story. It means the listener now shares responsibility for managing it. This connects closely to the way trust grows one layer at a time. When someone gives you access to a deeper layer of their life, they are also watching how carefully you hold it.

This is where many conflicts begin. The speaker assumes the rules are obvious, while the listener assumes limited sharing is harmless.

“Keep this private” may mean “tell absolutely no one” to one person and “do not spread it widely” to another.

The rules need to be spoken

After Sena confronted him, Julian said, “I only told someone I trust.”

Sena replied, “But I trusted you.”

That exchange revealed the real problem. Julian focused on whether the next person was trustworthy. Sena focused on whether Julian had permission.

Clear boundaries might have prevented the conflict. Sena could have said, “Please do not tell anyone until I tell you otherwise.” Julian could have asked, “Do you want me to keep this completely to myself?”

This is why communication is not complete until meaning is shared. Two people can use the same words and still operate with different rules in mind. If the privacy rule is not clear, both people may leave the conversation believing they understood the agreement.

The same problem appears in families, workplaces, friendships, and health conversations. A person may share a relative’s struggle because they want advice, while the relative experiences it as exposure. A manager may discuss an employee’s personal difficulty to solve a scheduling problem, while the employee feels private information has traveled too far.

Good intentions do not erase broken boundaries. They may explain a choice, but they do not automatically make it acceptable.

When boundaries become turbulent

Communication privacy management theory uses the term boundary turbulence for the disruption that occurs when privacy rules are unclear, misunderstood, or violated. The result may be embarrassment, anger, loss of trust, or stricter rules in the future.

That is what happened between Sena and Julian. Sena became more guarded. Julian felt unfairly judged because he had not intended harm. Both initially focused on defending themselves.

Repair began when Julian stopped explaining his intentions and acknowledged the impact.

“You asked me to keep it between us, and I did not,” he said. “I should have asked before telling anyone.”

That response did not undo the disclosure, but it recognized Sena’s ownership. They agreed that Julian would not discuss the job search and would direct any questions back to Sena.

In professional settings, this kind of repair also requires maturity. It is one reason people must learn to protect your boundaries professionally instead of relying on assumptions, hints, or emotional reactions after the damage is done.

How to handle private information well

The first step is to ask whether the information is yours to share. Knowing something does not automatically give you permission to repeat it. Before speaking, ask, “Is this my story, or am I carrying someone else’s?”

The second step is to clarify the boundaries when someone confides in you. A useful question is, “Should I keep this completely private, or is there anyone I may discuss it with?” That question may feel formal, but it prevents assumptions.

The third step is to be honest about exceptions. Some information cannot responsibly remain secret, especially when there is a credible risk of serious harm or when professional duties require action. Do not promise absolute confidentiality when you may be unable to keep it.

The fourth step is to avoid using private information for attention. A confidence can make someone feel important because they know what others do not. Repeating the story may earn a moment of interest while costing a relationship much more.

This is especially important at work, where friendliness can blur the line between connection and access. Closeness is not the same as permission. A coworker may be kind, supportive, and enjoyable without being entitled to every private detail of your life.

Finally, when you make a mistake, repair it without hiding behind your intentions. “I was only trying to help” may be true, but it does not restore trust. A stronger response is, “I shared something that was not mine to share. I understand why that affected you.”

Watch out for this

Healthy boundaries protect trust, but privacy should not become a tool for hiding wrongdoing or controlling others. A request for confidentiality does not always create an unlimited obligation.

Communication privacy management theory helps people manage disclosure and protection. It does not mean every secret must be kept under every circumstance. Wisdom requires considering safety, responsibility, law, and the nature of the relationship.

The goal is not silence at any cost. It is responsible communication about who owns the information, who may access it, and what rules apply.

One thing to remember

When someone shares private information with you, they are not simply giving you a fact. They are giving you access to a boundary, and that access carries responsibility.

Sena did not expect Julian to solve his career problem. He expected him to protect the information until Sena was ready to speak for himself. Their relationship began to recover when Julian understood that distinction.

Trust is built in small moments, and it is also broken in small moments. In organizations, friendships, and families, people decide whether they are safe to invest more of themselves based on how carefully others handle what has been shared. That is why trust is built in small moments long before a major crisis reveals whether the relationship can hold weight.

Before repeating another person’s story, pause and ask whether you have permission. When the boundaries are unclear, ask. Trust often depends less on what we know than on how carefully we hold what someone has trusted us to know.

Reflection question

What private information are you currently carrying for someone else, and have the boundaries around that information been made clear?

Organization, Garden, Krakaw, Poland

An organization is built in conversation

Communicative constitution of organizations theory argues that an organization is not simply a structure where communication happens. Communication helps create the organization itself. Through a story about a growing company, this article shows how meetings, roles, policies, stories, and everyday conversations build membership, coordinate work, shape identity, and connect the organization to the world around it each day with meaning.

Ambiguity, Gaudi's type writer

Ambiguity: when information isn’t enough

Organizational information theory explains why more information does not always create more clarity. Sometimes the real problem is ambiguity: people have the same facts but interpret them differently. Through a story about a confusing company announcement, this article shows how organizations make sense of unclear situations through conversation, interpretation, action, and learning; and why leaders must clarify meaning, not merely distribute information.

Technology, Gaudi House

Technology does not change teams by itself

Adaptive structuration theory explains why the same technology can help one team and frustrate another. Tools arrive with features and rules, but people quickly develop habits around how they actually use them. This article shows how teams reshape technology, why norms matter, and how better systems emerge when people deliberately align tools, behavior, and purpose together.

Structure, Aburi Botanical Garden

Structure is built by what people keep doing

Structuration theory explains how structure is created through the things people repeatedly do. Rules shape behavior, but behavior also keeps rules alive or slowly changes them. This article explores routines, culture, authority, and habit, showing why organizations rarely change through announcements alone. Lasting change happens when people begin practicing a different way of working together every day.

Stories, Mainz Germany

Stories turn individuals into a group

Symbolic convergence theory explains how shared stories turn individuals into groups with a common identity. Inside teams, families, companies, and communities, repeated stories create heroes, villains, values, memories, and expectations. This article explores how stories build belonging and motivation, but also how unhealthy narratives can distort reality when a group becomes more committed to its story than to the truth.

Decision, Aburi Botanical Garden

A good decision begins before anyone proposes a solution

The functional perspective on group decision making explains why good teams can still make bad choices. Strong decisions require more than discussion. Groups need to understand the problem, agree on what success means, consider real alternatives, and examine consequences. This article shows how a team nearly solves the wrong problem and how four simple communication functions can improve almost any important decision.