# Personal desktop moderation tool — policy clarification

**URL:** <https://discuss.dev.twitch.com/t/personal-desktop-moderation-tool-policy-clarification/65035>\
**Category:** API\
**Created:** [September 16, 2026, 10:17am UTC](https://discuss.dev.twitch.com/t/personal-desktop-moderation-tool-policy-clarification/65035 "2026-09-16T10:17:04Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Denys\_Rubchinsky](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/denys_rubchinsky/32/31864_2.png) [@Denys\_Rubchinsky](https://discuss.dev.twitch.com/u/Denys_Rubchinsky)\
**Post date:** [September 16, 2026, 10:17am UTC](https://discuss.dev.twitch.com/t/personal-desktop-moderation-tool-policy-clarification/65035/1 "2026-09-16T10:17:04Z")

</div>

```auto
Hello Twitch team,

I am developing a private Windows desktop application for my own use as a channel moderator.

It would receive chat messages and AutoMod-held messages through official EventSub subscriptions and highlight configured keywords in a private local queue. This helps me notice messages when chat moves very quickly.

Timeouts and channel bans would only be issued through the official API after I manually click a button. The queue would also update when another moderator takes action.

The application would NOT:
- Approve or deny AutoMod-held messages.
- Change AutoMod settings.
- Send messages to chat.
- Scrape Twitch pages or bypass access restrictions.

It would supplement the normal Twitch moderation interface.

The current prototype is offline. Before connecting it, could a Twitch staff member clarify:

1. Is this use case permitted?
2. Is any additional approval required?
3. What privacy notice and chat-log retention requirements apply to a private, single-user tool?

We plan to follow OAuth validation, permission, and API rate-limit requirements.

Thank you.

```

---

<div class="post-metadata">

**Author:** ![BarryCarlyon](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/barrycarlyon/32/253_2.png) [@BarryCarlyon](https://discuss.dev.twitch.com/u/BarryCarlyon)\
**Post date:** [September 16, 2026, 10:20am UTC](https://discuss.dev.twitch.com/t/personal-desktop-moderation-tool-policy-clarification/65035/2 "2026-09-16T10:20:56Z")

</div>

> [@Denys\_Rubchinsky](#):
>
> `Before connecting it, could a Twitch staff member clarify:`

You are unlikely to get an answer from staff here on the subject. If any staff are actively monitoring

> [@Denys\_Rubchinsky](#):
>
> `1. Is this use case permitted?`

Most channels likely keep this data on hand for referencing bad actors, historically, either for ease of access or for having data from before Twitch own logs began

> [@Denys\_Rubchinsky](#):
>
> ```auto
> 2. Is any additional approval required?
> 3. What privacy notice and chat-log retention requirements apply to a private, single-user tool?
> 
> ```

I’m not a lawyer and cannot give legal advice, I would consult a lawyer.

> [@Denys\_Rubchinsky](#):
>
> ```auto
> I am developing a private Windows desktop application for my own use as a channel moderator.
> 
> ```

Just make sure the channels you moderator for are aware as they may or may not want this sort of thing run on their channel and/or only be accessable by one moderator.

---

<div class="post-metadata">

**Author:** ![system](https://d2opxh93rbxzdn.cloudfront.net/original/2X/0/05909729875cce3b53e59d5561c4d23bb14948fc.png) [@system](https://discuss.dev.twitch.com/u/system)\
**Post date:** [October 16, 2026, 10:21am UTC](https://discuss.dev.twitch.com/t/personal-desktop-moderation-tool-policy-clarification/65035/3 "2026-10-16T10:21:15Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
