The honest version. Most privacy pages are written to make you forget the question. This one answers it, and then lets you watch it happen.
Every AI coding agent sends your code somewhere, and mine is no different. When you use Tīrtha, your request reaches a server I run. Anyone selling you a hosted coding agent that keeps your code entirely on your own machine is either self-hosted only, or not telling the truth.
What matters is what happens to it there. And that is where the real design is.
The thing that gets stored and reused is a proven, generic solution, stored under the problem it solves, not under who asked. Your code, your file paths, your API keys, your proprietary logic: those are not the cached object. There is no per-user record of your code sitting in a shared cache waiting to leak, because that is not what I cache.
Isolation is enforced, not promised. Anything specific to you lives behind a scope wall. Cache keys are content hashes computed on my server, never built from a URL you could craft. Every read is checked against who is asking. The classic shared-cache failures, where a crafted URL or a traffic spike serves one customer's data to another, are closed by construction.
Draw from and contribute verified generic answers. The whole gateway gets faster and costs less the more it is used.
Your own scope. You neither contribute to nor pull from the shared layer. Your work stays yours.
A dedicated single-tenant stack, own key, air-gapped. Not "I will not look," but "I cannot." For regulated work.
You choose. Contribute and save, wall it off, or a stack I structurally cannot reach into.
Everyone else asks you to trust a policy page. Paste a real coding request below and see, right now, what stays private and what could ever be shared. Nothing is sent anywhere. It runs in your browser.
This shows how cache admission actually works: only a verified, generic solution can be shared, addressed by the problem, never by you. Your prompt, code, file paths, and API keys never are. This demo detects common sensitive patterns in your browser to illustrate the rule; the live gateway enforces it by tenant scope and by verification.
I will not tell you your code can never be inferred, or that this is mathematically private. That would be a metaphysical promise, not an engineering one. What I can tell you is the enforced boundary: verified answers are shared, your prompts and code are not, and your data is walled off per tenant. That is a boundary you can hold me to, not a feeling I am asking you to have.