The main trust surfaces behind the workflow.
Access follows role and organization scope
EvalSuite uses role-based access and organization-scoped access patterns instead of treating workspace data as universally visible. Managers only see the performance and meeting context needed for their direct-report workflows. Admins manage workspace setup, billing, and operations without turning every page into a public feed. Non-public app routes are explicitly kept out of search indexing.
Meeting capture is scoped to the shipped surfaces
Transcript and recap workflows are limited to the meeting surfaces EvalSuite actually operates today. Live transcript capture is available in EvalSuite rooms and shared syncs. Transcript context can feed recap drafting and reviewable follow-up suggestions. Zoom-backed scheduling is supported, but Zoom transcript capture and an in-Zoom coach are not shipped today.
AI support is assistive, not autonomous
EvalSuite positions AI as writing and coaching support. The system does not claim to decide performance truth for your team. AI drafting uses role context, templates, and captured evidence when available. Managers still edit final reviews and confirm follow-up actions. Trust depends on showing what the AI does and where human review is still required.
Retention, billing, and support stay explicit
The trust surface links directly to the operational policies that matter when buyers evaluate a people product. Usage logs are retained for up to 12 months, and backup data may remain for up to 90 days after deletion. Paid checkout starts in Stripe, and only org admins can initiate paid billing from the app. Account access, auth troubleshooting, and Zoom setup guidance live in the public Help Center.