Privacy policy.

Last updated September 21, 2026

TipKick uses information to create tokens, authenticate wallet sessions, keep support accounting, and publish payment receipts. We do not ask for your private keys, seed phrase, or social login.

What the app processes

• Your public wallet address and wallet-signed authentication message.
• Token names, symbols, descriptions, artwork, selected Kick channels, transaction signatures, and other launch details you submit.
• Creator-fee collection records, dollar allocations, and payment records, including receipts uploaded by operators.
• Technical request information needed to host, secure, and troubleshoot the service, which hosting providers may process in their logs.

What is public

Token details, selected streamer handles, public blockchain addresses, transaction references, support amounts, and published receipt images are visible to visitors. Blockchain information is also independently public on Solana. Operators should remove personal and sensitive payment details from receipts before publishing them.

Why we use it

We use these records to prepare the launch you request, verify your wallet authorization, confirm transactions, enforce operator access, prevent duplicate or fraudulent records, attribute creator fees, and show the history of Kick support purchases.

Storage and service providers

TipKick uses Vercel for hosting and Supabase for application data and uploaded files. Solana RPC services and Pump.fun process information involved in token creation and transaction verification. Your wallet provider handles connection and signing. Clicking a Kick channel or external receipt destination may take you to a separate service with its own privacy practices.

Token metadata and artwork published for a launch may be distributed publicly outside the TipKick database. Public blockchain records cannot be removed by TipKick.

Cookies and device storage

The application uses session cookies to keep you authenticated after you prove wallet ownership. It may store connection preferences and a pending launch reference on your device to recover confirmation after a refresh. These features support the requested service. Do not launch from a shared device unless you are comfortable with these public transaction references remaining accessible there.

Retention and requests

We retain records needed to operate the service, account for support purchases, investigate abuse, and maintain public payment history. Removing an application record does not remove immutable blockchain records or copies held by independent services. To raise a privacy concern, start with a general request on the TipKick issue tracker without posting sensitive information. Do not attach private receipts, identifying documents, or wallet secrets to a public issue.

Changes

We may update this policy as the product changes. The date above identifies the latest published version.