Post-race proof
Claim your race proof after the finish line.
Results, photos, stamps, and certificates are the post-race loop that can turn a one-day event into a shareable runner profile. This page starts with reviewed claim requests before opening broader lookup.
Search race results
Full name + bib public by default (PH/VN/ID norm). Search by name or bib, then claim to your profile.
Select a race to browse its public results.
Runner claim intake
Request a result or photo claim
Claims are reviewed before anything is attached to a profile, certificate, stamp, or paid photo flow.
Official results
Runners can submit a guarded request for the team to review against organizer-owned results.
Request intake
Race photos
Bib-based photo claims can enter the same review queue before any delivery or profile attachment.
Request intake
Certificates and stamps
Approved claims become the bridge to certificates, stamps, cards, and app profile proof.
Approval layer
Requests reviewed in 1–2 business days. You’ll see status in app Profile → Claim requests after login.
Launch flow
How this becomes real
The product should earn trust one partner race at a time before any public result or photo browsing.
Organizer uploads
Results CSV, bib mapping, or photo batches land in admin first.
Runner requests
A signed-in runner submits a bib/name/photo claim from the public web.
Runner claims
The app handles identity, profile attachment, sharing, and purchases.
Privacy guardrails
No public result leak as a shortcut
The tempting move is to expose the existing app queries. The durable move is a public-safe claim layer.
Organizer approves what becomes public.
Public search avoids exposing full private profiles by default.
Claims require a runner account before anything is attached.
Payments and high-res photo delivery stay gated until the flow is verified.