Privacy.

kickinit is a toolkit for Kick streamers (games, tools, widgets, and Overlay Studio). This page explains what we collect when you Connect with Kick and what stays on your device.

Kick OAuth scopes

Connect with Kick uses OAuth 2.1 + PKCE. You never give kickinit your Kick password. We request:

• user:read — who you are on Kick
• channel:read — confirm your channel
• events:subscribe — chat and channel events for games/widgets (subs, gifts, kicks, follows, live status)
• chat:write — send command replies in your chat (for example !points on Plinko). Replies use your user token until Kick approves a bot badge
• kicks:read — kicks economy for Plinko auto-drops

You can disconnect from a setup page. Revoking the Kick app in Kick settings also cuts access.

What we store on our servers

After Connect we store your Kick user id, channel slug, OAuth tokens (to refresh chat/event access), a login session cookie (plinko_session), and per-product overlay tokens. Overlay URLs use an unguessable overlay id — not your OAuth token. Chat messages used for games are processed to run the product, not sold.

Overlay Studio

Kick Overlay Studio is 100% in your browser. Your files stay on your device. Media is processed in your browser. Projects live in IndexedDB on that computer. We do not upload Studio media to kickinit.

Cookies

We use a short-lived OAuth cookie during Connect, then a session cookie so Hub / Plinko / Rumble know you are logged in. OBS overlays use the overlay token in the Browser Source URL, not the session cookie.

Contact

Questions: the streamer who runs kickinit — travvvman on Kick.