NODE · LON-01|LONDON --:--:--
DAC | Digital Asset Claims
Legal Documentation

Digital Asset Claims Digital Asset Claims Third Party Information

How third-party information is used in deliverables — and why we cannot guarantee its accuracy.

This disclaimer explains how Digital Asset Claims Limited (trading as Digital Asset Claims) relies on information sourced from clients, third-party platforms and public records when producing deliverables. It is informational only and is not financial, investment, legal or tax advice.

Last reviewed: February 2026 · 20 sections

third-party-information-disclaimer.pdf · A4 · brandedAll documents
01

Purpose of disclaimer

  1. 1.1Digital Asset Claims publishes this disclaimer so users understand the limits of third-party information used in deliverables.
  2. 1.2A deliverable that relies on third-party information can only be as accurate as that information.
  3. 1.3The disclaimer applies to every deliverable that incorporates third-party content.
  4. 1.4Users should read this disclaimer before relying on a deliverable in any significant matter.
02

Meaning of third-party information

  1. 2.1Third-party information is any record, document or data point not generated by Digital Asset Claims itself.
  2. 2.2It includes information from clients, financial institutions, exchanges, platforms, public registers and analytics providers.
  3. 2.3Third-party information is treated as input, not as a verified fact.
  4. 2.4Sources are cited where they are material to a deliverable.
03

Client-supplied records

  1. 3.1Records supplied by clients are accepted in good faith and processed for the engagement.
  2. 3.2Digital Asset Claims does not independently verify the accuracy of client-supplied records.
  3. 3.3Where doubts arise, the client is asked to clarify or supplement the records.
  4. 3.4Clients remain responsible for the records they choose to supply.
04

Third-party records

  1. 4.1Exchange, custodian and platform records are reproduced as supplied and labelled with their source.
  2. 4.2Inclusion of a third-party record does not vouch for the accuracy of that provider's systems.
  3. 4.3Discrepancies should be raised with the issuing provider.
  4. 4.4Disputed records are noted in the report as in dispute.
05

Exchange records

  1. 5.1Exchange statements, trade reports and KYC documents are reproduced as supplied by the exchange or its API.
  2. 5.2Digital Asset Claims does not verify exchange platform integrity, uptime or backfill processes.
  3. 5.3Where an exchange has experienced known issues, those are noted in context.
  4. 5.4Disputed exchange records should be raised with the exchange operator.
06

Platform exports

  1. 6.1Exports from platforms (such as payment, accounting or analytics systems) reflect what the export produced at that moment.
  2. 6.2Subsequent platform changes can alter what an updated export would show.
  3. 6.3Exports are time-stamped and the export method recorded where possible.
  4. 6.4Replaying an export at a later date may produce different output.
07

Blockchain data

  1. 7.1On-chain data is reproduced from the blockchain or a documented analytics provider.
  2. 7.2Attribution of an address to a person, exchange or service is informational and may be incorrect.
  3. 7.3On-chain data is final on chain but interpretations of it are not.
  4. 7.4Where analytics confidence is low, the deliverable says so.
08

Public records

  1. 8.1Public registers and filings are consulted as available at the time of preparation.
  2. 8.2Public records may be updated or corrected after a deliverable is produced.
  3. 8.3Where currency matters, the date of the public record is cited.
  4. 8.4Digital Asset Claims is not responsible for the accuracy of public registers.
09

Correspondence and statements

  1. 9.1Correspondence and statements supplied by clients or third parties are taken at face value unless internally contradicted.
  2. 9.2Statements of opinion are presented as such, not as fact.
  3. 9.3Where a statement is material, the source and date are recorded.
  4. 9.4Conflicting statements are presented side by side rather than reconciled.
10

Screenshots and informal materials

  1. 10.1Screenshots and informal materials may be useful as illustrations but are not authoritative records.
  2. 10.2They are qualified accordingly in deliverables.
  3. 10.3Where authoritative records exist, they are preferred.
  4. 10.4Reliance solely on screenshots is not recommended for significant matters.
11

