Myrto arrived at the office earlier than usual on Monday. In less than an hour, her team was due to open a private pre-sale for a new premium development in Limassol, and she wanted to check the guest list one last time before anything went out. Twelve brokers were on it — people the developer had worked with before and trusted with the right kind of buyers. The project had not yet appeared on any property portals, prices were still missing from the developer’s website, and several of the most attractive units were being held back until the official public launch.
The selected brokers would receive a separate presentation and a private price list. Across the first page of the PDF, in large letters, were the words CONFIDENTIAL — PRIVATE PRE-SALE. Myrto scrolled through the document once more and stopped at the unit list. Everything looked exactly as a private launch should: a limited audience, preferential terms and a few days’ head start before the wider market saw the project.
“Did we check the final version?” she asked as the sales manager walked into the meeting room.
“Yes. Prices, availability, payment plan — everything is current.”
“And we’re sending it only to these twelve?”
“Only to them.”
“Then make sure the message says the materials aren’t to be shared.”
He nodded.
“Already done: Private release. Please do not distribute outside your team.”
Myrto closed her laptop.
“Good. Let’s go.”
The first few hours looked perfect
At 9:30, the materials started going out. Questions came back almost immediately: one broker wanted the penthouse floor plan, another asked about the payment schedule, and a third wanted to know whether a particular unit could be held for a buyer until the evening. It was exactly the kind of activity Myrto expected from a private pre-sale — no random enquiries, no public noise, just serious questions from a carefully selected group.
Around midday, one of the managers came over to her desk with his phone in his hand.
“Do you know Christos P.?”
Myrto looked up.
“No. Which agency?”
“That’s why I’m asking.”
He handed her the phone. A message was open on the screen.
“Hi, I received your private offer. Is Unit 504 still available at €685K?”
Myrto stared at it for a moment.
“Say the price again.”
“€685K.”
She opened the private price list straight away. Unit 504 was listed at exactly that amount. The figure had never been published anywhere and appeared only in the PDF sent that morning to the selected brokers.
“He’s definitely not on our list?”
“I checked twice. He isn’t.”
Myrto opened the spreadsheet herself and ran through the names. Christos P. was nowhere on it.
“Then how does he have the presentation?”
The manager shrugged.
“I can start asking.”
“Do that.”
Nobody had actually “leaked” anything
Within minutes, replies started coming back from the brokers. One said he had forwarded the file to a colleague inside his agency. Another had shown it to someone on his team. A third had sent a couple of pages to a buyer who might be interested in the project.
“I only shared it internally.”
“Just one colleague.”
“I sent the unit page to my client.”
Nobody was trying to damage the developer, and nobody thought they had done anything particularly serious. Each person had simply done something completely normal in day-to-day sales: they had received useful information and passed it to one more person who might need it.
“So someone got the PDF from a broker, who got it from another broker, and nobody even thinks of that as a leak?” Myrto asked.
“Looks that way.”
“And can we tell how many people have the file now?”
The manager hesitated.
“Not exactly.”
Myrto leaned back in her chair. That morning, she had had a neat list of twelve names, and the list had created a very reassuring sense of control. Now it was obvious that it only recorded the first step in the file’s journey.
Twelve recipients did not mean twelve viewers
A PDF does not know that only twelve brokers are supposed to see it. It does not understand that Unit 504 belongs to a limited pre-sale or that its €685K price is not meant to circulate beyond the selected audience yet. To an ordinary file, there is no such thing as private, VIP or selected-broker access; once it lands on someone’s device, it can be forwarded like any other document.
If the first broker sends it to a colleague, there is now a thirteenth recipient. If that colleague sends a single page to a client, there is a fourteenth. The client may forward it to a friend, the friend to their own agent, and that agent to someone else on the team. A few steps later, the developer may still be calling the launch private while having no clear idea who has actually seen the offer.
“So we know who we sent it to,” Myrto said, “but we don’t know who is reading it now.”
“Yes.”
“Excellent private launch.”
This time, the manager said nothing.
By the afternoon, it was no longer just a confidentiality problem
At 2:20 p.m., another message came in. This time it was from an agent Myrto’s company had never worked with. He was not asking whether he could receive the presentation or whether access was still available. He already had the materials.
“Another one?” Myrto asked.
“Yes.”
“What does he want?”
The manager turned the phone towards her.
“Can my buyer get the same private price?”
Myrto read the message twice. That morning, the price had been part of a limited pre-sale — an advantage reserved for a small group of brokers and their buyers. Now an agent who had never been invited into the launch was already treating it as a market price and using it as the starting point for a negotiation.
“Do we know who sent it to him?”
“Not yet.”
“And how many other people may already have that price?”
“We don’t know that either.”
That was the moment Myrto stopped thinking of the situation as a simple confidentiality issue. The problem was no longer just that somebody had forwarded a document. Her team had lost sight of the real size of the VIP audience, did not know which pages were circulating separately and could no longer say who had already seen the special terms.
She opened the PDF again. The word CONFIDENTIAL was still sitting confidently across the first page.
“Funny,” Myrto said.
“What is?”
“The word is still there. The control isn’t.”
By the end of the day, the list no longer proved anything
Before leaving the office, Myrto opened the spreadsheet with the twelve broker names one more time. That morning, she had seen it as the boundary of the private launch: these were the people allowed to see the offer, while everyone else remained outside. By evening, she understood that the spreadsheet showed something much narrower — only the people who had received the document directly from her company.
The team could not say who had received it after that, which units had been forwarded separately, how many buyers already knew the private price or how many copies of the presentation were sitting on phones and laptops across the market. The project was still absent from the public portals, but the absence of a public listing no longer meant the information itself was staying within the chosen circle.
The manager stopped at the door.
“Tomorrow, do we try to find out who forwarded it first?”
Myrto shook her head.
“I’m not sure that’s the real question.”
“Then what is?”
She looked at the list again.
“Why did we assume that sending a file to twelve people was the same thing as giving twelve people access?”
The manager had no answer.
Myrto closed the laptop.
The question remained.
What This Means
Myrto’s story shows the weakness at the heart of many private pre-sales: a Confidential label and the absence of public advertising do not create controlled access on their own. A developer may know exactly who received an offer first, but once the offer starts moving as a normal file, visibility over the real audience quickly disappears. The risk therefore begins long before anyone deliberately “leaks” confidential information — it starts when a private launch depends on a document that can be copied and forwarded indefinitely, while the original recipient list is still being treated as if it defines who actually has access.
Author
This material was written by Maria Vashchenko.
For questions, collaboration, or further discussion, feel free to contact me on LinkedIn.
