Personal Notes on a Work Laptop | Keep Them Off the Company Network

Eight hours a day on a company laptop, and the line goes soft. A side project idea arrives during a dull call. A plan for the holiday. A journal entry you would rather nobody read. It all ends up on a screen that belongs to someone else, and the question is what happens to it afterwards.

What a work setup can actually see

The network. Traffic usually runs through the company's own gateway. Web tools like Notion, Trello or Google Docs are requests going out through it, and requests get logged: which service, when, how often, and sometimes what.

The shared workspace. A private page inside the company Notion, Confluence or Asana is private from colleagues, not from administrators. Workspace admins can read what is in the workspace, whatever the folder permissions say, and an export of everything is two clicks for them.

Sync, in the background. Signing into your own Evernote or Apple Notes account on a work machine keeps a local cache and a steady stream of sync traffic. Both leave a trail even when you have closed the app.

What local-first changes

A local-first app keeps notes, tasks and settings on the disk in front of you rather than on a server. On a work machine that changes three things.

There is no traffic to log. An app that does not need the internet does not send anything through the gateway. Nothing is intercepted because nothing is sent.

There is no workspace admin. No account, no shared space, nobody with a key above yours.

It leaves with you. Markdown files copy to a USB drive and open anywhere. When the laptop goes back, the notes do not go with it.

The part no app fixes

A work computer is not yours, and it is worth saying so plainly. If the company installs monitoring on the machine itself, it can read files on disk, take screenshots or log keystrokes, and a local app is as visible to that as anything else. Local-first removes the network trail and the third party; it does not turn someone else's laptop into your private device.

The honest boundary: keep anything you would genuinely not want seen on hardware you own. Everything else, the side project, the reading list, the plan for Saturday, is the case local-first handles well.

A quiet setup that works

Markdown for capture. An idea in the middle of a call needs a keystroke, not a menu. Type it, format it with a dash and two asterisks, move on.

A board for the side project. Learn a language, plan an anniversary, run a freelance job. Cards move without anyone being notified, because there is nobody to notify.

Reminders that stay on the machine. A cloud app can throw a push notification onto the screen in the middle of a shared window. A local reminder does not travel, and it does not announce itself to a meeting room.

Where TaskNote fits

Ours, so read it as such. The Windows app runs with no account at all: notes, boards and reminders live in a folder on your disk, nothing is sent anywhere, and there is no sign-up to explain. A global hotkey opens a new note over whatever you are doing, and the line you write becomes a card on the board when it turns out to be a task.

One thing we will not claim: the desktop database is a plain file, not an encrypted vault, so it protects you from the network and from a shared workspace, not from someone with access to the machine. If you want encryption, that is the web app, where notes are encrypted on your device before they reach us and the key stays with you. Choosing between the two is a question of which risk you actually have, and the honest answer is usually the first one.

The short version

Personal thinking on a work laptop is normal. Doing it inside the company's tools is what makes it visible. A local-first app gives you a quiet corner on that desktop: no account, no sync, no trail through the gateway, with the limits of the machine itself stated out loud.