Public meet data, controlled by the event operator.

Published Result Data

Public result pages can include swimmer names, teams, age groups, events, heats, lanes, places, scores, and timing information.

This information is competition data provided for public meet viewing. The event organizer decides what appears in the source database and when updates are published.

Local Control

The meet operator controls the source database and decides when results are published or updated.

LiveResultMeet reads the configured meet data for display and does not create official timing records independently from the operator workflow.

Operations

Service logs may be used to monitor health, prevent abuse, and troubleshoot live event delivery.

Operational data can include request timing, browser delivery status, API health, tunnel reachability, and deployment diagnostics needed to keep live result pages available during competition.

Corrections

Questions about published competition data should go to the event organizer or the LiveResultMeet operator for that meet.

Correction requests should identify the meet, event, heat, lane, swimmer, team, and result field. The public site updates after the authorized operator corrects the source data and republishes it.

Spectator Access

Spectators can open the public dashboard without creating an account. The site uses browser storage and service worker caching only to improve loading, offline shell behavior, and live result viewing reliability.

Retention

Public result availability depends on the organizer's publishing process and the configured Cloudflare deployment. Operators can update, replace, or remove meet data by changing the source system and deployment settings under their control.