Your mouse jiggler got flagged. What happens next

A flag is usually a report, not a person

Most flags come from an automated anomaly report rather than a manager watching your screen in real time. Time Doctor 2, for example, has an Unusual Activity Report that marks monotonous clicking and mouse movement with no clicks; other trackers run similar pattern checks. An entry in that report and a conversation with your manager are two separate events, and the second does not automatically follow the first.

This matters because the emotional weight of the word "detected" usually outruns what actually happened. A row in a weekly report is data waiting to be read, not a decision that has been made. Whether anyone ever opens it, and what they conclude, depends on how closely your team reviews those reports at all.

Why the pattern got flagged

Anomaly detection generally looks for input that behaves too regularly to be human. A hardware dongle or a basic jiggler repeats one short path on a fixed timer, so every sampled interval looks identical: the same motion, the same spacing, no pauses, often no clicks at all. That evenness is the signature — real hands never move that consistently.

A flat activity line pinned near 100% for hours works the same way. Nobody produces input in every sampled moment of every interval, so a report that never dips reads as automation rather than diligence. The mechanics of how detection reads these patterns are covered in the detection write-up in the related links.

• One repeated path on a fixed interval.
• Movement with no clicks, or clicks with no movement.
• A line held flat near 100% with no natural dips.

What is already fixed and cannot change

Recorded data stays recorded. No app — Reaction included — can delete intervals from a tracker's history, withdraw a flag that already exists, or roll back a report that has been generated. The screenshots and input logs live on the employer side, outside anything you control.

So the honest framing is not "how do I erase this" but "how do I stop generating it." The old data is history; the only thing still open is the pattern you produce from now on.

• Past intervals stay in the tracker database.
• A raised flag cannot be withdrawn from your side.
• Screenshots and input logs live on the employer side.

Read your own situation before you react

Before assuming the worst, work out which event you are actually facing. A line in an automated report that nobody has mentioned is very different from a manager asking you about your hours. Reread your contract and any acceptable-use policy so you know what you agreed to, and check whether your pay is tied to a tracked timesheet — that distinction changes how seriously a flag is treated.

Rushing to explain something no one has raised can create a problem that did not exist. Understanding the metric and the report first lets you respond to what is real rather than to your worst guess.

What genuinely changes from here

The one thing still in your hands is the pattern going forward. A dongle repeats one path forever; varied input has no fixed period, so it stops producing the specific signature that triggers these reports. A presence app that changes its behaviour constantly does not leave the identical-interval trail a mechanical device does.

Reaction, for instance, moves the cursor along changing curves, mixes in navigation keys, occasional scrolling and window switches, and holds a set activity band instead of a flat 100%. The point is not a higher number — it is a line that varies the way a person's does, with the dips and rises real work contains.

• Vary path, speed and pauses instead of one repeated motion.
• Hold a realistic band, not a perfect score.
• Give control back at the first touch of the mouse.

The employment side

Whether a flag leads anywhere is decided by company policy and your contract, not by the technology. Most consequences in this area are disciplinary rather than legal — a conversation, a warning, or in some cases dismissal — and the outcome depends far more on what you agreed to than on which tool produced the pattern.

There is also a line worth knowing: keeping a status alive during a break is not the same as reporting hours you did not work. Where pay is tied to a tracked timesheet, inflating that record can be treated as misrepresentation rather than a policy matter, so keep any use of a presence tool inside your actual agreements.

If it does come up in conversation

If a manager raises it, the useful move is context, not denial. Your own timeline is evidence: quiet stretches that line up with meetings, reading or breaks explain themselves once someone can see them. Speak to what the report shows and what your work actually was, rather than arguing with the number in the abstract.

Where Reaction fits

Reaction sits in one narrow place: 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 within 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 moment you touch the mouse.

It cannot delete a report that already exists, and it cannot make low-input work look like high-input work while you are actually at the desk — those are limits of the record, not features. What it does is stop a normal break from reading as a dead, mechanical gap. Use it within your agreements; see the acceptable-use note in the related links.