TERA SIGNATURE

Sign with confidence.
Verify with evidence.

Upload a PDF or Word document, invite partners, track every signing event, and preserve verifiable evidence under TERA.

Human intent remains the gate. AI is optional and cannot apply a signature.

PDF + WordUpload what you already use Preview firstReview before anyone signs Human controlledNo automatic signature Evidence preservedActions stay accountable

Accepted documents: PDF · Word (.docx)

Trustworthiness

Efficiency

Reliability

Accountability

TERAAssurance

WORKFLOW

Partner signatures

EVIDENCE

Timeline

VERIFICATION

Verification status

T

TERA AssuranceTrustworthiness, Efficiency, Reliability, and Accountability guide every signing workflow.

WORKFLOW

Signature requests

See who has received, opened, and signed each document. Time is visible as part of the evidence.

Status Search

PREPARE

Create a signature request

Prepare the document, define each participant, choose the signing order, and set a signing deadline that matches the agreement or workflow.

1

Document

TERA records SHA-256 fingerprints for the source document and controlled signing copy before any invitation is created.

Upload your document Drag and drop your file here, or choose a file. PDFWord .docx Accepted formats: PDF or Word (.docx) · Up to 25 MB Choose file

Using Word?TERA first tries to prepare an Office-rendered PDF signing copy. If Office rendering is unavailable, your Word document stays accepted and you can attach a PDF exported from that same Word file. Your original Word file remains unchanged.

Request title Purpose

2

Participants

Every participant receives an explicit role and evidence trail.

Each partner can receive the signing experience in English or French. Secure access code verification is the default browser workflow.

3

Timing and order

The request owner controls the signing deadline. Verification codes expire separately after 10 minutes and do not shorten the signing window.

ParallelEveryone can sign as soon as the invitation is available. SequentialEach participant signs after the previous participant completes.

Signing deadlineChoose the date and time agreed for this request. Your browser uses local time; TERA records the normalized timestamp.No signing deadlineThe request remains active until completed, cancelled, or participant access is revoked. One-time verification codes still expire after 10 minutes. Document owner

ASSURANCE PATH

TERA Evidence Assurance

TERA records document integrity, signer intent, review decisions, timing, signature evidence, and chained workflow events. Connected mode adds secure partner access, shared workflow state, and server-backed evidence. Certificate-backed PDF signing remains an optional higher-assurance capability when configured.

Human controlledSHA-256Explicit consentPortable evidence

DOCUMENTS

Document evidence

Every request begins with a document fingerprint. TERA keeps the hash visible so integrity can be checked later.

PARTNERS

People in your workflows

Roles, request counts, and signature timing remain visible across your local workspace.

VERIFY

Verify a document

Check a document against TERA evidence without relying on AI. The verification result reports each evidence layer separately.

Verification inputs

DocumentTERA calculates SHA-256 locally in your browser. TERA evidence recordUse an exported evidence record or signed response.

No verification run yet.Choose a document and evidence record to compare their integrity data.

SIGNING ACCESS

Simple for people. Strong underneath.

TERA handles document fingerprints, access evidence, consent, and timing. People should not need to operate cryptography to sign responsibly.

YOUR SIGNING IDENTITY

How you appear when you sign

Display name Email

Human controlledYour signing identity is used only when you explicitly review, sign, release, or confirm an accountable action.

DEFAULT PARTNER ACCESS

Secure link + verification code

TERA creates a private signing invitation for each partner. The partner confirms access before reviewing and signing. The verification code confirms access to the signing session. It is not the signature and does not by itself prove identity.

RecommendedNo certificate knowledge required

No account required
Private signing link
One-time verification code
Explicit review and consent
Review signed document before submission
Time-limited signing access

Connected deliveryTERA can create secure partner signing sessions and shared workflow state. During deployment testing, invitation delivery can remain in controlled log mode until outbound email is enabled. Manual portable delivery remains available as a fallback.

Higher assurance options

Certificate-backed signing

Use an organization signing certificate only when a workflow requires it.

Signing certificateSecure signer file (.pfx or .p12)Certificate passwordThe password is never stored by this browser application.

FormatPKCS#12 (.pfx or .p12)Browser capabilityFile readiness onlyCryptographic PDF signingRequires connected signing service

ACCOUNTABILITY

Activity and evidence timeline

Every recorded event carries a time and integrity link to the prior event in its request.

SETTINGS

Local-first by default

TERA Signature works without AI. When deployed with the TERA connected service, secure invitations, expiring codes, shared signing state, revocation, and server-sealed evidence are enabled.

CORE

Browser workspace

Application entryindex.html

Local persistenceBrowser storage

Document storageIndexedDB

IntegrityWeb Crypto SHA-256

AI requirementNone

CONNECTED SERVICES

Deployment service

Service statusChecking deployment service...

Secure invitationsAutomatic email delivery with short-lived access codes when connected.

Shared stateServer-enforced deadlines, sequential order, revocation, and partner status.

Owner notificationsCritical events can notify the request owner when a remote participant signs, delivery fails, the workflow completes, or the Evidence Seal is created.

TERA Evidence SealCompleted workflows can receive a server-authenticated evidence seal after final owner review.

Certificate-backed PDF signingHigher-assurance path remains separate unless explicitly configured.

AI assistanceOff. Core signing and verification do not require AI.

PORTABILITY

Import and export

Move evidence between people without a central server.

TERA

Assurance principles

TrustworthinessEvidence says only what the system can establish.

EfficiencySimple signing flow with portable partner exchange.

ReliabilityStable hashes, event chains, and explicit states.

AccountabilityRoles, consent, timestamps, and actions remain visible.

Sign with confidence.
Verify with evidence.

Partner signatures

Timeline

Verification status

Signature requests

Create a signature request

Document

Review your document

Participants

Timing and order

TERA Evidence Assurance

Document evidence

People in your workflows

Verify a document

Verification inputs

Simple for people. Strong underneath.

How you appear when you sign

Secure link + verification code

Certificate-backed signing

Activity and evidence timeline

Local-first by default

Browser workspace

Deployment service

Import and export

Assurance principles

Confirm your signature

Review exactly what partners will receive

Review & Release could not complete

Partner access code generated

Review the completed PDF before sealing.

Review the signed document before confirming

Review your signed document

Sign with confidence.Verify with evidence.

Partner signatures

Timeline

Verification status

Signature requests

Create a signature request

Document

Review your document

Participants

Timing and order

TERA Evidence Assurance

Document evidence

People in your workflows

Verify a document

Verification inputs

Simple for people. Strong underneath.

How you appear when you sign

Secure link + verification code

Certificate-backed signing

Activity and evidence timeline

Local-first by default

Browser workspace

Deployment service

Import and export

Assurance principles

Sign with confidence.
Verify with evidence.