Terms, as plain questions.

“Groundrule” means the hosted service at app.groundrule.dev, its API, and the command-line tool and MCP server when they are connected to it. If you use Groundrule for an organization, you confirm you're allowed to accept these terms for it. The privacy policy is part of these terms.

The early access page lists what works, what is in progress and what isn't built, with the date it was last reviewed. If it and the product disagree, tell us and we'll fix one of them.

Checks find patterns your standards describe; they can miss problems and can flag code that is fine. Compliance mappings say which controls a standard relates to, not that you meet them. Whether your software is secure and whether you meet a legal or contractual obligation stay your judgment, and your auditors'.

“Your content” is everything your workspace puts into Groundrule: standards you write, settings, scan results, imported documents, proposals and decisions. You confirm you have the right to give it to us. We use it only to run, secure and support the service for you, and we don't use it to train any model. Standards from Groundrule's packs are open source, so you may use them under their license whether or not you use the service.

AI features only run in workspaces that turn AI on, within the budget an admin sets. AI can be wrong: a drafted check may miss cases or flag good code, and a rule found in a document may misread it. Groundrule shows the source and a confidence for each result, and tests drafted checks against their examples, but reviewing a suggestion before accepting it is your team's job. AI requests are sent to Anthropic, as the privacy policy explains, with secrets removed first.

Workspace admins decide who joins and with which role, and are responsible for keeping that list current. If a token leaks, revoke it in Settings → API tokens; if your password does, change it, which also signs out your other sessions. Write to support@groundrule.dev if you think someone else used your account.

• Don't try to reach another workspace's data, probe for vulnerabilities outside a responsible report to us, or get around rate limits and budgets.
• Don't upload documents or code you aren't allowed to share, or personal data you have no lawful basis to process.
• Don't use the service to build a competing service by copying it, or resell access without our written agreement.
• Don't put secrets where they don't belong. Groundrule redacts what it can recognize, but no redaction is perfect.

These terms don't take away any right the open-source license gives you. If you send us feedback or a suggestion, we may use it without owing you anything, and you keep any rights you had in it.

Connecting an app is your organization's decision, and you're responsible for having permission to connect it. We aren't responsible for those services being available or for changes they make. Disconnecting an app deletes the tokens we hold for it.

1. Keep. Your standards are YAML in the open rule format, and the agent files in your repositories are plain text. The open-source CLI keeps working without us.
2. Disconnect. Remove the platform line from each repository's .groundrule/config.yaml, revoke your API tokens and disconnect your apps.
3. Delete. Email us and we delete the workspace as the privacy policy describes.

We may suspend or close a workspace that breaks these terms or puts the service or other users at risk. If we close one for any other reason, including ending early access altogether, we give at least 30 days' notice.

In plain terms: Groundrule is free right now, so that limit is currently zero. We say that openly so you can weigh it. It's one reason a rule only fails a build once someone moves it to Enforce, and one reason your standards stay in an open format you can keep.

• To the extent the law allows, we give no warranty that the service will be uninterrupted or free of errors, that checks will find every problem, or that it fits a particular purpose.
• Neither of us is liable to the other for indirect losses such as lost profit or lost business.
• Our total liability under these terms is limited to the amount you paid us in the twelve months before the claim.
• Nothing here limits liability that the law doesn't allow to be limited, such as liability for fraud.

You're responsible for claims that arise from content you had no right to give us, or from your breach of these terms.

Write to legal@groundrule.dev and give us 30 days to put things right before starting formal proceedings. If you're a consumer with rights under the law where you live that can't be signed away, those rights stay.

If one part of these terms turns out to be unenforceable, the rest still stands. If we don't enforce something once, we can still enforce it later. You may not transfer these terms to someone else without our agreement. We may transfer them as part of a sale or reorganisation of Groundrule, and we'll tell you if we do.

Fixing a typo or making a sentence clearer doesn't count as a change that matters. Collecting something new, sharing data with someone new, or changing what you or we are committed to does. If you don't agree with a change, you can keep your standards (they are YAML in an open format) and close your workspace before it takes effect.

1. v1.010 October 2026

   First version, published with private early access.