Trust
Audit log and data trail
Which audit events the source records, and how backups differ from a customer data export.
The public release record lists v0.2.0 as available by request. These notes are not a guarantee that every workflow or provider integration is enabled in your build. Check the release record and ask support to confirm version-specific setup.
What gets recorded
The application source writes structured audit events for covered customer, order, product, broadcast, ticket, and permission operations. Confirm which events are available in the release and configuration you plan to use.
Audit records are append-only through the application API. This is an application control, not a claim that a server owner cannot alter the underlying database or backups.
Tenant isolation
The API scopes workspace records to the authenticated organization and permissions. Tenant-isolation checks are part of source and integration validation; verify the exact release and configuration during your evaluation.
Backups are not self-service exports
The deployment kit includes backup and restore procedures, but a server backup is not a portable customer data export. The current desktop client does not provide self-service workspace export. Agree the retention and data-exit process before onboarding.
Next: request access to the desktop app or read the public changelog.