On the Privacy Policy, Personal Data, and Trust of This Service

I would like to begin by explaining the privacy and personal data policy of this service.
Many websites publish policies that read like legal contracts, making them difficult for ordinary users — and even engineers — to understand.

Instead, I would like to speak more honestly about what I have learned from spending many years in the server industry,
and what I considered while launching this small service called RDP3389.

---

On Privacy:

I personally consider privacy to be extremely important, as a matter of principle.
Explaining this in detail would become philosophical, so I will summarize my view as follows:

1.  Privacy is a right that consumers should be able to choose for themselves,
    regardless of whether others consider that choice good or bad.
    (Much like choosing a product that suits one’s own preferences.)

2.  I simply wanted to provide a service that respects that choice,
    and that is what we aim to do.

RDP3389’s Privacy Policy in Practice:

RDP3389 is designed to store as little information as possible. We do not require email addresses, usernames, or passwords; instead, we use randomly generated tokens as the sole method of authorization. This approach has its disadvantages, but at present, we believe it to be the best option available. If a better method exists, we are fully open to adopting it.

Authentication tokens (UUIDv4) are never stored in plaintext and are transformed using HMAC-SHA256 with a server-side secret key before storage. With 122 bits of entropy (≈ 5.3 × 10³⁶ possible values), even an attacker capable of 10 trillion attempts per second would require over 10¹⁶ years to exhaust the space, far exceeding the age of the universe.

All sensitive server-side data is protected using full-disk encryption (LUKS) with encryption keys efficiently distributed among multiple trusted key holders located in different countries. Decryption is only possible when all key holders explicitly approve the operation, ensuring that no single party can independently access user data. In addition, we leverage SME/SMV technologies to protect in-memory data even while servers are running, significantly reducing the risk of data exposure from physical access, hypervisor compromise, or memory inspection attacks.

Regarding Law Enforcement:

We believe that law enforcement agencies are simply performing the duties assigned to them.

---

On Personal Data:

If you inspect RDP3389’s cookies using a browser extension such as a cookie editor,
you will notice that there is very little data to collect in the first place.

As a developer and operator, I cannot claim to know the full extent of everything that could ever be logged.
However, if you request it, we will do our best to help you review any data that may have been recorded unintentionally,
such as web server access logs.

---

On Trust:

To be honest, cloud services operate entirely on trust. In the end, the cloud is not a physical machine that you personally control.

We do not demand that you trust us. Whether you use RDP3389, another cloud provider, or move from another provider to us, it is simply a matter of shifting trust — in other words, a change in who you place that trust in.

Technically, we are capable of accessing user data if we choose to do so. In virtualized cloud environments, it is impossible to prevent this perfectly.

Even So:

I have worked in the IT industry for many years in environments where developers had access to highly sensitive information and customers’ personal data. This is not unusual.

But if you ask whether I ever felt interested in such information, the answer is no.

Hackers may invade privacy for fun or as a hobby. Companies like RDP3389, and others that handle information, do not. For them, it is not entertainment or curiosity — it is business. It is work.

You are one of many customers. We are not particularly interested in you as an individual. Think of it the same way you would think of a lawyer or a nurse.