LEGAL
The deal, in plain words.
What we promise and what we ask, said straight. The formal documents are underneath, and this page is an honest summary of what they say — not a friendlier version of a different deal.
How to read this
Drafted by the engineering team so that every factual statement traces to running code. Not reviewed by a qualified data-protection lawyer. Last checked September 13, 2026. Where we cannot yet make a commitment, the document says so, dates it, and names what would close it. We would rather you found the gap here than found it yourself.
What would change that: A review is commissioned when the first controller who is not us signs the processing agreement, or at the first paid business customer — whichever comes first. It is deferred rather than skipped: today there is no customer to make these statements to.
What changed in this version: Rewritten onto the new shell, and reconciled with what the service actually does: the storage claim now distinguishes the question we pass through from the conversation we keep, and every price is read from the running service rather than typed here.
A printed copy carries this version and its date, and leaves the navigation behind.
Your work
- The question you send is passed to whichever service answers it and is gone from us the moment the answer comes back. It is never written to our disks on the way through.
- Your conversation with Clint is a different thing and we do keep it, because a conversation you have to restart on every page is not a conversation. It is scrubbed of anything that looks like a key, an address or a card number, it is bounded, and it ages out on its own. The exact clock is in the privacy notice.
- We never train anything on your words, and we never let them decide which AI is any good — that comes only from our own frozen test set, so one person's traffic can never shape another person's answers.
- Work you mark private runs only on machines you own. If none of yours can take it, we refuse and tell you. We never quietly send it somewhere else.
- Some of the free services we send questions to do keep them, and at least one learns from them. We publish exactly who does what, generated live from the running service.
Your account and your keys
- Provider keys you hand us live sealed in a vault. Your Host.Rodeo keys are kept only as one-way scrambles — a stolen file reveals nothing — and you can revoke any of them at any moment.
- You can remove a helper, a machine, or the whole account whenever you like, and take your data with you.
- We can never reach into a machine you own. There is no remote shell and no way in: your machine dials out to us, and everything it does is something it chose to accept.
Using Host.Rodeo
- Use it for lawful things, and do not abuse the free services we connect on your behalf — their terms apply to that traffic and abusing them costs everyone else here.
- Bring your own accounts and keys for paid services if you want to; those providers' terms govern that traffic and their charges are between you and them.
- We send your request wherever it will be answered best and move on the moment something stops working. No service is up all the time, and we say so plainly when something is down rather than pretending otherwise.
- You can stop whenever you like. We can suspend an account that abuses the service.
The money
We could not read the current price as this page loaded, and we will not print one from memory into a contract. The pricing page reads the same running service, and a person will tell you if neither will load.
That is the whole bill from us. If Clint has to reach for a paid service, that service charges its own price against a ceiling you set, and it is itemised on your Trail. We take no share of what you spend and no share of what you save.
The full documents
Questions
Anything unclear is worth telling us about — if a sentence here reads as a trick, it is not one, and we will rewrite it. Data-protection questions, deletion requests and security reports all reach a real person.
Earlier versions
Every version this document has had. The one above is what you are reading now.
- Version 2.0 took effect September 12, 2026— current
We do not publish the superseded text, because a stack of old contracts on a public page is a way to be read out of context. The version you accepted stays retrievable: ask us naming the version and we will send you that exact text.
The rest of the shelf
Questions about any of this reach a real person at the contact page, with or without an account — [email protected] for anything about your own data, [email protected] for a security report. We answer within 10 working days.