Privacy and cookies

Account and sign-in

We store your email, Account UID, linked sign-in identifiers, verification status and account activity dates in the service’s server-side database to provide sign-in and manage access. If you set a password, our self-hosted authentication service stores its verification hash in that database. Google sign-in supplies your account identifier, email and verification details. Microsoft sign-in can also supply your name and other profile details. Our authentication service stores identity and profile details supplied by either provider. We do not request access to your email contents, contacts or files.

Why we process data

We process account data to provide the service you request, on the basis of performing that service agreement. Security records support our legitimate interest in protecting the service. Competition records support the legitimate interests of clubs and participants in ratings and an accurate history, balanced against the rights of the people concerned. You control optional browser saving using the setting below. This policy does not itself give permission to publish someone else’s data.

Club and competition records

The database on the service’s servers stores club and discipline names, member names and handles, account links, roles, membership requests, duel participants, results, dates, tags and changes to results. These records support club management and rating calculations. Club managers can add members and results for people who have no account.

What is public

Club pages, member display names and handles, ratings, duel history and the duel audit trail are public. New clubs appear in the public directory by default. The owner can remove a club from the directory in Club settings. An unlisted club is still accessible to anyone with its link. Audit entries retain the acting member’s name or Account UID at the time of the action. Account email and sign-in credentials are not included in these public views.

Club contributors must inform participants about public records and have a lawful basis to enter and publish their data. Use a nickname when a real name is unnecessary, and avoid sensitive or unrelated details. People without accounts can also ask about their data. The service has no general age restriction or automated parental-consent process; obtain parental or guardian involvement where the law requires it before entering a child’s identifying data. A parent or guardian can contact us about a child’s records.

Cookies and browser storage

Sign-in, security and navigation use functional cookies or browser storage. Remembering language, appearance, sorting preferences and form drafts is on by default; you can turn it off and remove saved values below. These features do not use advertising or analytics trackers.

• Browser settings (localStorage): theme, whether the header is collapsed, and club sorting choices. They are not saved as account preferences or synchronized between devices. The selected sort order is also sent to the server when requesting a club list.
• Language cookie: your chosen language is stored in your browser and sent with requests so the server can render pages in that language. It is not saved as an account preference.
• Sign-in and security cookies: the browser stores signed account and expiry data, sign-in flow protection and temporary password-operation results, and sends them with relevant service requests. Sign-in cookies cannot be read by page scripts. Sign-in and provider tokens are not stored in localStorage.
• Form drafts (sessionStorage): the current tab stores club and first-discipline names, discipline names, or member names and handles entered in creation forms, together with account and form identifiers and expiry times needed to restore them. Drafts are not uploaded to the server as drafts. Submitting a form sends its data to the server normally.
• Import data (page memory): the file contents, participant mappings and progress stay in the open page’s memory, without being saved to localStorage or sessionStorage. The original file is not uploaded. A capacity check sends the chosen club, discipline and record counts to the server. Starting the import sends the reviewed new member and duel records; accepted records are saved in the service database.
• Navigation: the browser also keeps technical page-history and scroll-restoration metadata. This remains available when optional saving is off; it does not contain saved form-field values. Browser-managed history or form recovery follows your browser’s own settings.
• Saving choice: a necessary cookie records your on/off choice, the notice version and decision time for up to 180 days. It contains no account identity. Turning saving off removes the site’s optional saved settings and drafts where browser access permits; turning it on again does not restore old drafts.

You can change optional saving above at any time. When enabled, the language cookie lasts up to 365 days, local preferences remain until replaced or cleared, and eligible drafts can be restored for up to 24 hours in the current tab. Drafts clear on sign-out or account change when storage is available. Sign-in cookies last up to 7 days; other authentication cookies are short-lived. Clearing all cookies and site data in your browser may sign you out. Turning off optional saving keeps you signed in.

Operations and service providers

Server logs record requests and errors for diagnostics and security. The web server’s access log includes IP addresses. These records are separate from public duel history. Hosting infrastructure processes data to run the site. The authentication email delivery service receives the recipient address and message content. External sign-in providers process the sign-in you initiate under their own policies. Discord is also an external service with its own data practices; we do not embed a Discord widget.

How long records stay

Account data is kept for sign-in and access management, and club, member and duel records for ratings and competition history. These account and competition records have no fixed retention period or automatic expiry. Technical logs contain request and error records, including IP addresses. Their local storage is limited by size, and older logs are removed as files rotate; this does not guarantee a retention period in days. Archiving, voiding a duel and signing out do not delete history.

Data requests

You can request a copy of your personal data in a machine-readable format, such as CSV or JSON, correction or deletion of the data, including deletion of your account. Use the contact below to submit a request.

Contact

Contact the Legends Wall team through Discord and ask for a private conversation. Identify the account or club/player page concerned. We may need to verify your identity or authority to act for someone else. Do not post passwords or personal information in public channels.

Community on Discord