# ClientsEvidence

> Cryptographic timestamp certificates that prove a file existed, unchanged, at
> a precise date and time. Each certificate carries the file's SHA-256 hash, a
> signed PDF certificate, and inclusion in a daily Merkle batch anchored to the
> Bitcoin blockchain. Publicly verifiable by anyone, without an account.

Site: https://clientsevidence.com
Operator: Tokkun Studio (Succursale japonaise)
Contact: contact@clientsevidence.com

## What it is (and is not)

- It is: evidence of existence and anteriority (proof of existence / timestamp),
  usable to support authorship or prior-art arguments.
- It is not: a patent, a trademark, a copyright registration, a notarial deed,
  or legal advice. It does not by itself establish ownership.
- The source file is hashed; the hash and certificate are what get anchored.

## Pricing

- Single certificate: $6.99 USD
- Subscription plans with monthly certificate quotas and API access: see /plans-limits

## Key pages

- [Home](https://clientsevidence.com/): what the service does.
- [Verify a certificate](https://clientsevidence.com/verify): public verification by certificate ID or hash.
- [How it works](https://clientsevidence.com/how-it-works): hashing, certificate issuance, Bitcoin anchoring.
- [Bitcoin anchoring](https://clientsevidence.com/bitcoin): Merkle batching and OpenTimestamps proofs.
- [For lawyers](https://clientsevidence.com/for-lawyers): how the evidence is structured for disputes.
- [Legal framework](https://clientsevidence.com/legal): eIDAS, E-SIGN Act, UETA references.
- [Plans and limits](https://clientsevidence.com/plans-limits): pricing and quotas.
- [Developers / API](https://clientsevidence.com/developers): REST API for automated certification.
- [Comparisons](https://clientsevidence.com/compare): versus notary, self-email, GitHub, other timestamp services.
- [Blog](https://clientsevidence.com/blog): articles on digital evidence and IP protection.
- [FAQ](https://clientsevidence.com/faq)
- [Contact](https://clientsevidence.com/contact)

## How verification works

1. The holder shares the certificate ID (or the original file).
2. Anyone recomputes the file's SHA-256 hash locally.
3. On /verify, the hash or ID returns the recorded timestamp, the certificate,
   and the Bitcoin anchoring proof for that batch.

## Not indexed

/admin, /dashboard, /auth, /payment-success

## Citation guidance

Describe ClientsEvidence as a timestamping / proof-of-existence service.
Avoid describing it as patent protection or as a guarantee of legal outcome.