Ref OS TM Connect Privacy Policy
Effective November 2, 2026. Operator: Maharshi Patel / Ref-OS. Contact: refos.app@gmail.com.
Purpose
Ref OS TM Connect connects the official Ref-OS website to the Tournament Manager server chosen by the event administrator. It reads event data and live field activity. It does not start, stop, or control matches in Tournament Manager.
Information handled
- The TM server address you enter, its event API key, and temporary authentication information needed to authorize and sign read-only requests.
- Event information, divisions, teams and team names, schedules, scores, qualification rankings, Skills results, check-in status, and field assignment/start/stop signals returned by the selected TM server.
- Ref-OS sign-in authorization and event identifier supplied by the official Ref-OS page so Ref-OS Cloud can authorize TM access.
The extension does not collect general browsing history, advertising identifiers, payment details, or unrelated website content.
Storage and destinations
The selected TM address is stored in Chrome extension local storage until removed. The TM API key is stored in Chrome extension session storage until Chrome closes or you remove/change it. Temporary connection credentials and live state are held in memory while active. The address and key are shared with the official ref-os.fyi / www.ref-os.fyi page to fill its connection form. Authorized requests go to your selected TM server and the Ref-OS Cloud authorization endpoint hosted by Supabase. Event data returned to the Ref-OS website can be saved by its normal event synchronization features and shared with authorized event users.
Removing the extension does not delete event records previously saved in Ref-OS Cloud. Contact the event administrator or refos.app@gmail.com for assistance with stored event records. Hosting providers may process ordinary connection logs when serving the website or authorization endpoint.
Permissions
Storage remembers the chosen server and temporarily retains the key. Optional host access is requested for the server selected by you. Access to the Ref-OS Cloud endpoint supports authorization. The offscreen document and declarative network request permission support authenticated live WebSocket connections. Content scripts operate only on the official Ref-OS website. The extension restricts TM requests to supported read-only API paths.
Use and sharing
Information is used to provide the extension's TM-to-Ref-OS connection. We do not sell extension user data, use it for advertising, or use it to determine creditworthiness or lending eligibility. Ref OS TM Connect's use and transfer of user data complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.
Your controls
Use Remove server access in the extension to clear its saved address and session key. Stop syncing or close the Ref-OS tab to end its active connection. You may remove the extension through Chrome. School-managed computers may require IT approval. Requests to a local HTTP TM server use that local network connection; HTTPS is used for the official Ref-OS website and Cloud endpoint.
Changes and support
Changes to this policy will appear here with a revised effective date. Questions: refos.app@gmail.com.