Draft. Lawpatch is in development and has no operating entity behind it yet, so the operator’s name and address below are placeholders and these terms are not in force. They are published so you can read what we intend to commit to, and they will be reviewed by counsel before they bind anyone.

Terms of service

These terms govern your use of Lawpatch, operated by [legal entity name] (“we”). By signing in, creating a workspace or running a scan you accept them.

Lawpatch is not a law firm and does not give legal advice.

Everything the product produces — findings, scenarios, exposure figures, suggested fixes — is automated analysis intended to help an engineering team decide what to look at first. It is not a legal opinion, it does not create a lawyer–client relationship, and it is not a substitute for advice from a lawyer qualified in the relevant jurisdiction. Decisions with legal consequences belong with qualified counsel. In jurisdictions that reserve legal advice to licensed practitioners — including Türkiye under the Attorneys’ Act and the several US states that regulate the unauthorised practice of law — nothing in the product should be read as such advice.

1. What the service does

Lawpatch scans a repository on your own machine, sends derived signals (not source code) to our API, matches them against a corpus of court decisions and regulator actions, and returns a report with suggested remediation. The security model describes exactly what leaves your machine.

2. Your account and your workspace

Lawpatch is a professional tool. You must be at least 18 and use it for your business, trade or profession, or on behalf of an organisation that has authorised you to accept these terms.
You need a Google account to sign in. You are responsible for who you invite into your workspace and what they can see.
API keys are shown once and stored by us only as a SHA-256 hash. Treat a key like a password; rotate it from the dashboard if it leaks.
You must have the right to scan the repositories you point the SDK at.

3. Acceptable use

Do not use the service to scan code you do not have permission to analyse.
Do not attempt to extract the corpus in bulk, circumvent rate limits, or resell the output as a legal-advice service.
Do not use the service to build a competing precedent corpus.
Report security problems to [email protected] rather than exploiting them. We will not pursue good-faith research that follows that route.

4. Your content

You keep every right in your code and in the signals derived from it. You grant us only the licence needed to run the analysis you asked for and to show you the result. We do not use your scan data to train models. Anonymised statistics that cannot be linked back to a customer, a repository or a person (for example how often a rule fires across all customers) may be used to improve detection.

5. The corpus

Court decisions and regulator actions are public documents. Our summaries, the fact-pattern taxonomy and the software lessons attached to each decision are our work and are licensed to you for use inside your organisation. Machine-summarised entries are labelled as such until a human editor verifies them.

We use source material under each source's own terms, such as the public-domain status of US federal government works, the Open Government Licence and CC BY 4.0. Where a precedent shows a credit for its source, keep that credit if you reuse the summary. These terms do not restrict your use of the underlying public documents, which you can obtain from their original sources.

6. Availability and change

We aim to keep the service running but do not promise a particular uptime unless we have agreed one in writing. Detection rules, the corpus and the agent pipeline change continuously; a finding that appeared in one scan may not appear in the next, and the reverse.

7. No warranty

The service and everything it produces are provided “as is” and “as available”. To the maximum extent the law allows, we give no warranty, express or implied, that a report is complete, accurate or current, that a finding or suggested fix is correct, that following the output will make a product compliant with any law, or that the service is fit for a particular purpose. Mandatory statutory rights, including those under consumer protection law, are not affected.

8. Liability

To the maximum extent the law allows, we are not liable for indirect or consequential loss, for regulatory action taken against you, or for a risk the product did not find. Static analysis cannot see behaviour configured outside the repository, and an absence of findings is not a statement of compliance. Our total liability is capped at the fees you paid in the twelve months before the claim. Nothing here excludes or limits liability that cannot lawfully be excluded or limited, including for death, personal injury, fraud, wilful misconduct or gross negligence (among others under Art. 115 of the Turkish Code of Obligations), or your rights under mandatory consumer protection law.

9. Termination

You may delete your workspace at any time from the team page, and a single project from its own page; both remove the associated scans and findings straight away, and both offer a JSON export first. Anyone can delete their own account from the team page. We may suspend an account that breaches section 3, and will tell you why unless the law prevents it.

10. Governing law

These terms are governed by the law of Türkiye, without prejudice to mandatory consumer protections in your own country of residence. If we change these terms in a way that matters, we will publish the new version on this page at least 30 days before it takes effect.

Contact

[legal entity name], [registered address] · [email protected]