Support and security reporting
A real monitored business contact and response window must be published before any paid release. Until then, do not send private files, vulnerability details, credentials, or customer data to an unverified address or social account.
Read the project page, Getting Started guide, release manifest, archive README, prerequisites, limitations, install steps, expected result, troubleshooting, uninstall, and rollback instructions. Stop if the package requests access unrelated to its stated function.
Use synthetic data and remove names, email addresses, tokens, paths, account IDs, private URLs, session state, and client information. Never send passwords, API keys, browser profiles, database exports, payment-card details, or production backups.
Stop using the affected release, preserve minimal evidence, revoke exposed access through the owning provider, and avoid public disclosure of exploitable detail. A verified private reporting method and coordinated disclosure process must exist before a paid product is released.
The site is built with keyboard, focus, contrast, reduced-motion, and semantic checks, but that is not certification. A monitored channel for access barriers and alternate-format requests remains an owner-controlled production requirement.