Privacy notice
Last updated: August 25, 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, product configuration, signed KICK event payloads, command usage, Loyalty usernames, balances, level progress, active-chat minutes, reward redemptions, sessions, and security or operational logs. Raw chat is processed ephemerally for configured commands, giveaways, Loyalty earning, configured moderation rules, Community Rankings, and live Chat Widgets; it is not maintained as a permanent chat archive. Community Rankings stores compact per-channel message, active-day, active-stream, and moderation-action counts plus the latest observed public username, avatar, and role-badge history; it does not store message content or claim to provide a complete KICK role roster. Moderation history stores the viewer ID, rule, action, result, and time—not the full message body. Viewer Guard processes official concurrent-viewer counts and aggregate engagement signals; it does not collect a viewer list or retain raw chat content. The security system processes IP addresses, limited user-agent summaries, request paths, risk signals, and account login associations to detect abuse and protect the service. Exact IP values are encrypted at rest; keyed hashes support lookup and deduplication. Anonymous browsing is retained primarily as daily aggregate observations.
Why we process it
Data is used to authenticate the channel, provide requested bot 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.
Community data
TuniBot Community stores the profile details you choose to publish, friendships and blocks, posts with up to four images, reactions, comments, room chat, direct messages, notifications, Streamer applications, and abuse reports. New posts default to Public visibility, and you can choose Friends before publishing. Direct messages are available only between accepted friends; history is preserved after unfriend or block while new messages are prevented. Deleted content is hidden or cleared, and deleting your TuniBot account removes related Community records. Uploaded images are access-controlled and stored with non-guessable identifiers. The TuniBot owner can review public-room content and only reported direct messages with limited context.
Retention
Accepted webhook payloads are retained for up to 24 hours, sessions for up to 12 hours, and administrative audit records for up to 365 days. Product configuration, Community content and relationships, Streamer application history, Loyalty records, and compact Community Rankings aggregates remain while the account exists; Community Rankings replay markers expire after 30 days. Privacy-minimized non-chat widget events expire after seven days. Moderation action logs use the streamer-selected 1–90 day retention period. Optional Loyalty reward input is limited to 240 characters. Operational backups are access-restricted and normally roll off after roughly 14 days. Viewer Guard raw 10-second samples expire after seven days and minute aggregates after 90 days; compact stream summaries remain for adaptive channel baselines. Shorter configured periods may apply. Security events normally expire after 90 days, high-risk evidence after up to 365 days, account login/IP history after 180 days, and anonymous daily observations after 14 days. The owner can configure shorter retention periods. Premium grants, code redemptions, platform suspensions, appeals, community moderation decisions, and essential owner audit events remain as needed to provide and secure the account service.
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 disconnect KICK and permanently delete account data. Disconnecting unsubscribes registered events where KICK is reachable, revokes OAuth tokens, and removes credentials and sessions. 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, trusted-proxy validation, rate controls, abuse detection, temporary platform IP blocks, 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.