Privacy Policy

• Authentication and API tokens required to connect authorized services.
• Basic account identifiers returned by authorized providers (for example, user IDs).
• Operational metadata such as request logs, security events, and rate-limit decisions.
• A local play history stored only in your browser: the IDs of clips Snippy has played and when each last played. It is used to avoid repeating clips too soon. The history itself is not sent to Snippy's servers; diagnostics include only aggregate counts, such as how many clips it holds.

• To authenticate users and perform requested actions.
• To operate core features, including clip retrieval and queue display behavior.
• To protect the service against abuse, scanning, and unauthorized access.
• To troubleshoot reliability and performance issues. While you are logged in, error reports and diagnostics are labelled with your Twitch user ID and login, so a problem can be traced to the channel it affected rather than blended with everyone else's. Nothing further is attached: not your display name, not your avatar, and no automatic collection of personal data such as IP addresses. Diagnostics recorded before you log in are not labelled this way.
• If you install Snippy's Streamer.bot actions, they check for updates in the background when Streamer.bot starts. That check sends the actions' version numbers and your Twitch user ID and login, which are used only to understand which versions are in use. Because the check is not logged in, that ID is recorded as unverified and kept apart from the diagnostics described above.

Snippy uses technical safeguards intended to protect data in transit and at rest. No method of storage or transmission is guaranteed to be fully secure.

Snippy does not sell personal information. Data may be processed by infrastructure or integration providers strictly to operate the service.

Data is retained only as long as needed for service operation, security, legal obligations, or dispute resolution. The local play history keeps at most 1,000 clips and removes the oldest automatically.

You can stop using Snippy at any time. You can revoke third-party authorization through the relevant provider settings here: https://twitch.tv/settings/connections. The application name is "DesertIce's Snippy".

You can erase the local play history at any time by clearing site data for Snippy in the browser it runs in. In OBS, the browser source's "Refresh cache of current page" button only reloads the page and does not remove this data. To remove it, close OBS and delete the obs-browser folder inside OBS's plugin_config directory, as described in the OBS guide to clearing browser data. OBS recreates the folder on its next start. This also signs every OBS browser source and dock out of the sites they were logged in to, Snippy included.

This policy may be updated from time to time. The current version is always the one published on this page with the updated date.