Terms of use
Terms of Use
The agreement between you and us for using the Milestone Ledger hosted service. Plain language where the law allows it.
Sandbox stage
The hosted service currently runs in PayPal's sandbox. No real money moves, only PayPal sandbox accounts can be connected, and agreements made on it are for evaluation. These terms govern that use now. They will be reviewed by counsel, and the fee schedule and governing law stated, before any live deployment accepts real payments.
1. The agreement
These terms are between you and Milestone Ledger ("we", "us"), the hosted service at app.milestone-ledger.com run by the maintainers of the open-source Milestone Disbursement Engine. By creating an account, joining an organization, connecting an agent or otherwise using the service, you agree to them. If you act for an organization, you confirm that you may bind it, and "you" includes that organization.
The Privacy Policy is part of these terms. If you run your own copy of the open-source engine, these terms do not apply; the AGPL-3.0 licence does.
2. What the service does
Milestone Ledger turns a grant or statement of work into tranches with acceptance criteria, lets each party confirm those criteria, holds the payer's funds at PayPal, takes in evidence, checks it against the criteria with deterministic checks and an AI verifier, routes close calls to people, and settles each tranche through PayPal. It keeps an audit log and produces compliance packets.
The service has two modes. Sandbox is connected to PayPal's sandbox: no real money moves. Live is connected to PayPal's production API, pays connected payees directly, and requires PayPal partner approval. The hosted service tells you on every page which mode it is in.
3. Accounts, organizations and roles
- You must be at least 18 and able to enter contracts. You sign in with an email address you control, or through your organization's identity provider.
- Everything is done as a person acting for an organization, with a role (owner, admin, member or viewer). The organization is responsible for who it adds, what roles it gives them, and what they do.
- API keys and connected agents act with the organization's authority. Keep keys secret, revoke them when they are no longer needed, and tell us at once if one is exposed.
- You are responsible for the accuracy of what you enter, including the PayPal account an organization connects.
4. Agreements between parties
- An agreement on the service is between its parties: the payer, the payee and any reviewers. We are not a party to it. We provide the tooling that records it, verifies evidence against it and settles it; we do not guarantee that either party will perform.
- Each party signs the exact criteria it reviewed. You are responsible for reading them before you confirm. The criteria lint and the extraction are aids; they do not replace your judgement.
- You are responsible for your agreements complying with the law that applies to you, including grant terms, tax and employment rules.
5. Payments and PayPal
- All payments are made through PayPal under PayPal's user agreement and its fees. You need a PayPal account to pay or be paid, and PayPal may decline, hold or reverse a payment under its own rules.
- Funds held for a tranche are held by PayPal under an authorization the payer approved, not by us. In live mode payment goes from the payer to the payee directly; we never hold funds.
- PayPal authorizations expire. If a hold expires before a tranche verifies, the payer may need to fund it again.
- After a capture there is a contest window during which the payer may contest the tranche. Contests and PayPal disputes pause payment to the payee until a reviewer resolves them or, failing that, until PayPal's own timelines apply. The ledger shows the window for each tranche.
- We are not responsible for PayPal's acts or omissions, for exchange rates, or for a payee's failure to connect or maintain a PayPal account that can receive payment.
6. Verification and automatic release
- Verdicts combine deterministic checks with an AI verifier that returns a confidence and citations. A verdict is an assessment, not a guarantee that the work meets the criteria. The verifier can be wrong, and evidence can be misleading.
- Each organization chooses whether tranches can release automatically and the confidence it requires. If you turn on automatic release, you accept that a tranche meeting your threshold will be captured and released without a person looking at it first, subject to the contest window.
- Below the threshold, or with automatic release off, a person with the right role decides. The record of who decided, and on what, is in the audit log.
- You must not try to influence a verdict other than by submitting genuine evidence. Instructions hidden in evidence, fabricated artefacts and tampered check results are a breach of these terms and may be an offence.
7. Deliverables we hold
- When an agreement withholds work until payment, we hold the payee's deliverables, encrypted, and release them to the payer when the tranche is captured. Until then the payer sees only what the agreement allows, such as a commit's tree and its check results.
- The payee keeps all rights in the work until the agreement between the parties says otherwise. We take no rights in it beyond what we need to hold, verify and hand it over.
- Retention of originals after a tranche closes follows the deployment's retention setting, as described in the Privacy Policy. Hashes are kept so the record stays verifiable.
- If a handover fails its integrity check, it fails closed and both sides are told. We are not responsible for the content of deliverables.
8. Fees
- The sandbox service is free. No fees are charged while the hosted service is in sandbox mode.
- When the service goes live, we intend to charge the payer a platform fee on each captured tranche, collected through PayPal at capture, and to offer paid plans for funders running grant programs. Payees never pay to get paid; pre-check and the criteria lint stay free. The fee schedule will be published and shown before you fund a tranche, and these terms will be updated first.
- PayPal's own fees are separate and are set by PayPal.
9. Acceptable use
You agree not to:
- use the service for anything unlawful, or for agreements that are themselves unlawful;
- use the sandbox service to document real obligations as if money had moved, or represent a sandbox transaction as a real payment;
- connect a PayPal account you do not control, or impersonate a person or organization;
- take or attempt a step your role does not allow, or gain access to another party's data;
- attempt to influence a verdict other than with genuine evidence (see section 6);
- probe, load-test or attack the hosted service, or use it to attack others. Security research is welcome against your own instance; see the security page;
- scrape the service or resell access to it;
- upload content you have no right to upload, or content that is malicious.
10. Your content
- You own what you put into the service: documents, criteria, evidence, deliverables. You give us a licence to store, process, display to the parties entitled to see it, send to our processors (including the AI verifier) and hand over as the agreement requires, for the purpose of providing the service.
- You are responsible for having the rights to what you upload.
- Feedback you give us about the service may be used without obligation to you.
11. Agents and the API
- MCP clients and API keys act for the organization that authorized them, within the tools shown at consent. Steps that bind a party or move money (confirming criteria, funding, reviewing, releasing, contesting, disputing, and organization administration) are never available to them.
- You are responsible for what your agents do with the access you give them, and for keeping their credentials safe.
- We may change the API. We will keep documented endpoints stable where we can and announce breaking changes in the repository.
12. The open-source engine
The engine's source code is licensed under the GNU Affero General Public License, version 3. That licence governs the code; these terms govern your use of our hosted service. Nothing in these terms limits your rights under the AGPL to run, study, change and share the code.
13. Third-party services
The service depends on PayPal, Anthropic, GitHub, Resend, Render and Cloudflare. Their terms govern your relationship with them where you have one (for example, your PayPal or GitHub account). We are not responsible for their availability or conduct.
14. Disclaimers
The service is provided "as is" and "as available". To the extent the law allows, we make no warranties, express or implied, including of merchantability, fitness for a particular purpose, non-infringement, or that verdicts will be correct, that payments will complete, or that the service will be uninterrupted or error-free. The sandbox service in particular is an evaluation environment and may be reset or changed without notice.
15. Limitation of liability
To the extent the law allows, we are not liable for indirect, incidental, special, consequential or punitive damages, or for lost profits, revenue, data or goodwill, arising from your use of the service. Our total liability for all claims relating to the service in any twelve-month period is limited to the fees you paid us in that period, or one hundred US dollars if you paid none. Nothing here limits liability that cannot be limited by law.
16. Your responsibility to us
If a third party brings a claim against us because of your content, your agreements or your breach of these terms, you will defend us and cover the resulting costs, damages and reasonable legal fees, to the extent the law allows.
17. Ending this agreement
- You may stop using the service at any time and ask us to delete your account as the Privacy Policy describes.
- We may suspend or end your access if you breach these terms, if the law requires it, or if we stop offering the service. We will give notice where we reasonably can.
- Agreements in progress are not cancelled by an account ending. Funds held at PayPal remain subject to PayPal's rules, and the record of an agreement remains available to its other parties.
- Sections 10 and 14 to 19 survive termination.
18. Changes to these terms
The effective date at the top changes whenever these terms do. For a material change we will email every account before it takes effect and say what changed. If you keep using the service after that date, the new terms apply. The history is in the repository.
19. Governing law and disputes
These terms are governed by the laws of the United States and of the state in which we are organized, without regard to conflict-of-law rules. Before bringing a claim, you agree to write to us at legal@milestone-ledger.com and give us 30 days to resolve it. The specific state and venue will be stated here, after legal review, before any live deployment.
20. Contact
Questions about these terms: legal@milestone-ledger.com. Anything else: support@milestone-ledger.com.