Transparency

How We Build Trust

Every public property earns its trust level through evidence checks, direct path review, and data freshness signals. Badges are not paid placements.

Trust score

Trust score measures evidence depth

The trust score reflects how complete, fresh, and verifiable a property profile is. It is based on public data quality, confirmed direct booking paths, source consistency, and evidence freshness.

Trust scores are not guest ratings and do not guarantee service quality or safety. They explain the depth of data verification behind a public profile.

Public trust tiers

High trust

The strongest visible tier, used when evidence is broad, fresh, and consistent across direct booking and source checks.

Strong trust

Used when the property has solid verification and a confirmed direct path, with enough evidence for confident discovery.

Verified trust

Used when core profile checks are complete and the property is eligible for public discovery, while deeper evidence may still be developing.

Data sources

Trust signals are derived from evidence that can be checked without exposing private owner or internal audit data.

  • Profile completeness, including name, property type, location, and official website signals.
  • Direct booking path evidence, including official website and PMS availability where available.
  • Freshness of the latest successful verification, price check, or availability sync.
  • Consistency between public sources, direct booking data, and the property graph record.

Verification badges

Badges show completed checks

Verification badges summarize specific evidence that has passed review. They help travelers understand why a profile is considered distribution ready.

Badges are earned through verification and cannot be bought for ranking advantage.

Owner verified

The public profile is tied to a property or owner signal that passed identity and ownership review.

Source checked

The visible profile data was compared with public sources and internal graph records for consistency.

Direct evidence

The property has a reviewed path that leads travelers toward the official site or a direct booking channel.

Direct path

Direct path status explains booking route confidence

Direct path status describes how clearly Trippchain can connect a traveler to the property without relying on an OTA as the primary route.

Verified savings

A direct route exists and price evidence indicates the direct option is better than the comparable OTA result at the time of verification.

Official available

An official booking route is available, but current savings evidence is not strong enough to show a verified savings badge.

PMS available

A property management system or booking engine signal supports direct booking or availability evidence.

Official site only

An official website is available, but Trippchain has not confirmed a stronger direct booking or price evidence signal.

Missing

No reliable official direct path is available for public promotion, so the property cannot claim direct booking strength.

Price evidence

Price badges explain verified savings

How savings are calculated

Savings are derived from comparable public offers, currency-aware price checks, and the direct booking route available at verification time.

Price freshness

Price evidence is time sensitive. When a check becomes stale or inconclusive, the public badge is removed until fresh evidence is available.

Availability evidence

Availability badges describe booking reliability signals

Availability evidence explains whether Trippchain has a fresh signal that a direct booking route can support traveler intent.

PMS connected

A PMS or booking engine signal is available and can support a public availability badge when freshness checks pass.

Calendar synced

Calendar evidence may support internal review, but the current public availability badge is reserved for supported PMS signals.

Manual review

Manual evidence can support profile review, but it does not replace a fresh machine-readable availability signal.

Sync freshness

Availability badges depend on the latest successful sync. Stale or failed syncs remove the badge until the signal is healthy again.

Publish gates

Publish gates protect public discovery

A property appears in public search only when it meets the minimum publication and evidence requirements for distribution.

Minimum requirements

  • The public profile must be explicitly marked as published.
  • The internal trust threshold must be met before the profile can be indexed or shown in search.
  • The profile must have enough location, official website, and direct path evidence for a safe public listing.

Below the gate

Properties below the gate stay out of search and public sitemap surfaces until missing evidence is resolved.

Operational methodology

For proof tiers, verification cadence, public data, and correction gates, read Methodology.