Terms of Service

Quick Summary (Not a Substitute for the Full Terms)

• STELR signs and verifies AI-generated text and agent actions to establish provenance.
• Billing is handled through AWS Marketplace or direct subscription, based on your plan.
• You remain responsible for your content and for your own compliance with applicable regulations.
• The Service is provided “as is”; our liability is limited as described below.

1. Accounts & Eligibility

You must be at least 18 years old and capable of forming a binding contract. If you're registering on behalf of an entity, you represent that you're authorized to bind that entity. You must comply with applicable export control laws. We may suspend accounts for misuse or non-compliance with these Terms.

2. Subscriptions, Marketplace, and Payment

You may subscribe directly or through AWS Marketplace. For AWS Marketplace subscriptions, AWS Marketplace terms apply in addition to these Terms, and AWS provides a registration token used solely to resolve your customer identifier and provision your account. Usage is metered and reported to AWS Marketplace for billing.

Confirm before publishing: the previous version of this page named specific plans (Free / Pro / Enterprise) and a per-request overage fee ($0.001/request). Those numbers looked like placeholder content rather than real pricing decisions. Don't publish specific fees, plan names, or overage rates until they match your actual AWS Marketplace listing, since this section becomes a binding pricing term.

3. License & Acceptable Use

We grant you a limited, non-exclusive, non-transferable license to use the Service for your internal business purposes, subject to these Terms.

Acceptable use

• No illegal, harmful, infringing, harassing, or privacy-violating activity.
• No attempting to break, bypass, overload, or tamper with the Service, including rate limits, security controls, or signing mechanisms.
• No reverse engineering or benchmarking the Service for a competing product without our written consent.
• No using the Service to generate or authenticate content for fraudulent, deceptive, or harmful purposes.
• We may review your usage to ensure compliance with these Terms.

4. Your Content & Signing

“Content” means text, documents, and metadata you submit to the Service. You retain ownership of your Content and grant us the rights needed to process, sign, verify, and generate provenance records from it.

Important disclosures

• What signing proves, and what it doesn't: a signature verifies that specific content, in the exact form it was signed, originated from the model and at the time indicated. It does not survive arbitrary downstream edits, paraphrasing, translation, or reformatting, this is a known limitation of cryptographic and statistical content-provenance methods generally, not unique to STELR.
• Third-party marks: where we surface third-party provenance indicators, such as C2PA metadata, on a best-effort basis, we don't guarantee their accuracy or completeness.
• AI-generated classifications: any AI-generated determination is based on signed metadata where available and is not a legal or forensic finding.

5. Privacy & Security

Our Privacy Policy describes how we handle data. We use AWS KMS for cryptographic signing and apply reasonable safeguards. You're responsible for securing your API keys and reporting unauthorized access promptly.

6. Intellectual Property

The Service, its documentation, and underlying technology are the intellectual property of STELR, Inc. and our licensors. No rights are granted except as expressly stated here.

7. Availability & Support

We do not guarantee uninterrupted service. Confirm before publishing: the previous version committed to 99.9% uptime. Don't publish a specific uptime number until it reflects an SLA you can actually stand behind operationally, this is a real commitment that gets tested the first time something breaks. Support channel: support@stelrai.com. Enterprise support terms, if any, should be specified in an actual signed contract, not asserted here.

8. Previews & Beta Features

Features labeled alpha, beta, or preview are provided “as is,” may be changed or withdrawn without notice, and aren't production-ready.

9. Third-Party Services

The Service runs on AWS infrastructure, including KMS, DynamoDB, Lambda, SQS, Cognito, and CloudWatch, and may integrate with other tools you select. We're not responsible for third-party services or their terms.

10. Indemnification

You'll defend, indemnify, and hold us harmless from claims arising from your Content, misuse of signed or verified content, or violation of these Terms or applicable law.

11. Disclaimers

THE SERVICE IS PROVIDED “AS IS” AND “AS AVAILABLE.” WE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT.

12. Limitation of Liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW, WE WILL NOT BE LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR ANY LOSS OF PROFITS OR REVENUE.

Confirm before publishing: the previous version capped total liability at fees paid in the preceding 12 months, or $100 for free-plan users. That structure is a very standard SaaS pattern, but the actual dollar figure and time window should be a deliberate decision made with counsel, not a number carried over from a template.

13. Term, Suspension & Termination

These Terms apply while you use the Service. We may suspend or terminate access for non-payment, abuse, security risk, or legal compliance. On termination, your license ends, and we may delete or restrict access to Content as permitted by law.

14. Changes

We may update these Terms and will post the new effective date. Where required, we'll notify you by email or website announcement. Continued use after changes take effect constitutes acceptance.

15. Governing Law & Disputes

These Terms are governed by the laws of [confirm state/country of incorporation], excluding its conflict-of-law rules. Confirm before publishing: the previous version specified Delaware and arbitration in Wilmington. Keep this only if that's actually your entity's jurisdiction, don't publish a jurisdiction clause that doesn't match your real incorporation.