Summary
- This website sets no cookies. Visits are counted with PostHog (EU) in cookieless mode: no profile is created, and you cannot be recognized on another day.
- The plugin sends player IP addresses to the detection services the server operator enables. Since version 0.5 its cloud link to connectionguard.net is on by default: until a server is linked it sends only anonymous install, health and total figures and, from version 0.6, anonymous error reports, no player IPs, UUIDs or names. From version 0.6 the server also downloads detection lists from us once a day; that download contains no player data either. Server operators can turn it off completely (section 4).
- The dashboard uses Discord sign-in, one necessary session cookie and usage analytics you can switch off. Once an operator links a server, it also receives each login check with the player's IP address and verified UUID; we process that only on behalf of the server operator.
- Data is stored in the EU. We do not sell data, and we do not use it for advertising.
1. Controller
The controller under the General Data Protection Regulation (GDPR) is:
Gero Lindner
c/o SourceArt · VM-00003645
Fritz-Thiele-Straße 3
28279 Bremen-Obervieland
Germany
Email: privacy@connectionguard.net
We are not required to appoint a data protection officer. For any privacy question, write to the address above.
2. This website (connectionguard.net)
2.1 Hosting and delivery
The website is delivered by Cloudflare, Inc. (101 Townsend Street, San Francisco, CA 94107, USA) as our processor. To deliver pages and protect them against attacks, Cloudflare processes connection data: IP address, date and time, the requested address, the referring page and browser information (user agent). We do not store these logs ourselves.
Legal basis: Art. 6(1)(f) GDPR. Our legitimate interest is a fast, secure and reliably available website.
2.2 Cookies and browser storage
This website sets no cookies. If you choose a light or dark theme, that choice is saved in your browser's local storage (cg-theme) and never leaves your device. This storage is strictly necessary for a function you request (§ 25(2) no. 2 TDDDG).
2.3 Visit statistics (PostHog, cookieless)
To learn which pages help server owners and where people download the plugin, we use PostHog. The provider is PostHog Inc. (USA), acting as our processor. The data is hosted in the EU (Frankfurt), and requests go through our address t.connectionguard.net.
- What is recorded: pages viewed and how far they were scrolled, the previous page, clicks (for example which download site or question you choose), page speed (web vitals), script errors, and browser, device type and operating system.
- How visits are counted without cookies: PostHog combines your IP address and browser identifier with a random value that changes every day into a one-way hash. The daily value is deleted afterwards. No profile is created, you cannot be recognized across days, and nothing is stored on your device. IP addresses are not stored (IP anonymization is on).
- Opting out: if your browser sends Global Privacy Control or Do Not Track, nothing is recorded.
- Retention: events are deleted after one year.
Legal basis: Art. 6(1)(f) GDPR. Our legitimate interest is understanding and improving the website with as little data as possible. Because nothing is stored on or read from your device, no consent under § 25 TDDDG is required. You can object at any time (see section 9).
2.4 No other third-party content
Fonts, images and scripts are served from our own domain. Download counts shown on the website are read from Modrinth, SpigotMC, Hangar and GitHub when we build the website, not from your browser. Links to those sites and to Discord only transfer data once you follow them; the respective provider's privacy policy then applies.
3. The dashboard (app.connectionguard.net)
3.1 Sign-in with Discord
You sign in with your Discord account. Discord Inc. (444 De Haro Street, Suite 200, San Francisco, CA 94107, USA) runs the sign-in as a separate controller. We request only the identify permission and keep your Discord user ID, display name and the address of your avatar image. We do not receive your email address, servers or messages. Your avatar is loaded from Discord's servers when the dashboard shows it, which transmits your IP address to Discord.
Legal basis: Art. 6(1)(b) GDPR, to provide the dashboard you sign up for.
3.2 Cookies and browser storage
cg_session: keeps you signed in, valid for 30 days or until you sign out.cg_oauth_state: protects the Discord sign-in against forgery, valid for 10 minutes.- Local storage for your choices: theme (
cg-theme), notes you dismissed (cg-dismissed:…,cg-checklist-dismissed:…) and, if you switch off usage analytics, that choice (cg-analytics-optout, plus PostHog's own__ph_opt_in_out_…).
All of these are strictly necessary for functions you request (§ 25(2) no. 2 TDDDG; Art. 6(1)(b) GDPR). The dashboard sets no tracking cookies.
3.3 Account, networks and servers
We store what you enter or what results from using the dashboard: network and server names, your role in each network, when you accepted the data processing agreement, the settings you send to your servers, and an audit log of who changed what and when. API keys and webhook addresses you enter are stored encrypted only until your server confirms receipt, then deleted from our systems. The dashboard also processes data that linked servers send (section 4.2).
Team: members of a network see each other's Discord display name, avatar and role. Invitation links work once for 7 days; we store only a hash of them. Discord alerts: if you connect a Discord webhook, we store its address encrypted and post alerts to it. Alerts contain server names and counts, never player data.
Legal basis: Art. 6(1)(b) GDPR. The audit log also serves our legitimate interest in security and traceability (Art. 6(1)(f) GDPR).
Retention: sign-in sessions end after 30 days. Account, network data and audit log are kept while you use the dashboard. You can download your data and delete a network or your whole account yourself under "Account and data" and on the network's page; deletion takes effect immediately. You can also write to privacy@connectionguard.net; we then delete within one month.
3.4 Usage analytics (PostHog)
To improve the dashboard, we record how it is used with PostHog (EU), as in section 2.3, but linked to your account. That way we can see where setting up a server fails.
- What is recorded: pages viewed, clicks, progress through the setup assistant, errors and page speed. Session recordings show the page layout and where you clicked, with all text and everything you type hidden. Areas showing player data are excluded from click tracking.
- Identification: by your random dashboard account ID and the ID of the network you are viewing. Your Discord name and ID are never sent. Nothing is stored on your device for this, and IP addresses are not stored.
- Retention: session recordings are deleted after 30 days, other events after one year.
- Switching it off: under your avatar, "Share usage data". Global Privacy Control or Do Not Track switches it off automatically.
Legal basis: Art. 6(1)(f) GDPR. Our legitimate interest is a dashboard that works for its users. You can object at any time with the switch described above.
3.5 Server logs
The dashboard and its interface run on Cloudflare Workers. For error analysis, Cloudflare keeps request logs, which can include your IP address, for up to three days. Legal basis: Art. 6(1)(f) GDPR (secure and reliable operation).
4. The plugin's cloud link (api.connectionguard.net)
Since version 0.5 the plugin connects to the dashboard by default. Players' logins never wait on this connection. Server operators turn it off completely with cloud.enabled: false, /cg cloud disable or the environment variable CONNECTIONGUARD_CLOUD=false; then no request reaches us.
4.1 Servers not linked to an account (default)
The plugin sends an anonymous install ID, the platform and versions, the protection mode, totals per interval (checks, refusals, cache hits, response times, counts per country and reason) and the health of the detection services. It sends no player IP addresses, UUIDs or names, and no API keys or webhook addresses. We use this to run the service, plan capacity and count active servers.
Legal basis: Art. 6(1)(f) GDPR. Our legitimate interest is operating and improving the plugin; server operators can object by turning the link off. Retention: installs that stop reporting are deleted after 30 days; hourly totals are kept for 13 months.
4.2 Linked servers: processing on behalf of the server operator
After a server operator links a server and accepts the data processing agreement, the plugin also sends one entry per login check. Each entry contains the time, the player's IP address and verified UUID, the verdict and reason, and what each detection service answered (country, network, provider, risk). We process this data only on behalf of and as instructed by the server operator (Art. 28 GDPR), who is the controller, under our data processing agreement. Players should address questions about this data to the operator of the server they joined; we support operators in answering them.
To show player names instead of UUIDs, the dashboard looks up the public Minecraft profile name for a UUID at Mojang AB (Sweden), and searching decisions by name looks up the matching UUID. Names are cached for up to 24 hours in Cloudflare's cache and are not stored in our database. Access rules that the operator adds can contain a player's UUID or IP address; they are processed under the same agreement.
Retention: entries are deleted after 30 days, hourly totals after 13 months. Unlinking a server deletes its entries immediately.
4.3 Product statistics about servers
From the cloud link we also derive statistics such as "a server was installed, linked, applied settings or sent its first checks", plus a daily count of active servers. We send these to PostHog (section 2.3), keyed by the install ID or your account ID. They contain platform and version details, never player data, setting values or keys. Legal basis and retention as in section 3.4.
4.4 Plugin error reports (from version 0.6)
When a programming error occurs in Connection Guard itself, the plugin sends a summarized error report with its next sync: the names of the error class and its cause, the places in Connection Guard's own code (class, method, line), the area (start, reload, check, cache, cloud link or command), how often the error occurred and when first and last, and the plugin, platform and Java versions. Error messages and code locations of other plugins or the server are not sent. Reports therefore contain no player IP addresses, UUIDs or names, no file paths and no keys.
We send the reports to PostHog's error tracking (section 2.3), keyed by the install ID, to find and fix errors in new versions and on untested platforms. For linked servers the dashboard also shows them to the server operator and stores them for that purpose until 30 days after the last occurrence. Legal basis: Art. 6(1)(f) GDPR; our legitimate interest is a working plugin. Retention at PostHog as in section 3.4. Server operators turn the reports off on their own with cloud.error-reports: false, or together with the whole cloud link.
4.5 Connection Guard Intel: downloading the detection lists (from version 0.6)
When Connection Guard Intel is on (the default for new installs), the server downloads lists of known VPN servers, Tor exits, privacy relays and data centres from intel.connectionguard.net once a day. Players are then checked on the server only; no player data is sent. A download technically gives us and our host Cloudflare the Minecraft server's IP address and the plugin's user agent. We do not analyse it and keep no download logs; Cloudflare processes it to deliver the files and to fend off attacks. Legal basis: Art. 6(1)(f) GDPR, our legitimate interest in providing the lists. Server operators turn the download off with provider.local.connectionguard-intel.enabled: false. The lists and their sources are public at github.com/gerolndnr/connection-guard-intel.
5. Contacting us
If you email us, we process your address and message to answer you. Messages to @connectionguard.net addresses are forwarded to our mailbox by Cloudflare Email Routing. Legal basis: Art. 6(1)(b) or (f) GDPR. We delete the messages when the matter is closed, unless statutory retention obligations apply.
6. Processors and recipients
- Cloudflare, Inc.: hosting, delivery, security, databases (dashboard data is stored in the EU), email forwarding. Processor.
- PostHog Inc.: product analytics, hosted in the EU. Processor.
- Discord Inc.: sign-in, and alerts to webhooks you connect. Separate controller.
- Mojang AB (Sweden): looking up public Minecraft player names for UUIDs. Separate controller.
We have concluded data processing agreements with our processors. We do not pass on data otherwise, unless we are legally required to.
7. Transfers outside the EU
Cloudflare, PostHog and Discord are companies based in the USA. Although our data is stored in the EU wherever the service allows it, access from the USA cannot be ruled out. Such transfers rest on the European Commission's adequacy decision for the EU-U.S. Data Privacy Framework (Art. 45 GDPR) where the company is certified under it, and otherwise on the EU standard contractual clauses (Art. 46(2)(c) GDPR).
8. Automated decisions
We make no automated decisions about you within the meaning of Art. 22 GDPR. Whether a player may join a Minecraft server is decided by the plugin on that server, according to the rules its operator chose.
9. Your rights
You have the right to access your data (Art. 15 GDPR), to rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18) and data portability (Art. 20). To use them, write to privacy@connectionguard.net.
Right to object (Art. 21 GDPR): where we process data based on legitimate interests (Art. 6(1)(f) GDPR), you can object at any time on grounds relating to your particular situation. For the dashboard's usage analytics, the "Share usage data" switch is enough.
You also have the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR), in particular in the EU member state where you live, work or where the alleged infringement took place. The German authorities are listed by the Federal Commissioner for Data Protection.
10. Changes
We update this policy when our services or the law change. The date at the top shows the current version. The German version of this policy is legally binding: Datenschutzerklärung.