Secure Remote Support — How We (and You) Can Do It Safely

What This Guide Covers

Sometimes the fastest way to learn is to have someone show you — on your own screen. This guide explains how remote support works, how to stay safe while someone else has access to your computer, and exactly what StarCaller Academy does (and doesn't do) during a hands-on session.

You don't need to be technical to understand this. If you've ever shared your screen on a video call, you already understand the basic idea — remote support is just the next step, where the other person can click and type as well as look.

Step 1. What Remote Desktop Access Actually Means

Remote desktop access lets someone see and control your computer screen from a different location. Think of it as handing someone your mouse and keyboard while still sitting next to them — you can see everything they're doing, and you can take back control at any time.

The software we use is RustDesk — a free, open-source remote desktop tool (see our full RustDesk guide if you want to use it yourself). It encrypts the connection end-to-end, so nobody in between can see what's happening.

During a session, you'll see everything we do on your screen in real time. Nothing happens without you watching — there is no "hidden" or "background" access.

Step 2. The Most Important Safety Concept: Session-Based vs Persistent Access

This is the single concept most non-technical people never learn, and it's the difference between safe remote support and a security risk:

Our policy: We never configure persistent, unattended, or always-on access on a client's machine. Every session uses a one-time code. When the call ends, access ends — there is no way for us to reconnect without you generating a new code.

Step 3. How a StarCaller Academy Remote Session Works

Here's exactly what happens, step by step, every time:

• 1.We ask for verbal consent — before anything technical happens, we say: "I'm now going to take control of your screen — say stop at any point and I'll release it immediately." This mirrors our existing consent framework for recordings (see our FAQ).
• 2.You open RustDesk — if you don't have it installed, we'll walk you through installing it. It takes about 60 seconds. No account, no registration, no email.
• 3.You see your session code — RustDesk displays a 9-digit ID and a one-time password on your screen. These change every session.
• 4.You share the code with us — read it aloud or paste it into chat. We enter it on our end to connect.
• 5.You see everything we do — the session is fully visible on your screen. We narrate any administrative actions (installing software, changing settings) before doing them — nothing happens silently.
• 6.You can end it any time — close RustDesk, click the Disconnect button, or just say "stop." The connection drops instantly.
• 7.When the call ends, access ends — that session code will never work again. There is no way to reconnect without a new code.

Step 4. How to Verify You're Only Granting Temporary Access

Before and during any remote session, you can check these things yourself:

• •The session code is new each time. If someone asks you to use a code you recognise from before, that's a red flag — RustDesk generates a fresh code every time you open it.
• •No permanent password was set. In RustDesk, the one-time password appears in the main window. If someone asks you to set a permanent password (it's a separate menu option), ask why — we never do this.
• •You can see the connection status. RustDesk shows a green "Connected" indicator while someone is connected. When they disconnect, it changes to "Ready."
• •The session ID is random. Your 9-digit ID is not tied to your identity or email — it's just a random number. Nobody can look you up by name.

Step 5. How to Revoke Access If Something Feels Wrong

You are in control at all times. If anything makes you uncomfortable, you can end the session immediately — no awkward conversation needed. Here's how:

• 1.Close RustDesk — click the X or red close button. The connection drops instantly.
• 2.Click Disconnect — in the RustDesk window, there's a prominent Disconnect button during any active session.
• 3.Say "stop" — our policy is to release control immediately on that word. No questions, no delay.
• 4.Disconnect your internet — as a last resort, turn off Wi-Fi or unplug your network cable. This is the nuclear option, but it always works.

After the session ends, RustDesk returns to its idle state. That session code is gone forever. We cannot reconnect without a brand new code from you.

Step 6. Our Operational Security Commitments

These aren't just guidelines — they're how every StarCaller Academy remote session operates:

• •Session-based access only. We use one-time codes generated by RustDesk. No permanent passwords, no unattended access, no "always on" configuration. When the session ends, so does access.
• •Explicit verbal consent at the start of every session. Before we take control, we tell you what we're about to do and confirm you're comfortable. This mirrors the consent language in our recording policy.
• •No admin or sudo actions without narration. We explain what we're doing and why before any privileged action — installing software, changing a system setting, editing a configuration file. Nothing happens in silence.
• •You see everything. There is no hidden session, no background process, no "headless" mode. What you see on your screen is everything that's happening.
• •Minimal connection logs. We run our own RustDesk relay server. It logs timestamps of when connections start and end, for security auditing — it does not log screen content, keystrokes, or what happened during the session. If you ever want to see your session logs, just ask.
• •RustDesk is open-source and auditable. The code is public on GitHub. Anyone can inspect exactly how the encryption works. There are no backdoors.