✧ Key takeaways
As a freelancer, you're your own IT department — and your clients' data is on your laptop. Here's the practical setup that keeps it safe.
When you work for a company, someone else worries about security. There is an IT team, a firewall, a policy document, and a person whose job is to say no to the risky thing. When you freelance, that person is you. Your laptop holds client logins, customer lists, payment details, and half-finished work that belongs to someone else — and nobody is watching the door but you.
That sounds dramatic, and the risk is usually not dramatic at all. Nobody is targeting you specifically. The attacks that catch freelancers are the boring, automated ones: a phishing email that looks like a client, a password reused across ten sites, a laptop left unlocked in a cafe, a backup that never existed until the day it was needed. The good news is that boring attacks have boring defences, and most of them take an afternoon to set up.
This guide is that afternoon. It covers the setup that keeps client data safe without turning your workday into a security drill — including a VPN for the networks you don't control, a password manager, backups that actually restore, and a plan for the day something goes wrong.
The threat model, in plain terms
Before buying anything, think about what you're actually protecting. For most freelancers it comes down to three things: your clients' accounts and data, your own accounts (especially email, which resets everything else), and your work files. The threats are equally ordinary: someone guesses or steals a password, someone tricks you into handing over access, someone reads your traffic on an open network, or your device gets lost, stolen, or encrypted by ransomware.
Notice what isn't on that list: a hacker in a hoodie targeting you personally. You don't need defences against a nation-state. You need defences against the automated, opportunistic attacks that sweep up thousands of people a day. Those are cheap to stop, which is the whole point.
For the full picture of how VPNs actually work and which one fits different needs, see our guide to VPNs explained. The rest of this guide assumes you have one and shows where it fits.
1. Separate work from personal
The simplest security win costs nothing: keep client work in its own space. A separate user account on your laptop for work, a separate browser profile, a separate folder tree. When work and personal files mix, a mistake in one leaks into the other — a personal app with broad permissions reads a client folder, or a client file gets attached to a personal email by autocomplete.
The same rule applies to accounts. One email for client work, another for personal life. Your work email is the key to your clients' systems, so it deserves its own inbox, its own strong password, and two-factor authentication. Never use it to sign up for newsletters, loyalty programs, or anything that might end up in a breach database.
2. Lock the device itself
Your laptop is the front door. Three settings matter most. First, full-disk encryption — FileVault on Mac, BitLocker on Windows — so a stolen laptop is a brick, not a data breach. It is usually one toggle in settings and costs nothing in daily speed. Second, automatic updates for the operating system and the apps you use daily. Most successful attacks use vulnerabilities that were patched months ago; updating closes them. Third, a lock screen that kicks in after a minute or two of idling, plus a habit of locking the screen every time you stand up. In a coworking space or a cafe, an unlocked laptop is an open door.
3. A password manager and two-factor authentication
This is the single highest-value step in the whole guide. A password manager gives every account its own long, random password, so one breach doesn't hand attackers the keys to everything else. Two-factor authentication adds a second check — usually a code from an authenticator app — so a stolen password alone isn't enough.
Start with email, because email resets nearly every other account. Then banking, then client dashboards, then everything else. Use an authenticator app rather than SMS codes where you have the choice; SMS codes can be intercepted, app codes can't be phished as easily.
Pick a manager and commit to it. NordPass is the simplest of the serious options, with Premium from $1.49 a month on a 2-year plan (verified 16 November 2026), and it covers the basics well: strong encryption, autofill, a password health check, and apps for every device. Our ranking of the best password managers in 2026 compares it with 1Password and Proton Pass if you want the full picture, and our two-factor authentication guide walks through setup app by app.
Email is the master key
Your email account is the most valuable account you own, and it is the one most freelancers protect least. Almost every other account — client dashboards, banking, cloud storage, your password manager's recovery — can be reset through email. If someone gets into your inbox, they don't need your other passwords; they can reset them one by one. That makes email the first account to secure, not an afterthought.
Start with a separate work inbox, as above, then give it the strongest treatment: a unique password from your manager, two-factor authentication with an authenticator app, and a recovery email and phone number you actually control and keep up to date. Then check two settings most people never look at. First, mail forwarding rules — an attacker who briefly gets into an inbox often sets up a hidden rule that forwards a copy of every email to themselves, so they keep reading even after you change the password. Second, connected apps and third-party access — old tools you authorised years ago can still read your mail. Review both once, then again whenever anything feels off.
One more habit: never use your work email as the login for personal services, and never use a personal email as the login for client systems. When a breach database lists your work address, you want the damage contained to one side of your life. A free email alias — a forwarding address that hides your real one — works well for newsletters and signups, so your real inbox stays out of breach lists in the first place.
4. A VPN on any network you don't control
Your home network is yours. The cafe, the hotel, the airport, the client's office, and the coworking space are not. On an open or shared network, your traffic can be watched, and on a network with a compromised router, it can be altered. A VPN encrypts your connection so the network in the middle sees noise instead of your work.
Use it whenever you work outside your home: before opening email, before logging into a client dashboard, before touching anything with a password. A good VPN runs quietly in the background and reconnects itself — if yours needs constant attention, it is the wrong one. NordVPN is the default pick for most freelancers: fast, available on every device, with a kill switch that cuts the connection if the VPN drops so nothing leaks onto the open network. Our roundup of the best VPNs for freelancers and remote workers compares it with the other serious options.
One honest note: a VPN is not a magic shield. It protects your traffic on the network, not your device from malware, and not you from a phishing email. It is one layer, and it only works when it is on.
5. Phishing: the client-impersonation trick
The phishing email that catches freelancers rarely pretends to be a bank. It pretends to be a client. "Can you review this invoice?" with a document attached. "We changed our payment details, please update them." "Quick call — I need you to buy gift cards for the team." The sender's name looks right. The logo looks right. The urgency feels real, because clients are always urgent.
Three habits stop most of it. First, verify payment changes through a second channel — call or message the client on a number you already have, never one from the email. Second, treat unexpected attachments with suspicion, even from known senders; a compromised client account sends malware too. Third, slow down when an email demands immediate action. Urgency is the attacker's favourite tool, and it works because freelancers are busy. A two-minute pause is cheaper than a compromised account.
Client portals and shared accounts
Clients often hand you a single shared login — one username and password for the whole team, sometimes sent in a plain email. Push back gently and ask for your own account. Individual accounts mean your access can be revoked when the project ends without breaking everyone else's, and if something goes wrong, the audit trail shows who did what. A shared login gives you neither.
When a client genuinely can't create separate accounts — a small business with one admin login, for example — store that credential in your password manager, never in a document or a chat, and keep a note of exactly which systems it opens. The moment the project ends, tell the client to change it, and delete your copy. Keep a simple access inventory for each client: which systems you can reach, which email the account uses, and when access should end. It takes five minutes per client and it is the difference between a clean handover and a year of wondering whether you still hold the keys to someone else's store.
6. Share files safely
Email attachments are the worst way to move sensitive files: they sit in inboxes forever, get forwarded by accident, and live on servers you don't control. Use a shared drive or a file-sharing link with an expiry date instead, and set the link to expire when the work is done. For contracts, IDs, and payment details, prefer a link that requires sign-in over a public one.
When a project ends, delete what you no longer need. Client files sitting in your downloads folder two years after the project ended are a breach waiting for a lost laptop. Your contract should say how long you keep files and when you delete them — more on that below.
Coworking spaces and client offices
Working from a coworking space or a client's office feels safer than a cafe, but the risks are different, not smaller. The person at the next desk can read your screen; the shared printer holds the document you forgot to collect; the meeting-room computer still has your session logged in after you leave. The fixes are small and mostly social. Use a privacy screen filter if you handle sensitive data in the open. Collect printouts immediately and never leave them in the tray. Never log into anything on a shared or meeting-room computer — if you must, use a private browsing window and log out before you walk away, then change the password later if you forgot.
Shared USB drives and cables are another quiet risk: a drive left in a meeting room can carry malware, and a cable you borrow can be more than a cable. Carry your own, and don't plug in storage you didn't bring. And the oldest rule still applies: never leave your laptop unattended, even for a coffee run in an office full of friendly people. Lock the screen every single time — it takes one second, and an unlocked laptop in a busy office is the easiest breach there is.
7. Backups: the 3-2-1 rule
Backups are the defence against the one attack no password can stop: ransomware, and the simpler disasters — a dead drive, a spilled coffee, a stolen bag. The rule is 3-2-1: three copies of anything important, on two different kinds of storage, with one copy offsite. For most freelancers that means the laptop, an external drive, and a cloud backup that runs automatically.
Automatic matters. A backup you have to remember is a backup that won't exist the week you need it. Set it up once, then test the restore once — pick a file, delete it, bring it back. A backup you have never restored is a hope, not a backup.
8. Put data handling in the contract
Security is also a business question. Your agreement with each client should say, in plain language: what data you will access, where you store it, who else can see it, and when you delete it. Clients notice this, and the ones who care about their own data will trust you more for having it written down.
If a client sends you a non-disclosure agreement, read the data-handling part before signing, not after. If it requires security measures you don't have — encrypted storage, a specific VPN, deletion within thirty days — say so and price it in. Agreeing to terms you can't meet is worse than negotiating them.
When a client asks you to do something unsafe
Sooner or later a client will ask for something that makes you wince: passwords sent in plain text over email, two-factor authentication turned off "just for today", a login shared in a chat message, or client files uploaded to a personal account because it is faster. It usually isn't malice — they just want the work done, and the secure way takes an extra step.
Say no, but say it helpfully. Don't lecture; offer the secure alternative in the same breath. "I can't email the password — here's a shared vault entry instead, and I'll revoke it when the project ends." "I can't turn off two-factor, but I can set you up with an authenticator app in two minutes." Clients almost always accept when the alternative is right there and costs them nothing. If a client keeps pushing, put the risk in writing: a short message explaining what you were asked to do and why you won't do it protects you if that data ever leaks. And remember that agreeing to an unsafe practice is a business decision with your name on it — if their data leaks through the shortcut you agreed to, the client will remember who set it up.
9. Public Wi-Fi rules
Work from a cafe when you like, but with rules. Connect through your VPN before opening anything work-related. Prefer the venue's password-protected network over a fully open one. Turn off file sharing and AirDrop while you're there. Never log into a client account on a shared or borrowed computer — the browser may save the session, and the next person to sit down inherits it. And keep your phone's hotspot as the fallback: your own data connection is almost always safer than a network you didn't set up.
Travelling with client data
Travel concentrates every risk in this guide into a few days. Hotel and airport Wi-Fi are networks you don't control, so the VPN rule from section 4 applies double — connect before opening email or a client dashboard, and use your phone's hotspot when the Wi-Fi looks suspicious or demands strange permissions. Public charging stations deserve the same caution: use your own charger and cable, or a power bank, rather than a public USB port, and never accept a borrowed cable you haven't inspected.
Before you leave, make a fresh backup and check that it actually restored — losing a laptop abroad is bad enough without discovering the backup was stale. Keep client files you don't need for the trip off the device entirely; the less data you carry, the less you can lose. If the laptop is stolen, the plan is the same as at home — change passwords from a clean device, revoke sessions, tell the client — but do it fast, because a thief with your unlocked laptop abroad has the same access a thief at home does. And if you cross a border, remember that your device can be inspected: a separate travel profile with only the files you need keeps the rest of your client work out of the conversation.
Your home network deserves attention too
Most freelancers secure the laptop and forget the router, which is like locking the front door and leaving the windows open. Three router jobs take twenty minutes and last for years. First, change the default admin password — the factory password for your router model is public knowledge, and anyone on your network who knows it can change your DNS settings. Second, update the router's firmware, or turn on automatic updates if it offers them. Router vulnerabilities are common and rarely patched by owners. Third, put smart-home gadgets and cheap IoT devices on a separate guest network, away from the laptop that holds client work. A compromised smart bulb shouldn't be a path to your files.
While you're there, check who is on your network. An unknown device on your Wi-Fi is worth investigating before you shrug it off — it might be a neighbour, or it might be a device you forgot about. Either way, you want to know. And if your work involves client data that is genuinely sensitive — health records, financial data, legal files — consider a separate network for work devices entirely. A second SSID costs nothing and keeps a compromised personal device away from client files.
Tools worth paying for
Most of the setup in this guide is free: encryption, updates, separate accounts, sensible habits. Three things are worth paying for. A password manager, because the free tiers limit devices or features in ways that push you back to bad habits — NordPass Premium at $1.49 a month on a 2-year plan is the cheapest serious option. A VPN, because free VPNs pay their bills by selling your data, which defeats the purpose. And a cloud backup service, because a backup that runs itself is the only kind that exists when you need it. Together, those three cost less than a single hour of most freelancers' time, and they cover the gaps that free tools leave open.
How to check whether your passwords already leaked
Most freelancers have at least one password in a breach database and don't know it. You don't need to panic about that — you need a routine for finding out and acting on it. Most password managers include a breach scanner or health report that checks your stored logins against known leaks; open yours once a month and look at what it flags. If an account shows up as breached, change that password first, then check whether you reused it anywhere else — if you did, change those too, because credential stuffing, where attackers try a leaked password on every major site, is exactly how a breach of one service becomes a breach of five.
While you're there, look at the weak and reused passwords the health report flags, and fix the worst ones — starting with email, banking, and client dashboards. You don't have to fix everything in one sitting; fixing the top ten most important accounts covers nearly all the real risk. And if you ever get an alert that a service you use was breached, don't wait for a reminder email: change the password that day, turn on two-factor authentication if it wasn't on, and check the account's recent activity for logins you don't recognise.
10. When something goes wrong
Sooner or later, something will go wrong — a phishing click, a lost device, a suspicious login alert. What matters is not that it happened, but what you do in the first hour. Write this checklist down now, while nothing is burning:
Contain it. Change the affected passwords from a clean device, revoke active sessions, and disconnect the device from the network if you suspect malware. Tell the client. Promptly and honestly: what happened, what data was involved, and what you've already done. Clients forgive mistakes far more easily than silence. Check for misuse. Review sent mail, login history, and recent file access for anything you didn't do. Document everything. Times, screenshots, what you changed. If the client needs to report it, your notes are the evidence. Fix the gap. The incident tells you exactly which control failed. Close it before the next one.
A first-week checklist for a new client
Every new client deserves a short setup ritual before any real work starts. It takes twenty minutes and it prevents the mess that shows up months later when a project ends and nobody knows who has access to what. Create a folder for the client and keep everything in it. Set up a separate browser profile if you'll be logging into their systems daily. Save their logins in the password manager, never in a chat thread or a document. Ask for your own account on every system rather than a shared login, and note the access in a simple inventory. Read the data-handling part of the contract — or write one if there isn't one — and confirm how long you'll keep their files and when you'll delete them. Finally, agree on how you'll share files and how you'll reach each other for urgent changes, so a payment detail never arrives by surprise in a plain email. Do this for every client, even the small ones, and security stops being a project you put off and becomes the way you start work.
The 10-minute weekly routine
Security fails when it depends on memory, so make it a routine. Once a week, ten minutes: install pending updates, glance at the login alerts in your email, check that the backup ran, and clear out files from finished projects. Once a month, add two more jobs: open your password manager's health report and fix any weak or reused passwords it flags, and review which apps have access to your Google or Microsoft account, revoking anything you no longer use. Old app permissions are a quiet risk — a tool you tried once in 2024 still holding access to your email is a door you forgot you left open. That is the whole maintenance plan. Everything else in this guide is setup you do once.
Bottom line
Freelance security is not about buying expensive tools. It is about closing the obvious gaps: unique passwords with two-factor authentication, a VPN on networks you don't control, an encrypted and updated device, backups that restore, and a plan for the bad day. Set it up once, keep the weekly routine, and get back to the work your clients actually pay for.
Disclosure: this page contains affiliate links. If you buy through them, SaaSNivo may earn a commission at no extra cost to you. Research-based guidance on publicly documented products and practices; this is not a claim of independent hands-on testing.
Explore partner offers
Check the provider’s current pricing, availability and terms before buying.