Skip to content

TRUST / PERMISSION / RESPONSIBILITY

Trust starts with being clear.

Who supplied the information? Who granted permission? What has been reviewed, and what remains unknown? These questions come before each collaboration.

01

A visually browsable scene

For visual experience and spatial presentation. 3DGS is not a collision map, metric navigation system or controller for high-responsibility robots. The two current inputs are unverified and embedding is disabled.

02

An accepted navigation map

Requires field testing and acceptance under defined operating conditions, including devices, precision, safety scope and responsibility. Visual presentation does not grant navigation permission.

03

An ecological outcome record

Must reference a specific methodology, evidence sources, review and verification process. An evidence record is not a certified carbon credit, and viewing a space does not prove ecological outcomes.

Three uses. Distinct validation requirements.

These are not the same certification and cannot be inferred from one another. A hash supports version integrity; it does not prove factual accuracy, copyright, legal title or carbon-credit issuance.

SEPARATE PERMISSIONS

A separate permission for each use.

Permission to view is not permission to train. An enquiry does not grant rights to a full spatial model or video.

01DisplaySeparate authorization
02DownloadSeparate authorization
03Agent retrievalSeparate authorization
04Robot navigationSeparate authorization
05TrainingSeparate authorization
06RedistributionSeparate authorization
07Commercial settlementSeparate authorization

Training on identifiable-person video, live-video trading, data sales and robot commands are disabled by default. This website does not send robot motion commands or initiate transfers or other high-responsibility actions.

A REVIEWABLE COLLABORATION

Keep records that people can review.

Identity & responsibility

Identify the requester, authorizer, actual service provider and reviewer. CanopyProof Limited, the Life++ brand, the protocol and a Shenzhen service provider are distinct roles.

Sources & versions

Record original sources, versions, uses and gaps. When capture date, location, provider or asset format is unknown, mark it pending rather than inventing a value.

Authorization & review

State permission scope, expiry, task boundaries and acceptance criteria. AHIN and related capabilities depend on actual implementation and acceptance; a displayed name is not an active credential.

Challenges & correction

Raise concerns about sources, permissions or displayed content through the enquiry route, identifying the page, issue and requested action. Review outcomes and response times are not promised without confirmation.

YOUR DATA / YOUR CHOICES

Export, deletion and withdrawal in practice.

Review and export

You can generate an enquiry draft and copy its text. CAI accounts and cloud data export are not currently available here. A pilot must first define export format, scope and delivery channel.

Deletion and minimal retention

Clear an unsent draft on this page or close the page. If real receipt is enabled, records must be cleaned under an approved retention period. Deletion scope and required legal or audit retention must be stated separately; deletion of all historical records is not promised.

Withdraw and correct

An enquiry grants no training or spatial-asset permission. Future authorizations should allow you to stop subsequent uses; prior lawful processing, third-party copies and dispute evidence require agreed review. Prepare a withdrawal enquiry and follow the form’s actual receipt status.

WITHDRAWAL & CONTACT

Raise a concern.
Request a withdrawal.

Provide the relevant page, a minimal description and a contact channel. Do not send identity documents or sensitive source material publicly. Confirm the withdrawal scope, identity checks, subsequent data handling and applicable retention requirements with the actual recipient.

Prepare a concern or withdrawal enquiry
Trust, permissions & responsibility