The intended contract, service, and data lifecycle.

The intended provider is Syntax Studios, Dennis Spannagel, c/o Postflex #10315, Emsdettener Str. 10, 48268 Greven, Germany. Direct contact details are in the legal notice.

The checkout must identify the selected plan, recurring total price, payment provider, renewal, minimum term, cancellation path, service scope, and mandatory consumer information before the order is submitted. The final terms must define exactly when an order is accepted and the contract begins; the current implementation alone is not a substitute for that wording.

The intended monthly prices are Basic EUR 10, Standard EUR 20, Pro EUR 35, and Premium EUR 70, plus any taxes that law requires. The first month costs EUR 5, EUR 15, EUR 27, or EUR 60 respectively. PayPal processes the recurring payment. The service records PayPal customer, plan, subscription, transaction, refund, reversal, and dispute identifiers and states, but does not receive card details or PayPal login credentials.

A monthly subscription renews until validly ended. A provider event is accepted only after verification and deduplication. A recorded refund approval does not itself move money; until the provider integration offers a reliable automated primitive, approved refunds are executed in PayPal and reconciled from verified events.

Each paid subscription covers one dedicated OpenClaw or Hermes runtime under the shared-standard resource profile. Included model credits are displayed as a remaining percentage. They do not promise a fixed number of messages, tokens, or requests. Normal customer screens do not expose provider keys.

The selected plan also controls advertised maintenance or backup features. Syntax Studios provisions, monitors, patches, and stops the runtime through its Manager and assigned node. No uptime percentage, response-time service level, geographic redundancy, or uninterrupted availability is promised in this draft. Maintenance, provider outages, security work, resource limits, and customer configuration can affect availability. Any commercial availability promise and final consumer wording must be legally approved and supportable before checkout.

Managed inference requests are routed to OpenRouter when that model route is used. OpenRouter receives prompt or conversation content and technical metadata needed to answer the request. OpenClaw customers can optionally configure Telegram; Telegram then processes bot messages and metadata. PayPal and the configured email provider process the data required for their functions.

AI and third-party outputs can be incomplete, incorrect, delayed, or unsuitable for a particular decision. Customers must review output before relying on it in legal, medical, financial, employment, safety, or other consequential contexts. This warning does not remove any non-waivable provider duty.

Customers control their prompts, files, installed skills, integrations, and customer-owned credentials and must have the rights and lawful basis needed to upload or process them. They must not submit another person's data without authority or expose secrets in prompts or support messages unnecessarily.

A configured Telegram bot token is encrypted in portal state, delivered to the customer runtime, and can remain in runtime backups as customer configuration. Authorized Syntax Studios staff can access operational or customer data when necessary to provide support, secure the service, investigate an incident, or comply with law. The privacy policy explains the current data map.

Pro automatic snapshots currently default to one every 24 hours with 14 automatic snapshots retained. Manual, pre-patch, pre-restore, and final-retention archives can also exist. Restores are validated and audited, but a backup is a recovery control rather than a permanent archive or a guarantee against every loss.

Node archives use restrictive file permissions and managed platform secrets are replaced in sanitized archives. Built-in archive encryption at rest, off-host replication, legal-hold handling, and independent expiry paging are not currently implemented. These limits must be reflected consistently in the final service promise.

For ordinary cancellation, renewal is intended to stop while the paid runtime remains active through the PayPal-confirmed paid-through time. The authenticated billing flow verifies cancellation with PayPal. The public cancellation form currently stores the declaration and attempts email delivery, but it is not connected to an operator decision queue or to PayPal cancellation; that provider execution path is a launch blocker.

At paid-through, the runtime is stopped, managed inference is disabled, and one validated final archive is created. Its expiry is exactly 30 days after paid-through. At expiry, the data becomes due for deletion and the system attempts the purge. Failures are recorded and retried, so actual completion can occur later. Billing, legal-request, audit, or other records can remain where a separately approved legal retention rule requires them.

Customers must not use the service for unlawful activity, attacks, unauthorized access, malware distribution, infrastructure abuse, cryptocurrency mining, plan-limit evasion, infringement, or interference with another customer or operator system. They must keep login and integration credentials confidential and promptly report suspected compromise.

The final terms must define proportionate warning, restriction, suspension, and extraordinary termination rights for credible security, abuse, payment, or legal risks, including when immediate action is necessary and how the customer can contact the operator. Protective action must not be broader or longer than justified.

Customers can report defects or support issues to kontakt@syntax-studios.org. Refund requests receive individual staff review and do not produce an automatic decision. The form records request identity, contract reference, message, delivery status, staff actor, decision, and timestamps; an exact legal-record deletion schedule is still open.

Nothing in these draft terms excludes statutory defect remedies, repayment duties, withdrawal rights, or other mandatory consumer protection. The refund page, cancellation function, and withdrawal function describe the implemented intake paths.

The final terms must preserve mandatory consumer, data-protection, defect, product-safety, withdrawal, and liability rights. Any limits for ordinary negligence, indirect loss, data loss, force majeure, third-party services, or customer conduct require qualified legal drafting and cannot cover liability that German law does not permit the provider to exclude.

Governing law, jurisdiction, consumer dispute resolution, language priority, changes to terms, severability, extraordinary termination, and the exact treatment of early service performance during a withdrawal period remain unresolved. No clause on this page should be treated as a waiver of mandatory rights.