What you are buying, and where it stops.

Plain English, and specific where it costs us to be. The usage limits below are not a policy someone wrote — they are the constants the inference gateway enforces on every request, and they are listed here because finding out about a cap by hitting it is a bad way to learn your software has one.

Who we are

Kato is operated by A10X (Armando Alvarez). Contact for anything on this page, including billing: iam@armando.mx. These terms govern the Kato macOS app and the Kato Pro subscription. By installing the app or subscribing, you agree to them.

The app, and what a subscription adds

Kato is a macOS app that reads on-screen text and, with permission, transcribes calls on-device, so it can keep track of what you have committed to. What it reads, stores and sends is described on the privacy page, which is the authoritative document for data handling.

Kato Pro is hosted inference. The judgment layer runs on a large language model, and a subscription means we supply and pay for that model access through our own gateway, so you never configure an API key. You can instead bring your own Anthropic key, in which case you pay that provider directly and none of the limits in the next section apply to you — they are limits on our gateway, not on the app.

The usage limits, stated exactly

Every Kato Pro request passes through our gateway, which enforces the following. These are per licence, on UTC days and UTC calendar months.

• 300 model calls per day.
• 800,000 input tokens per day and 4,000,000 input tokens per calendar month.
• 400,000 output tokens per day.
• 20 calls per minute, a burst limit that clears after sixty seconds.
• 3 devices in a rolling 30-day window. Devices already in the window keep working; a new fourth device is what gets refused.
• Model and request shape: the gateway serves claude-sonnet-5 and claude-haiku-4-5, clamps max_tokens to 4096, and rejects request bodies over 256 KB.

What actually happens when you reach one. The cloud-backed features pause, and Kato tells you which limit it was and when it resets — daily limits at the next UTC midnight, the monthly one on the first of the next month. It does not silently downgrade you to a weaker model, and it does not queue the work. Everything that does not need the model keeps running, and nothing already in your brain is lost or deleted.

For scale: over a full month of heavy daily use by the person who builds Kato, the 300-call daily limit was reached on about one working day in twelve, and the monthly token limit was never reached. That is a real measurement rather than a reassurance, and it is the honest reason the number is published instead of buried — if your work is heavier than that, you should know before you pay. We may raise these limits; we will not lower them without telling subscribers first.

Price, trial, renewal and cancellation

The price and the trial length are whatever the checkout page showed you, and your emailed Stripe receipt carries both along with the exact date of your first charge. We deliberately do not restate them here, because we run more than one plan and a number typed onto a page is a number that eventually disagrees with the one you were actually charged.

Billing is handled by Stripe; we never see or store your card details. The subscription renews automatically until cancelled. Cancel yourself at any time from the billing portal — the link is in your receipt and in the app's billing menu — and access continues to the end of the period you already paid for. If a trial is running, cancelling before it ends means you are not charged.

Refunds. If Kato did not do what this site said it would, email us and we will refund you. We would rather return the money than argue about it.

What we do not promise

• Kato's output can be wrong. It is a language model reading your screen. It will occasionally mis-transcribe a call, attribute a commitment to the wrong person, or invent detail. Everything it produces is a draft for you to check, and you remain responsible for what you send, sign or act on.
• No guaranteed uptime. The gateway depends on providers we do not control. We do not offer an SLA, and outages are not grounds for anything beyond a pro-rated refund if you ask.
• The underlying models will change. We move to newer models as they ship, which can change how Kato words things.
• Not professional advice. Kato is not a lawyer, accountant or doctor, and reading your screen does not make its suggestions advice.

To the extent the law allows, our total liability for any claim relating to Kato is limited to what you paid us in the twelve months before it arose. Nothing here limits liability that cannot legally be limited.

Fair use

The licence is for you, on your own Macs. Do not resell access to the gateway, share a licence across an organisation, or route unrelated traffic through it. If we see a licence being used as a general-purpose API key, we will contact you before doing anything about it.

Your data

Your journal and memory live on your Mac; we do not hold a server-side copy. The privacy page sets out exactly what leaves the device, when, and how to verify it with the app's own egress ledger. If you cancel, your data stays where it always was — on your Mac — and you can export it with kato export.

Changes

If we change these terms in a way that affects what you are paying for, we will email subscribers before it takes effect. Everything else gets a new date at the bottom of this page.

Governing law

These terms are governed by the laws of Mexico, and any dispute belongs to the courts of Mexico City — after you have emailed us and given us a chance to fix it.

Last updated September 12, 2026. Every limit on this page is the constant the gateway enforces at this date. If this page and the software ever disagree, that is a bug — tell us and we will fix whichever one is wrong.