BlitzForge security information: HTTPS, authentication, payments through providers, vulnerability reporting and careful limitations.
This information describes the paths and rules currently applicable to BlitzForge. Contact support with any questions.
Last updated: 2026-07-09
Public environments should use HTTPS to protect network exchanges. Final configuration must be validated at deployment time.
The product uses secure sign-in and session mechanisms. Secrets, sign-in codes and passwords must never be shared by email.
Premium flows may rely on payment or store providers. Do not send card data to support.
To report a vulnerability, contact support with a clear description, reproduction steps and estimated impact, without further exploiting the issue.
BlitzForge does not promise zero vulnerabilities. Security measures must be maintained, tested and reviewed regularly.
