How does CommentMuxer handle my Twitch sign-in token?

Updated

Short answer: CommentMuxer never sees your Twitch password and does not keep the token.

How Ecamm signs in

When you add the Twitch destination, Ecamm does the Twitch sign-in itself, with Twitch, using your Twitch account. CommentMuxer does not take part. It never sees your Twitch password.

What reaches the app

While Muxing is on, Ecamm's Twitch traffic is answered on your Mac. Ecamm sends its Twitch sign-in token along with that traffic, as it would to Twitch.

What the app does with it

  • It ignores the token. It does not need it and does not check it.
  • It does not store it.
  • It does not log it. The app also does not log header values or query strings.
  • It does not send it anywhere. The app removes the token from the request before it passes it on inside the app.

What is left alone

Only the addresses Ecamm needs for chat, the stream key and video are answered locally. Twitch's sign-in addresses are not touched, so signing in still goes to the real Twitch.

Which Twitch account?

A normal free Twitch account is enough. We do not collect your Twitch account details.

Why this matters

Our How it works page and the Privacy Policy state this openly. It is part of why we ask you to stay in control: you can press Stop Muxing at any time to send Ecamm back to the real Twitch.

If you are still concerned

You can end the redirect any time. See Start Muxing and Stop Muxing. To change your Twitch password, do that at Twitch. Nothing in CommentMuxer needs updating afterwards.

If that didn't work

Contact support with your question.

Was this helpful?

Still need help? Contact support

Related articles

Back to support