Plain terms for an alpha.
Written to be read, not skimmed past. Last updated 2026-07-11. These are plain-language terms for the alpha, pending formal legal review — if your procurement needs signed paper, ask us.
The service
LoopOps ("we", operated by the LoopOps team) turns telemetry you send into an approval-gated improvement loop your coding agent can drive. It is an alpha: features change, interfaces move, and availability is best-effort — there is no SLA yet. Don't make it the only copy of anything.
Your data stays yours
You own the telemetry, feedback, and configuration you send. You grant us only what operating the service requires: storing it, scrubbing it at ingest, deriving the loop's projections from it, and serving it back to keys and accounts you control. We never sell it, never train models on it, and never share it beyond the infrastructure providers that run the service (see Privacy).
Your responsibilities
Keep your keys secret (they are shown once and stored only as hashes — rotation is self-serve with your recovery code). Only send telemetry you have the right to send. Minimize personal data in what you emit — scrubbing defaults are on, but producer-side capture flags are the first line. Don't probe other tenants, evade rate limits, or use the service for anything unlawful.
The approval boundary is part of the deal
LoopOps never posts issues, opens pull requests, merges code, or changes your production. Every external write happens in your systems, by your agent, after your approval. What your coding agent does with the evidence we serve is between you and it.
Ending things
Leave anytime: archive a project to stop ingest and downgrade its keys; ask and we delete everything. We may suspend projects that abuse the service or threaten other tenants — abuse ceilings and quotas are documented in the docs.
No warranty, limited liability (plainly)
The alpha is provided as-is, without warranties. To the maximum extent the law allows, our liability for anything arising from the service is limited to what you paid us for it — which, during the free alpha, is nothing. Don't rely on an alpha for anything whose failure you can't absorb.
Changes
When these terms change, the update lands here with a new date and a changelog entry. Continuing to use the service after a change means you accept it.