Most remote desktop apps ask for an email before you can connect your own devices to each other. We think that is backwards. Here is why Remio is designed to know nothing about you — and why that turned out to be a feature, not a limitation.
Five axioms behind a zero-account product
Before the engineering, there was a position. Remio is built on five sentences we keep returning to whenever a new feature tempts us into asking for an email. Read them once and the rest of this post is just colour.
If a sign-up is the first thing a user sees, the product has already taken something from them. We refuse to charge that toll. A six-digit code is enough to authorize a device for a session — anything more is a relationship the user did not ask for.
Every database of users is a future incident report. The safest place to put your email is in a column that does not exist. We treat user data the way a careful builder treats lead paint — interesting in theory, unwelcome on site.
Your phone and your Mac are sitting on the same desk. The trust they need to establish lives in that room, not in a data centre on another continent. Remio's PIN exchange is a handshake between two devices, witnessed by no one.
What Remio cares about is whether the machine you are pointing at is the one you paired yesterday. A cryptographic key proves that. A name and email never could. Authorize devices. Forget about people.
The right way to leave a product is to drag it to the trash and be done. No dashboard. No "are you sure?" survey. No data-export ticket. If uninstalling does not delete you, the product knew too much about you in the first place.
The question nobody asks
When you download a remote desktop app, the first thing it asks for is usually your email. Then a password. Then maybe a phone number for two-factor auth. Then it wants you to verify your email. Then you can start connecting your devices.
We are so conditioned to this flow that nobody stops to ask: why?
You own both devices. They are sitting right in front of you. One is your computer. The other is your phone. You want to see your computer's screen on your phone. That is the entire transaction.
Why does a company in another country need to know your name, your email, and your device inventory to make that happen?
The real reason apps want your email
Let us be honest about why most apps require accounts: it is not for your security — it is for their business model.
An email address is the foundation of a user profile. A user profile enables usage tracking. Usage tracking enables targeted upselling. Upselling drives revenue. The account is not a feature — it is a funnel.
There are legitimate reasons for accounts in some apps. If you need cloud sync, team management, or cross-device persistence, a user identity makes sense. But for connecting two devices on the same desk, an account is overhead — for you and for your privacy.
The account is not a feature. It is a funnel. Once you see that, you cannot unsee it — and you stop accepting it as the cost of opening an app.
How PIN pairing works
Remio uses a six-digit code for pairing. No email. No password. No account.
The flow is simple. Install Remio on your computer. It shows a PIN. Type that PIN on your phone. You are connected. The whole process takes under ten seconds.
The PIN is a six-digit code you can rotate anytime. Once your devices are paired, they remember each other using cryptographic keys exchanged during the first handshake. The PIN itself is never stored on our servers.
This is not just simpler — it is more secure than email-and-password authentication. There is no password to leak in a data breach. No account to phish. No credential database for attackers to target. You cannot hack an account that does not exist.
What other apps know about you. What Remio knows.
The clearest way to explain a philosophy is to put it side by side with the alternative. Here is what a typical commercial remote desktop product collects to put a session on your screen — and what Remio collects to do the same job.
- Full name and email address
- Verified phone number
- Every device you have ever paired
- Every connection, with timestamp and IP
- Geolocation derived from those IPs
- OS, hardware model, app version
- Crash reports tied to your identity
- Click-stream analytics and feature usage
- Marketing-attribution cookies
- Payment profile and billing address
A breach of any one row leaks all the rest.
Nothing.
Your device ID lives on your device. You can rotate the code any time you like. Pairing keys never reach our infrastructure. There is no account to attach anything to — anonymous crash and reliability diagnostics keep the app stable, but they carry no identity and never a frame of your screen.
A breach of our servers leaks encrypted traffic we could not read anyway.
No user profile. No ad SDKs. No data brokers. No marketing pixels. The anonymous reliability diagnostics that do exist cannot be joined back to a person — there is no identity in the system to join them to.
Trust through architecture, not policy
Here is the uncomfortable truth about privacy policies: they exist to describe data collection, not to prevent it. A policy that says "we collect usage data to improve our service" gives a company legal cover to track almost anything.
We took a different approach: make data collection architecturally impossible.
Remio connects your devices directly whenever possible. Your screen data does not pass through our servers. We do not run relay infrastructure that could inspect your traffic. The connection is end-to-end encrypted with keys that only your devices hold.
When a direct connection is not possible — strict networks, corporate firewalls — the connection falls back to an encrypted relay. The relay only sees encrypted bytes. It cannot decrypt your screen, your input, or your audio. It is a dumb pipe by design.
We do not ask you to trust our privacy policy. We ask you to trust the architecture. The code cannot collect what the code cannot see.
The business case for not knowing
People ask us: "How do you make money without user accounts? How do you do marketing without emails? How do you measure engagement without analytics?"
Fair questions. Our answers:
- Your data is never the revenue model. Remio is completely free — no ads, no data sales, no paid tiers. People recommend it because the software is good, not because we funnelled them through a drip campaign.
- Marketing happens through word of mouth and content like this article. People share tools they love. No mailing list required.
- Engagement is measured by download counts and app store reviews. We do not need session analytics to know whether users are happy — they tell us.
Is this harder than the SaaS norm? Absolutely. Most playbooks assume you have a database of user emails to market to. We do not. We have accepted that trade-off because we believe it is the right one.
A bet on the future
We think the era of "give us your email to use our product" is ending. Users are tired. They are tired of spam, tired of data breaches, tired of finding out their "anonymous" data was sold to an advertising network they had never heard of.
The next generation of great software will compete on the product, not on the data. It will earn trust by not asking for information it does not need.
Remio does not want your email. We do not want your name. We do not want your usage patterns. We just want to help you see your computer from your phone — and to get out of the way while you do it.
That is not a limitation. It is the entire design.
