Foundation in place
Name the unknown.
Source, freshness, availability caveats, demo labels, and permission boundaries help distinguish an observed record from a verified fact.
Review safety guidanceFull systemFeature 09 / 09
Confidence, without theater
Clear provenance. Fewer blind spots.
Safety guidance, reporting, dispute surfaces, and explicit uncertainty designed into the product—not added after the fun part.
Read the safety guide
Stokd study / Trust
Current stateFoundation in place
Safety guidance and reporting or dispute-related routes exist in the product. They reduce ambiguity but cannot guarantee identity, behavior, product condition, outcomes, or recovery.
09.0 / The premise
Trust should not be a glossy badge. It should be a series of visible boundaries: where information came from, what is still unknown, what action was taken, and who actually has authority.
Foundation in place
Create a path to speak up.
Reporting and dispute surfaces give concerns a structured place to go. Their existence does not promise a particular resolution or replace urgent local help.
Foundation in place
Keep agents inside the lines.
Agents can summarize, organize, and suggest. Sensitive actions—money, messages, commitments, account changes—should require explicit authority and auditable boundaries.
09.4 / Product boundaries
Built around what it should not fake.
- P1Provenance over polish.
- P2Uncertainty is shown, not hidden.
- P3Sensitive actions require authority.
- P4Safety tools do not replace judgment.
Read before relying
Stokd cannot guarantee a person, listing, camp, vendor, service, transaction, or event. For emergencies or immediate danger, contact the appropriate local emergency service—not an in-app report.
Next move
Trust the boundary because you can see it.
The product earns confidence by being precise about what it knows, what it does, and what still belongs to you.
Read the safety guide