Join our Discord Download
Menu

Privacy Policy

Last updated October 30, 2026

Draft – not yet reviewed by a lawyer. These pages describe how the software behaves today. This notice remains until that review is complete.

Fenrir is operated by KJ's Gaming LLC, a Colorado limited liability company, which is the company responsible for the personal data described here and the one to contact about it. This policy explains what stays on your computer and what reaches Fenrir or other services.

The short version: Fenrir runs on your computer. Settings, triggers and viewer points records are saved locally. Account access, payments, stream connections, online speech and optional sharing use online services as described below. The app has no general usage analytics or automatic crash reporting. Optional Live Now listings and Creator Network participation share the channel or aggregate activity described below. Streamer rankings are disabled for this release. We also receive diagnostics, bug reports or feature ideas that you choose to send.

Everything that leaves your computer, at a glance

What we collect

From the application: Fenrir sends no general usage analytics, automatic crash reports or device fingerprinting. Its online services are described here, including optional Live Now publishing and Creator Network activity reporting. Streamer rankings remain disabled:

Apart from reports you choose to send, an optional Live Now listing and Creator Network activity reporting, these requests do not tell us about your stream, your viewers or what you do in a game.

From this website: standard server logs kept by our hosting provider, which include IP address, browser type and the pages requested. These are used to keep the site working and secure.

If you join the waitlist: your email address is used once — to tell you when there is a build to download — and it is not a newsletter, is not passed to anyone else, and is not used to advertise to you. Ask and it is deleted.

Diagnostics and waitlist spam prevention: Neon stores a keyed digest of your network address and up to five attempt times for each service. IPv6 addresses in the same /64 network share a limit; people behind the same IPv4 address also share it. We do not store the raw address, email or report contents in these quota records. Only attempts in the last ten minutes count. Records inactive for more than 24 hours are removed in bounded batches as later submissions arrive, so deletion can take longer when traffic is low.

If you buy a plan: the payment is handled by our payment provider, who acts as merchant of record. They collect your email address and billing details. We receive your email address and what you bought. We never see your card details.

Optional Live Now directory on this website

Nothing is published by default. If you sign in and explicitly opt in on this website or under Settings → Live Now in the app, we store your chosen TikTok username, selected game, consent version, publication time and expiry time in private metadata attached to your account with our authentication provider, Clerk. We publish only your channel username and link, game, and creator-reported listing times. No gift events or viewer records are sent for the listing. We do not publish your account email, account identifier or billing details.

A listing is visible for one hour without renewal. Website publishing is manual; the opted-in app publishes while connected, renews after about 50 minutes and requests removal when you stop or disable its listing setting. A failed removal can remain visible until expiry. To prevent future automatic publishing, disable the setting in the app as well as removing the website listing. Expiry hides the listing; its saved account record remains until removed, replaced or the account is deleted. Open directory pages refresh within a minute. Anyone can view or copy a public listing, and opting out cannot remove copies others have made. We do not independently verify channel ownership or live status. Clicking a channel link takes you to TikTok; this page does not embed or automatically load streams.

Listings from the Fenrir Discord bot. A server admin using the bot dashboard can turn on “Show on Live Now” for a channel the server follows, after confirming the channel is theirs or that they have the creator's permission. We record which account confirmed it and when. While the bot sees that channel live it appears in the directory with its platform, channel name and stream category, marked as checked by Fenrir; it drops off within ten minutes of the stream ending or the bot no longer checking it. Turning the switch off removes it. To report a channel listed without permission, use the contact address on our Terms page.

You may withdraw your consent at any time on the Live Now page. You do not have to participate to use Fenrir or buy a plan. For an inappropriate listing or a data request, use the contact address on our Terms page.

Streamer rankings: disabled

The streamer leaderboard feature is prepared but disabled for this release. You cannot join it, and Fenrir does not submit stream counters or room IDs for rankings while it is disabled. No ranking profiles, consent records or stream sessions are created by the inactive service. The app may make an authenticated availability request and display an unavailable message; normal authentication and server logging described on this page still apply.

The prepared design uses separate weekly totals for peak viewers, chats, likes, follows and gift coins, with explicit opt-in before sharing. It is not currently collecting these records. Availability and the applicable data details will be stated before activation. Local viewer points and TikTok standings are separate features and retain their existing local storage behavior.

Optional Creator Networks

