Terms of service · as of 2026-09-23
What you are buying, and what I do not promise.
This is short on purpose. If a sentence here is unclear, write to me before you subscribe — I would rather rewrite it than argue about it later.
Who you are contracting with
Growing Peas — Lawrenza SRL, a société à responsabilité limitée under Belgian law, registered office rue de Soignies 140, 7800 Ath, Belgium. RPM Tournai. Company and VAT number BE 0747.683.918. One person builds and maintains lexrates. Correspondence goes to info@growingpeas.dev.
What the service is
lexrates publishes statutory reference figures — mileage scales, per-diem and meal allowances — with the authority that published each one, the address it was read from, the day a human last verified it, and the day it must be re-read. It also computes with those figures, and shows the working.
It is an information tool. My obligation is one of means, not of result: I undertake to read the sources, to record what they say, to say when a figure was last checked, and to tell you when one moves. I do not undertake that any figure is correct at any moment, that a source has not changed since it was read, or that a calculation made from these figures satisfies the law that applies to you.
What it is not
It is not tax, legal, accounting or payroll advice, and I am not qualified to give any. It does not decide anything that depends on your own facts. Where a figure has a condition — an eligibility test, an evidentiary requirement, a distance cap — the condition is published beside it and left for you to apply. The API refuses rather than guesses.
It is not a substitute for the source. Every answer carries the address it came from, and you are expected to check it before acting on a figure that matters. That is not a disclaimer: it is why the addresses are there.
When I get it wrong
If a published figure is wrong, tell me and I will correct it, say so in the change log, and re-verify the source. That correction is the remedy this service provides.
- Indirect loss
- Excluded. Loss of profit, loss of business, penalties, interest, reputational harm and the cost of recomputing your own records are not recoverable from me.
- Direct loss
- Capped at what you paid me in the twelve months before the event. If you paid nothing, that cap is zero.
- Fraud and intentional fault
- Not capped and not excluded. Belgian law does not permit it, and I would not ask for it.
- Death or personal injury
- Not capped. It cannot arise here, and the exclusion is stated anyway.
I do not carry professional indemnity insurance today. If that matters to your procurement, say so before you subscribe rather than after — it is the sort of thing I would rather arrange for a customer who needs it than pretend about.
The open tier
Everything the corpus held twelve months ago — 366 periods — is published as static files, with no key, no request ceiling and no account. Those files carry no terms, and I am not going to pretend otherwise: they are on a CDN, anyone may take them, and there is no agreement between us if you do. What I ask, and what every licence behind the underlying data asks, is attribution: keep the sources that travel with each figure, or name the authority yourself. That is the one condition the public-sector re-use rules attach, and it is explained on the sources page.
The paid tier
What it is. The last twelve months, anything published for a period still to come, the expiry alert, and the year-to-date engine. Billed monthly through Stripe.
Your key. One key per subscription, issued when the payment clears and shown in your account. Keep it to yourself: usage is metered against it, and a shared key exhausts your own ceiling.
Storing what you fetch. You may keep the figures you retrieve for as long as your subscription runs, and afterwards for as long as you need them to reproduce or defend a calculation you already made. I am not going to ask you to delete a payslip’s evidence because you stopped subscribing.
Cancelling. Cancel from your account at any time. The key stops at the end of the period you have paid for. No refund for a period already begun, and no notice required.
Price. The price you subscribed at holds for as long as your subscription runs uninterrupted. If it changes, it changes for new subscriptions.
Availability
There is no service level agreement, and I will not pretend to one I cannot staff. The open tier is static files on a CDN and does not depend on me being awake. The API is subject to request ceilings, stated on the pricing page and enforced in the code — they exist so that a runaway client cannot spend without a stop.
What I know about you
An account — your e-mail address and sign-in record, held by Firebase Authentication — plus an API key, the Stripe customer it was issued for, and request counters. No name and no e-mail is stored beside a key: the key store is read on every paid request and has no business holding personal data it does not need. Stripe holds your billing details under its own terms. The whole of it is set out on the privacy page.
Law and courts
Belgian law applies. The courts of the judicial district of Hainaut, division of Tournai, have jurisdiction. If you are a business, these terms are the whole agreement between us unless we sign something else; if we do sign something else, that one wins.
These terms are dated 2026-09-23. If I change them, the change applies to your next renewal, not retroactively.