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

Digital Asset Claims Digital Asset Claims Document Authenticity

What our documentation work does, and does not, certify about the underlying records.

This disclaimer clarifies the limits of the document review carried out by Digital Asset Claims Limited (trading as Digital Asset Claims). It is informational only and is not financial, investment, legal, tax or forensic advice.

Last reviewed: February 2026 · 20 sections

document-authenticity-disclaimer.pdf · A4 · brandedAll documents
01

Purpose of disclaimer

  1. 1.1Digital Asset Claims publishes this disclaimer so users understand what its document work does and does not certify.
  2. 1.2Documentation work organises and presents records; it does not, on its own, prove their authenticity.
  3. 1.3The disclaimer applies to every deliverable produced by Digital Asset Claims.
  4. 1.4Users should consult this page before relying on a deliverable for a regulated or legal purpose.
02

Client-provided materials

  1. 2.1Deliverables are built from materials supplied by the client.
  2. 2.2Digital Asset Claims does not independently verify that client-provided materials are genuine or complete.
  3. 2.3Where doubt arises, the client is asked to confirm or supplement the materials.
  4. 2.4Clients remain responsible for the materials they choose to supply.
03

Third-party records

  1. 3.1Deliverables may incorporate records issued by third parties such as banks, exchanges, platforms and authorities.
  2. 3.2Third-party records are reproduced as received, unless reformatting is needed for presentation.
  3. 3.3Digital Asset Claims does not, by use of a third-party record, vouch for the issuing party's accuracy.
  4. 3.4Where a record is suspected to be inauthentic, the client is asked to clarify the source.
04

Source limitations

  1. 4.1Records inherit the limitations of the systems that produced them.
  2. 4.2System defects, exports of partial data and timing differences can all affect what a record shows.
  3. 4.3Digital Asset Claims notes such limitations where they materially affect a deliverable.
  4. 4.4Source limitations are not a basis for inferring that a record is false.
05

No automatic authenticity guarantee

  1. 5.1Inclusion of a record in a Digital Asset Claims deliverable is not, by itself, a guarantee that the record is authentic.
  2. 5.2Authenticity is a legal and forensic question separate from organisation and presentation.
  3. 5.3Authenticity questions should be referred to a qualified specialist.
  4. 5.4Where Digital Asset Claims is asked to test authenticity, that scope is recorded in writing in the engagement letter.
06

No forensic verification unless agreed

  1. 6.1Standard documentation work does not include forensic verification of records, signatures, metadata or images.
  2. 6.2Where forensic verification is needed, it is engaged separately with the client's express written agreement.
  3. 6.3Forensic findings, where produced, are clearly labelled and scoped.
  4. 6.4Without an explicit forensic scope, no forensic conclusions should be inferred from a deliverable.
07

No legal validation

  1. 7.1Digital Asset Claims does not provide legal advice or legal opinions on the validity of any document or claim.
  2. 7.2Statements of legal effect should be obtained from a qualified solicitor or barrister.
  3. 7.3Deliverables may quote relevant legal provisions for context, not as advice.
  4. 7.4Reliance on a deliverable for legal validation is not safe.
08

No financial validation

  1. 8.1Digital Asset Claims does not provide regulated financial advice, audit opinions or financial certifications.
  2. 8.2Financial conclusions should be obtained from a qualified accountant, auditor or regulated adviser.
  3. 8.3Deliverables may present financial data for organisation purposes, not as audited statements.
  4. 8.4Reliance on a deliverable for financial validation is not safe.
09

No tax validation

  1. 9.1Digital Asset Claims does not provide tax advice or tax filings, and does not certify the tax position of any record.
  2. 9.2Tax conclusions should be obtained from a qualified tax adviser.
  3. 9.3Deliverables may organise records relevant to a tax matter, without taking a position on tax liability.
  4. 9.4Reliance on a deliverable for tax validation is not safe.
10

No investment validation

  1. 10.1Digital Asset Claims does not provide investment advice, recommendations or appraisals of investment products.
  2. 10.2Investment conclusions should be obtained from a regulated investment adviser.
  3. 10.3Deliverables may organise records relating to investment activity for documentation purposes only.
  4. 10.4Reliance on a deliverable for investment decisions is not safe.
