dayFlow

Spoof and proxy protection

Catch the four usual ways attendance is faked

Attendance fraud usually means one of four things: a fake location, a photo of a photo, a colleague clocking in for you, or a changed phone clock. dayFlow checks for each and sends what looks wrong to one review queue.

  • Fake locations and weak signals
  • Photos of photos and replayed pictures
  • Someone else clocking in for you, or a changed clock
4 kinds of fraud
location, photo, proxy, clock
1 review queue
everything doubtful in one place
Evidence kept
photo, score and decision

In plain words

What is spoof and proxy protection?

Attendance fraud is usually one of four things: a fake location, a photo or screen held up to the camera, a colleague clocking in for you (a proxy), or a phone clock set to the wrong time. Each is cheap to try and each is hard to prove after the fact.

dayFlow checks for all four when the punch arrives, not at month end. Anything suspicious is recorded, not discarded, and put in one review queue with the evidence beside it, so honest mistakes can be cleared quickly and real fraud is visible.

What you get

Spoof and proxy protection, feature by feature

Location that has to be true

The position is judged against the work area together with its accuracy. Mock-location apps are detected, and punches from a place the person is not assigned to are flagged.

In practice

  • Mock-location detection
  • Outside-area and unassigned-location flags
  • Optional hard block outside the area

A face that has to be live

Selfies are checked for signs of a photo or a screen, and for being an exact copy of an enrollment picture. A face that belongs to someone else does not match.

In practice

  • Live-person and replay detection
  • Match against the person's own face
  • One face cannot be registered for two people

A clock that has to agree

The phone's time is compared with the server's. A large difference suggests the clock was changed to make a punch look earlier or later, and the punch is flagged.

In practice

  • Phone clock compared with the server
  • Offline punches keep their real time
  • Large differences flagged for review

One queue, with evidence

Everything doubtful lands in the exceptions list with the reasons, the selfie and the registered face. A manager accepts or dismisses; a dismissed punch no longer counts towards hours.

In practice

  • Reasons shown with each exception
  • Accept or dismiss, recorded by name
  • Open exceptions block approval of the day

The difference

What changes when you use it

Without dayFlow

With dayFlow

You find out at payroll, if at all

Each punch is checked when it arrives

Suspicions are argued

The queue shows the evidence beside the punch

One check is easy to beat

Location, face and clock are checked together

Examples

How teams use it

  • Example 1

    A supervisor who suspects buddy punching

    She opens exceptions on Monday and sees two mismatches from the same gate. The photos show the same person clocking in for a colleague.

  • Example 2

    A fake-location app

    A worker uses an app to appear at the site. The punch is flagged as a mock location and the manager sees it before approving the week.

  • Example 3

    An honest mistake

    A worker's phone clock was wrong after a battery change. The punch is flagged, the manager sees the explanation and clears it in seconds.

The details

What you can set

Location checks
Work area, accuracy, mock-location, assigned location
Face checks
Match, live-person, replay, photo quality
Clock check
Phone time against server time
Outcome
Recorded, flagged, and listed in the review queue
Review
Accept or dismiss, with the decider recorded
Evidence kept
Doubtful selfies only, for a limited time

How it works

Up and running in three steps

  1. 1

    Each punch is checked when it arrives.

  2. 2

    Anything suspicious becomes a review item with the evidence.

  3. 3

    A manager accepts or rejects it, and the day updates.

Who it is for

Made for teams like these

  • Companies that have met buddy punching
  • Operations with unsupervised sites
  • Clients who audit supplier hours
  • Anyone who wants proof, not trust

Part of a whole

How it fits with the rest of dayFlow

The protections are the same checks described on the face and location pages, collected into one place: a single review queue that must be cleared before a day can be approved.

Questions

Things people ask

Does a suspicious punch block the worker?

Not unless you chose to block outside-area punches. Otherwise it is recorded and sent for review so honest mistakes are not punished.

Can a phone with a wrong clock cheat?

The phone's clock is compared with the server's; a large difference is flagged.

Who sees the review queue?

Managers with the right to decide exceptions, for the employees they look after.

Will honest workers get blocked?

Only if you choose to block outside-area punches. By default doubtful punches are recorded and reviewed, so a mistake costs a minute of a manager's time, not a day's pay.

Can fraud be completely stopped?

No system can promise that. dayFlow makes the common methods hard and visible, and keeps evidence so you can act on them.

Who can see the review queue?

Managers with the right to decide exceptions, for the employees they look after.

What happens to a rejected punch?

It stays on record but no longer counts towards the person's hours.

Try Spoof and proxy protection with your team

Set up your locations, register faces and let your team clock in. Your company gets its own address.