Trust, data, and support
What the console can safely show, what an export contains, and how to get help without widening the trust boundary.
Safe diagnostics
The Activity page combines a workspace lifecycle timeline with current connection health, OAuth readiness, and recent request summaries. A workspace owner, admin, or operator can download a safe support bundle generated locally in the browser.
The bundle includes workspace lifecycle state, connection health, scoped-client count, and the last 20 request summaries. It deliberately excludes OAuth tokens, client secrets, request arguments, response payloads, payment details, raw provider errors, and webhook bodies.
Retention and export
With PostgreSQL, Engine audit summaries default to AUDIT_RETENTION_DAYS=30; set 0 only when an operator deliberately wants indefinite retention. The local file store instead keeps its newest 500 audit rows. Payload recording is optional and should be enabled only when its privacy and encryption requirements are understood.
Portable configuration export contains the connection, endpoint, and policy shape, never credentials or recorded payloads. It is not a database backup or a way to restore OAuth grants, ownership ACLs, connection scopes, or MCP-client registrations.
Deletion, recovery, and incidents
Deleting a connection removes that Engine credential and its tools. Hosted workspace deletion is not self-service today: support verifies the request scope and recovery implications before a permanent operation. The console does not represent a configuration export as a backup or promise a restore point it cannot show.
Paystack webhook bodies and cloud-provider diagnostics stay server-side. When provisioning has a safe remediation path, the console exposes a short support reference rather than raw provider output. Include that reference and the safe support bundle when writing support@synaxis.tools.