Privacy Policy

Scope and roles

This policy describes how ForensicTrail handles information in its public website and authenticated financial-analysis service. A customer organization controls the case material its users upload. ForensicTrail processes that material to provide the service and operates account, security, support, and billing records for the service.

Information we handle

• Account and membership information, such as name, email address, role, organization, and authentication identifiers.
• Case evidence and work product, including uploaded financial, tax, brokerage, credit-report, family, and court-related documents; extracted text; transactions; classifications; notes; prompts; outputs; and audit history.
• Operational information, such as tenant, case, file and job identifiers; request metadata; security and access events; diagnostics; and server-access logs.
• Public-site inquiries submitted through the demo or contact forms.

How information is used

We use information to authenticate users, isolate organization data, process evidence, provide analysis and work product, operate and secure the service, troubleshoot failures, respond to support requests, maintain audit trails, and administer the customer relationship. Automated outputs are review aids; the service does not determine admissibility, legal conclusions, or professional opinions.

AI and document processing

Depending on the enabled feature and deployment configuration, case information may be sent to OpenAI or Anthropic for language-model processing and to Microsoft Azure Document Intelligence for document extraction. Requests to OpenAI are configured with store:false, but ForensicTrail does not currently claim Zero Data Retention or a no-training contractual term. Provider retention and training terms must be confirmed against the agreements actually executed for launch.

• Some calls can contain full statement content or case data; others contain transactions, document layouts, or selected fields.
• The live C# extraction, classification, and assistant paths do not currently anonymize all information before provider calls.
• Current providers and purposes are listed on the Subprocessors page.

Storage, encryption, and access

Application data is stored in AWS. Tenant-scoped API routes require an authenticated membership check. The primary evidence bucket is private, versioned, and encrypted at rest with a dedicated customer-managed AWS KMS key; protected identifiers use their existing separate KMS boundary. Encryption and access controls reduce risk but do not guarantee that a security incident cannot occur.

Retention and deletion

Active case records and source evidence remain available according to the customer workflow and applicable subscription retention settings. Case deletion removes live application data and current objects through an auditable workflow, but retained object versions, audit history, backups, and logs can remain for their configured periods.

• DynamoDB point-in-time recovery can retain recoverable history for up to 35 days.
• Superseded or deleted source-evidence versions can be retained for seven years unless an approved purge removes them.
• Derived outputs and intermediate artifacts have shorter lifecycle periods, generally 7, 90, or 365 days depending on the prefix.
• S3 access logs are configured for 365 days; API Gateway access logs for 90 days. Some Lambda log groups do not yet have an explicit deployment retention setting.
• Tenant deletion removes attributable live rows and owned object versions, but does not promise immediate removal from backups, logs, another tenant's data, or ambiguous legacy records.

Disclosure and subprocessors

We disclose information to infrastructure, document-processing, and model providers as needed to operate the service; to a customer's authorized users; and when required by law or necessary to protect the service and its users. We do not present customer evidence as public content. See the Subprocessors page for the current provider categories and unresolved contract-review items.

Security and incident response

Controls include tenant authorization, private storage, encryption at rest and in transit, least-privilege service roles, versioned evidence storage, and audit records. No certification or independent assurance report is represented by this policy. Security concerns may be reported through the Contact page.

Choices and requests

Customer administrators control memberships and case access. Requests to access, correct, export, or delete information should ordinarily be made through the customer organization that controls the matter. Some deletion requests require an operator-assisted purge because historical versions, audit rows, backups, and logs are intentionally separated from live records.

Changes and contact

A material update will receive a new version and effective date. Authenticated users may be required to accept the new version separately for each organization. Questions may be submitted through the Contact page.