Privacy Policy

Short version

Messages you send through Clutch are never logged or stored, the same as they've always been. The one exception is templates: if you choose to save a message as a reusable template, that content (header text, sign-off, and stream slot details) is stored so it's there next time you log in. It stays until you delete it. Nothing else you type or send is kept anywhere.

What Clutch asks Discord for, and why

• When you log in, Discord shares your username, user ID, and which servers you're in along with your permissions there. This is used once, at login, purely to confirm you're an admin or owner of the server you want to use, then it's discarded except for what's placed in your session cookie (see below).
• The Clutch bot, once added to a server, can only see that server's list of webhooks and channel names, so it can list them for you to pick from. It cannot read messages, and isn't granted any permission to.
• Messages you compose are sent directly to the Discord webhook you choose, the same way any Discord webhook works. Clutch does not log, store, or retain a copy of anything you send.

Saved templates

If you use "Save as template," the header text, sign-off line, and stream slot details you saved are stored in a database, tied to the Discord server you're using Clutch on. Anyone who's an admin on that server and logs into Clutch can see and use templates saved there, same as they can see any webhook or channel in the server. Nothing about sending a message uses this storage, only the deliberate "save as template" action does. Delete a template any time from the Templates panel, and it's gone immediately. You can also use "Delete all data for this server" in the server card at the top of Clutch to remove every template saved for your server at once.

Saved templates are encrypted before they are stored (AES-256-GCM), and the server ID used to find them is stored as a hash rather than in plain text. The encryption key is kept in Clutch's server settings, separate from the database, so a copy or leak of the database on its own is unreadable. Clutch's servers do decrypt a server's templates when its admins open the Templates panel, so this protects the stored copy; it isn't a promise that nobody could ever reach it.

The session cookie

After logging in, your browser holds one signed, HttpOnly cookie containing your Discord user ID, username, and which server you selected. It expires automatically after 12 hours, or immediately if you click "Log out." It never leaves your browser except back to Clutch's own server to prove you're logged in, and it isn't sent to Discord or anyone else. This cookie itself is never written to a database, saved templates are the only thing that is.

Cookies overall

Clutch sets no analytics, advertising, or tracking cookies. The only cookies are the login session described above and a couple of short-lived ones used only during the login handshake itself (oauth_state, pending), which expire within minutes.

Third parties

The only third party involved is Discord itself, since Clutch is a tool built on Discord's own login and webhook systems. Discord's handling of your data is covered by its own Privacy Policy. Clutch doesn't sell, share, or hand data to anyone else.

Who runs Clutch, and why

Clutch was made by one developer, Sabotazh, out of a wish to help streamers. There are no ads and no paid plans, nobody's data is sold, and it isn't run for profit. Donations are an optional thank-you and never required.

Clutch is run for free by one person. If the developer can't keep running it for free at any point, it will be closed down and all stored data will be deleted.

Changes

If this policy changes, the "last updated" date above will change too.

Contact

Made by Sabotazh. See the Terms of Service for the rules of using Clutch.