Proof standards

How Proof Harbour makes evidence reviewable

These standards explain how Proof Harbour turns supplied records into structured, privacy-conscious material that a bank, lender, adviser, board, KYB team, or compliance reviewer can understand.

The evidence position, gaps, limits, and approval status should be clear, while first contact stays high level and unrelated sensitive material stays out of the pack.

Evidence first

Public claims, draft packs, route summaries, and working outputs should be grounded in records, source material, and structured review.

Privacy first

Proof Harbour is designed to reduce unnecessary exposure of personal, financial, wallet, asset, company, and reviewer detail. Information should be controlled, limited, and redacted where needed.

Evidence before release

Nothing is issued externally until the supporting records, gaps, scope, privacy boundary, and human approval point have been checked.

Human approved

Draft assistance may support preparation, but final responsibility stays with human review, approval, and controlled release.

Non-custodial

Proof Harbour is not a custody provider, exchange, lender, broker, wallet-access service, or transaction execution service. It focuses on proof, structure, records, and documentation.

Minimal disclosure

A pack should show what is needed for the stated purpose without exposing unrelated wallets, unrelated balances, unrelated entities, private access material, or raw records that are not needed.

Tokenisation boundary

Tokenised asset, tokenised credit, real-world asset token, tokenised collateral, tokenised fund interest, tokenised security, and digital-rail questions are evidence-readiness and reviewer-context matters only unless a later controlled product route is approved.

Scoping before complexity

Tokenised asset, protocol, lending, staking, bridging, vault, DeFi, collateral, company, or urgent evidence questions should move to human review or paid scoping before quote, payment, matter opening, or evidence request.

Tokenised assets and new financial rails

Evidence readiness, not token issuance

Proof Harbour may support people and companies who need to explain tokenised assets, tokenised credit, real-world asset tokens, tokenised collateral, tokenised fund interests, tokenised securities, or other digital-rail records to banks, lenders, advisers, boards, companies, KYB teams, or compliance reviewers.

The support boundary is evidence readiness, reviewer context, governance trail, documentation boundaries, structured records, and privacy-conscious explanation. The boundary is not token creation, token design, token sale preparation, investment promotion, platform selection, lending arrangement, custody, or transaction execution.

Proof Harbour does not issue tokens, advise on token structure, promote investments, arrange lending, provide custody, recommend protocols, move assets, execute transactions, or verify the investment value, suitability, or regulatory status of a token.

A controlled process, not generic text

Drafting tools can assist with preparation. The product value is the evidence process around them: scope, matter controls, evidence logs, redaction, gap recording, human approval, and controlled release.

Before evidence

During evidence handling

Secure matter folder, upload inbox, evidence log, redaction discipline, and forbidden-material control.

Before issue

Draft review, missing evidence note, approval log, and release decision.

After issue

Retention review, change log, and refresh route where the evidence position changes.

Evidence boundary

Proof Harbour does not request evidence through the public website. Initial contact, Register Interest, and public contact should stay high level.

Future evidence requests should follow a separate scope, payment, matter reference, and secure upload process. That applies to digital asset, tokenised asset, company, protocol, collateral, and reviewer-readiness matters.

Accepted only when scoped

Evidence records are requested for a defined matter only after payment has cleared and the upload route has been issued.

Do not send through public forms

Wallet addresses, transaction IDs, token contract addresses, issuer documents, subscription documents, offering documents, bank statements, exchange statements, ID documents, screenshots, tax memos, legal opinions, or sensitive evidence.

Never requested

Private keys, seed phrases, recovery phrases, wallet backups, wallet passwords, exchange passwords, bank logins, browser-wallet access details, or files that give control over funds, wallets, accounts, or assets.

Controlled communication and matter handling

Controlled work should use matter-specific communication, private storage, limited access, and live operating registers that are kept separate from the public website.

Public pages support high-level first contact and public-safe status information only where approved. Evidence, matter folders, and private operating records remain outside public pages and forms.

Encryption is one layer. The wider control model also depends on controlled requests, evidence logs, retention review, refusal of wallet-control material, and human approval before release.

Operating standards

1. Scope and payment before evidence

Evidence handling should not begin until the route is scoped, payment has cleared, and a matter reference exists.

2. Public-safe first contact

The public website is for high-level contact, route information, and public-safe document-status verification only. Evidence files belong only in a separately issued matter route.

3. Complex matters are scoping-first

Tokenised asset, tokenised credit, real-world asset token, protocol, lending, vault, staking, bridging, DeFi, collateral, or digital-rail matters should move through human review or paid scoping before quote, matter opening, or evidence request.

4. Matter-specific upload only

Where a matter is opened, any upload access should be limited to the matter-specific inbox. Internal folders and operating records should remain private.

5. Evidence log and retention control

Files should be checked before they enter the matter record. The evidence log should record what was received, where it is held, what it supports, and when retention will be reviewed.

6. Forbidden material is isolated

If wallet-control or login material is received, work on that file stops. Access is restricted, the event is recorded, and replacement evidence is requested where appropriate.

7. Human approval before release

Draft outputs should be reviewed against scope, evidence, gaps, privacy boundary, external purpose, and any tokenised asset or protocol boundary before release.

8. Status-only verification

Public verification pages should confirm document status only. They must not expose evidence, document contents, private folder links, wallet data, token contract data, payment status, client files, or internal notes.

Important boundary

Proof Harbour does not provide legal advice, tax advice, investment advice, token issuance, token-structure advice, financial promotion, custody, lending, broking, protocol recommendation, transaction execution, wallet access, or regulated financial advice.

Proof Harbour focuses on structured evidence support, documentation, reviewable records, governance context, and privacy-conscious presentation.