BlitzForge security information: HTTPS, authentication, payments through providers, vulnerability reporting and careful limitations.
Product and technical baseline to be legally reviewed. Explicit placeholders must be replaced before official App Store, Google Play or legal publication.
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 authentication mechanisms such as JWT/auth and may rely on Clerk identifiers. Secrets, tokens 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.
