Privacy policy
Version 2 · Published: 22 August 2026Privacy policy
This policy explains how WOSU and the connected LOSU and DOSU services process personal data. It applies to WOSU users and members of osu! teams authorised for WOSU.
1. Controller
Dimitri Lehmann
Zeieweg 41, 4900 Langenthal
info@dimon.ch
2. Data processed
Depending on the functions used, WOSU may process account data, linked osu! identity and team data, gameplay/profile data retrieved from osu!, scores, beatmaps, PP, ranks and timestamps, replay data and derived timing/skill/training values, team and community data, Discord identity/guild/role data through DOSU, technical information such as IP address, user agent, request ID, login/security events, errors and audit records, and technically necessary session/OAuth/language cookie data. Local passwords are not stored in plain text.
3. Sources and purposes
Data may come from the user, the linked osu! account and osu! API, authorised team/community data, Discord where DOSU is used, and technical use of the services. It is processed to verify identity and access, operate team/community functions, display scores and progress, provide replay/skill/training features, operate Discord onboarding and quests, secure and troubleshoot the platform, audit administrative actions and improve data quality. WOSU does not use personal data for personalised advertising and does not sell personal data to advertisers.
4. Community visibility
Data such as osu! username, team membership, scores, rankings, achievements or community progress may be visible to authorised signed-in community members. Personal views are restricted to the signed-in user where intended.
5. osu! OAuth and Discord
Normal access uses osu! OAuth. Authentication is performed by osu!/ppy and WOSU does not receive the osu! password. Existing permissions may be used for features requiring further osu! data or replays. Where Discord functions are used, DOSU processes the data required for guild, role, onboarding and quest features.
6. Cookies and sessions
WOSU uses technically necessary session, temporary security/OAuth return and language cookies. The current default session idle limit is 12 hours and the absolute maximum lifetime is 7 days. WOSU currently does not set its own advertising or marketing cookies.
7. Security logging
Login attempts, security events, administrative changes and technical errors may be logged with IP address, user agent, request ID, time, affected function and outcome for abuse prevention, rate limiting, incident analysis and accountability.
8. Third parties and international processing
WOSU loads fonts from Google Fonts. Google may technically receive IP address and browser information. Bootstrap and Bootstrap Icons are served locally by WOSU. WOSU also communicates with osu!/ppy and Discord where required. Personal data is not sold. International providers and infrastructure may process data outside Switzerland subject to applicable Swiss requirements and the providers' privacy terms.
9. Retention
Data is retained only as long as necessary for the relevant purpose, secure operation, traceability of community/game history or legal obligations. Sessions expire under the periods above. Security, audit and error data is retained as necessary for protection and analysis. Score, profile, skill, achievement, team and training data may be retained longer as part of continuing community and progression history while a corresponding purpose exists.
10. Rights
Under applicable Swiss data protection law, affected persons may request information about their personal data and correction of inaccurate data. Depending on the circumstances, additional rights such as deletion, restriction, data delivery or objection may apply. Requests can be sent to info@dimon.ch and identity verification may be required.
11. Security and changes
WOSU uses access controls, role-based permissions, secure sessions, CSRF protection, rate limits, audit logging and protected transport connections. Absolute internet security cannot be guaranteed. This policy may be updated when functions, processing or legal requirements change. The published version with its publication date is authoritative.
Last updated
21 August 2026