Security
Report sensitive issues without making them public.
Check the Chronal repository's Security page for the current reporting route before sharing details about Chronal Studio or Chronal Engine.
Open the repository Security page
What to include
- A clear description of the issue and its impact.
- The relevant Chronal Studio build or source revision and operating system, if applicable.
- Steps to reproduce or a minimal proof of concept.
- Whether Chronal Engine, 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 issue.
Response expectations
Chronal does not currently publish a response-time guarantee. Include a safe way to contact you and coordinate disclosure through the private reporting route.