Terms and conditions
The practical rules for using the plugin and the public services that support it.
Effective 15 July 2026. Applies to GeoRestrict v2.0.0.
1. Using GeoRestrict responsibly
You may install, inspect, modify and redistribute GeoRestrict under its GPL-3.0 license. You are responsible for your server configuration, the rules shown to players, and compliance with laws and platform policies that apply to your community. Test changes before relying on them in production.
2. What GeoRestrict is and is not
GeoRestrict is a connection-policy tool based on approximate IP geolocation and network data. It is not identity verification, an exact-location service, a complete VPN detector, a DDoS shield, legal advice, or a guarantee that an unwanted person cannot connect. Mobile networks, carrier gateways, corporate networks and VPNs can produce incomplete or unexpected results. Operators should provide a reasonable appeal or support route for players affected by a false result.
3. Public hosted services
Demonz Development currently provides a public Worker, documentation site, and protected fallback server for convenience. They are provided without a paid service-level agreement. We may rate-limit, update, move, suspend or discontinue a hosted endpoint to protect it, comply with provider requirements, or keep the project maintainable. Keep a tested failure policy in config.yml rather than assuming the public path will always be available.
4. Acceptable use
Do not use the hosted services to attack, scan, scrape, overload or bypass protections; test stolen or unauthorized credentials; conceal abusive automation; resell raw lookup access; or interfere with other users. Normal player admission checks, admin lookup commands, health checks, and reasonable development testing are allowed. We may block abusive traffic or compromised credentials.
5. Configuration and security
Most operators should leave the generated Worker settings unchanged. You are responsible for credentials and endpoints under your control. Never post gateway tokens, Discord webhook URLs, or player IPs in a public support message. Operators running their own infrastructure should follow the security notes in the GitHub README.
6. Privacy and third-party data
Our Privacy Policy explains the lookup path, caching and optional Discord notifications. IPinfo, DB-IP, Cloudflare, Discord, bStats, Modrinth and infrastructure providers have their own terms and policies. Their availability, data and decisions are outside our control. Attribution requirements for bundled or downloaded data must be kept when the relevant license requires it.
7. Support and community conduct
Demonz Development tries to listen to users before anything else, and reports are genuinely welcome. Community support is offered on a best-effort basis with no guaranteed response time. Be respectful, remove sensitive information, explain what you expected, and include useful logs or configuration excerpts with secrets redacted. Harassment, hate speech, threats and targeted disclosure of personal information are not accepted in project spaces.
8. Warranty and liability
The software and hosted services are provided “as is” and “as available,” without promises that every lookup will be correct or every service uninterrupted. To the extent permitted by applicable law, Demonz Development and project contributors are not liable for indirect, incidental, special or consequential loss arising from configuration choices, unavailable providers, false geolocation results, blocked players, lost revenue or misuse of the project. Rights that cannot lawfully be excluded remain unaffected.
9. Changes and contact
We may revise these terms when the service, providers or legal obligations change. Material updates will receive a new effective date and a changelog entry. Continuing to use a hosted service after a published change means you accept the updated hosted-service terms; if you do not, stop using that hosted endpoint. Your GPL rights in a copy of the software remain governed by the license.
Questions, bugs and respectful criticism are welcome through the GitHub issue tracker or the Demonz Development Discord.