Claywood Group - Contact

Whenever you stop by at Claywood or meet a Claywood Group staff menber, feel free to appoach us! Of course, you can also message Claywood Group staff members directly via the chat anytime.

If there is no Claywood Group staff member at hand, you can leave a written message at our letterbox at Claywood.

If you have a more detailed inquiry, can't or don't want to approach us in-game or just find this more comfortable, you can reach us at claywood@posteo.com.

Discord doesn't reliably protect user data end-to-end, especially for text: Discord's own documentation says message content is not end-to-end encrypted because of its moderation approach. Beyond encryption, Discord has also faced security incidents involving sensitive user information, including a disclosed incident where a compromise of a third-party customer support provider exposed data from users who contacted Discord support/trust & safety (such as names/usernames, email/contact details, limited billing details, IP addresses, and messages exchanged with support agents, and in some cases limited government-ID images used for age appeals).

On verification and "data minimization," Discord's help center states that accounts may be required to verify email and/or phone number as part of its safety system, and that in some cases it may require a valid phone number; it also explains that the phone number used for verification cannot be attached to an existing Discord account. Discord's Terms also explicitly allow that it may require users to provide contact methods such as email and/or phone number and birthday, and that in some cases users may be required to verify their account or provide additional information. With age restrictions, Discord has minimum-age rules that vary by country, and it has been rolling out "age assurance" systems in specific jurisdictions due to regulations such as the UK Online Safety Act and similar frameworks in other countries.

In its UK-specific documentation, it describes a privacy-forward age assurance flow and states that UK users can only access age-restricted content or change certain settings after verifying their age through that process. Separately, Discord has stated that after backlash it delayed/modified parts of its global age verification approach to the second half of 2026 and is changing the implementation details and vendor options. Overall, if your priority is minimizing what you must trust - both in day-to-day operations and in how personal data is handled - Discord can be hard to treat as "unrestricted and unequally trustworthy," because it is a centralized service and because its strongest privacy protections are not uniform across message types and features.

That's exactly the motivation for considering a protocol like Matrix: Matrix is an open standard for federated communication where you can use different client apps with the same Matrix account (similar to how email works across providers/clients), and the server-side infrastructure is under your community's or organization's control if you host your own homeserver. Matrix also supports end-to-end encryption for rooms in a room-by-room, client-side way using Olm/Megolm-style ratchets (so the homeserver typically can't decrypt message contents by default when encryption is used correctly). Matrix generally improves privacy and data control by design and reduces "single-provider dependence". I recommend to move, to target encrypted-room usage from day one (and to plan for moderation/mod tooling in that context).

If a full migration isn't feasible, a practical stepping stone is to create a parallel Matrix space and use a bridge to the Discord server selectively to ease onboarding—while being transparent that bridged rooms can change the privacy/security properties compared to native encrypted Matrix-only conversations.

Check out Matrix for yourself: