notific.me

Security and proof

The heavier the decision, the stronger the proof.

Each request sets how much proof the answer needs, and every answer leaves a record that can be checked.

Request early access

Verification levels

How much proof an answer needs

LevelWhat the person doesGood for
0One tapAcknowledgements and low-risk choices
1Answers from an unlocked phone or a signed-in sessionRoutine approvals
2Biometrics or the device passcode in the app, or an authenticator code on the webDeploys, refunds, an AI agent that wants to act
3Biometrics or a fresh authenticator code for each action, online and within a short windowMoney, production access, deleting data

Whoever asks sets the minimum level. The organization can raise it, never lower it.

Guarantees

What the server enforces

  • One answer, accepted once

    The server is the only authority. It accepts exactly one valid answer per request, and a repeated submission runs once.

  • Deadlines are real

    Expired requests and outdated versions are refused, and the person is told why.

  • Nothing sensitive offline

    Level 3 answers are never accepted offline.

  • Lost phone, revoked device

    Disconnect a device from the panel and its sessions end at once.

The record

Every answer keeps its signature

Who answered, when, how they confirmed and from which device, next to the answer itself.

An approved purchase order in the web app with the answer and the signature details: answered by, when, how and device.
An approved purchase order with the note the approver left and the signature panel.

Electronic signature

A visible signature, when the request asks for one

The person adopts a signature once: their name in a handwriting style, or drawn, plus initials. A request can require it on top of the verification level, and the receipt carries it.

A signed agreement in the web app: the answer, the “Signed electronically” block with signature and initials, and who answered, when, how and from which device.
A services agreement signed by the CFO: the signature, the initials and the record of how it was confirmed.

Evidence trail

A trail that can be checked

  • From delivery to decision

    Created, sent, delivered, opened, answered: each step is recorded with the person, the device and the time.

  • Chained records

    Each record carries the hash of the one before it, so a change in the middle breaks the chain and shows.

  • A signed receipt

    Export a receipt signed by the server and verify it with the published public key, without access to notific.me.

  • Signed replies to your systems

    Webhooks carry an Ed25519 signature that your code verifies in one call.

Coming soon: face verification for the heaviest decisions.

Be among the first teams to use it

Tell us what you want to unlock. It helps us decide who to invite first.

Request early access