Acceptable use policy
What the product may not be used for, and what happens if it is.
Not reviewed by counsel. Not in force.
This document has been drafted to describe what the product actually does, and it has not been reviewed by a qualified lawyer. It is published here so that it can be read, checked against the system, and corrected — not so that anybody can rely on it.
Nothing in it takes effect, nothing in it is an agreement, and no date has been set for either. Where it describes a practice, that description is accurate today; where it states a term, that term has not been settled.
If you need any of these in force before contracting — a data processing agreement, usually — say so and you will be told where the review has got to. Write to privacy@taxorch.com.
What this covers
This describes what the product may not be used for. It is part of the terms of service.
Most of it is what you would expect. Two items are specific to what this product is, and those are the ones worth reading.
Do not defeat the abstention
The product refuses to answer when it cannot prove an answer. That refusal is the mechanism the whole system is built around.
Do not use the product to produce a filing position it declined to give. Do not present an abstention to a third party as though it were an answer. Do not represent a beta-jurisdiction figure as a reviewed result when it has not been reviewed.
Overriding the system's judgement is something you may do — you are the professional. Doing it while representing the output as the system's conclusion is not.
Do not extract what makes it work
Do not attempt to extract, copy or reconstruct the corpus, the parameter datasets, the models or the evaluation harness, whether by bulk querying, by scraping, or by any automated means beyond the documented API.
Do not resell or sublicense access without a written agreement.
Ordinary limits
- No use that breaks the law in your jurisdiction or ours.
- No attempt to access another tenant's data, or to test whether you can, other than under the published disclosure terms.
- No load that degrades the service for other tenants. Rate limits exist; work within them rather than around them.
- No uploading of malicious files. Uploads are scanned, and a scan that fires is treated as an incident rather than as a mistake.
- No use of the product to build a competing corpus or model.
Security research
Security research is welcome, and the terms for it are published in full on the security page rather than buried here. In summary: report it, give us reasonable time, do not access data that is not yours, and you will get an acknowledgement within two business days and credit in the fix notes unless you would rather not have it.
Testing that degrades the service for other tenants is not research, and is the one thing those terms exclude.
What happens if this is breached
Access may be suspended. Where a breach is a mistake, the first step is a conversation; where it is deliberate — extraction, resale, another tenant's data — it is not.
Nothing here waives anything else available at law.
How changes will be communicated
- Every version carries the date it took effect, and every earlier version stays reachable at the same address.
- A change is summarised in the terms a reader would care about. “Updated our terms” tells nobody anything and is why change notices go unread.
- A material change is notified to account holders in advance, not announced by a banner after the fact.
- Continuing to use the product is not treated as agreement to a change that was never sent.