Security

Protect sensitive details while Chronal is coming soon.

A dedicated private reporting route will be published here before the first public build is available.

Do not send sensitive details through public channels.

The private reporting address and encryption guidance will appear here before release.

What a future report should include

A clear description of the issue and its impact.
The relevant Chronal Studio build and operating system, if applicable.
Steps to reproduce or a minimal proof of concept.
Whether project content, local files, connected outside agents, or local model files are involved.

What not to include publicly

Do not post exploit details, private project data, access tokens, license material, or unredacted logs to a public forum.

Response expectations

Chronal does not currently publish a response-time guarantee. The release-specific reporting route will state how to coordinate disclosure safely.