Security

Your data, used for you alone.

Client data is encrypted and used for that client alone. The software reads it. Before we receive any client data, we will hold each client's data apart from every other client's, never pooled, and limit EagleEye's people to tasks the client approves, recording every access.

Read-only, always.

EagleEye reads. It never pays, posts or changes anything in a client's systems.

  • The connectors send only read requests, to known hosts. The platform never writes to a client system, and never tests access by writing without your written consent.
  • Or no connection at all. A client can send standard exports instead.
  • Nothing EagleEye does can move money.

Encrypted, for one client.

Each client's data is encrypted and used for that client and for nothing else. Before we receive any client data, it will be held apart from every other client's.

  • Never shared, and, before we receive any client data, never pooled with another client's. Only if a client agrees, counts of confirmed findings by kind of check, with no names, amounts or records, help tune the checks.
  • The software runs the checks on it. Before we receive any client data, we will limit EagleEye's people to tasks the client approves, and record every access.
  • Data handling is set in the agreement before anything is connected.

Fixed rules.

The checks use fixed rules and statistics, never AI or language models. Before we receive any client data, the same data will always give the same result. A language model can explain a finding only if a client agrees in writing (privacy policy, section 6).

  • Every finding can be traced to its rule and its source records. Before we receive any client data, every finding will also be repeatable from its recorded inputs.
  • No run by EagleEye lowers or removes a finding. Only your people close one, on the record.

Decided by your people.

The software runs the checks; your own people make every decision.

  • Approve, query, hold, release or close: each by a named person at the company.
  • Certain kinds of finding above a set amount take two people to clear; above a set amount, someone other than whoever confirmed a claim records the money or closes it.
  • Fraud-type items are decided one at a time, on evidence, never in bulk.

Separation of duties, enforced.

The separations are in the software, not in a policy.

  • Whoever sends a payment file cannot release what it holds.
  • Above a set amount, recording money received, or closing a claim, takes someone other than the person who confirmed it.

Every change recorded.

Every approval, query, hold, release and closure is recorded on the finding, by whom and when.

  • The record stays with the finding, from first sight to cash received.
One finding's history line in FinanceEye: Found 3 Oct, Approved 6 Oct, Claimed 7 Oct, Received 21 Oct. One finding's history line in FinanceEye: Found 3 Oct, Approved 6 Oct, Claimed 7 Oct, Received 21 Oct.
Example data. Illustration, not results.

This website.

This site runs no analytics of our own and loads no third-party scripts of our choosing; our web host adds one script of its own, which we are removing. The demo form sends your name, company and work email to EagleEye and nothing else.

Report a security concern to contact@eagleeye.io. The same contact is published at /.well-known/security.txt.

Contact

Request a demo

Twenty minutes on the business, its systems and whether the checks are worth running.

How an engagement runs