Privacy Notice
Version 2026-09-02-beta-2 · Effective September 2, 2026
GULP records the information needed to run and secure the beta. Do not upload secrets, private keys, confidential information or content you are not permitted to use.
What the beta processes
GULP may process wallet addresses, signed authentication messages, channel and token configuration, prompts, uploaded media, generated output, votes, chats, clips, ad campaigns, transaction identifiers, device and request metadata, and versioned legal acceptance records.
Why it is processed
Information is used to operate and secure the beta, authenticate wallets, generate and deliver media, administer channel budgets, process requested blockchain activity, moderate content, measure performance, prevent abuse, troubleshoot failures and document legal acceptance.
Legal acceptance records
For evidence and security, GULP records the accepted terms version and time, a random acceptance identifier, and salted hashes derived from IP address and browser user-agent. When you connect a wallet, the acceptance record may be associated with that public wallet address.
Service providers and public chains
AI, hosting, database, streaming, storage, analytics and blockchain providers may process data needed to perform their services. Information submitted to a public blockchain is public and may be permanent. GULP cannot delete or modify public-chain records.
Retention and choices
Beta records may be retained while reasonably needed for security, accounting, dispute handling, legal compliance and product testing. Privacy rights vary by location. A final public release requires an operator identity, privacy contact, retention schedule, processor list and jurisdiction-specific rights process approved by counsel.
Security
No system is perfectly secure. Never provide GULP with your private key or seed phrase. Wallet authentication asks only for a message signature and should not submit a transaction or spend funds.