RiftSight Privacy Policy

Last updated: August 2026

RiftSight has two parts: a browser extension a streamer installs, and a Twitch Extension that renders the overlay for viewers. RiftSight is an unofficial, fan-made project and is not affiliated with Riot Games, UVS Games, Rift Atlas, or Twitch.

If you're a viewer

RiftSight does not collect, store, or process any personal data about viewers. When you watch a stream with RiftSight activated, your browser verifies your session with Twitch's own Extension platform to confirm which channel you're watching — this happens entirely through Twitch's standard Extension Helper mechanism and is never stored by RiftSight. We do not use cookies, analytics, or tracking of any kind on the viewer-facing overlay.

If you're a streamer: the browser extension

The RiftSight browser extension is what you install to publish card data from your own Rift Atlas games. Its content script only runs on play.riftatlas.com — it doesn't run on, or have access to, any other site you visit. While active, it reads card information already rendered on your screen (card art, names, positions, which zone each card is in) and sends it over an encrypted connection (wss://) to RiftSight's backend, which forwards it to your stream's overlay. It never reads or sends anything Rift Atlas itself is keeping hidden from you (an opponent's hand, a face-down card) — the same visibility rules that apply to what you can see in the game apply to what the extension will ever publish, and nothing is retained after your stream ends. Card art images are a separate exception: your browser fetches those directly from Rift Atlas's own image CDN, the same way loading any web page fetches its images — that traffic never passes through RiftSight's servers.

The extension requests three permissions, each scoped to exactly what it needs:

• storage — remembers whether you'd like publishing on or off, locally in your browser.
• alarms — schedules periodic reconnect/heartbeat checks to RiftSight's backend without keeping the extension constantly active in the background.
• host permissions (RiftSight's own backend domain only) — the extension's sole network destination; it never requests access to sites it doesn't need.

No analytics, no third-party trackers, no advertising SDKs, no browsing history, no data from any site other than play.riftatlas.com, and no remotely loaded or dynamically evaluated code — everything the extension does is contained in the code you install.

Connecting your Twitch account (OAuth)

To use RiftSight as a streamer, you connect your Twitch account through Twitch's own OAuth authorization flow. We store:

• Your Twitch user ID and Twitch login name, so we know which channel to publish card data to.
• A one-way cryptographic hash of a connection credential we issue you (never the credential itself), so we can verify future connections came from you.
• Basic timestamps (when your account was linked, when a credential was last used or rotated).

We never store your Twitch password — that's handled entirely by Twitch's own OAuth consent screen and never passes through RiftSight. We do not sell or share this data with any third party.

Operational logs

RiftSight's backend keeps short-lived operational logs (connection counts, error rates, timestamps) to keep the service running reliably. These logs never include card data, viewer identities, or full credential values.

Removing your data

If you stop using RiftSight, you can ask us to remove your linked account and all associated data by emailing riftsight.support@gmail.com.

Contact

Questions about this policy: riftsight.support@gmail.com