Security & Architecture

This page documents where Home Field Big Screen stores data, how data moves between systems, and the safeguards protecting it. See also the Big Screen Privacy Policy.

Where data is stored

• Supabase (Postgres, AWS us-east-1): your email, AES-256-encrypted Ring access and refresh tokens, your Ring device list and per-camera Big Screen settings, and for each paired TV a device name, timestamps, and a SHA-256 hash of its access token.
• Vercel (US): hosts the application and API. No customer data is stored at rest.
• The TV: one opaque device token, in the Apple TV Keychain. No Ring credentials.

No live video or audio is stored anywhere by Big Screen.

Pairing flow

1. The TV requests a pairing code. The code expires after 10 minutes.
2. A signed-in person enters the code at app.homefield.tv/pair. Consent comes from the person, not the device.
3. The TV, polling every 3 seconds, receives an opaque device token. Only its SHA-256 hash is stored on our side.

Live view flow

1. The TV creates a WebRTC connection offer and sends it to our server (app.homefield.tv) with its device token.
2. Our server checks the device token, signs the offer with your Ring access token, which never leaves our server, and sends it to Ring's live-streaming (WHEP) endpoint.
3. Ring answers, and our server returns Ring's answer to the TV.
4. Live video and audio travel directly from Ring to your TV over an encrypted WebRTC connection (DTLS-SRTP). They never pass through Home Field servers.

• Our server carries signaling only: the SDP offer, the SDP answer, and the request that closes a session. No media server or TURN relay is part of Big Screen, so live media has no path through Home Field infrastructure.
• Session close: close requests are HMAC-SHA256 signed and bound to the TV that opened the session, and our server sends them only to Ring's API host.
• Session length: Ring ends each session at about 60 seconds. The TV opens a replacement before the cutoff and closes the old one explicitly, so cameras are never held awake.

Access controls

• Every API request from a TV requires its device token. Revoked TVs are rejected on every request.
• Per-camera visibility and the Big Screen on/off switch are enforced on our server, not on the TV.
• Every database row is scoped to its owning user with Postgres Row-Level Security.
• Ring access uses Ring's official Partner API OAuth flow. Tokens are encrypted at rest and used only server-side.
• All API traffic uses TLS. Live media uses DTLS-SRTP.
• No person at Home Field views customer video.

Revocation and deletion

• Revoking a TV stops our server from signing any further requests for it. A session already open ends at Ring's 60-second limit and cannot be renewed.
• Disconnecting Big Screen in the Ring app or deleting the account deletes Ring tokens and Big Screen records within seconds.

Backups

The database is backed up daily by our managed database provider. Backups contain no video, because Big Screen stores none.

Big Screen documents

Privacy Policy · Terms of Service · Support · Security & Architecture

Home Field Big Screen is a third-party app and is not affiliated with, endorsed by, or sponsored by Ring or Amazon. Ring is a trademark of Ring LLC. Apple TV and tvOS are trademarks of Apple Inc.