Terms of Service

---

Each section opens with a plain-language summary in a box like this one. The summary helps you read; the full text under it is the agreement.

---

1. Who we are, and what you're agreeing to

In plain terms: Mapparoo is run by Water and Stone. Creating an account means you accept these Terms and the Privacy Policy.

Mapparoo ("Mapparoo," the "Service") is operated by [Water and Stone, a [entity type] organized under the laws of [state]] ("Water and Stone," "we," "us"). These Terms of Service (the "Terms") are a binding agreement between you and Water and Stone. By creating an account, or by using the Service, you agree to these Terms and to our Privacy Policy. If you do not agree, do not use the Service.

If you use the Service on behalf of a company or another person, you represent that you have authority to bind them, and "you" includes them.

You must be at least 18 years old to create an account.

2. What Mapparoo is — and what it is not

In plain terms: Mapparoo analyzes your planning documents and your repository and produces guides — maps, audits, and briefs. The analysis is produced by AI systems with automated verification. It is genuinely useful and honestly labeled, but it can be wrong, and it is not professional advice.

The Service ingests planning documents and a connected code repository, analyzes them using large language models and automated verification (including executing your repository's install, build, and test steps in an isolated sandbox), and produces interactive guides: plan views, discovery guides, audits with decision briefs, gap views, and re-checks.

The Service produces analysis, not certified fact. Specifically:

(a) Findings, severity assessments, verification outcomes, and all guide content are generated by automated systems. Every guide states its own coverage and limits in a banner; those statements are part of the deliverable and you should read them.

(b) A finding may be incorrect, incomplete, or out of date the moment your code changes. The Service provides a feedback mechanism for suspected accuracy problems, but there is no dispute or adjudication process, and feedback carries no promise of response or correction.

(c) Nothing the Service produces is legal, financial, security-certification, or professional engineering advice, and no guide is a substitute for professional review where the stakes call for one. You are responsible for decisions you make — including decisions about code you ship, contractors you pay, or acquisitions you close — regardless of what a guide says.

3. Accounts

In plain terms: Sign up with email + password or GitHub. Keep your credentials safe; what happens under your account is on you. You can delete your account yourself, and deletion actually deletes your work.

You register with an email address and password, or through GitHub. You are responsible for safeguarding your credentials and for all activity under your account. Notify us promptly at [support@mapparoo.com] if you believe your account has been compromised.

You may delete your account at any time from the account view. Deletion removes all projects and their artifacts (runs, registries, guides, uploaded documents), revokes all hosted share links, and revokes our GitHub authorization. Purchase records are retained as required for financial and legal compliance, dissociated from your deleted profile to the extent the law allows.

4. Your content and repository access

In plain terms: Your code and documents stay yours. You give us only the narrow permission we need to analyze them and show you the results. We access repositories read-only, through a GitHub App you install on the specific repositories you choose.

Ownership. You retain all rights in the repositories, documents, and other materials you connect or upload ("Your Content"). Nothing in these Terms transfers ownership to us.

License to us. You grant Water and Stone a limited, non-exclusive, worldwide license to access, copy, transmit, process, and display Your Content solely to operate the Service for you: running the analyses you invoke, storing the resulting artifacts as your work product, and serving them back to you and to people you deliberately share them with. This license ends for any item of Your Content when it is deleted from the Service, except for evidence excerpts embedded in artifacts you have not yet deleted.

We do not train models on Your Content. Your Content is processed by our AI provider under terms that do not use it for model training; the current arrangement is disclosed on our custody page.

Repository access. Repository access is read-only, granted through a GitHub App you install on the repositories you select, using short-lived per-run tokens. Runs happen only when you invoke them. You can revoke access at any time through GitHub or the account view.

Your responsibilities for Your Content. You represent that you have the necessary rights to connect and upload Your Content — including where the repository contains third-party or employer-owned code — and that doing so does not violate law or another agreement. If you share a stakeholder edition containing someone else's confidential information, that disclosure is your decision and your responsibility.

Prohibited content. You must not connect, upload, or otherwise submit to the Service any repository or document that contains special categories of personal data (as defined under GDPR Art. 9 — e.g. data revealing racial or ethnic origin, political opinions, religious beliefs, health, biometric or genetic data, or sexual orientation), government identifiers, or payment-card data. The Service analyzes source code and its accompanying documents and is not designed to process such data; submitting it breaches these Terms and the data-processing terms of our subprocessors.

5. Code custody

In plain terms: Your full repository exists in exactly two places during a run — GitHub and the sandbox — and the temporary clone is deleted when the run ends. What we keep is your work product: the guides and registries, which contain only the excerpts cited as evidence. Everyone who processes your code is named publicly.

We make the following custody commitments, which also appear (with the current processor list) on our public custody page:

(a) Repository access is read-only.

(b) The temporary full-repository clone used for a run is deleted after the run ends. We do not retain raw clones.

(c) Analysis artifacts — registries and guides — are retained as your work product until you delete them (or the project, or your account). They contain only the limited code and document excerpts cited as evidence.

(d) Every third-party processor of customer intellectual property is disclosed plainly on the custody page. Adding a processor is a change we announce, not something that happens silently.

(e) Full project deletion and full account deletion are always available, self-serve.

6. Runs, credits, and pricing

In plain terms: Paid capacity is denominated in runs and credits — never tokens. Every run shows you its price before you commit, and no run ever costs more than its preview said. Current prices and tier contents live on the pricing page.

Pricing. Current subscription tiers, credit quantities, rollover caps, top-up prices, and one-off prices are stated on the pricing page, which is incorporated into these Terms. We may change prices prospectively; changes never apply retroactively to credits you already hold or runs you already confirmed.

Run previews are binding. Audit-class runs (Audits and Discovery) are priced in audit credits by size class, computed from your repository snapshot and declared at the run preview before you confirm. A credit is a claim on a run: no run ever costs an amount its preview did not state.

Credits. Credits debit when you confirm a run and spend oldest-first. Unused monthly allowance credits roll over up to your tier's cap while your subscription is active. Purchased top-up credits are not bounded by the rollover cap and remain usable for 90 days after your subscription ends, then lapse.

Subscription management. Subscribe, upgrade, downgrade, and cancel are each self-serve, single-action operations. Upgrades take effect immediately, prorated; downgrades and cancellations take effect at period end, and everything already granted remains usable until then. If a renewal payment fails, we follow the payment provider's standard grace and retry; if unresolved, your account reverts to the free entry — nothing is deleted, only capacity lapses.

Payment processing. Payments are processed by our payment provider (currently Stripe). We do not store your card details.

7. Refunds

In plain terms: Failed runs refund themselves — automatically. Beyond that, there are no partial or prorated refunds, and we say so before you pay, not after.

(a) Automatic: if an audit-class run fails after retry, or you cancel a run while it is still queued, your credit is returned automatically — or the cash refunded to your original payment method, where the run was a one-off purchase.

(b) A partial run at or above the minimum deliverable is delivered as-is and is not refunded. The guide states what was and wasn't completed.

(c) There are no partial or proportionate refunds. Unused allowance credits lapse without refund when your subscription ends; purchased top-ups lapse without refund 90 days later. Both facts are stated in the purchase and cancellation flows before you commit.

(d) Refunds beyond the automatic cases, and courtesy credit grants, are at our discretion.

8. Sharing and downloads

In plain terms: Guides are private by default. Sharing is a deliberate act with real controls — but a downloaded file can never be recalled, and what you choose to share is your call.

No guide is reachable by anyone but its signed-in owner until you create a stakeholder edition. When you create one, you choose its contents, review every evidence excerpt it would expose, and share it via a hosted link with expiry and revocation controls. Revocation and expiry apply to hosted links only; a downloaded file can never be recalled. You are responsible for what you include in an edition and whom you give it to.

Stakeholder editions are snapshots. They do not update when you run new analyses, and readers see the edition's coverage banner, which cannot be removed.

9. Acceptable use

In plain terms: Use Mapparoo on repositories you have the right to analyze, and don't attack the service. The sandbox exists to run untrusted code safely — probing it for sport is the one thing that gets an account closed fast.

You agree not to:

(a) connect or upload content you lack the rights to, or content that is unlawful;

(b) attempt to break out of, probe, or interfere with the analysis sandbox, or craft repository or document content designed to manipulate the analysis pipeline into producing outputs for anyone other than you (the Service detects and discloses suspected manipulation as integrity notices; deliberate attacks are a violation of these Terms);

(c) interfere with or disrupt the Service, circumvent rate limits or access controls, or access another user's projects;

(d) resell, sublicense, or offer the Service to third parties as your own service without our written agreement;

(e) use the Service to develop a competing product by systematically extracting its outputs.

Security research conducted responsibly is welcome — contact us first at [support@mapparoo.com].

10. Our intellectual property

In plain terms: The guides are yours to use and share. The software, the pipeline, and the Mapparoo name are ours.

The Service — including its software, analysis pipeline, guide renderer, severity rubric, templates, and branding — is owned by Water and Stone or its licensors. These Terms grant you no rights in them except the right to use the Service. The guides, registries, and other artifacts produced from Your Content are yours: you may use, download, share, and modify them freely, subject to the coverage banner remaining intact in unmodified copies you share.

11. Third-party services

In plain terms: Mapparoo depends on named third parties — GitHub, our AI provider, the sandbox vendor, storage, payments, email. If one of them has an outage, runs can fail; failed runs refund automatically.

The Service depends on third-party providers, disclosed on the custody page and in the Privacy Policy. Their availability affects ours. Where a provider outage causes a run to fail, § 7(a) applies. Your use of GitHub is governed by your agreement with GitHub; we are not responsible for GitHub's acts or omissions.

12. Service changes and availability

In plain terms: We can change the product, and we don't promise 100% uptime. What we do promise: we won't silently take away credits you've paid for, and if we ever shut down, you get notice and time to download your work.

We may modify, add, or remove features. We do not guarantee uninterrupted availability. If we discontinue the Service entirely, we will give at least 30 days' notice by email, during which you can download your guides, registries, and data; credits rendered unusable by a discontinuation are refunded pro rata at their purchase price notwithstanding § 7.

13. Termination

In plain terms: You can leave any time. We can suspend or close accounts that violate these Terms — and if we close yours without cause, unused purchased credits are refunded.

You may stop using the Service or delete your account at any time. We may suspend or terminate your account for material violation of these Terms (with notice stating the reason, except where the violation is an active attack), or where required by law. If we terminate your account without cause, we will refund the unused portion of purchased top-up credits and any prepaid subscription period. If we terminate for cause, § 7's no-refund rules apply. Sections 2, 4 (your responsibilities), 5(c)–(d), 7, 10, and 14–17 survive termination.

14. Disclaimers

In plain terms: The service is provided as-is. The honest version of that sentence is § 2 — AI analysis can be wrong — plus the coverage banner on every guide.

TO THE MAXIMUM EXTENT PERMITTED BY LAW, THE SERVICE AND ALL OUTPUTS ARE PROVIDED "AS IS" AND "AS AVAILABLE," WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, ACCURACY, OR COMPLETENESS. WITHOUT LIMITING THE FOREGOING, WE DO NOT WARRANT THAT ANY FINDING, VERIFICATION OUTCOME, OR GUIDE IS CORRECT OR COMPLETE, OR THAT THE SERVICE WILL IDENTIFY EVERY GAP, DEFECT, OR RISK IN A REPOSITORY.

15. Limitation of liability

In plain terms: Our liability is capped at what you paid us in the last 12 months. If you're making a decision worth far more than that, use the guide as one input, not the only one.

TO THE MAXIMUM EXTENT PERMITTED BY LAW: (a) WATER AND STONE WILL NOT BE LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR FOR LOST PROFITS, REVENUE, DATA, OR GOODWILL, ARISING FROM OR RELATING TO THE SERVICE OR ITS OUTPUTS; AND (b) WATER AND STONE'S TOTAL AGGREGATE LIABILITY WILL NOT EXCEED THE AMOUNTS YOU PAID US IN THE TWELVE (12) MONTHS BEFORE THE EVENT GIVING RISE TO THE CLAIM. SOME JURISDICTIONS DO NOT ALLOW CERTAIN LIMITATIONS; IN THOSE JURISDICTIONS, THESE LIMITS APPLY TO THE FULLEST EXTENT PERMITTED.

16. Governing law and disputes

In plain terms: [State] law governs; disputes go to [state] courts. (Whether to add arbitration is an open decision — see the note.)

These Terms are governed by the laws of the State of [state], excluding its conflict-of-laws rules. Disputes will be resolved exclusively in the state or federal courts located in [county, state], and both parties consent to their jurisdiction.

[Drafting note, remove before publishing: many US SaaS terms add binding arbitration + a class-action waiver here. It cuts litigation exposure but is increasingly seen as hostile in developer-facing products, and mass-arbitration costs can backfire. Decide deliberately.]

17. Changes to these Terms; general

In plain terms: If we change these Terms in a way that matters, you get email notice before it takes effect — continuing to use the service after that is acceptance.

We may update these Terms. For material changes we will give at least 14 days' notice by email before the new Terms take effect; continued use after the effective date is acceptance. The current Terms are always available at this page with their effective date.

These Terms (with the Privacy Policy and pricing page) are the entire agreement between you and Water and Stone regarding the Service. If a provision is unenforceable, the rest remains in effect. Failure to enforce a provision is not a waiver. You may not assign these Terms without our consent; we may assign them in connection with a merger, acquisition, or sale of assets, with notice to you.

Contact: [support@mapparoo.com]