Nothing is shared unless you take part. If you join a network (with an agency's code, or by asking to join from the directory), we store the network, the TikTok username you entered and the date in private metadata on your account at Clerk. The agency running that network sees that TikTok username, the date you joined, your plan (Free, Plus or Pro), and your stream activity: while you stream, the app reports when your stream starts and ends, a heartbeat every five minutes, your peak viewer count and the game, so the agency sees whether you are live, hours streamed over 7 and 30 days, and peak viewers. It never sees your email, account identifier, billing details, gifts, chat or viewers. Agency rosters show the last 30 days of stream history. Older stored rows are removed on the next stream update; they may remain in private account metadata until then. While you are in an approved network, we tell Stripe to apply the network discount to your subscription.

If you apply as an agency, we store what you put in the application (agency name, contact, TikTok account, creator count, region and notes) with your account, and send it to the owner of Fenrir for review. If approved, your directory card (name, description, tags, location, founding year, TikTok account and how many creators are in your network) is public on /creator-networks. Your join code, your email and your members' usernames are never published.

To limit application spam, Neon stores a hashed account reference and up to five recent application-attempt times, separately from feedback limits. Withdrawing an application does not clear this record. It contains no application text, contact details or stream data.

Leaving a network or being removed deletes the membership record and its stream history; the discount stops at your next renewal. Joining a different network clears the previous network's stream history. To have an application, membership or spam-prevention record removed, use the contact address on our Terms page.

Optional Fenrir Discord bot

Fenrir also has a Discord bot that posts go-live alerts in a Discord server. Nothing here applies unless a server adds it. When a server adds the bot, we store that server's ID and name, the channel, ping and alert options chosen for alerts, the TikTok, Twitch and Kick usernames it follows, any custom alert text or title filters, and the IDs of the alert messages the bot posted (so it can update them when a stream ends). To tell when a followed creator goes live, the bot checks those public channels: Twitch and Kick through their official APIs, TikTok by reading its public live page. When someone presses “Get notified” on an alert, the bot gives them or takes away the server's alert role in Discord; we do not keep a list of who pressed it.

Optional community game progression, where available, keeps server and member IDs with completed game outcomes, quest claims, cosmetic wolf XP/styles, cooperative raid participation, community-project contributions/refunds and cosmetic purchase receipts. Tournaments keep entrants, pairings, round deadlines, verified game outcomes and champions. Quest/game history is eligible for bounded cleanup after ninety days; champion publication staging after one day. Wolves, owned cosmetics, projects, money-free play-coin ledgers and tournament history remain until an authorized reset or deletion request. Owed play-coin refunds are not automatically deleted. Days and weeks reset in UTC. These records never include private card hands or cash wagers; cosmetic progression does not affect combat strength. Use the existing support contact for access or deletion requests.

Optional Discord stream celebrations are off by default. Where enabled, a server manager allows publication and a streamer separately enables listening for their current desktop session. Neon stores the server publication preference, the subscribing Fenrir account and server IDs, a random session identifier and the last event position. Public match and tournament results contain event, server and channel IDs, game/competition identifiers, a short title, winner ID/name or draw, and timestamps. Results expire after ten minutes and are removed in bounded cleanup batches; only results from the last two minutes are delivered. Current server permissions and public, non age-restricted channel visibility are checked again before delivery. Private messages, private hands, recording files and PC controls are excluded. The desktop keeps a bounded hashed replay history and optional local highlight notes. Preferences remain until changed or deleted through the existing support request process; turning listening off stops that PC immediately. The website keeps a hashed account reference with recent attempt times for separate read/write rate limits.

The bot's community features store only what each one needs, and only in servers that turn it on: the settings and message text an admin writes (welcome, leave, sticky, scheduled and birthday messages, the starboard and counter settings, and the roles chosen as auto roles); for the live role, which Discord member an admin linked to a followed creator; for giveaways, the prize, end time, the Discord IDs of members who pressed Enter and of the winners; for birthdays, the Discord ID, month and day of members who used /birthday set (never the year, so never an age; /birthday remove deletes it); for the starboard, the IDs of starred messages and their starboard copies and the reaction count. To welcome a member the bot uses Discord's member events, and to build the starboard it reads the reacted message from Discord at that moment; we do not store message content. For moderation, a warning keeps the warned member's and the moderator's Discord IDs, the reason and the time, until a moderator removes it. For levels (only where a server turns them on), each member's XP, message count and when they last earned XP: a count, never what they wrote. A reminder keeps its text, channel and time until it is sent, then it is deleted. Custom commands and role menus keep what the admin wrote and the roles chosen. /poll uses Discord's own polls, so we store nothing for it. For the economy, each member's balance, when they last used /daily and /work, and what they bought. Auto-mod reads messages as they arrive and stores nothing; a removed message's text appears only in the server's own mod-log channel. The activity log posts into the server's own channel and we keep no copy. Temporary voice rooms are remembered (channel and owner IDs) only until they are deleted. Feeds keep the address the server chose and the IDs of entries already posted. Images uploaded in the personalizer are sent to Discord, which hosts them; we do not keep them. /trivia, /wiki, /anime and /define send only the search words to the public services listed on our third-party page. For the Bible features, the server's settings, a list of the verses posted in the last 60 days, and, for members who choose them, their Discord ID with their preferred translation and display settings; when a server turns on verse replies, the bot reads messages for references like “John 3:16” and stores nothing, and only the reference is sent to bible-api.com. The same deletion request covers all of this.

If you use the bot dashboard on this website, you connect your Discord account through our authentication provider, Clerk, and allow Discord to share the list of servers you are in (the “guilds” permission). We use that list, each time you open the dashboard, to show and check the servers you can manage; we do not store it. For a server you manage, the dashboard also asks Discord, through the bot, for that server's channels, roles, member counts, your linked Discord membership and role permissions, and the bot's own permissions, to fill in the settings and check who may grant a role; these are shown to you and not stored. When you save a server's settings we record your account identifier and your Fenrir plan against that server, because a Plus or Pro plan unlocks the bot's paid features there. Server settings are stored in a database hosted by Neon for us. To have a server's settings deleted, ask us using the contact address on our Terms page; removing the bot from a server keeps them, so adding it back restores them.

If you buy the bot's Plus, Pro or lifetime Pro inside Discord, Discord processes the payment. We receive only Discord's purchase record: the purchase (entitlement) ID, the product ID, your Discord user ID and the server ID it applies to. We never see your card or billing details. Discord subscriptions are checked from Discord and kept only in the bot's memory; for a lifetime Pro we store which server you claimed it for, until you ask us to delete it using the contact address on our Terms page.

One-server lifetime bot purchases keep a separate order in Neon: the selected Discord server ID, the buyer’s Fenrir account ID and email address, the configured price, amount and currency, Stripe checkout and payment identifiers, whether it was a test or live payment, the checkout reservation, status and timestamps. This supports payment retries, the server’s bot access, refunds and dispute handling. Card details stay with the payment provider. This bot-only record does not grant desktop features.

Discord games include chess, checkers, Trail Race and Fenrir Pack Clash, an original 16-card game available on the public bot. Pack Clash stores card counts and saved decks under the server and member IDs in Neon. Its expedition feature stores the last claim time, Discord interaction ID and result, including the card and server-coin award, to enforce a six-hour cooldown and prevent duplicate awards. That receipt is replaced on the next successful claim; it is not automatically deleted after six hours.

Game invitations and unfinished matches stay in the bot’s memory and are canceled on restart or after 20 minutes without a move; invitations expire sooner. Hands and active deck order are not saved to Neon. Boards and invitations are Discord messages visible to people who can read their channel. A member’s hand is sent only to that member as an ephemeral Discord response. Discord handles those messages under its own policies. The games have no currency wagers, cash redemption or paid combat advantages; paid plans only increase the number of saved Pack Clash decks. Ask for game-data or lifetime-record deletion through the existing contact address on our Terms page; accounting and payment records may need to be retained as described below.

What stays on your computer

Optional BO2 Gift revive reads game-script down/alive telemetry over loopback RCON on your PC. Native nonce, epoch, player and session identifiers are held only in memory, are not published and are not retained. The overlay displays your chosen gifts, target and progress using the existing local overlay and opt-in cloud-mirroring behavior. This feature adds no account or external provider destination and does not automatically upload native telemetry.

Fenrir stores several things locally, in its own folder (%APPDATA%\Fenrir Desktop Beta\engine-data). These remain local except for the specific sharing and account records described above:

Because you are the one holding your viewers’ information, you are the one responsible for it. Depending on where you live that may carry obligations of its own.

Earlier editor and streaming implementations

Stream Studio and Video Editor are not included in the current desktop beta. The details below are retained for people using earlier implementations or keeping their files; they do not describe included features or guarantee how a future release will work.

  • Video projects, source-file references, imported captions, previews and exported videos are processed and saved on your PC. Editing does not upload your footage to Fenrir. Automatic caption generation and its runtime setup remain disabled.
  • When you start a Stream Studio output, Fenrir sends the selected video and audio directly to the destination you configured, including each extra destination you enable. That service receives your broadcast and connection information under its own policy; the broadcast does not pass through Fenrir's website. It can include your screen, microphone, and viewer names or chat shown in overlays.
  • Browser sources load the sites you add. Those sites can receive your network address and their normal web requests. Review each source before showing it on stream; use trusted sites and keep private information off screen.
  • Studio scenes, collections and destination settings are local. They can name the windows, applications, cameras and web addresses you use. Saved stream keys and protocol credentials use Windows account protection. A destination receives the credentials needed to connect; do not share keys, private backups or screenshots containing them.
  • Recordings and saved replays go to Videos\Fenrir unless you choose another folder. Optional highlight clips use its Highlights folder, with a notes file containing the event, viewer name and time. These files stay local unless you share them; delete them like any other files.
  • The encoder check stores graphics-card names, driver versions and encoder results locally. The optional Virtual Camera passes the Studio picture to another app through Windows memory. That receiving app may record or share it. The camera keeps a technical log with process details, picture size and your Windows account security ID; it rotates after roughly 256 KiB. The log does not contain video frames.

Third parties the application talks to

Fenrir connects to TikTok LIVE as an anonymous viewer to read public stream events. It never asks for your TikTok password and cannot post as you. It also downloads TikTok’s public gift list and the gift images from TikTok’s own servers, so the gift browser and overlays can show them.

The connection requires a signed WebSocket address, which is obtained from Euler Stream, a third-party service. Their terms and privacy practices are their own.

Text to speech sends the words to be spoken. Fenrir ships two voice engines. The default uses the same free voices Microsoft Edge uses for read-aloud, which means the text being spoken — which may include a viewer’s chat message or their display name — is sent to Microsoft to be turned into audio. No Microsoft account or API key is required, but the spoken text leaves your computer and may itself identify someone. The other engine uses installed Windows voices to generate speech locally. Select it on the TTS page to avoid sending speech text to Microsoft; this does not turn off Fenrir’s other online connections. Available offline voices depend on your Windows installation. Fenrir attempts an offline fallback if online rendering fails, but either engine can fail to produce audio.

Generated speech audio is cached locally in tts-cache for reuse. If a viewer name or chat message is spoken, that audio can contain it. This is separate from the viewer points file; choosing offline voices does not remove previously generated audio.

The application also contacts download sites when you ask it to install a prerequisite — for example PaperMC or Adoptium for the Minecraft server, Thunderstore for Valheim’s BepInEx loader, or mGBA’s download host for the Pokémon FireRed and Emerald player. Those are the publishers’ own sites and they see an ordinary download request. For launchers it does not install itself, such as Plutonium, it only opens the publisher’s website in your browser.

A diagnostics report you choose to send passes through our website and is delivered to a private, staff-only channel on ourDiscord server, which is where our team reads it. Discord stores it under its own terms and privacy policy. Only Fenrir staff can see that channel.

If you choose to install an update from inside the application, the installer is fetched from GitHub, where our releases are published. GitHub sees a download request like any other.

Visit counts on this website

fenrirapp.com counts page visits with Vercel Web Analytics, so we can see which pages people read. For each page view it records the page, the site you came from, your rough location (country, region, city), and your browser, operating system and device type. It uses no cookies; a visit is recognized only by a hash that Vercel discards after 24 hours, it is not tied to your IP address, and it does not follow you to other websites. We remove everything after the ? in a page address before it is sent, so sign-in and checkout details never reach it. This is the website only — the Fenrir application has no analytics.

Cookies

This website uses only what is necessary to make it work and to keep you signed in if you have an account. We do not use advertising or tracking cookies, and the visit counts above use none.

How long we keep it

Our Neon database holds the Discord bot's server settings, lifetime-purchase records, game collections/decks and last expedition receipts when those games are released, and submission spam-prevention records (described above). It does not store feedback report text or desktop game data. Accounts live with our authentication provider, payments live with the payment provider, optional Live Now listings and Creator Network records also live with our authentication provider, and the application data described above stays local except where stated. We are not holding a warehouse of data with a retention policy bolted on afterward.

Your rights

Depending on where you live you may have the right to ask what personal data we hold about you, to have it corrected, to have it deleted, to object to how it is used, or to receive a copy of it. For us that includes your account and plan, voluntary Live Now listings, Creator Network applications, membership and activity records, reports you sent, and your record of accepting the terms. We cannot reach data that stays only on your machine.

Ask by writing to the address on the Terms page, and say what you want. We answer within 30 days. There is no charge, and asking costs you nothing else — we will not close your account or treat you differently for it.

One limit worth being honest about. If you are a viewer of someone’s stream rather than a Fenrir user, and you want your name removed from their points or leaderboard data, we cannot do that for you. That file is on their computer and we have no copy and no access. Ask the streamer — deleting it removes every balance in it.

To delete what is on your computer, uninstall the application (the uninstaller asks whether to remove your data) or delete the %APPDATA%\Fenrir Desktop Beta\engine-data folder yourself.

Children

Fenrir is not intended for use by anyone under the minimum age required by TikTok’s own terms, and we do not knowingly collect information from children.

Changes

If this policy changes materially we will update the date at the top and say so in the application.

Contact

Questions about this policy can be sent to the contact address on the Terms page.