Account / Security
Keep credentials and side effects controlled
Use scoped workspace keys from trusted server code, isolate projects, and keep application actions behind explicit validation.Credentials
- Store NeoSyntropy and provider keys in a secrets manager or server environment.
- Never place keys in URLs, browser bundles, graph state, examples, or logs.
- Issue the narrowest scopes required and rotate credentials after suspected exposure.
- Use a separate project identifier to isolate Framework data and run history.
Application safety
- Treat model output as untrusted data until it passes schema and business-rule validation.
- Declare allowed actions rather than executing model-generated names.
- Require application approval for financial, destructive, or externally visible side effects.
- Preserve request and run identifiers so incidents can be traced without logging secrets.
Report a security issue
Use the Contact Sales channel for private security coordination. Do not include live credentials or customer data in the first message.