11

Reliance on source documents

  1. 11.1Deliverables rely on the records made available; what is in the deliverable reflects what was in the records.
  2. 11.2Records that were not supplied cannot be inferred or filled in.
  3. 11.3Where reliance is material, the source record is cited.
  4. 11.4Loss of reliance on a source record reduces the weight of the affected part of the deliverable.
12

Incomplete records

  1. 12.1Where records appear incomplete, the gap is noted in the deliverable.
  2. 12.2Digital Asset Claims does not fabricate content to fill gaps.
  3. 12.3Digital Asset Claims requests additional records from the client to close gaps where possible.
  4. 12.4Persistent gaps limit the conclusions Digital Asset Claims records in the deliverable.
13

Conflicting records

  1. 13.1Where two or more records conflict on a material point, the conflict is presented rather than resolved.
  2. 13.2Resolution of conflicts is a matter for the client or their professional adviser.
  3. 13.3Digital Asset Claims may identify possible explanations, without endorsing one over another.
  4. 13.4Conflicting evidence is a normal feature of documentation work, not a failure of it.
14

Missing metadata

  1. 14.1Records may arrive without useful metadata such as creation date, author or system of origin.
  2. 14.2Missing metadata is noted where it materially limits the deliverable.
  3. 14.3Digital Asset Claims does not synthesise metadata.
  4. 14.4Clients may consult specialist tools to retrieve metadata where needed.
15

Screenshots and exported files

  1. 15.1Screenshots and exports are treated as illustrations of what a system displayed at a point in time, not as authoritative records.
  2. 15.2Reliance on screenshots is qualified accordingly in a deliverable.
  3. 15.3Where authoritative records are available, they are preferred over screenshots.
  4. 15.4Screenshots are retained with their source context where possible.
16

Bank and exchange records

  1. 16.1Statements and trade reports from banks and exchanges are reproduced as supplied.
  2. 16.2Digital Asset Claims does not, by including such records, certify the accuracy of the issuing institution.
  3. 16.3Where records appear inconsistent with the client's account, the client is invited to investigate.
  4. 16.4Disputed institutional records should be raised with the institution that issued them.
17

Blockchain or digital asset records

  1. 17.1On-chain data is reproduced from the blockchain or a documented analytics provider.
  2. 17.2Attribution of an address to a person is informational and may be incorrect.
  3. 17.3Digital Asset Claims does not custody or transact in digital assets.
  4. 17.4Digital asset risks are addressed separately in the Crypto Asset Risk Disclosure.
18

Client review responsibility

  1. 18.1Clients should review deliverables on receipt and tell Digital Asset Claims about errors, omissions or doubts about source records.
  2. 18.2Review by the client does not transfer professional responsibility for the underlying work.
  3. 18.3Where errors are reported, they are investigated and corrected as appropriate.
  4. 18.4Repeated review cycles are part of normal documentation work.
19

Professional advice recommendation

  1. 19.1Where a deliverable touches a legal, financial, tax or regulatory question, clients should obtain advice from a qualified specialist.
  2. 19.2Digital Asset Claims can refer clients to suitable specialists where appropriate.
  3. 19.3Specialist advice should be obtained in writing where the matter is significant.
  4. 19.4Specialist advice is a separate engagement and is governed by its own terms.
20

Final limitation statement

  1. 20.1Nothing in a deliverable should be read as a guarantee that any underlying record is authentic, complete, accurate or legally valid.
  2. 20.2Reliance on a deliverable for any regulated purpose is at the user's own risk.
  3. 20.3Where there is doubt, the underlying record 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 certify that my documents are genuine?
No. Documentation work organises and presents records. Authenticity is a separate forensic or legal question that requires a specialist.
Can I use your deliverables in court?
Digital Asset Claims delivers organised source-linked documentation that parties may submit in proceedings, but the underlying records and any required expert opinion remain the responsibility of qualified specialists.
What happens if records conflict?
We present the conflict transparently in the deliverable rather than resolve it for you. Resolution is a matter for you or your professional adviser.
Will you verify metadata?
Not by default. Forensic verification of metadata or signatures is an additional scope that must be agreed in writing in the engagement letter.
Related legal pages