Privacy Policy
Red Ball Token is designed for minimal personal-data collection. Most activity is wallet and event based, not traditional profile-account based. This page clearly explains what we collect, what we do not collect, and how data is used.
Storage Transparency (Clear Summary)
- Stored on your device: wallet access material and local app state.
- Synced to relay/backend: signed protocol events needed for network consistency.
- Public to community users: RedPost, announcements, Redbugs posts, and reactions you submit.
- Not centrally stored in plaintext: private keys, passcodes, security answers.
Data We Collect
- Public wallet address used for protocol identity.
- Signed events required for protocol operation and replay (match actions, rewards, transfers, etc.).
- Community posts and reactions (RedPost, Redbugs, announcements, upvote/downvote/Redflag actions).
- Technical service logs for uptime, sync reliability, and abuse prevention.
Data We Do Not Collect
- No plaintext private keys.
- No plaintext passcodes or plaintext security answers.
- No mandatory email/password account profile for core protocol use.
- No sale of personal data to data brokers.
Optional Data You May Provide
- If you contact support, you may provide email/message details voluntarily.
- If you post publicly, your submitted content is visible to other users.
- Avoid posting sensitive personal, banking, or identity information.
How We Use Data
- To operate core protocol features and maintain wallet/event synchronization.
- To show balances, rewards, transfers, and community activity.
- To investigate bugs, enforce abuse controls, and improve reliability.
- To protect platform integrity and security.
Data Sharing
- Public protocol/community data is visible in public app/website views.
- Service providers may process infrastructure logs under contractual controls.
- Data may be disclosed if required by applicable law or lawful process.
Retention and Control
- Event history may be retained for continuity, replay validation, and auditability.
- Public posts may remain visible in community timelines.
- Wallet recovery/access control remains user responsibility.
- You can limit shared data by avoiding sensitive submissions in public fields.
What “On Device” Means
- Local wallet credentials and sensitive access factors are intended to remain device-local.
- If you uninstall the app or lose device access without recovery details, access may be unrecoverable.
- Network-visible activity (events/posts/reactions) is not device-private once submitted.
- For full privacy, do not submit personal or confidential information in community fields.
Your Rights and Questions
Privacy rights vary by jurisdiction. If you have a privacy question or request, contact support@redballtoken.com. We may update this policy as the product evolves; updated versions will be published on this page.