Trust
Watch decisions can involve significant money and sensitive ownership information. Blue Dial Labs is being designed so commercial incentives, weak identity evidence, and unnecessary data exposure do not quietly distort the outcome.
Three trust surfaces
01 / Independence
Affiliate, dealer, marketplace, retailer, or data relationships must remain separate from collector-facing ranking, confidence, and recommendation logic.
Independence & disclosure02 / Data standards
Canonical watch identity, source lineage, matching confidence, normalization, and correction are treated as core infrastructure rather than hidden implementation details.
Data Standards03 / Privacy
Buying thresholds, ownership records, documents, serials, and other sensitive information should be collected only when needed and protected according to their risk.
PrivacyAcross the portfolio
A WristAtlas customer relationship must never create hidden preference inside WristOwl.
Why company-level
WristOwl and WristAtlas solve different problems, but they share the same need for explicit provenance, confidence-aware claims, privacy discipline, and separation between commercial relationships and product truth.
When WristOwl makes a recommendation, the collector's supported outcome is the objective—not transaction volume for Blue Dial Labs or a partner.
WristAtlas should not silently turn uncertain source evidence into certain canonical identity. Uncertainty must remain visible.
The existence of a useful future feature is not a reason to collect sensitive collector data today.
Public copy should distinguish what is implemented, what is estimated, what is inferred, and what remains in development.
Questions
The current disclosure, data-standard, and privacy pages document the intended boundaries for the pre-launch company and will need to evolve as product access, integrations, analytics, or commercial programs become real.