Legal

Terms of Service

Last updated: June 12, 2026

Draft — pending legal review. Not yet a binding agreement. This text describes how Trimml actually works today and will be replaced by counsel-approved terms before general availability.

1. The service

Trimml provides a prompt-compression API. You send text to POST /v1/compress with an API key; we return the same text with low-information tokens removed — a strict subsequence of your input, never a paraphrase — together with token counts for the original and compressed versions. A web console at this site lets you manage API keys, view metered usage, and see billing derived from that usage. The full interface is described in the API documentation.

2. Accounts

You need an account to use the service. You must provide accurate information, be at least 18 years old (or the age of majority where you live), and use the service on behalf of a business or for professional purposes. You are responsible for everything that happens under your account and for keeping your password confidential. Tell us immediately at support@trimml.com if you suspect unauthorized access.

3. API keys

API keys are bearer credentials: anyone holding a key can spend under your account. Each key's secret is shown exactly once at creation — we store only a one-way hash and a short display prefix and cannot recover a lost secret. You are responsible for storing keys securely, rotating them when staff or systems change, and revoking compromised keys in the console. Usage incurred with your keys before revocation is yours, including usage you did not intend.

4. Acceptable use

You agree not to:

  • send content you have no right to process, or content whose processing by us would violate applicable law (including export control and sanctions law);
  • probe, overload, or disrupt the service, or attempt to bypass authentication, metering, or any usage limits;
  • reverse engineer the compression models or use the service to build a directly competing token-compression product;
  • resell access to the API without our written agreement; or
  • misrepresent metered savings figures to third parties as ours.

5. Fees

Trimml charges a savings share: 20% of measured savings, and nothing else — no subscription, no minimum, no per-seat charge. Savings are computed from metering on each request:

  • tokens saved = original input tokens − compressed output tokens, as counted by the service per request;
  • savings value = tokens saved priced at a transparent blended rate of $3.00 per million input tokens (a fixed blend, not your model's actual rate);
  • your fee = 20% of that savings value, aggregated monthly.

If a request saves nothing (including short inputs we pass through unchanged), it costs nothing. Invoices are reproducible from the per-request usage table visible in your console. Fees are exclusive of taxes; you are responsible for applicable sales/VAT taxes. We may change the fee rate or the blended rate with at least 30 days' notice; changes apply only to usage after the notice period.

6. Your content and data

You retain all rights to the prompts you send. We process them transiently to perform compression and persist only token counts and timing metadata, as described in the Privacy Policy — we do not store prompt text or use it to train models. You grant us only the limited license needed to process each request and return the result.

7. Availability and disclaimers

The service is provided "as is" and "as available", without warranties of any kind, express or implied, including merchantability, fitness for a particular purpose, and non-infringement. We do not warrant that the service will be uninterrupted or error-free, or that compressed prompts will produce model outputs equivalent to your originals in every case — you are responsible for validating compression quality for your workload (the API's aggressiveness setting exists for this). Performance figures on our site are internal benchmark measurements, not guarantees.

8. Limitation of liability

To the maximum extent permitted by law, neither party is liable for indirect, incidental, special, consequential, or punitive damages, or lost profits, revenue, or data. Our total aggregate liability arising out of the service is capped at the greater of (a) the fees you paid us in the three months before the event giving rise to the claim and (b) US $100. Nothing in these terms limits liability that cannot be limited by law.

9. Suspension and termination

You can stop using the service at any time and delete your account from the console's settings page. We may suspend or terminate access for material breach of these terms, non-payment, or where required by law; where practical we will notify you and give you a chance to cure. On termination your API keys stop working; accrued fees remain payable, and the data-retention rules in the Privacy Policy apply.

10. Changes to these terms

We may update these terms. For material changes we will give at least 30 days' notice by email or in the console; continued use after the effective date is acceptance. The "Last updated" date above always reflects the current version.

11. Governing law and disputes

[Placeholder pending counsel: governing law, venue, and dispute resolution — e.g. the laws of the State of Delaware, USA, excluding its conflict-of-laws rules, with exclusive venue in its courts.]

12. Contact

Questions about these terms: support@trimml.com.