Skip to content
Legal

Terms of Service

These draft terms describe the basic rules for using the Appaloft website, console, and related early-access services.

Last updated: June 25, 2026

This is a public draft for the early Appaloft Cloud website. It is not final legal advice or formal commercial terms, and should be reviewed by counsel before commercial launch.

Early access scope

Appaloft currently provides early access to the website, console, CLI/AI skill entrypoints, Blueprint marketplace, deployment workflows, and related Cloud features. Some features may still be in testing, staged rollout, or manual review.

Accounts and access

You are responsible for your account, organizations, team member permissions, deployment credentials, server access keys, and third-party connections. Contact us quickly and rotate affected secrets if you suspect unauthorized access, incorrect authorization, or credential exposure.

Acceptable use

You must follow applicable law and may not abuse the service, bypass security controls, attack other systems, send spam traffic, mine cryptocurrency, host malware, or upload content that infringes third-party rights.

Deployments and resources

Appaloft helps deploy projects to infrastructure you control or are authorized to use. You remain responsible for app content, dependency licenses, runtime costs, and server security.

Credentials and secrets

Deploy tokens, database URLs, SSH keys, cloud provider tokens, and third-party secrets should be injected through runtime secrets or trusted environments, not committed to repositories, public issues, logs, or docs.

Billing

Appaloft Cloud is currently designed around monthly subscription plans. Free, paid plans, and add-ons are controlled by the Cloud billing page, Stripe-hosted billing, payment provider records, and formal terms.

Third-party services

Appaloft may connect to GitHub, payment, email, database, object storage, DNS/CDN, server, or other infrastructure providers. Those services may have their own availability, fees, limits, data handling rules, and terms.

Changes and availability

We work to keep the service reliable, but early services may be paused, degraded, or changed for maintenance, third-party services, network events, security needs, or product changes. Any formal SLA requires a separate agreement.

Suspension and termination

If an account creates security risk, abuse, unauthorized access, unpaid usage, unlawful content, or behavior that affects other users or system stability, we may restrict, suspend, or terminate access and provide an explanation or recovery path where reasonable.

Liability boundaries

Formal liability limits, indemnities, dispute terms, and governing law still require legal review. Do not treat this draft as a complete contract before it is finalized.