Terms
Service terms
These terms describe the current OperatorLoop baseline for async fit-checks, scoped installs, recurring improvement, and approval-aware workflow execution.
What OperatorLoop sells
OperatorLoop sells a productized digital service.
The current offer is one approval-aware post-checkout workflow install plus recurring monthly improvement.
The intended buyer is a founder-led or AI-first digital service seller with a clear paid-order workflow to tighten.
How work starts
Fit-check emails do not create a contract on their own.
Work starts only after scope, delivery path, commercial terms, and approval boundaries are confirmed in writing.
Delivery model
OperatorLoop is async-first. Setup, review, and support run in writing unless a specific exception is agreed.
Week one is one narrow workflow first, not a broad transformation engagement.
Client responsibilities
The client is responsible for timely access, accurate source information, and clear approval decisions where the workflow requires them.
Missing inputs, withheld access, or delayed approvals can change delivery timing.
Approval boundary
Public, financial, refund-related, legal-sensitive, destructive, identity-shaping, or otherwise irreversible actions stay approval-gated unless written scope says otherwise.
Routine bounded actions inside the agreed workflow may run automatically.
Scope changes and refunds
Anything materially outside the agreed workflow is re-scoped before execution.
Refund handling follows the public policy on /refunds plus any narrower written terms agreed for the specific engagement.
Payment rail status
No self-serve checkout is live on this site yet.
When checkout is enabled, Polar will handle checkout, billing, and tax as Merchant of Record.
That payment rail does not change the service scope sold by OperatorLoop.