Privacy Policy

Last updated: July 14, 2026

This policy describes FireTop's current connectivity, content protection, and operational-data boundaries.

No Accounts Required

FireTop requires no sign-up, login, or account. Device pairing uses a QR code or pairing code displayed by the host.

Pairing and Device Data

• Pairing credentials — protected pairing and registration identifiers or keys may transit FireTop relay infrastructure when the relay path is used.
• Face ID / Touch ID — used locally to gate access to sessions. No biometric data ever leaves your device.
• Camera — used only to scan the QR code during pairing. No images are stored or transmitted.

Connectivity

FireTop uses LAN/direct connectivity first and a FireTop-operated relay as a fallback. There is currently no active, supported Tailscale media path.

FireTop does not currently package a self-hosted relay setup flow or relay configuration UI. Screen, audio, and input content are end-to-end protected with Noise from the relay: the relay forwards opaque protected content and cannot decrypt it. Routing, session, and operational metadata remain visible to the relay. Protected pairing and registration identifiers or keys may also transit relay infrastructure.

Diagnostics and Updates

FireTop includes diagnostics and update checks. Diagnostics can be collected for troubleshooting, and the desktop updater uses FireTop infrastructure.

Third-Party Services

FireTop has no third-party integrations, advertising networks, or data brokers.

Contact

Questions? Open an issue at github.com/roguecomet-dev/FireTop/issues.