Trust center

Safety data is operational evidence. Review the controls before sharing it.

Use this checklist to review access, AI handling, exports, and your organization’s requirements before sharing worksite records.

Tenant isolation

Confirm how company scope, user roles, and cross-client access boundaries are enforced in the product app.

Evidence trails

Confirm which reports, investigations, signatures, document versions, and AI-assisted actions are logged.

Controlled AI use

Confirm which records are used as AI context and where human review is required before publication.

Exportable records

Confirm what documents, source records, and evidence packages can be exported during and after a guided rollout.

App separation

Your team uses the product at app.strawboss.ai. Review product access controls separately from this public website.

What buyers should review before sending safety data

Safety records can include worker names, incident facts, photos, training status, medical-adjacent details, client information, and operational evidence. Buyers should treat those records as business-critical data during security review.

During a security walkthrough, buyers can review what data enters the platform, which teams can access it, how AI features use source records, what gets exported, and what changes for a broader production rollout.

AI handling

Review which workflows use AI, which records are used as context, and where human approval is required before publication.

Data boundaries

Confirm company scope, user access, app separation, and how customer data would be segmented from other customer workspaces.

Exit path

Discuss exports for documents, source records, audit evidence, and operational handoff before production use.

Next step

Bring your security checklist to the walkthrough.

We will walk through data boundaries, exports, AI handling, and what changes before production rollout.

Book security walkthrough