Anonymity

Anonymity that is architecture, not a promise.

The moment a report is submitted, identity is stripped at the network edge and replaced with a case key. There is no administrative function — for you or for OSIT — that can resolve a key back to a person.

Book a 45-minute demo Request a quote

Edge

Zero-trace intake

Source IP and device fingerprints are discarded at the edge, before any application service can observe them.

Design

Case-key follow-up

Reporters track status and answer questions with the key alone — no login, no phone number, no trace back.

Dialogue

Sealed two-way messaging

Investigators and reporters converse for as long as the case needs, with identity cryptographically sealed.

Choice

Three reporting modes

Anonymous, confidential or identified — chosen by the reporter per case, on every channel.

Guarantee

No unmasking function

The case key is generated client-side of any identity store. Unmasking is not restricted — it is impossible.

Architecture

Trust boundary in hardware

Above the boundary nothing identifying is kept; below it every action is attributed and audited.

Questions we hear first.

Is anonymous reporting really anonymous?

In Raqeeb, yes — anonymous reports carry no IP address, no account and no device identifier, and the case key cannot be resolved back to a person by any function in the product.

How do reporters get updates without an account?

With the case key issued once at submission. Entering it shows case status and any questions from the investigation team — answerable without revealing identity.

Why does anonymity matter for report volume?

Employees and vendors only report when anonymity is credible. Organisations with trusted channels detect fraud significantly faster, and tips remain the number-one detection method worldwide.

See it in the product

Try the reporter experience → How identity is severed →

Related solutions: Whistleblowing System Case & Investigation Management Ethics & Compliance Platform