Public verification link

In any dispute over property condition, the party making a claim carries the burden of proof. A host who says the property was clean before the guest arrived must demonstrate that claim with evidence a neutral third party can evaluate. Evidence that only the host can access or interpret is not independently verifiable: the reviewer must take the host’s word that the document says what the host claims it says.

A public verification link removes that dependency. The reviewer, arbitrator, or reviewer accesses the document directly from a neutral URL. They see the same content the host sees. They can confirm the GPS coordinates, timestamps, and photo sequence without any intermediary. The document either matches the claim or it does not, and that check happens outside the host’s control.

This matters most in situations where the other party contests the authenticity of the documentation. A guest who claims the inspection was faked, back-dated, or altered has no rebuttal available when a public verification link demonstrates the document has been cryptographically unchanged since generation. The dispute shifts from “did this happen?” to “what happened?”

A public verification link proves two things. First, that the document content visible at the link has not changed since the report was generated. Second, that the link is publicly accessible without credentials, which means any party in a dispute can access the same document without requiring cooperation from the host.

It does not prove that the inspection was conducted honestly. GPS coordinates can be spoofed if a device’s location services are manipulated. Timestamps can theoretically reflect the wrong time if the device clock is incorrect. A public verification link is not a replacement for honest inspection practice. It is a confirmation mechanism that authentic records remain authentic after they are generated.

In combination with GPS-verified photos and a structured room-by-room inspection sequence, the verification link provides the strongest publicly auditable record available to a short-term rental host. It is the format Airbnb’s April 2026 evidence standard implicitly describes when it calls for documentation that can be “independently verified.”

When a Checkout Shield report is generated, the system creates a cryptographic hash of the report content: a fixed-length string derived deterministically from the full document data. If any part of the document changes, the hash changes. The hash is stored alongside the report record and is not modifiable after generation.

The public verification link serves the current document content alongside the stored hash. Any viewer can confirm the two match. If the document had been altered since generation, the served content would produce a different hash, and the verification page would show a mismatch. The verification check runs client-side: the viewer does not need to trust Checkout Shield to perform it correctly. They can recompute the hash independently if they choose to.

Reports on paid plans are hosted with permanent links that never expire. Reports on the free plan are accessible for the duration of the free link window. For claim purposes, the link should be shared at the time of filing; a reviewer checking the link days later will see the same content if the link is still active.

Not all shareable links are verification links. A Google Drive link, a Dropbox share, or a link to a PDF stored in cloud storage is a shared link. The recipient can access the document, but they cannot confirm it has not been modified after creation, because nothing prevents the document from being replaced or edited in the original storage location.

A verification link is specifically a link where the act of accessing it includes a tamper check. Viewing the page confirms authenticity. A shared link is a convenience. A verification link is an evidence mechanism. In a dispute context, this distinction becomes significant: a party can argue that a shared document was altered; a party cannot argue that a document whose public verification link confirms it unchanged since generation was altered after the fact.