Evidence Integrity Disclaimer

Effective Date: September 6, 2026 Version: 2.0 Last Updated: September 6, 2026

This disclaimer governs the interpretation and use of the Platform's evidence-integrity records and of the reports generated from them. Read it before relying on any Platform output in appraisal, litigation, or a regulatory proceeding.

Two clarifications first, because earlier versions of this document stated both incorrectly:

Evidence integrity is not a plan feature. It operates on every account, on every plan, including FIELD. It is not purchased, enabled, or restricted to CERTIFY.
There is no "certified evidence package" artifact. The Platform does not produce, seal, or certify a bundle. What exists is a per-file integrity record and an append-only event log, plus whatever report you compose yourself.

1. Nature of Evidence Generated

The Estimatics Platform captures and organizes field evidence — photographs, videos, GPS coordinates, timestamps, and property measurements — submitted by professional users. The Platform does not independently collect evidence. All underlying evidence is captured by a human inspector using the Estimatics iOS application.

2. The Evidence-Integrity Record

2.1 What Is Recorded, and When

For each media file, at the moment the file arrives at the Platform, the server records:

A server-computed SHA-256 hash, derived by re-reading the bytes the server actually received
The device-declared SHA-256 hash, if the uploading client supplied one — retained, but never relied upon by itself
A verification status comparing the two
The clock offset between the uploading device and the server at upload time
The device-reported capture timestamp, the device's time zone, and whether location permission was granted, denied, or unavailable
Device provenance: device identifier, model, operating system and version, and the application version
The capture origin — a team member or a FIELD Lite invitation

These entries are written to an append-only evidence event log. Entries are added; they are not edited or removed.

2.2 The Verification Statuses

Status	Meaning
Pending	Received; the server has not yet completed re-reading the file
Match	The server-computed hash equals the device-declared hash
Mismatch	The two differ
Unverifiable	The server hashed the file, but the device declared no hash to compare against
Unreadable	The server could not re-read the stored bytes

"Unverifiable" is not equivalent to "Match." It means one half of the comparison is absent. Any party relying on the record must read the status, not merely the presence of a hash.

2.3 What the Record Demonstrates

Where the status is Match, the record demonstrates that the file held by the Platform is byte-for-byte the file the uploading device reported sending, and that it has not been altered in Platform storage since that hash was computed.

That is the entire scope of the demonstration.

2.4 What the Record Does Not Demonstrate

The record does not demonstrate, and Estimatics makes no representation as to:

Anything occurring between capture and upload. The hash is computed on arrival, not in the camera. The Platform cannot speak to the interval before a file reached it
The time of capture. The capture timestamp is reported by the device. The Platform records it, and records how far the device's clock sat from the server's — which is evidence about a timestamp, not proof of one
Physical presence at the property. The Platform records whether the device reported a location and whether permission was granted. A device may be wrong; permission may be denied
The accuracy of GPS coordinates, which are subject to device precision
The identity or licensure of the person who captured the file
The condition of the property at any time other than what a given file depicts
Legal sufficiency or admissibility in any jurisdiction

The record is not a digital signature, a notarization, a third-party attestation, or a certification by Estimatics or any other party of the truth of the file's contents.

2.5 Annotated vs. Original Evidence

The Platform preserves both the original file and any annotated version. Annotations are stored as a separate layer and do not modify the original. The integrity record attaches to the original file. An annotated version is a derived work and carries no integrity record of its own.

3. AI-Generated Content

AI findings — damage classifications, scope items, narrative descriptions — are the output of machine learning models applied to the files you submit. They are retained as a contemporaneous record of what a model reported at a point in time.

AI findings carry no integrity guarantee and are not certified facts. Evidence integrity concerns the underlying file; it says nothing about the correctness of any interpretation drawn from it. AI outputs require review and validation by a licensed professional before being relied upon in any proceeding. See our AI & Automated Systems Disclosure at aiestimatics.com/legal/ai-disclosure.

4. Evidence Completeness Check

The evidence completeness check is a post-capture quality-guidance tool that helps professionals assess the completeness of their documentation before submission. It is a quality guidance tool — not a legal assessment or admissibility guarantee.

A passing completeness check indicates that documentation follows the Platform's internal quality criteria. It does not constitute an opinion of counsel or a guarantee that the evidence will be found credible, admissible, or sufficient in any administrative, appraisal, or judicial proceeding.

5. Professional Responsibility

Platform outputs are tools for licensed professionals. The professional submitting any claim or report bears full responsibility for:

Verifying that the evidence accurately represents the property condition
Applying independent professional judgment to all AI-generated outputs
Ensuring compliance with all applicable professional licensing requirements
Ensuring compliance with applicable state and federal insurance regulations

6. Jurisdiction-Specific Considerations

The legal standards for electronic evidence admissibility vary by jurisdiction. Users intending to rely on Platform records in litigation or a regulatory proceeding should consult qualified legal counsel in the relevant jurisdiction. Estimatics does not represent that any Platform record satisfies any evidentiary standard.

7. No Legal Advice

Nothing in this document, or anywhere in the Estimatics Platform, constitutes legal advice. Estimatics is a technology company, not a law firm. Users requiring legal advice regarding evidence, insurance claims, or regulatory compliance should consult a licensed attorney.

Contact

Questions about evidence integrity:

Estimatics, Inc. legal@aiestimatics.com