The operating rules for Exit Protocol accounts, forensic reports, integrations, payments, and professional review responsibilities.
By creating an account, accessing, or using the Exit Protocol platform ("Service"), you agree to be bound by these Terms of Service ("Terms"). If you do not agree to these terms, you must not use our Service.
We reserve the right to modify these terms at any time. Material changes will be communicated via the email address associated with your account. Continued use of the Service after notification constitutes acceptance of updated terms.
The reports, graphs, calculations, and narratives generated by this Service are for informational and organizational purposes only. The LIBR engine implements a selected tracing model over reviewed records and documented assumptions. Whether that model fits a matter is jurisdiction- and fact-dependent, and the output does not replace a qualified attorney or forensic accountant.
You acknowledge that:
Exit Protocol's core LIBR tracing engine operates on deterministic mathematical processing applied to reviewed ledger rows and explicit source records. The LIBR engine enforces the selected formula St = min(St-1, Bt), where St is the traceable separate property on day t and Bt is the modeled account balance. Exact-byte SHA-256 comparison and local record-grouping or rule-based review signals are also deterministic, but those signals do not establish identity, ownership, concealment, wrongdoing, or a legal conclusion.
Separately, optional communication scoring or rewriting and transaction/message contradiction review may use a configured external language-model provider. The request can contain selected message text and metadata or selected transaction date, description, and amount. Provider and model selection are deployment-dependent. These probabilistic outputs are preliminary review aids that must be reviewed by qualified human professionals. The current automated legal-strategy, narrative, cross-examination, and judicial-simulation web routes are retired and fail closed.
The Service includes deterministic calculations, local record-organization tools, and optional model-assisted review tools. Each path has specific limitations you must understand.
The document extraction pipeline uses native PDF text extraction where available. Extracted rows are presented for human review before import. For scanned statements, a local OCR runtime may be used only when configured in your deployment; optional cloud OCR via Azure Document Intelligence requires explicit enablement and user acknowledgement. OCR may misinterpret characters (e.g., reading a "6" as an "8") on poor-quality scans. You explicitly agree to audit all extracted financial figures against original source documents. We are not liable for calculation errors resulting from OCR inaccuracies or incomplete statement coverage.
The core tracing engine applies the selected Lowest Intermediate Balance Rule strategy to reviewed ledger rows and explicit source records. Under that deterministic model, later deposits do not restore a depleted traceable cap unless a separately documented source is explicitly modeled. The output requires a qualified professional to validate source characterization, statement coverage, transaction accuracy, and jurisdictional fit.
The current automated legal-strategy, narrative, cross-examination, and judicial-simulation web routes are retired. Stored legacy drafts, local record summaries, or a separately enabled future drafting path must be treated as review-required organizational material, not a statement of fact, legal argument, filing, expert report, or prediction of a court outcome.
When a user starts the optional review and an external model provider is configured, the service can compare a selected set of imported withdrawal transactions with nearby stored case messages. Transaction date, description, amount, message text, sender, and time metadata may be transmitted to that provider. A saved result is a preliminary model-generated review signal, not a comparison against a sworn affidavit, proof of inconsistency, proof of perjury, or an expert finding. The source records and context must be independently reviewed before any reliance.
The relationship graph groups imported transaction descriptions and account records, then aggregates apparent flow direction, amount, and frequency. Keyword, velocity, circular-flow, and pass-through labels are heuristic review signals. The graph does not resolve a legal entity, identify a beneficial owner, verify a destination account, or establish concealment without independent source investigation.
The current service does not include a live bank feed or continuous transaction monitoring. Stored alert rows may come from an authorized, separately invoked batch rule, administrator action, or synthetic demo seed. Any displayed large-transfer, keyword, cryptocurrency, or gambling label is a heuristic review prompt that may be incomplete or wrong. It is not evidence of dissipation, hidden assets, misconduct, or wrongdoing.
The Shadow Report inspects the underlying layer structure of uploaded documents to detect ghost text layers (unflatted redactions), embedded XMP metadata (author, creation timestamps, producer software), and EXIF data in embedded images (GPS coordinates, camera models). This analysis is best-effort and does not guarantee detection of all hidden content or data leakage.
Evidence files and selected sensitive database fields are encrypted at rest using application-layer encryption appropriate to the deployment. SHA-256 hashing provides integrity references for uploaded documents and generated exports — useful for reviewers to check whether recorded bytes appear unchanged since ingestion or export. However, your data security ultimately depends on your management of credentials.
The "Duress Password" feature is provided "as-is." While designed to protect user safety by loading an alternate environment, we cannot guarantee it will withstand all forensic examination scenarios.
Current case access uses active case-party memberships and per-case permission flags for financial records, communications, and evidence. Labels such as Paralegal, Forensic Accountant, and Auditor are case-level labels; they do not create firm-wide roles or an organization tenant. An individual user profile can carry an optional IP/CIDR allowlist that restricts that profile's requests when configured. The current product does not provide firm or organization tenant administration, delegated administrators, centralized invitations, or firm-wide offboarding. Operators remain responsible for directly managing each case membership and user profile.
Selected application events generate operational audit records. These records are not represented as cryptographically immutable or storage-enforced WORM logs. Any external SIEM forwarding must be separately configured and validated.
A containerized self-hosted deployment may be available under a separate agreement. Network isolation, key custody, backups, telemetry, optional cloud providers, and support access must be defined for that deployment. Docker alone does not create an air gap.
Exit Protocol may allow user-authorized connections to configured third-party services. The current Clio workflow uses OAuth 2.0 and remains limited to the scopes and user-selected matter/document behavior described below.
Exit Protocol is not a law firm. Outputs are attorney-reviewable workpapers, not legal advice, formal opinions, or guarantees of court admissibility, legal outcome, or forensic acceptance. You must have the authority to connect the Clio account, select the matter, and choose the document. Exit Protocol is an independent application and an independent third-party application; it makes no claim of Clio endorsement, certification, or public App Directory listing.
The current pilot workflow uses user-selected document and CSV imports. A live Plaid bank-monitoring connection is not part of the current production service representation. Imported and extracted rows require user review and reconciliation against source records.
Exit Protocol is not responsible for outages, data losses, or API changes caused by any third-party provider. Our liability is restricted solely to the data once it has been securely received within our platform.
Public self-service checkout and payment acceptance are currently disabled. This page does not offer a paid subscription, fixed-price report, freemium entitlement, refund promise, or production-service commitment. A public account or synthetic demo session does not create a right to use the platform with client data.
Any non-demo access must be approved under a written controlled-evaluation agreement. The supported V1 evaluation scope may include only the functions expressly enabled for that evaluation, such as:
Pricing, term, authorized users and matters, data classification, support, retention, security responsibilities, external providers, workpaper-use rights, suspension, termination, refunds, self-hosted deployment, and any production transition must be set out in a signed agreement. In a conflict, that agreement controls. No marketing page, demo, generated file, or unsigned email creates a commercial license or service level.
Exit Protocol provides a "Demo Sandbox" populated with synthetic financial data, allowing attorneys and pro se litigants to test the platform's capabilities without making any financial commitment. The Demo Sandbox:
You agree not to use the Service for:
We reserve the right to terminate accounts found violating these prohibitions without refund.
The usefulness of a tracing workpaper depends on complete, accurate, and lawfully obtained source records. You agree not to alter records, misstate provenance, or intentionally omit known statement periods in order to manipulate an output.
Automated metadata and structural checks are best-effort review signals and do not determine intent or authenticity. Suspected misuse may be reviewed and access may be restricted under the applicable agreement. Prohibited conduct includes:
TO THE MAXIMUM EXTENT PERMITTED BY LAW, EXIT PROTOCOL SHALL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR ANY LOSS OF PROFITS OR REVENUES, WHETHER INCURRED DIRECTLY OR INDIRECTLY, OR ANY LOSS OF DATA, USE, GOODWILL, OR OTHER INTANGIBLE LOSSES.
IN NO EVENT SHALL OUR AGGREGATE LIABILITY EXCEED THE AMOUNT YOU PAID FOR THE SERVICE IN THE TWELVE (12) MONTHS PRECEDING THE CLAIM.
The Service does not currently expose a complete self-service case or account deletion workflow. Requests are handled manually after identity, authority, legal holds, preservation duties, and deployment storage are reviewed.
Application records, stored files, historical orphan objects, and backups have separate lifecycles. Any deletion and backup schedule must be documented for the applicable deployment. Do not rely on a request as a substitute for counsel-directed preservation, production, or legal-hold obligations.
You may submit an account or data deletion request by contacting legal@exitprotocols.com. Requests remain subject to eligibility, identity and authority verification, applicable retention and preservation duties, legal holds, security requirements, backup schedules, and deployment constraints.
Exit Protocol or its applicable licensors claim rights in the platform's original source code, tests, templates, user-interface expression, documentation, branding, and specific implementation details. These Terms do not claim ownership of the Lowest Intermediate Balance Rule doctrine, underlying mathematical concepts, case law, professional standards, or other public-domain methods.
You retain full ownership of all data you upload to or create within the Service. By using the Service, you grant Exit Protocol a limited, non-exclusive license to process your data solely for the purpose of providing the Service to you.
Protected platform materials include original code, tests, templates, interface assets, documentation, and the specific expression and arrangement of implementation details. Exit Protocol does not claim ownership of LIBR as a legal doctrine or mathematical concept, any court's reasoning, or generally known tracing and accounting methods.
Exit Protocol is designed to organize forensic tracing work into attorney-reviewable workpapers with visible methodology, source references, and integrity metadata. Forensic practitioners may use analytical tools when they understand the methodology and maintain control over working papers — but the platform does not substitute for practitioner judgment, professional-standards review, or expert foundation work. Exit Protocol does not claim that using the platform establishes SSFS compliance.
Law firms may export Exit Protocol data packages to licensed CPAs, forensic accountants, or retained experts. Those professionals must review automated findings, validate OCR accuracy and source coverage, and decide whether and how to rely on outputs in their own work product. Exit Protocol does not guarantee acceptance by opposing counsel, courts, or regulators.
The deterministic LIBR calculation applies transparent, testable, and repeatable rules to reviewed structured data. Local grouping and rule-based review signals are heuristics, while optional model-assisted outputs are probabilistic drafts. Admissibility, evidentiary weight, and filing suitability are decided by individual courts and retained professionals in each matter. Exit Protocol makes no guarantee of admissibility or legal outcome in any jurisdiction.
These Terms are intended to be interpreted under applicable law and the jurisdiction designated in the final signed agreement between the parties. If no separate written agreement exists, disputes should first be addressed through good-faith written notice and commercially reasonable efforts to resolve the matter before formal proceedings.
Contact: For questions about these Terms, contact us at legal@exitprotocols.com.