Book a demo 121

Terms of Service

The terms for the open-source TokenJam package and for TokenJam Cloud, the hosted service. Last updated 2026-09-16.

Who these terms are between

TokenJam is built and operated by Metabuilder Labs ("we", "us"). These terms are an agreement between us and you, the person or organization using TokenJam. If you use TokenJam Cloud on behalf of an organization, you confirm that you can bind that organization to these terms, and "you" means the organization.

There are two things you can use, and the terms differ for each: the open-source package, and the hosted service. The privacy policy describes what data each one handles and is part of these terms.

The open-source package

The tokenjam package (the tj command, the Python SDK and the TypeScript SDK) is published under the MIT License. The full license text is in the repository. That license, not these terms, governs your use of the code. In short: you can use, copy, modify and redistribute it, including commercially, as long as the copyright and license notice stay with it.

The software is provided "as is", without warranty of any kind, express or implied, including warranties of merchantability, fitness for a particular purpose and non-infringement. We are not liable for any claim, damages or other liability arising from the software or your use of it. This is the standard MIT disclaimer, restated here so nobody has to open a second page to find it.

The package runs on your machine and stores its data there. Cost figures it reports are computed from token counts and a pricing table, so they are estimates. Optimization findings are candidates to review, not instructions. Nothing the package prints is financial, legal or engineering advice, and you are responsible for any decision you make from it.

TokenJam Cloud

TokenJam Cloud is the hosted service at cloud.tokenjam.dev. It receives telemetry you choose to send it, stores that telemetry for your organization, and shows cost and usage reports to members of your organization. The sections below apply to Cloud only.

Design-partner period

Cloud is offered under a design-partner arrangement. Organizations are created by invitation. Features change, sometimes without notice, and we may withdraw the service or an organization's access to it during this period. If you need commitments beyond what this page states, ask us for a written agreement before relying on the service.

Accounts

Sign-in is handled by Clerk, an authentication provider. You need an account there to use Cloud. You are responsible for keeping your sign-in credentials private and for what happens under your account. Tell us at support@tokenjam.dev if you believe an account or key has been compromised.

Organization members have one of two roles, member or admin. Admins can change organization settings and retrieve or rotate the organization's ingest keys. Adding someone to your organization gives them access to your organization's data in Cloud.

Ingest keys

Each organization has an ingest key that authorizes telemetry sent to Cloud. Anyone who holds the key can write telemetry into your organization, so treat it like a password: keep it out of source control, rotate it if it leaks, and revoke a key you no longer use. Cloud supports holding two active keys so you can rotate without downtime. Telemetry that arrives with a valid key is treated as sent by you.

Your data

The telemetry you send to Cloud, the organization structure you set up there, and the reports derived from them belong to you. We use them only to run the service for your organization, to keep it secure, to fix problems, and to produce aggregate figures that do not identify your organization or its members. We do not sell your data and we do not use it to train models.

You are responsible for what you send. Cloud strips prompt, completion and tool content out of incoming telemetry unless your organization has asked us to keep it, but the metadata that remains, such as file paths and tool names, is chosen by the exporters you run. Do not send telemetry you do not have the right to share with us, and do not send secrets. The privacy policy lists what Cloud stores and for how long.

If an admin connects a third-party source such as GitHub, your use of that provider stays governed by the provider's own terms, and you confirm that you hold the right to grant Cloud read access to the repositories you choose. The App is read-only and can be uninstalled from GitHub at any time; the privacy policy describes what it reads and what happens to stored records when you uninstall it.

You can export your organization's cost data from the service, and deleting your organization deletes its data. We keep telemetry for the retention window stated in the privacy policy and delete it after that.

Acceptable use

You agree not to:

We may suspend an organization or key that breaks these rules, and we will tell you why unless we are legally prevented from doing so.

Availability and support

We run Cloud with care, and we monitor it, but we make no uptime commitment and there is no service-level agreement during the design-partner period. Ingest can fail, reports can be delayed, and maintenance can interrupt the service. Keep your own copy of anything you cannot afford to lose: the open-source package stores telemetry locally, and Cloud does not replace that copy. Support is by email at support@tokenjam.dev, on a best-effort basis.

Fees

Cloud is free during the design-partner period. If we start charging, we will publish the fees on tokenjam.dev and tell existing organizations in writing at least 30 days before any fee applies to them. Nothing you have already used becomes billable retroactively.

Termination

You can stop using Cloud at any time. Deleting your organization removes its data from the service. We can suspend or end an organization's access for a breach of these terms, for a legal requirement, or at the end of the design-partner period; where we can, we will give you notice and a chance to export your data first. Sections of these terms that by their nature should survive, such as the disclaimers and the limitation of liability, do.

Disclaimers

Cloud is provided "as is" and "as available". We do not warrant that it will be uninterrupted, error-free or secure, or that the figures it shows are accurate or complete. Cost figures are estimates derived from token counts and published prices, which change. Optimization findings are candidates for you to review; we do not claim that a suggested change is safe, that it preserves quality, or that it produces any particular saving.

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 TokenJam. To the same extent, our total liability for any claim relating to Cloud is limited to the amount you paid us for the service in the twelve months before the claim, or one hundred US dollars, whichever is greater. Nothing here limits liability that cannot be limited by law.

Governing law

These terms are governed by the laws of the State of Delaware, United States, without regard to its conflict-of-law rules. Disputes are resolved in the state or federal courts located in Delaware, and you and we each consent to that jurisdiction. If a court finds part of these terms unenforceable, the rest still applies.

Changes to these terms

When we change these terms, the date at the top moves and the change is visible in this site's public repository history. For a change that materially reduces your rights or expands your obligations under Cloud, we email organization admins before it takes effect. Continuing to use TokenJam after a change means you accept it.

Contact

Questions about these terms go to support@tokenjam.dev. Other ways to reach us are on the contact page.

Metabuilder Labs publishes these terms in good faith to describe how TokenJam is offered today. They are written in plain language and have not yet been reviewed by counsel.

Get TokenJam updates