Is a mouse jiggler legal, and can you get fired for one?

Owning and installing one is not a crime

A program that moves the cursor is ordinary software. It breaks into nothing, requests no access you were not already given, and reads no data it should not — it simply issues the same mouse and keyboard events any input device would. In most jurisdictions that is not a criminal matter, and nobody is going to court over a cursor that drifts on its own.

The point is easy to confirm. Hardware jigglers — little USB dongles and motorised pads — are sold openly on mainstream marketplaces, shipped worldwide, and marketed by name. A category that were genuinely illegal would not sit next to phone chargers in a shopping cart. The legal exposure most people quietly worry about does not attach to the tool itself.

• No hacking, no unauthorised access, no data theft.
• Hardware versions sold openly on major marketplaces.
• The tool's own legality is rarely the real question.

The real question is your contract, not the criminal code

If there is a consequence to running a jiggler at work, it is almost always disciplinary rather than legal: a conversation, a warning, or dismissal, depending on the employer and on what you signed. The rules that actually matter live in your employment contract, your company's acceptable-use policy, and — for anyone freelancing — the terms of service of the platform you bill through.

Most organisations that use monitoring software also write down how it may and may not be handled. A clause about not tampering with, disabling, or automating monitoring tools is common, and a mouse jiggler can fall under it even when the word "jiggler" never appears. Reading those documents is the whole decision; the criminal code has almost nothing to add.

• Your employment contract and acceptable-use policy.
• Team or company rules on monitoring tools.
• Platform terms of service, for freelance work.

What monitoring and acceptable-use policies usually say

Acceptable-use policies vary, but a few themes recur. They usually reserve the employer's right to monitor company devices, prohibit interfering with security or monitoring software, and require that logged time reflect actual work. A jiggler does not breach the first of those, may breach the second depending on the wording, and only touches the third when it is used to misstate hours.

The practical takeaway is that "am I allowed?" rarely has a yes-or-no answer written for jigglers specifically — it is inferred from broader clauses. If your policy is silent and your manager is relaxed about short breaks, the picture is very different from a policy that explicitly forbids any automation of input. Only your own paperwork tells you which one you are in.

Freelance platforms play by their own rules

On hourly freelance platforms the governing document is the platform's terms, not an employment contract, and those terms tend to be stricter about automated input because billing depends directly on the tracker. Many hourly agreements expect that tracked activity corresponds to work actually performed, and some explicitly prohibit software that generates input to keep the meter running.

Manual time exists for a reason: most platforms let you add hours you worked away from the keyboard, with a note the client can see. That route keeps you inside the terms; automating the tracker to paper over the same gap generally does not. What the platforms care about is the honesty of the record, not the mechanism behind it.

Presence and billed hours are not the same line

There is a real and important difference between keeping a status green and reporting hours you did not work. Holding a messenger presence up while you refill your coffee is, for most employers, unremarkable. Logging a full billed timesheet for a day you spent elsewhere is a different thing entirely, and where pay is tied to a tracked record it can be treated as misrepresentation rather than a policy slip.

This is where consequences escalate from "awkward conversation" toward "clawback or termination for cause", and, in the sharpest cases involving deliberate false invoicing, toward something a lawyer would want to talk about. The tool did not create that line; the claim about hours did. Keeping presence alive during a genuine short break sits on one side of it; inflating a billable record sits on the other.

How it tends to play out by situation

The same tool carries different weight depending on how you are paid and watched. A salaried employee on a team that cares about outcomes has the most latitude; an hourly worker on a strict activity target has less; a freelancer billing through a platform's tracker has the least, because the record is the invoice.

None of this is legal advice, and none of it is fixed — a relaxed policy can tighten, and a strict one can go unenforced for years. Treat the list below as a way to gauge how much the written rules will actually bite, then go and read yours.

• Salaried, outcome-focused team — usually a minor policy question at most.
• Hourly with an activity target — depends heavily on the written rules.
• Freelance, platform-tracked — the timesheet is the payment, so the terms bite hardest.

Being allowed and being noticed are separate questions

Permission is one axis; detection is another, and they do not move together. A tool can be perfectly within your agreements and still stand out in a report, or be quietly tolerated while technically against a policy nobody enforces. It helps to keep the two apart rather than collapsing both into "is it safe?".

On the detection side, modern trackers increasingly look at the shape of input, not just whether it happened. A cursor that repeats one dead-straight path on a fixed timer is exactly the pattern that automated-activity checks are built to flag; input that varies in pace and mixes movement, scrolling and typing reads very differently. The mechanics are covered in the detection write-up linked below — and no honest tool calls itself undetectable.

Where Reaction fits

Reaction is built for one narrow situation: the stretches when you step away from the keyboard but the session should stay alive — the coffee, the stretch, the school run. It keeps a natural, human-like level of presence inside a range you set, using varied cursor motion, a living keyboard rhythm, occasional scrolling and window switches, and it starts only when the computer is genuinely idle and steps aside the instant you touch the mouse.

It cannot, and does not try to, make low-input work look like high-input work while you are actually at the desk doing it — that is a limit of the metric, not a feature. And it does not settle the question this article is about: whether you may run it is still your contract and your tracker's terms. Use it within your agreements.