The rules behind the curtain.
What Yon keeps, what the public site may show, what stays private, and how a member can pull the plug.
Information Yon may store
Depending on the features a member uses, Yon may store a Discord user ID, submitted RuneScape name, membership track, profile preferences, goals, competition participation, nominations, claims, votes, and a stable Dink account hash used to connect RuneLite activity to the correct Discord member.
Dink connection data
A private connection token is created when a member runs /yon-dink connect. Running the command again replaces the previous token. Private configuration and event URLs function like credentials and should never be shared.
Dink screenshots are accepted for forwarding to the configured Discord channel and are not intended to become a permanent screenshot archive on the relay. The bot may retain limited metadata needed for identity, filtering, deduplication, rate limiting, and recent activity status.
Public website data
The public website contains clan-approved information such as event guides, selected winners, and achievements. Private profiles, connection tokens, Discord credentials, server addresses, logs, and administrative controls are never published.
Accuracy and verification
Dink events are submissions from a member’s RuneLite client. They are useful for community celebration, but they are not direct verification from Jagex. Staff may review unusual claims or remove posts when necessary.
Member controls
Members can use /yon-dink disconnect to revoke a Dink connection. Profile and privacy tools are available through /yon. Contact clan staff in Discord for help with correction or deletion requests.
Contact and member requests
Existing members can contact a clan moderator in Discord for profile corrections, deletion requests, Dink connection help, or removal of an achievement from public display. Staff will review each request and handle it as soon as reasonably possible.
Last reviewed: July 20, 2026.