Spanda Works LLC · Last updated July 4, 2026 · support@spandaworks.com · For the interactive walkthrough of how your code is handled, see how privacy works.
Your coding requests reach our gateway so we can route and verify them. We do not train models on your
prompts or code. When an answer passes verification we store it together with the prompt that produced it,
and that store is shared by default; send tirtha.no_cache to skip it for a request. We
collect the minimum we need to run the service, and you can ask us to delete your data.
in your browser's session storage to learn which channels work. This is first-touch only.
honest about this: the request does not stay on your machine. We log request metadata (timestamps, model
tier served, token counts, key ID) to operate metering, rate limits, and billing.
it together with the prompt that produced it, because the prompt is the key the entry is found under. That
store is shared by default. Send tirtha.no_cache with a request to skip the cache for that
request. Private, isolated scopes exist and are available by arrangement; they are not the default.
Corrected August 6, 2026: this policy previously said we did not place prompts in the shared cache.
That was wrong, and we checked the running system rather than the wording. Every cached entry carries the
prompt that produced it.
cookies from our infrastructure provider. We do not run third-party advertising or tracking cookies.
not train on them either.
scope unless it is configured to, and no tenant reads another tenant's scope.
To provide, secure, meter, and bill the Services; to fix problems; to improve the system using aggregate,
non-identifying measurements; and to email you about your account, the beta, and material changes to our
terms. You can opt out of non-essential email at any time.
Service data is processed on infrastructure in the United States. Data is encrypted in transit (TLS) and at
rest. Access is limited and audited. No system is perfectly secure, but security is a design principle here,
not an afterthought.
We share data only with the service providers needed to run Tirtha (cloud hosting, model serving, payments,
email), each bound to use it only to provide their service to us, and where required by law. No selling, no
ad networks.
isolated tier.
We honor them on request. California users: you have equivalent rights under the CCPA/CPRA, including
the right to know and delete; we do not sell personal information.
Account data is kept while your account is active and deleted on request. Request logs are kept as needed for
metering, billing, and abuse prevention, then aged out. Verified solutions in the cache are retained
as part of the service, and a cache entry stores the question that produced the answer alongside it. We do
not redact that text, so do not send secrets you would not want cached. Send tirtha.no_cache on a
request to skip the cache entirely, and you can ask us to delete cached entries derived from your traffic.
The Services are not directed at anyone under 18, and we do not knowingly collect data from children.
We will notify you by email of material changes to this policy before they take effect.
Questions or requests: support@spandaworks.com ยท Spanda Works LLC, South Carolina, USA