Accuracy limitations

  1. 11.1Third-party information may contain errors, omissions or stale data beyond Digital Asset Claims's control.
  2. 11.2Where errors are visible, they are noted; where they are not visible, they cannot be corrected.
  3. 11.3Users should not assume that absence of a noted error means information is accurate.
  4. 11.4Significant matters warrant verification with the originating party.
12

Completeness limitations

  1. 12.1Third-party information may be incomplete, missing periods, counterparties or details.
  2. 12.2Gaps are noted in deliverables where they materially affect conclusions.
  3. 12.3Digital Asset Claims does not synthesise data to fill gaps.
  4. 12.4Persistent gaps reduce the weight that can be placed on related parts of the deliverable.
13

Timeliness limitations

  1. 13.1Third-party information reflects a point in time; later events may change the picture.
  2. 13.2Deliverables are dated to make their timeliness explicit.
  3. 13.3Where information is highly time-sensitive, the deliverable says so.
  4. 13.4Re-running a deliverable later may produce different output.
14

Contradictory information

  1. 14.1Where two third parties supply contradictory information, both are recorded and the contradiction explained.
  2. 14.2Digital Asset Claims does not act as arbiter between contradicting third parties.
  3. 14.3Resolution is a matter for the client or their professional adviser.
  4. 14.4Material contradictions may justify pausing reliance on the affected information.
15

Missing information

  1. 15.1Where information is missing entirely, the gap is recorded.
  2. 15.2Deliverables do not include content that is not supported by an available source.
  3. 15.3Clients are invited to supply additional sources where useful.
  4. 15.4Conclusions are scaled back where information is missing.
16

No guarantee of third-party accuracy

  1. 16.1Digital Asset Claims gives no warranty, express or implied, as to the accuracy or completeness of third-party information.
  2. 16.2Reliance on third-party information is at the user's own risk.
  3. 16.3The absence of a warranty does not lower the care taken in processing the information.
  4. 16.4Limitations of warranty are consistent with applicable consumer law.
17

Client review responsibility

  1. 17.1Clients should review deliverables that rely on third-party information they supplied and flag errors promptly.
  2. 17.2Review by the client does not transfer professional responsibility for the underlying work.
  3. 17.3Where errors are reported, they are investigated and corrected as appropriate.
  4. 17.4Repeated review cycles are part of normal documentation work.
18

Independent verification

  1. 18.1Significant matters warrant independent verification by qualified specialists.
  2. 18.2Digital Asset Claims can refer clients to suitable specialists where appropriate.
  3. 18.3Independent verification is a separate engagement and is governed by its own terms.
  4. 18.4Digital Asset Claims does not provide independent verification as a standalone service unless agreed.
19

Effect on deliverables

  1. 19.1The weight of a deliverable section is bounded by the third-party information it relies upon.
  2. 19.2Where third-party information is partially reliable, the deliverable says so.
  3. 19.3Where third-party information is wholly unreliable, the deliverable excludes the affected section.
  4. 19.4Users should consider these qualifications before acting on a deliverable.
20

Final reliance limitation

  1. 20.1Nothing in a deliverable should be read as a guarantee that third-party information is accurate, complete, current or fit for any particular purpose.
  2. 20.2Reliance on a deliverable for any regulated, legal or financial purpose is at the user's own risk.
  3. 20.3Where there is doubt, the underlying source and qualified advice should be sought.
  4. 20.4This disclaimer prevails over any inconsistent statement that may appear in a deliverable.
Frequently Asked Questions

Questions about this page

Do you verify everything in your deliverables?
No. We organise and present information; we do not independently verify the records and data supplied by clients or third parties.
What if a third-party record is wrong?
The deliverable will only be as accurate as the record it relies on. Disputes about a third-party record should be raised with the issuing party.
How do you handle conflicting sources?
We present both sources side by side and explain the conflict. We do not act as arbiter between contradicting third parties.
Where can I get independent verification?
We can refer you to suitable specialists. Independent verification is a separate engagement with its own terms.
Related legal pages