Terms of service

Supplemental terms for the DSAIL hosted service, under Jaxon's Terms and Conditions. They state what this service does differently from Jaxon's other products — no model, no training, no reading of stored rules — and take precedence over the general terms where the two differ.

Version 2026-09-14. Draft pending review by outside counsel. Effective from the date in the version string; the string changes when the text changes in a way you would need to re-accept, and a change is announced on this page at least fourteen days before it takes effect. dsail_get_account_status (and GET /v1/account) reports the version that governs your tier, so an agent can tell you which terms apply without you coming here to look.

How these terms fit together

The DSAIL hosted service at agents.jaxon.ai — reached over MCP, REST, the dsail Python package and the connectors and plugins Jaxon publishes for it — is a Service of Jaxon, Inc. ("Jaxon") and is governed by:

1. Jaxon's Terms and Conditions (the "General Terms"),
2. Jaxon's Acceptable Use Policy,
3. Jaxon's Privacy Policy, read with the hosted-service privacy notice, and
4. this page, which is supplemental terms for the hosted service under §2.2 and §14.1 of the General Terms.

Where this page and the General Terms or Privacy Policy differ about the hosted service, this page controls, to the extent of the difference. Everything this page does not address — the warranty disclaimer, the limitation of liability, your indemnity, feedback, export and sanctions, U.S. Government use, governing law (Massachusetts) and dispute resolution (CPR arbitration in Boston), and the rest — is the General Terms, unchanged. A separate written agreement between you and Jaxon controls over all of the above where it says so.

How you accept

By approving the connector's consent screen, by obtaining or using a credential, or by making any call to the service, you accept the General Terms, the Acceptable Use Policy and the version of this page in force at that moment, on behalf of yourself and of any organisation whose policy you submit. If you do not agree, do not connect and do not call. Continued use after a new version takes effect is acceptance of the new version. At this version the hosted service has no account registration; §1 of the General Terms (Accounts) applies to the credential or connector authorization you hold, which is your access credential for that section's purposes and must be kept confidential in the same way.

What the service is

DSAIL exists to turn a written policy into rules a program can check, and get the same answer every time. You describe a policy; a model running on your own account drafts DSAIL source; this service compiles that source to a formal ruleset and, given claim values you extract, returns each assertion's own result — TRUE, FALSE, UNKNOWN or AMBIGUOUS — each naming the assertion that decided it. There is no web application of ours behind it and no human-facing account portal.

In the vocabulary of the General Terms, your ruleset source, names, notes, approvals, unit converters and labels are your Prompts, and the compile and check responses are your Outputs; together, Materials. The sections below narrow what Jaxon may do with them.

Where this service departs from the General Terms

These are the differences, stated so a reader of the General Terms knows exactly which sentences do not apply here.

1. No model in the loop. At this version of the service, Jaxon calls no language model on any tier, for any purpose, and shares no Materials with any AI provider. §5 of the General Terms (Third-Party Services) and the Privacy Policy's "Third-Party AI Partners" provisions therefore describe nothing that happens on this service. Every model step — drafting rules, extracting claim values, proposing a category label — runs on your own model, on your own subscription, in your own client. What crosses the wire at inference is a schema-bounded claim dictionary, never the underlying document. If a future version ever changed this, it would be a new version of this page with notice; it would never arrive silently.
2. No training, no improvement use, no content analysis. §4.6 of the General Terms ("we may use Materials to provide, maintain, and improve the Service and to develop other products and services", with its trust-and-safety exception) and the Privacy Policy's statement that Customer Content may be used to train or enhance models do not apply to this service. Jaxon uses your Materials solely to provide the service to you, as licensed below. No tier's terms grant Jaxon any right to analyse the content of your rulesets; if such a right is ever offered it will be an explicit, separately accepted opt-in on a designated tier, never a default.
3. We do not read the policies we store. The service holds your rules text and DSAIL source so that it can compile them and so that an approval can be bound to exact bytes. Jaxon does not read them for any other purpose: no search, no indexing, no sampling, no analysis. Usage metering records metadata only, and the code that writes it has no parameter that could carry policy text or a claim value.
4. Confidentiality runs both ways. §8 of the General Terms protects Jaxon's confidential information. For this service Jaxon additionally undertakes to hold your Materials in confidence, use them only as this page allows, and disclose them to no one except as required by law — telling you unless the law forbids it — and to give the notice stated under Security incidents. Jaxon's hosting subprocessor is Amazon Web Services; Jaxon will announce on this page, with notice, before adding any other subprocessor that would hold your Materials. §14.14 of the General Terms (reporting Prompts or Outputs to law enforcement) is limited, for this service, to what §8.5 of the General Terms and applicable law require.
5. Deletion and export are stated, not discretionary. In place of §13.3 of the General Terms, the Deletion and Termination sections below apply.

