Privacy Policy
This privacy policy applies to voidlog (voidlog.breakbar.cc). The main site breakbar.cc and the other tools on its subdomains have their own privacy policies. The German version is authoritative; this English text is a courtesy translation.
Last updated: October 2026
1. Controller
The controller within the meaning of the GDPR is Patrick Schmidt, Fischenzstr. 39, Konstanz, Germany, e-mail: [email protected]. Further details are in the legal notice at https://www.breakbar.cc/impressum.
2. What this is
voidlog is a fan project for uploading, analysing and comparing Guild Wars 2 combat logs (EVTC) within projects (e.g. training groups). It is not an official ArenaNet service. Using it requires signing in with Discord.
3. Hosting and server logs
voidlog runs on a virtual private server (VPS) that I rent from netcup GmbH, Emmy-Noether-Str. 10, 76131 Karlsruhe, Germany. When you visit the site, the web server automatically processes technically necessary connection data (IP address, date and time, requested URL, amount of data transferred, browser/user agent, referrer). This is required to deliver the site and to prevent abuse (Art. 6(1)(f) GDPR). The data is kept only as long as needed for operation and security and is not combined with other data. A data processing agreement (Art. 28 GDPR) is in place with netcup.
The domain breakbar.cc is managed through Cloudflare, Inc. (101 Townsend St, San Francisco, CA 94107, USA). Requests to voidlog are routed through Cloudflare's network (reverse proxy); Cloudflare processes technically necessary connection data (in particular the IP address) and forwards the requests to my server.
4. Sign-in with Discord
Sign-in is exclusively via “Sign in with Discord” (OAuth2). You are redirected to Discord and authenticate there; I never receive your password. I request the “identify” and “email” scopes and store:
- your Discord ID, display name and profile picture (avatar URL),
- the e-mail address stored with Discord,
- the access tokens issued by Discord (technically required for sign-in),
- your registration date and your memberships and roles (admin, contributor, viewer) in projects.
5. Purpose and legal basis
Account and project data and uploaded logs are processed to provide the platform (Art. 6(1)(b) GDPR). Where logs contain data about other players who have no account themselves (see section 6), processing is based on my legitimate interest in letting player groups analyse their shared sessions (Art. 6(1)(f) GDPR). Security and abuse prevention likewise rely on Art. 6(1)(f) GDPR.
6. Uploaded combat logs
When you upload logs, the original files (.evtc/.zevtc) are stored in object storage and analysis data derived from them is stored in the database. A log contains, for every participant of the fight, among other things:
- the Guild Wars 2 account name (e.g. Name.1234) and character name,
- profession, squad group and possibly role,
- damage, downs/deaths, mechanic events and their timing.
7. Transfer to dps.report
For analysis, every uploaded log file is sent to the service dps.report (https://dps.report), which processes the log with Elite Insights and returns the result. This creates a report there with a link that is accessible to anyone who knows it. The link is stored in voidlog and can be opened by project members. I have no influence on retention or deletion at dps.report; deletion requests must be directed to them. dps.report's own privacy information applies.
8. Object storage at Cloudflare R2
The original log files are stored in object storage (Cloudflare R2) operated by Cloudflare, Inc., USA. When uploading, your browser sends the file directly there; Cloudflare receives technically necessary connection data such as the IP address. The files are not publicly accessible. For transfers to the USA, Cloudflare relies on the EU-US Data Privacy Framework and standard contractual clauses.
9. Visibility within projects
Logs and analyses are visible to all members of the respective project, not to outsiders. Project members also see your display name as the uploader and the player data contained in the logs. Access is granted through invite links created by project admins; only a hash of the invite token is stored in the database.
10. Cookies and local storage
voidlog uses no tracking or analytics cookies and embeds no advertising or analytics services. Only strictly necessary cookies are used, which require no consent (§ 25(2) no. 2 TDDDG):
- Sign-in session cookie (authjs.session-token, prefixed __Secure- in production) – keeps you signed in; the session is kept server-side in the database and expires automatically.
- Sign-in security cookies (authjs.csrf-token, authjs.callback-url, prefixed __Host- / __Secure-) – forgery protection and return to the page after signing in.
- Language setting (breakbar-language) – stores German/English, valid for one year, shared with the main site and the other breakbar.cc subdomains.
11. Fonts
The fonts used (Inter, Chakra Petch) are served from my own server. No connection to Google servers is made when you visit the site.
12. Retention and deletion
Your data remains stored as long as your account or the project exists. Under “Account” you can at any time yourself:
- delete all logs you uploaded (including the original files in object storage),
- delete your account entirely. Projects of which you are the only admin are deleted with all their data; for projects with other admins, ownership passes to one of them. Logs you uploaded to projects that continue remain there but are no longer linked to an account.
13. Your rights
You have the right of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and to object to processing based on legitimate interests (Art. 21 GDPR). Consent you have given can be withdrawn at any time. Please contact [email protected].
You also have the right to lodge a complaint with a supervisory authority, e.g. the State Commissioner for Data Protection and Freedom of Information of Baden-Württemberg, Lautenschlagerstraße 20, 70173 Stuttgart, Germany.
14. Necessity of data and automated decisions
voidlog cannot be used without the account and connection data described above. There is no automated decision-making, including profiling, within the meaning of Art. 22 GDPR.
15. Changes
I will update this policy when the platform or the legal situation changes. The version published here applies.