Authentication and access
Dashboard and mobile access use Clerk-authenticated sessions. Application data is scoped to the active organization, and sensitive setup actions are reserved for admin or owner roles where supported.
Secrets and payments
Stripe and integration credentials are stored through backend-managed configuration flows. Workspace operators should rotate credentials if they suspect exposure and should avoid sharing API keys outside the dashboard setup flow.
Operational safeguards
The product includes typed backend functions, organization guardrails, webhook event records, invoice events, cleaner assignment state, and lead lifecycle events so important workflow changes can be reviewed.
Recommended launch controls
Before broad production rollout, each customer should confirm user access, connected integrations, payment configuration, backup exports, incident contacts, and expected support response paths.
These pages describe the current pilot product posture and are not a substitute for a signed customer agreement. Production customer agreements should be reviewed by counsel before broad launch.