Privacy notice

Last updated: August 18, 2026

Who operates TuniBot

TuniBot is an independent private-release service. For privacy questions, access requests, or deletion support, contact support@tunibot.live.

Data we process

TuniBot receives KICK identity and channel information, the permissions you grant, encrypted OAuth credentials, settings and automation configuration, uploaded media, signed KICK event payloads, minimized activity and moderation records, aggregate counters, sessions, and security or operational logs. Raw chat is processed ephemerally for configured commands, moderation, and giveaways; it is not maintained as a permanent chat archive.

Why we process it

Data is used to authenticate the channel, provide requested bot and OBS functionality, enforce tenant isolation and safety controls, diagnose delivery failures, secure the service, honor account controls, and comply with legal and KICK developer obligations. We do not sell personal data or use stored chat to build advertising profiles.

Retention

Accepted webhook payloads are retained for up to 24 hours, minimized activity and moderation records for up to 30 days by default, sessions for up to 12 hours, and administrative audit records for up to 365 days. Configuration and aggregate metrics remain while the tenant exists. Operational backups are access-restricted and normally roll off after roughly 14 days. Shorter configured periods may apply.

Sharing and transfers

Data is sent to KICK when necessary to perform an authorized action and may be processed by infrastructure providers used to host the service. It may also be disclosed when required by law, to address abuse or security incidents, or as part of a lawful service transfer with appropriate safeguards. TuniBot does not give another streamer access to your tenant.

Your controls

The dashboard lets you download configuration, disconnect KICK, revoke OBS access, and permanently delete account data. Disconnecting unsubscribes registered events where KICK is reachable, revokes OAuth tokens, removes credentials and sessions, and revokes overlay links. You may also ask to access, correct, restrict, object to, or delete personal data where applicable law provides that right.

Security and cookies

TuniBot uses encrypted credential storage, hashed opaque tokens, signed webhook verification, CSRF protection, ownership checks, and restricted service networks. Essential session and CSRF cookies are used to keep authenticated dashboard requests secure; no advertising cookie is required by this build. No internet service can guarantee absolute security.

Children and changes

TuniBot is not directed to children who cannot legally consent to the service. This notice may change as the private release develops; material changes will update the date above.