Privacy Policy

This policy describes the information Slop Crypto processes when you watch the stream, authenticate a wallet, submit a prompt, or use the payment flow. The service is designed to work without requiring an email address or conventional profile.

1. Information collected

• Wallet and chain data: public wallet addresses, signed authentication challenges, transaction signatures, amounts, assets, slots, and confirmation evidence. Private keys and seed phrases are never requested or stored.
• Submission data: prompts, optional display names, selected duration, moderation decisions, generated media, queue and playback history, and accepted policy version and digest.
• Operational data: IP address, request identifiers, browser and device information normally present in HTTP requests, rate-limit events, security logs, provider request identifiers, and error records.

2. Why information is used

Information is used to authenticate wallets, verify payment independently, moderate and generate content, operate the queue and livestream, investigate failures or abuse, process refund or credit reviews, secure the service, maintain accounting records, and comply with applicable obligations.

3. Public information

Blockchain transactions and wallet addresses are public by design. Approved prompts, optional display names, generated clips, and playback events may appear publicly. Selecting anonymous attribution hides the display name from the public presentation; it does not remove the wallet and submission relationship from operational records.

4. Service providers

Information is disclosed only as needed to infrastructure, media-generation, object-storage, blockchain RPC, security, and hosting providers that operate the service. A generation provider receives the moderated prompt and generation settings. Public blockchains process payment data independently under their own protocols. We do not sell personal information.

5. Retention

• payment, treasury, policy-acceptance, moderation, and material audit records are retained long term for accounting, safety, and dispute evidence;
• approved normalized masters and playback history may be retained long term for archive replay;
• original provider outputs are retained for 30–90 days (90 days by default), while raw webhook payloads follow the configured operational retention interval, unless either is needed for a dispute, abuse investigation, or legal obligation;
• failed temporary media is normally removed within 1–7 days;
• local playout cache is managed by size and may be removed after durable storage is verified.

Actual retention can be longer when necessary to protect the service, resolve a payment or moderation dispute, comply with law, or preserve the only evidence of an aired paid submission.

6. Security and choices

Access controls, encryption, constrained provider credentials, checksum verification, and audit logs are used to protect service data. No system is perfectly secure. You can watch without a wallet and submit without a display name. You may request access, correction, or deletion where applicable, although public blockchain records and records required for security, accounting, or legal obligations cannot necessarily be changed or deleted.

7. Contact and changes

Privacy requests should identify the relevant wallet or submission without providing a private key and be sent to [email protected]. Material changes will receive a new policy version and effective date.