Privacy notice · Public TEST beta
Your wallet. Your play. Clear boundaries.
This notice describes the data handled by the current valueless CLASH TEST environment.
TEST beta privacy
- 01What this beta processes
Your public wallet address, clan and gameplay activity, submitted answers or TEST evidence, server timestamps, and limited security and operational logs.
- 02Why
To authenticate players, run Clan Wars, verify scores and proofs, prevent replay or abuse, resolve results, support players, and operate the TEST beta.
- 03Public information
Clan names, public wallet addresses, War scores, and verified results may be visible to other beta players. Never submit a private key or seed phrase.
- 04Sensitive evidence
Do not upload IDs, payment details, secrets, or unnecessary personal information. Accepted image formats are malware-scanned, decoded, stripped of metadata, re-encoded, encrypted, and available only through the authorized founder review workflow.
- 05Storage and retention
The original file and filename are not retained. The sanitized encrypted image expires after 30 days by default and is then scrubbed by the documented retention workflow. Proof decisions and redacted audit records may remain for game integrity.
- 06Clan chat
Messages, player names and server timestamps are stored in the TEST database. Current clan members can read the latest 100 messages, including messages sent before they joined. Leaving or being removed revokes access. Chat is not end-to-end encrypted; do not share secrets or sensitive personal information.
- 07No real-value processing
This public beta uses valueless TEST credits. It does not enable real-money payments, real-token custody, or real-asset settlement.
- 08Contact
For privacy, support, or incident questions, contact the official @clashdotfun account on X before submitting sensitive information. Never send private keys, seed phrases, IDs, or evidence through a public post.
This is a limited public TEST-beta notice, not production-token or real-value launch terms. Updated notices must be published before those boundaries change. Support: @clashdotfun on X.