Summary
- forge is a desktop app that runs on your own computer. The developer runs no server for it and receives none of your data.
- forge has no analytics, no telemetry and no ads.
- When you connect YouTube, forge uses your Google data only to provide the YouTube features you use in the app.
- Sign-in tokens are encrypted and stored only on your device. Chat history and settings stay in a local database on your device.
- Your data is never sold. It leaves your computer only to the places you set up yourself.
About forge and this policy
forge is a free, open-source desktop application for live streamers, developed by IceSqueez and published at github.com/IceSqueez/forge. It connects to Twitch, YouTube and Kick, to OBS and to other tools you choose, and runs automations you configure. In this policy, “forge” means the desktop application and “we” means its developer.
This policy covers the forge application. The icesqueez.com website itself uses Cloudflare Web Analytics, which counts page views without cookies and is not connected to the app in any way.
Google user data that forge accesses
forge uses YouTube API Services. When you choose to connect a YouTube account, forge opens Google’s sign-in page in your browser and uses OAuth 2.0 (Authorization Code with PKCE and a loopback redirect to your own computer). forge never sees your Google password.
forge requests a single scope: https://www.googleapis.com/auth/youtube.force-ssl (“See, edit, and permanently delete your YouTube videos, ratings, comments and captions”). With it, forge accesses:
- live chat messages on your broadcasts and their author details (display name, channel ID, profile image, and whether the author is the owner, a moderator, a member or verified), including Super Chats, Super Stickers and membership events shown in chat;
- your own live broadcasts and their video metadata: title, description, category, privacy status, thumbnail, and live status;
- your channel information, and membership and subscription information used to show stream events;
- chat moderation data: banned users and the list of moderators on your chat.
forge does not access your Gmail, contacts, Drive, calendar or any other Google service.
How forge uses Google user data
forge uses Google user data only to provide the features you use in the app:
- show your YouTube live chat in forge, next to Twitch and Kick chat;
- send chat messages as you, and run the automations you set up (for example, replying to a chat command or thanking a member);
- moderate your chat when you or your automations ask it to: delete messages, ban or time out users, unban them, add or remove moderators;
- read and update your own broadcast details when you ask it to: title, description, category, privacy status and thumbnail;
- turn chat messages, Super Chats, memberships and stream status changes into events that fire the triggers you configured, for example an overlay alert or a line of text-to-speech.
forge does not use Google user data for advertising, does not build profiles of you or your viewers, and does not use it to train machine-learning or AI models.
How data is stored
- OAuth tokens (for Google and for the other services you connect) are stored only on your device, encrypted with AES-GCM. The encryption key is kept in a key file in forge’s data folder on your computer.
- Chat history, settings, actions and other app data are stored in a local SQLite database in the same data folder.
- Nothing is stored on servers run by the developer. There are none.
forge’s data folder is ~/.local/share/forge on Linux, %APPDATA%\forge on Windows and ~/Library/Application Support/com.icesqueez.forge on macOS, unless you point the FORGE_DATA_DIR environment variable at another folder.
Google API Services User Data Policy
forge’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
- Google user data is used only to provide and improve the user-facing YouTube features of forge described above.
- It is transferred to others only as needed to provide those features at your direction (as listed in “How data is shared”), to comply with applicable law, or as part of a merger, acquisition or sale of assets with notice to users.
- It is not used or transferred for serving ads, including retargeting, personalized or interest-based advertising.
- No human reads it. The developer has no access to it, because it never leaves your computer except to the places you set up.
By connecting a YouTube account you also agree to the YouTube Terms of Service. Google’s handling of your data is described in the Google Privacy Policy.
Retention and deletion
forge keeps local data only within limits. Chat history keeps the most recent messages of each viewer (50 by default, adjustable in settings) and drops older ones. The event log and action history are pruned after the number of days set in settings (7 by default). You are in control:
- Revoke forge’s access to your Google account at any time at security.google.com/settings/security/permissions. After that, forge can no longer access your YouTube data.
- Delete all forge data, including stored tokens and chat history, by quitting forge and deleting its data folder (locations above). Uninstalling the app alone may leave this folder in place.
Security
forge connects to Google and other platforms over HTTPS, encrypts stored tokens, and keeps sign-in tokens out of its logs. Its source code is public, so anyone can check how data is handled.
Children
forge is a tool for streamers and is not directed at children under 13. We do not knowingly collect personal information from children, and forge does not send any data to the developer.
Changes to this policy
If this policy changes, the new version is published on this page with a new “Last updated” date. If forge starts using Google user data in a new way, it will ask for your consent first.
Contact
Questions about this policy or about your data: forge@icesqueez.com. You can also open an issue on GitHub.