DBATR Enterprises · trust layer

Digital notarization, certified identity, verified process

Everything we build moves faster than paper — so the proof has to move with it. One signer is certified once, every signature is captured with consent on the record, every finished document is sealed against tampering, and anyone holding the file can verify it without an account, a fee, or a phone call.

Free to families, always. 💎 the global standard.

The gates automation never touches

The six stages of a verified signature

  1. 01

    Identity certification

    Before a signature means anything, the signer is certified once: government ID checked against a live capture, name and role bound to a DBATR credential, and a certificate issued that can be verified by anyone holding the link.

    Proof kept: Certificate ID + issue date + verifying page

  2. 02

    Consent on the record

    The signer sees exactly what they are signing, who receives it, how long it is kept, and what happens if they withdraw. Consent is captured as its own signed artifact — never buried in a checkbox.

    Proof kept: Signed consent artifact, revocable in writing

  3. 03

    Signing session

    Documents are signed electronically under E-SIGN and UETA, and for anything requiring an oath, through a commissioned remote online notary with the audio-video session recorded end to end.

    Proof kept: Session recording + notary commission number

  4. 04

    Seal & tamper evidence

    The finished document is hashed, the hash is written to an append-only log with a trusted timestamp, and the seal travels with the file. Any later edit breaks the hash and shows up immediately.

    Proof kept: SHA-256 hash + timestamp + append-only log entry

  5. 05

    Verification anyone can run

    A court clerk, a partner, a hospital, or a family member can drop the file on the verify page and get a plain answer: who signed, when, under what identity certificate, and whether it has been altered since.

    Proof kept: Public verify link, no account required

  6. 06

    Archive & audit trail

    Every artifact — certificate, consent, recording reference, hash, and delivery receipt — is retained together as one evidence bundle that can be exported for filing or handed to an auditor.

    Proof kept: Exportable evidence bundle

What we certify — personal and professional

Personal identity

This is really the person they say they are.

Government ID + live capture + one-time code to a verified phone or email.

Retained: Certificate reference and match result. No ID images stored after the check.

Professional identity

This person really holds the license or role they are signing under.

Licence or registration number checked against the issuing board, plus employer or practice confirmation in writing.

Retained: Licence number, issuing body, status, and check date.

Authority to bind

This person can actually sign for the organization.

Signed authority statement naming the entity, the title, and the scope of what they may commit.

Retained: Authority statement as a signed artifact.

Process verification

The document itself has not changed since signing.

Hash + trusted timestamp + append-only log, verified on demand.

Retained: Hash and log entry — forever, so old files stay checkable.

Permanent prohibitions