JavaScript Required

BlockMedic requires JavaScript to function properly. Please enable JavaScript in your browser settings and reload the page.

Menu
HomeAPI DocumentationFAQStatus
Sign In
Legal

Privacy Policy

Last updated

AMPZ Network — BlockMedic

This Privacy Policy explains how AMPZ Network ("we", "us", or "our") collects, uses, and protects information when you use BlockMedic ("the Service"). By using the Service, you agree to the practices described here.

1. Information We Collect

1.1 Log Content

When you submit a log file or paste log content, we store the text you provide. This may include server configuration details, mod lists, error messages, and other information present in your log file. We do not require personal information to submit a log.

1.2 Technical Data

When you interact with the Service, we automatically collect:

  • IP address — used for rate limiting and abuse prevention.
  • Upload timestamp — recorded alongside the log entry.
  • Detected metadata — such as Minecraft version, mod loader, and operating system, as parsed from the log content.
  • Upload source — whether the log was submitted via the web interface, Discord bot, or the API endpoint.

1.3 Account Data

If you register for an account, we collect and store:

  • Username — your chosen display name.
  • Email address — used for authentication, account recovery, and optional two-factor authentication (2FA) codes.
  • Password — stored as a one-way bcrypt hash; we cannot recover your plaintext password.
  • Profile information — such as your avatar image, profile banner, and Minecraft username, if you choose to provide them.
  • Account creation date and the date of your last sign-in.
  • Two-factor authentication data — if you enable 2FA, we store a TOTP secret (for authenticator app method) or a time-limited OTP hash (for email method). We do not store plaintext codes.

1.4 Session Data

When you sign in, we create a session record containing:

  • A randomly generated session token (stored as a cookie in your browser).
  • Your browser's user-agent string — used to display device information in your account settings.
  • The IP address at the time of sign-in — recorded for security alerts and audit purposes.
  • Sign-in timestamp and session expiry time.

You can view and revoke your active sessions at any time from your account settings.

1.5 Third-Party Connections

If you link a third-party account (Discord or GitHub) to your BlockMedic account, we store the account ID returned by that provider. We do not store your OAuth access tokens beyond what is required to complete the linking process.

1.6 Discord Data

If you use the Service through our Discord bot without a registered account, we collect your Discord server (guild) ID to enforce per-server rate limits and settings. We do not collect your Discord user ID in this context.

2. How We Use Your Information

We use the information we collect solely to:

  • Analyse your log file and return diagnostic results.
  • Create and manage your account and authenticate you when you sign in.
  • Send account-related emails such as password reset links, security alerts for new sign-ins, and 2FA codes.
  • Display session and device information within your account settings.
  • Enforce rate limits and prevent abuse.
  • Maintain the security and integrity of the Service.
  • Delete stale data in accordance with our retention policy.

We do not use your data for advertising, profiling, or any purpose unrelated to providing the Service.

3. Data Retention

Log entries are stored for a limited retention period (typically 30 days) and then automatically deleted. Logs may be deleted earlier at our discretion, for example following an abuse report. You may also request early deletion of a specific log by contacting us with the log URL.

Account data is retained for as long as your account is active. If you delete your account, all associated personal data (email address, password hash, profile information, session records, and linked third-party connections) is permanently deleted. Anonymised or aggregated log records that cannot be traced back to you individually may be retained for statistical purposes.

Session records expire automatically and are purged once expired. You can revoke any active session early from your account settings.

4. Log Visibility

Log URLs are randomly generated and not listed publicly. However, they are not password-protected — anyone in possession of the URL can view the log. Do not submit logs containing passwords, authentication tokens, or personal information you do not wish to be accessible to others.

5. Data Sharing

We do not sell, trade, or rent your data to third parties. We may share data only:

  • With service providers necessary to operate the Service (e.g., database hosting), under strict confidentiality obligations.
  • As required by law, such as in response to a valid legal request from a competent authority.

6. Cookies & Local Storage

The Service uses:

  • A session cookie (bm_session) to keep you signed in. This cookie is HTTP-only and expires when your session ends or you sign out.
  • A locale cookie (bm_locale) to remember your language preference.
  • Browser localStorage to remember your theme preference. No tracking cookies or third-party analytics are set.

7. Security

We take reasonable technical and organisational measures to protect data held by the Service, including:

  • Passwords are hashed using bcrypt and are never stored in plaintext.
  • Session tokens are cryptographically random and stored server-side.
  • Security alert emails are sent when a sign-in is detected from a new device or IP.
  • Two-factor authentication is available for all accounts.

However, no system is completely secure. Log URLs are unguessable but not encrypted at rest in a manner that prevents access by authorised administrators.

8. Children's Privacy

The Service is not directed at children under the age of 13. We do not knowingly collect personal information from children. If you believe a child has submitted personal information to the Service, please contact us so we can remove it.

9. Your Rights

Depending on your jurisdiction, you may have rights regarding your personal data, including:

  • Access — you may request a copy of the personal data we hold about you.
  • Correction — you may update your email address, username, and profile information directly in your account settings.
  • Deletion — you may delete your account at any time from your account settings. This will permanently erase your personal data. You may also contact us to request deletion of a specific log entry.
  • Portability — you may request an export of your personal data by contacting us.

To exercise any of these rights, please contact us at the address below. We will respond within a reasonable timeframe.

10. Changes to This Policy

We may update this Privacy Policy from time to time. The "Last updated" date at the top of this page will reflect the most recent revision. Continued use of the Service after changes are posted constitutes your acceptance of the updated Policy.

11. Contact

If you have any questions or requests regarding this Privacy Policy, please contact us at:

Email: support@ampznetwork.com
Discord: discord.ampznetwork.com

Questions? support@ampznetwork.com

Terms of Service