Tiers

Terms are versioned per tier. Today every tier is bound to the same version of this page; the table records what each tier fixes so that a difference, when one arrives, is a visible row rather than a footnote.

No tier claims content-analysis rights, and none ever will by default. That is not a statement of current practice: the tier registry the service runs refuses at start-up to describe any tier as holding them, and refuses to publish a tier whose terms are not stated here. If content rights are ever offered they will be an explicit opt-in on a designated tier, negotiated, and visible in this table as a row that says so.

A production API key carries its account's allowance, not one of its own. The key you ask for after subscribing and the chat session you asked from are the same customer with one meter and one subscription. A key is only ever issued to a caller already signed in to the account, never on a page reached by a link, and each tier states how many an account may hold.

"Hash-addressed, operator-readable for compile only" means: your normalised source is stored at its content hash on an encrypted volume; the service reads those bytes back to compile them when you ask for a check by hash, and for nothing else. A Jaxon administrator with access to the host could read them, is bound by the confidentiality undertaking above not to, and does not do so in any procedure Jaxon operates. A blind-storage posture, under which Jaxon would hold ciphertext it could not read, is designed but not offered; a tier that runs it will have category labeling off, because a label about content the operator cannot read would be the one readable fact about it.

§2.2 of the General Terms limits evaluation use to internal, non-commercial purposes; that applies to the unmetered-preview and evaluation tiers here. Production use is the metered, api_key, full or enterprise tier.

What you may do

Use the service to compile, check, store, load, approve and label rulesets you have the right to hold, through any of the supported surfaces, within the limits your tier states (dsail_get_account_status reports your position) and within the Acceptable Use Policy. Ruleset creation, compilation and storage are free; inference — a check call — is the metered operation.

Your account, and what happens at a limit

An account is an organization, not a person. Which organization you belong to is decided by your identity provider when it names one: colleagues in that organization share one project, one ruleset library and one allowance, which is the point, since a policy library is a team's rather than an individual's.

Sharing an email domain does not by itself place you in an organization with its other holders. Where your identity provider names no organization, each verified address gets a project of its own unless Jaxon has specifically recorded that domain as one organization at that customer's request. You are never placed in a namespace with strangers because you happen to use the same mail provider as them.

Only checks are metered, in Jaxon Verified Units. One JVU is one rule checked against up to 1,000 characters of the claim values you submit, so a call carrying more rules or more text consumes more than one. If your allowance is spent, checks pause and nothing else does: compiling, editing, saving, loading, approving and labelling continue to work and continue to be free. Your stored rulesets, approvals and unit library are untouched.

Payment is on a page Stripe hosts. Jaxon operates no billing page, collects no card details and stores none. Upgrading takes effect on the next call, in the conversation you are already in. Jaxon holds a Stripe customer reference and your organization name; Stripe holds the payment relationship and is the controller of the payment data it collects, under its own terms.

If a subscription lapses, the account returns to the free tier. Nothing is deleted: your rulesets, approvals, namespace and unit library remain exactly as they were, and only the ceiling moves. A failed card payment does not immediately suspend anything while the payment provider is still retrying it.

A free allowance is granted once and does not reset. It is a fixed number of Jaxon Verified Units for the life of the account rather than a monthly ration, so once it is spent, continuing means a payment method on file. dsail_get_account_status reports the position at any time, and warns you as the allowance runs low, so a limit is something you can see coming.

What each tier includes is set in the payment provider's dashboard, not in the service, and is reported to you by dsail_get_account_status. Jaxon may change a tier's price or its included units; a reduction in what your current tier includes does not apply to units you have already been granted.

What you may not submit

The service holds no authorization to receive controlled information, and its operators are not screened for one. In addition to the Acceptable Use Policy, do not submit: classified information; Controlled Unclassified Information (CUI) or information marked for limited distribution; technical data controlled under ITAR or the EAR; Criminal Justice Information (CJIS); protected health information (PHI) under HIPAA; cardholder data; or personal data about identifiable people beyond the names and notes fields described under Your content. A ruleset about a classified, controlled or clinical policy must be written so that the ruleset itself carries none of that content — the category security_classification in the published vocabulary exists for exactly that distinction. Jaxon has no obligation to recognise or treat submitted content as controlled, and does not screen for it; if you submit it anyway, you are responsible for the consequences under the indemnity in the General Terms.

The hosted service holds no FedRAMP authorization, no DoD provisional authorization, no CJIS agreement, no HIPAA business associate agreement and no PCI attestation. It is hosted in a commercial AWS region in the United States by personnel who are not screened for clearance.

