Deploy your StellarClaw agent in under 1 minute.

Effective 2 May 2026 · StellarClaw pilot (v0.1) · stellarclaw.xyz

This is a binding agreement between you and StellarClaw for the capped pilot program. It is not legal advice; consult counsel if you need help interpreting it.

1. Acceptance

By connecting a Telegram bot, submitting credentials through this site, or otherwise using the pilot, you agree to these Pilot Terms and our Privacy Policy. If you disagree, do not use the service.

2. What the pilot is

StellarClaw provides infrastructure that binds your Telegram bot (which you create and control via BotFather) to a dedicated Stellar wallet and optional AI tooling so end-users can interact through chat. In this pilot, exposed capabilities may include: sending USDC on Stellar, swaps via Soroswap, virtual card purchases via Cards402, and autonomous payments to allowlisted x402-compatible APIs. Features change without notice.

3. Experimental software

The pilot is early-stage software on live networks. Outages, bugs, failed transactions, incorrect AI outputs, or third-party failures can occur. We may suspend, reset, or discontinue access at any time.

4. Your responsibilities

• You must lawfully obtain and safeguard your Telegram bot token. Anyone with the token may impersonate your bot toward our API.
• You are responsible for messages sent through your bot and for complying with Telegram’s policies, sanctions, AML/CFT obligations where they apply to you, and local laws.
• You must not use StellarClaw to launder funds, defraud users, harass, violate IP, or circumvent security or caps.

5. Custodial wallet & keys

For each deployed bot instance we provision Stellar signing keys that we custody server-side to operate the pilot (encrypted at rest with AES-256-GCM; not written to application logs as secrets). You do not hold the raw signing key in this pilot flow. On-chain activity is public on Stellar; wallet addresses and transaction details are visible like any blockchain wallet.

6. Hard caps (cannot be overridden from chat)

Server-enforced limits apply per deployed bot, including without limitation: per-send USDC cap (≤ 5), cumulative lifetime send cap (≤ 10 USDC in aggregate across sends where applicable), per-swap cap (≤ 2 USDC), Cards402 per-purchase cap (≤ USD 200), Cards402 lifetime allowance (≤ 10 successful purchases), and allowlisted x402 endpoints only. Production values may follow environment configuration; we may tighten or widen caps for risk or compliance.

7. AI & LLM routing

Your selected model may be fulfilled via providers such as OpenRouter or similar. Prompts, tool calls, and bot chat metadata necessary to operate the agent may transit those providers under their terms. The model can hallucinate or misunderstand instructions; it is not a financial adviser.

8. Third-party services

Telegram, Stellar validators/Horizon, Soroswap, Cards402, x402 merchants, hosting providers, and LLM vendors are independent parties. Their downtime, fee changes, policy enforcement, or loss events are outside our control.

9. Fees & taxes

Network fees (e.g., Stellar base fees, resource consumption) and third-party fees may apply. You are responsible for taxes arising from your use.

10. Disclaimers

The service is provided “as is” without warranties of any kind, express or implied, including merchantability, fitness for a purpose, non-infringement, uninterrupted operation, or error-free behaviour.

11. Limitation of liability

To the maximum extent permitted by law, StellarClaw and its contributors are not liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or loss of profits, data, goodwill, or crypto assets, arising from the pilot—even if advised of the possibility. Aggregate liability for direct damages arising from the pilot shall not exceed the greater of (a) USD 100 or (b) amounts you paid StellarClaw specifically for this pilot in the six months preceding the claim (if any).

12. Indemnity

You will defend and indemnify StellarClaw against claims, fines, and expenses (including reasonable legal fees) stemming from your bot’s conduct, your users, your misuse of the service, or your breach of these terms.

13. Termination

We may suspend or terminate deployments or access immediately for risk, abuse, legal process, or operational reasons. Provisions that should survive (limits of liability, indemnity, governing law) survive termination.

14. Changes

We may update these terms by posting a revised version here and updating the effective date. Continued use after posting constitutes acceptance.

15. Contact

Questions about these terms: support@stellarclaw.xyz.

Effective 2 May 2026 · StellarClaw · stellarclaw.xyz

This policy describes how we handle information in the pilot. Blockchain data is inherently public; custody does not make on-chain activity private.

1. Who we are

StellarClaw operates the website and APIs at stellarclaw.xyz (the “Service”). For privacy inquiries contact support@stellarclaw.xyz.

2. Data we process

• Account email: address you use for Supabase magic-link sign-in (stored with your auth user).
• Deployment inputs: bot instance name/id you choose, Telegram bot token you submit, selected LLM model, and related HTTP metadata (IP address, user-agent, timestamps) from your browser/API calls.
• Custodial wallet data: derived Stellar addresses, encrypted signing material, transaction requests/responses needed to operate tools.
• Runtime telemetry: application logs for reliability and abuse detection (we aim not to log secrets or raw private keys).
• Third-party content: messages flowing through Telegram’s platform subject to Telegram’s privacy policy.

3. Purposes & legal bases

We process data to deploy and operate your bot, enforce pilot caps, secure accounts, debug outages, comply with law, and improve the Service. Depending on jurisdiction, bases include performance of a contract, legitimate interests (security/fraud prevention), and legal obligation.

4. AI providers

To fulfill model selections, prompts and tool traces may be transmitted to LLM vendors or aggregators (e.g., OpenRouter). Review their policies for retention and subprocessors.

5. On-chain transparency

Stellar ledger history is public. Do not treat wallet addresses or transaction hashes as confidential.

6. Sharing

We share data with infrastructure hosts, analytics/monitoring vendors where used, LLM providers as needed to route models, and competent authorities when required by law. We do not sell personal information.

7. Security

We apply administrative and technical safeguards including encryption for custodial secrets at rest (AES-256-GCM). No method is 100% secure; you accept residual risk.

8. Retention

We retain pilot records while your deployment is active and for a reasonable period afterward for legal, security, and operational purposes, unless law requires longer retention.

9. International transfers

Subprocessors may process data in countries outside your own. Where required we implement appropriate safeguards.

10. Your rights

Depending on where you live, you may have rights to access, rectify, delete, restrict, object, or port certain personal data, and to lodge a complaint with a supervisory authority. Email support@stellarclaw.xyz to exercise rights; we may verify ownership before acting.

11. Cookies & storage

This pilot page uses minimal local mechanisms primarily for session/API authentication where applicable. Third-party analytics, if enabled elsewhere on our domains, will be disclosed separately.

12. Children

The Service is not directed to children under 16. Do not deploy bots aimed at children.

13. Changes

We may update this policy and revise the effective date. Material changes will be highlighted here.