Privacy Policy
The short version
MCPing has no account, no analytics, no telemetry and no advertising. It collects nothing about you. Everything it stores stays in your browser.
What MCPing stores
All of it lives in your browser's local extension storage (storage.local) and never leaves your device:
- The servers you added — display name, hostname, port, edition.
- The most recent reading for each server — online/offline, player count, version, MOTD, server icon, ping.
- A history of player counts, kept for as long as your retention setting says (7 days by default, 1–30 configurable).
- The usernames you chose to watch, if any.
- Your settings — theme, language, check interval, notification preferences.
You can erase all of it at any time: Settings → Data → Reset everything. Uninstalling the extension also removes it.
What MCPing sends, and to whom
To find out whether a server is online, MCPing asks a public status API about it. Exactly two endpoints are contacted, and only ever with the server address you entered:
| Service | Used for | Privacy policy |
|---|---|---|
api.minetools.eu | Java server status and ping latency | minetools.eu |
api.mcsrvstat.us | Bedrock status, and a second opinion for Java | mcsrvstat.us |
These requests contain the server hostname and port you asked about — nothing else. No identifier, no account, no browsing data. Like any HTTP request, your IP address is visible to those services; that is inherent to making a network request and is not something MCPing adds.
A third API, mc-heads.net, is only contacted if you use watched-player alerts: it draws a player's skin head from their username, and it is only ever called for a player you explicitly asked to be told about.
Requests are made on a repeating background schedule (every 3 minutes by default) and when you refresh manually. If you remove all servers, no requests are made at all.
What MCPing never does
- No tracking, fingerprinting, analytics or crash reporting.
- No reading of the pages you visit. The extension requests no host permissions and runs no content scripts, so it has no access to your browsing whatsoever.
- No access to your history, bookmarks, cookies, downloads or passwords.
- No remotely-hosted code. Everything that runs was reviewed as part of the package.
- No selling, sharing or transferring of data, because there is no data to sell.
Permissions, and why each one exists
| Permission | Why |
|---|---|
storage | To save your servers, settings and history on your device. |
alarms | To wake the extension on a schedule so it can check your servers in the background. |
notifications | To tell you when a server goes down, comes back, or fills up. Alerts are entirely optional and can be switched off. |
offscreen | Chromium only. To play the optional notification sound; a service worker cannot produce audio on its own. |
MCPing deliberately requests no host permissions. Both status APIs allow cross-origin requests, so the extension does not need — and cannot obtain — access to any website.
Children
MCPing is a server-monitoring utility. It collects no personal information from anyone, including children.
Changes
Any change to this policy ships with a new version of the extension and updates the date above.
Contact
Questions or concerns: alexbur.msgabo@gmail.com