Terms of Service

Last updated: May 2026

These Terms of Service ("Terms") govern your access to and use of contextspa.com and its API (the "Service"), operated by [ENTITY NAME] ("we", "us", "our"). By creating an account or using the Service you agree to these Terms.

1. The Service

contextspa is a context distillation API. It accepts a messages array and returns a transformed, compressed version using AI language models. The Service does not store your conversation content beyond the duration of a single API request.

2. Distilled Output — No Warranty

The Service provides output on an "as-is" basis with no warranty of any kind, express or implied. Distillation is a lossy transformation. Information may be summarized, reordered, or omitted. We do not guarantee that distilled output is accurate, complete, or fit for any particular purpose.

You are solely responsible for reviewing distilled output before using it — in AI prompts, in code, in communications, or anywhere else. We accept no liability for outcomes resulting from your reliance on distilled content.

3. Credits and Billing

Bonus credits ($1.00 granted at signup) are non-refundable and have no cash value. They expire when your account is closed.

Purchased credits are refundable to your original payment method, minus any credits already consumed, subject to:

Refund requests must be made within 30 days of the original purchase.
Only the unconsumed purchased balance is eligible — consumed credits are non-refundable.
Refunds are processed via Stripe and may take 5–10 business days to appear.

Credits never expire while your account is active. Minimum deposit is $5.00. Maximum single deposit is $500.00.

4. Acceptable Use

You may not use the Service to:

Transmit content that is illegal, harmful, harassing, or infringes third-party rights.
Attempt to extract, reverse-engineer, or circumvent the distillation models or platform logic.
Create multiple accounts to accumulate free bonus credits.
Resell API access without prior written permission.
Conduct automated high-volume requests that degrade service for other users (rate limits apply).

We reserve the right to suspend or terminate accounts that violate these terms without prior notice.

5. API Keys

Your API key is your credential. You are responsible for keeping it confidential. Do not commit it to version control or share it publicly. If you believe your key has been compromised, regenerate it immediately from your account page — the old key becomes invalid instantly.

6. Availability

We do not guarantee uptime or availability. The Service runs on Azure Functions Consumption Plan, which may experience cold starts or brief unavailability. We will make reasonable efforts to maintain availability but provide no SLA.

7. Data and Privacy

We do not store the content of your API requests beyond the duration of the request. We store:

Your Google account email and user ID (for authentication).
Your hashed API key and credit balance.
Aggregate telemetry (token counts, strategy used, timestamps) — no message content.
Feedback payloads, only when you explicitly submit feedback via the feedback endpoint, including any messages you include.

We do not sell your data. Telemetry is used exclusively to improve the Service.

8. Limitation of Liability

To the fullest extent permitted by law, we shall not be liable for any indirect, incidental, special, or consequential damages arising from your use of the Service, including but not limited to lost profits, data loss, or decisions made based on distilled output. Our total liability for any claim is limited to the amount you paid us in the 30 days preceding the claim.

9. Changes to These Terms

We may update these Terms at any time. Continued use of the Service after changes are posted constitutes acceptance. Material changes will be noted with an updated "Last updated" date above.

10. Governing Law

These Terms are governed by the laws of [JURISDICTION], without regard to its conflict-of-law provisions. Any disputes shall be resolved in the courts of [JURISDICTION].

Questions? Contact us via GitHub.