The Acceptable Use Policy and what this service returns

The Acceptable Use Policy prohibits, among other things, automated decisions about employability and about eligibility for housing including home loans, and criminal-justice decisions. This service returns what a ruleset's assertions concluded about claim values you supplied — never an overall verdict, never a decision. Whether a use of those conclusions is a prohibited automated determination under the Policy is decided by how you act on them: the Policy's human-in-the-loop and disclosure requirements apply to you where your use falls within them, and Jaxon may suspend or terminate for a violation as the Policy states. Do not send us documents: a check receives claim values you extracted, not the text they came from, and the service is not built to receive or hold the text.

Your content, and the licence you grant

Rulesets, revisions, unit libraries, names, notes and approvals you create are yours, as §4.1 of the General Terms says. In place of §4.6, you grant Jaxon a non-exclusive, worldwide, royalty-free licence to store, copy, transmit, back up and process that content solely to provide the service to you: to compile it, to answer checks against it, to bind approvals to it, to return it to you, and to keep and restore backups of it. You additionally grant Jaxon the right to compute and publish aggregate statistics from the usage metadata and the vocabulary ids described on the data handling page, subject to the minimum cell size stated there. No other right in your content is granted, and none is implied.

Approver names and notes are text you choose to submit. They are stored beside the ruleset hash they refer to and used for nothing else; do not put personal data in them beyond what an approval record needs. Where such text is personal data under a data-protection law, Jaxon processes it on your instructions and for that purpose only, as the privacy notice states.

Deletion

You may delete what you stored by asking Jaxon at the address below. Deletion removes the objects and their metadata rows from the live store at once. Backup copies age out on the schedule stated on the data-handling page (at most 400 days) and are not restored selectively; usage events already recorded about the objects are not deleted, because they carry no content.

The one derived field

The only thing the service derives from your rulesets is an application-domain category label, and it is produced by your model, not ours. The label is stored as ids from a published vocabulary, never as the text your model wrote; a term enters that vocabulary only when at least K customers independently land on it; you may decline labeling on any call, and an operator can turn it off for an account. A label never changes any result. K is at least 5, and the minimum cell size N below which no aggregate figure leaves Jaxon is at least 5. The current values are published live on the vocabulary page and printed on every report; reducing either below 5 is a version change to this page, with notice. How the figures are protected is on the data handling page.

Security incidents

If Jaxon confirms a security incident affecting your stored content or your credential, Jaxon will notify you without undue delay, and no later than 72 hours after confirming it, describing what was affected. The design bounds what an incident can expose: the store holds rules text, names, notes and approvals; the usage stream holds metadata only; neither holds claim values, documents or any assertion's result.

Termination

§12 and §13 of the General Terms apply, with these additions for this service. Jaxon may suspend or terminate a credential or connector authorization without notice for a breach of What you may not submit, the Acceptable Use Policy or §2.3 of the General Terms, for non-payment where a tier is paid, or where continued service would expose Jaxon or other customers to harm; and with thirty days' notice for any other reason. You may stop using the service at any time and ask for deletion. On termination for any reason other than your breach, Jaxon will keep your stored rulesets retrievable for thirty days so you can export them, then delete them.

Results are the rules' conclusions, not advice

The service reports what the rules concluded about the claim values you supplied — per assertion, in the engine's own four words — and never an overall verdict, never a judgement that anything is approved, compliant, denied or lawful. Nothing the service returns is legal advice or a compliance determination; what a FALSE should cost is your decision. §4.5 of the General Terms (reliance on Outputs) and the Acceptable Use Policy's independent-verification requirement apply.

Your extraction is your responsibility

A result is a formal consequence of the claim values you supplied under the ruleset you compiled. Whether those values faithfully describe a document is your extraction's responsibility and sits outside any guarantee. The service never sees the document, and cannot know whether a claim value is true of it. UNKNOWN is a legitimate result, not a failure: it means a claim the rule needed was not determined.

Service levels

Jaxon's Service Level Agreement applies to Services under a Subscription Contract. At this version the hosted service is offered without a Subscription Contract, so no availability commitment or credit applies to it; §12 of the General Terms (modification, suspension, discontinuation) governs availability. That changes when paid tiers do, by a version of this page.

Contact

Jaxon, Inc., 68 Harrison Avenue, Suite 605, Boston, MA 02111, USA — <https://jaxon.ai>. Questions about these terms: support@jaxon.ai or (877) 209-7055. Deletion, export and privacy requests: privacy@jaxon.ai.

Related: Privacy notice, Data handling, Published vocabulary; Jaxon's Terms and Conditions, Acceptable Use Policy, Privacy Policy and Service Level Agreement.