UTC: 00:00:00
SID: UNAUTHEN...
SYNC_ID: --
ENCRYPTION: ACTIVE (AES-256)
DEFCON: Lvl 4
• LIBR_ENGINE: DETECTED_DIP [$14,500 RECOVERED] • ENTITY_RESOLUTION: FLAGGED_CRYPTO_TRANSFER [COINBASE -> UNKNOWN_WALLET] • INTEL_ANALYSIS: BLOCKED_HOSTILE_TEXT [RISK_LEVEL: HIGH] • ALERT: NEW_OFFSHORE_NODE_IDENTIFIED • SYSTEM_STATUS: ENCRYPTION_ACTIVE (AES-256) • LIBR_ENGINE: DETECTED_DIP [$14,500 RECOVERED] • ENTITY_RESOLUTION: FLAGGED_CRYPTO_TRANSFER [COINBASE -> UNKNOWN_WALLET]
Security Architecture

Security controls for privileged financial evidence.

Exit Protocol is designed around sensitive discovery: encrypted records, role-based access, evidence integrity metadata, audit logs, AI boundaries, and enterprise deployment options for firms with strict data-control requirements.

Last updated: 15 January 2026

security-controls.json MONITORED
EncryptionRecords protected in transit and at rest.
ACTIVE
Integrity HashingEvidence and reports can be tied to hashes.
ACTIVE
Role-Based AccessMatter access scoped by user role.
ACTIVE
Audit LogsImportant actions recorded for review.
ACTIVE
Control Surface

Defense in depth, explained plainly.

No web platform can credibly claim to be unhackable. The practical goal is layered protection, least privilege, reviewable events, and clear escalation paths.

Encrypted Evidence Storage

Uploaded documents and sensitive data are handled through encrypted storage patterns appropriate to the deployment and application layer.

Evidence Integrity Metadata

SHA-256 style hashing can help reviewers verify whether recorded source files and report artifacts appear unchanged.

Bounded AI Processing

AI-assisted drafting and review are kept separate from deterministic tracing calculations that decide forensic balances.

Role-Based Access

Teams can separate intake, review, calculation, administration, and export responsibilities by matter role.

Audit Logging

Important actions such as upload, report generation, export, and access events can be logged for later review.

Controlled Integrations

Third-party integrations use scoped permissions, revocable access, and clear data-handling policies.

Safety Features

Built for sensitive and sometimes unsafe situations.

High-conflict matters can involve coercion, surveillance, or pressure around credentials. Safety features are designed to reduce exposure during risky moments.

Duress Mode

A secondary login path can show a neutral interface instead of sensitive matter data when a user may be under pressure.

Quick Exit

A rapid escape interaction can clear the screen, end the session, and move the browser away from the platform.

Safety features are backups, not substitutes for a safety plan. Users facing immediate danger need local emergency resources and trusted counsel.
Evidentiary Posture

Reviewable evidence beats black-box confidence.

Exit Protocol is designed to support professional review with source references, hashes, calculation logs, and deterministic methodology.

View Warrant Canary

Deterministic Calculations

Core LIBR tracing uses explicit repeatable logic, not generative AI judgment.

Professional Review

Reports are intended for attorney, CPA, expert, or firm review before litigation use.

Sovereign Mode

Enterprise firms can evaluate private deployment with BYOK patterns and reduced external data exposure.

Clean Exports

Generated packets avoid hidden revision history and preserve a cleaner source-to-report path.

Security Review

Need firm-level diligence?

Review the enterprise spec sheet or contact the deployment desk for data residency, access control, logging, and private deployment questions.

Protected Content Copy, cut, and right-click export actions are disabled on this site.