Tīrtha by Spanda Works
Get an API key

Privacy Policy

Spanda Works LLC · Last updated July 4, 2026 · [email protected] · For the interactive walkthrough of how your code is handled, see how privacy works.

The Short Version

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.

1. What We Collect

  • Account data: your email address and name when you create an account.
  • Attribution: if you arrive from a link, we may record the source (for example a UTM tag and referrer) in your browser's session storage to learn which channels work. This is first-touch only.
  • Service data: your API requests (prompts and code) reach our gateway so we can process them. We are 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.
  • Cached solutions, and this includes your prompt text. When an answer passes verification we store 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.

  • Billing data: handled by our payment processor; we do not store your card number.
  • Cookies: our site uses minimal cookies. Login-protected areas (the dashboard) use authentication cookies from our infrastructure provider. We do not run third-party advertising or tracking cookies.

2. What We Do NOT Do

  • We do not use your prompts or code to train models, and we verified that our upstream serving providers do not train on them either.
  • We do not sell your personal information.
  • We do not serve cached content across tenant boundaries. An isolated tenant does not read the shared scope unless it is configured to, and no tenant reads another tenant's scope.
  • We do not send SMS messages or run third-party ads.

3. How We Use Data

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.

4. Where Data Lives and How It Is Protected

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.

5. Sharing

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.

6. Your Choices and Rights

  • Private scope: private scopes, where nothing you produce is shared, and a dedicated isolated tier are available by arrangement; they are not the default.
  • Access and deletion: email [email protected] to request a copy of your data or its deletion.
  • EU/UK users: you have rights under the GDPR (access, rectification, erasure, portability, objection).

    • 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.

7. Retention

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.

8. Children

The Services are not directed at anyone under 18, and we do not knowingly collect data from children.

9. Changes

We will notify you by email of material changes to this policy before they take effect.

Questions or requests: [email protected] · Spanda Works LLC, South Carolina, USA