← ChroniclePrivacy & data

RIFTBOUND CHRONICLE

Your matches belong to you.

Chronicle captures only what it needs to build your Riftbound match log and optional replay. It does not sell data, use it for advertising, or guess hidden opponent information.

What Chronicle handles

The extension reads realtime messages from the RiftAtlas game tab, including player names, legends, your submitted decklist, cards revealed during play, game actions, and results. If you start video capture, it records the selected RiftAtlas tab. Chronicle also keeps the extension’s settings, a browser-scoped private identifier, and short-lived abuse-prevention counters.

Where it is stored

Signed-out match logs stay in your browser unless you create a public share link. When you create a Chronicle account, match records are stored under a stable account identifier so they can return after browser data is cleared or on another device. Supabase handles email/password and enabled social sign-ins; Chronicle does not receive or store passwords. Replay video remains in the extension until you choose a YouTube destination. For Chronicle-channel uploads, encrypted HTTPS chunks pass transiently through Chronicle’s upload relay to YouTube and are not retained on Chronicle’s servers.

YouTube uploads

Uploading is optional and always begins with an explicit choice. You can upload to the Riftbound Chronicle YouTube channel under the license described in the Terms of Use, upload to your own YouTube channel, or keep the replay local. Personal-channel authorization requests only the YouTube upload permission and keeps the access token in the open page’s memory. Chronicle-channel authorization is held securely by the service and is not shared with users. Chronicle sends your selected title, description, visibility, and made-for-kids setting to YouTube. Google may force uploads from a new, unaudited API project to remain Private.

Use and sharing

Captured data is used only to create the logs, statistics, exports, and replay features you request; to maintain those features; and to prevent abuse. Creating a share link publishes the selected match report to anyone who has its unlisted URL. A share stores lightweight match data and, only if you enable the replay option, the YouTube video identifier needed to embed that video. The share does not copy the video. Data is processed by the infrastructure providers used to run Chronicle, including Supabase for authentication, and is not sold or shared for advertising.

Security and control

Data is transmitted over HTTPS. Downloaded match packages are saved directly to the location you choose. Deleting a game or Chronicle account data removes Chronicle’s match records and share links, but it does not automatically delete a YouTube video. Manage personal-channel uploads in YouTube Studio. For a Chronicle-channel video, request removal at riftboundchronicle@gmail.com. The control below deletes all Chronicle match records and public share links associated with your current browser or signed-in account.

Chrome Web Store Limited Use

Chronicle’s use of information received from Chrome APIs complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. Browser permissions and captured content are used only for the extension’s single purpose: recording a user-initiated RiftAtlas match and building its private match log and replay.

Questions

Use the support contact on Chronicle’s Chrome Web Store listing for privacy questions or deletion assistance. This policy will be updated when the product’s data practices change.

This removes Chronicle match data and public report links. It does not delete YouTube videos or the separate authentication identity held by Supabase.