Becoming A Tech Tycoon Begins With Regression novel Chapter 13

Chapter 13: Response

Ethan clicked open the email in a secure environment and watched as the contents loaded.

___________

Dear OmniTech,

This is Amelia Rhodes, Lead Security Architect at Google.

I’ve reviewed your report, and after verifying three of the vulnerabilities, I can confirm their authenticity. As such, I would like to schedule a secure, formal discussion regarding the remaining fifteen vulnerabilities, their scope, and the terms under which you intend to disclose them.

Please propose a channel and time that works for you.

Sincerely,

Amelia Rhodes

Lead Security Architect

Google Inc.

_______

The email was more or less what he expected so he went directly to his encrypted mail and started typing a reply.

---

Dear Ms. Rhodes,

Thank you for your swift response. As for the remaining fifteen vulnerabilities, their potential impact ranges from data exfiltration to full service disruption on core systems.

In the wrong hands, they represent a systemic risk to over 2.3 billion active users. I’m sure you understand why I chose to limit the initial disclosure.

I am willing to discuss the compensation for these in full, but only under the following conditions:

1. The communication must take place through a mutually agreed-upon, zero-trust environment.

2. Any shared data remains under NDA with legally binding terms of non-retaliation.

3. The compensation structure must reflect the scope, complexity, and critical nature of these findings.

As for our communication channel, I’ll send you a link to my encrypted video chat software at 10:00 AM EST

I look forward to your response.

OmniTech

_____

Ethan kept his response as simple and straight forward as possible before hitting send.

As for the video chat software, he opened up a file and loaded it into his IDE. This was a project he had been working on at this time.

It was end-to-end encrypted video communication suite.

The software allowed it’s user to create customized the channel parameters to block all packet inspection attempts.

And even add a digital self-destruct timer on the session logs.

This was just a fun little project his past self had created but had abandoned mid way since his time was extremely limited and the software didn’t have any chance of making him money whatsoever.... Or so he thought.

Until now.... Now, he was glad that project was created

Ethan smirked as the old codebase came to life on his screen. It wasn’t market-ready, but he didn’t need it to be—it just had to work this once.

With his future knowledge and current experience, fixing the unfinished parts took less than an hour.

Soon enough, the packaged software was sitting on his laptop, ready to be opened.

He clicked the software’s icon and it immediately opened, displaying the name Ethan had chosen,

CryptCall

VERIFYCAPTCHA_LABELVerify