Choose the right channel
Use support@neuraldefend.com for API access, staging credentials, endpoint scope, technical support, and suspected vulnerabilities. The repository also links GitHub Issues for public, reproducible SDK or documentation defects.
Do not turn a security report into a public issue. The security policy asks for the affected package and version, reproduction steps or a proof of concept, observed impact, and a safe way to contact the reporter.
Prepare a useful technical request
State the client package and exact version, language runtime, selected environment, operation, and whether the failure is local validation, HTTP, service status, timeout, network, protocol, or an unexpected result. Include a sanitized request_id or unique_trx_id if the client made one available.
Describe the expected and observed outcome without attaching real customer media. Use a synthetic fixture or a minimal reproduction when possible. Remove keys, headers, local paths, filenames, raw media, and unnecessary personal data.
Check the public contract first
Confirm the current package guide, changelog, registry release, OpenAPI contract, media requirements, and error policy. Many 400, 401, 403, no-face, missing-audio, and Retry-After outcomes have documented recovery paths.
If the public sources do not answer an account-specific question about limits, access, security terms, data handling, or commercial service levels, ask through the account support channel rather than inferring an answer.
Evidence boundary
Limitations
- No reviewed public source specifies support hours, response targets, resolution targets, escalation tiers, or contractual service levels.
Source record
