How Coder IDE Keeps Your Code Safe

Opening your computer's editor from your phone is convenient, and convenience is exactly what should make you ask questions. Who else could open it? Where does your code go on the way? What happens if you lose your phone? This post answers those in plain terms: what Coder IDE does to keep your code and your computers yours, and, just as important, what it can't protect you from.

Your code stays on your computer

Coder IDE doesn't copy your projects anywhere. There's no cloud workspace and no sync of your files to our servers. The only copy of your code is the one on your machine, and the editor you open from your phone or browser is running on that machine.

When you're away from home, the connection between your phone and your computer goes through our relay. The relay forwards traffic between the two. It doesn't store or log what passes through it, and that traffic is encrypted in transit the whole way between your browser, the relay and your computer.

When you're at home on the same network as your computer, the editor connects to it directly instead. It switches between the direct connection and the relay on its own when you change networks, and falls back automatically if the direct connection fails.

Every computer is approved by you

A computer can only join your account if you say so. When you sign in Coder IDE on a new machine, it shows a short code, and the machine is only added after you confirm that code from a browser or phone where you're already signed in.

The approval screen is designed so you can tell a real request from a fake one:

• It shows which computer is asking, by name and operating system, and how long ago the request was made. The code also has an expiry time.
• It warns you when the request comes from a different network than the one you're on. That's the classic sign of someone trying to link their own machine to your account. Only approve if you just started the sign-in yourself.
• It shows which account you're approving for, so you don't add a computer to the wrong one.
• You can deny it. A request you don't recognise doesn't have to sit there until it expires. Tap Deny and it's refused.

The Android app can also notify you when a computer on your network wants to sign in, so you hear about a request even if you didn't start it. The same approval flow covers Android TV, which you sign in by approving a code from your phone.

Signing in without a password

Your Coder IDE account doesn't have a password. You sign in with a one-time link sent to your email, or with Google. There's nothing to phish, guess or reuse from another site's breach.

One-time links have their own trap: someone could send you a link that signs you in to their account instead of yours, hoping you won't notice and will connect your computer to it. Coder IDE checks for that. If you're signed in and open a link for a different account, you're asked first. The page shows which account you're signed in as and which one the link is for, and only continues if you choose to switch.

Removing a device works immediately

If you sell a laptop, hand back a work machine or just stop using a computer, you can remove it from your account. Removing a device from the dashboard revokes it at once. Its access stops working immediately, not at the end of a session or the next day.

On the computer itself, the desktop app gives you the same control. In Settings, Account, Unlink this computer removes it from your account and signs it out, and Sign out removes its credentials without unlinking it. Either way, the editor on that computer can't be opened from your phone or the web until you sign it in again. The desktop app tour covers those options in detail.

Checking the connection with a security number

The desktop app can show a security number for your computer, in Settings, Account. Your browser or phone shows a number for the same connection. If the two match, you know you're talking to your own computer and nobody is sitting in the middle.

You don't need to check it every time. It's there for when you want to be sure, such as the first time you connect from a new device, or on a network you don't trust.

Previews are private too

The dev servers you open from your phone get the same treatment as the editor. A preview link works for you, and you sign in the first time you open it. Hiding a port in the editor's Ports list also closes its link, so a port you can't see isn't quietly left reachable. Ports and private previews has the full story.

What this doesn't protect against

No security model covers everything, and it's better to know where the edges are:

• Anyone holding your unlocked, signed-in phone. If someone can use your phone as you, they can open your editor as you. Use a screen lock, and treat a signed-in phone like a key to your computer.
• Your email or Google account. Since you sign in with an email link or Google, whoever controls those can sign in as you. Protect them with a strong password and two-step verification.
• Approving a computer you don't recognise. The approval screen warns you, but the decision is yours. If you didn't just start a sign-in, deny it.
• Extensions you install. VS Code extensions run with access to your computer, the same as they do in desktop VS Code. Install them from publishers you trust.
• What you let Claude do. Claude Code runs on your computer with the permissions you give it. Approving a command from your phone is the same as approving it at your desk, and modes that skip permission prompts skip them everywhere. Approving Claude Code permissions from your phone covers what to look for before you tap Approve.
• Your computer's own security. Coder IDE can't make an already compromised computer safe. Keep its operating system up to date and its accounts locked down.

Wrap-up

Coder IDE's security model comes down to a few simple rules. Your code stays on your machine. The relay forwards traffic without storing it. Every computer joins your account only when you approve it, you can deny or remove one at any time, and removal takes effect immediately. The rest is up to the same habits that protect any computer: a locked phone, a protected email account, and care with what you install and approve.

There's a short summary of all this in the security section of the home page, and how Coder IDE works shows how the pieces fit together.

Start free and approve your first computer yourself. It takes about a minute.