Terms of Service

Last updated: October 9, 2026 · Version 2026-10-09 · Yeeted (beta)

The service

Yeeted is a beta platform-as-a-service for deploying applications built and operated by AI agents. These terms are an agreement between you and Yeeted LLC ("we", "us") covering your use of the platform: the dashboard, the MCP server your AI agent connects to, the deploy and build pipeline, managed databases, logging, and the gateway that serves your applications (together, the "Service"). By creating an account or using the Service, you accept these terms. If you do not accept them, do not use the Service.

Your account and eligibility

• You must be at least 13 years old (or the minimum digital-consent age where you live) and able to form a binding contract.
• The beta is invite-gated: creating an account requires an invite code unless we have opened signup, and we may limit, pause, or close registration at any time.
• Provide accurate registration information, verify your email address, and keep both current.
• You are responsible for everything that happens under your account, including actions taken by AI agents you authorize and by anyone you share credentials with. Keep your password, OAuth credentials, and API keys secret; tell us promptly if they are compromised.
• One person or organization per account unless we agree otherwise. Do not share an account to circumvent plan limits, and do not create accounts in bulk.

Your content, and who owns it

You keep all ownership of the source code, data, and other content you deploy or store ("Your Content"). You grant us only the limited licence we need to operate the Service: to store, copy, build, transmit, cache, and display Your Content for the purpose of running it for you, keeping it available, moderating it as described below, and troubleshooting the Service. That licence ends when you delete the content or close your account, subject to the retention windows in our Privacy Policy.

You are responsible for having the rights to everything you upload, and for Your Content complying with the law. Whether our staff may look at Your Content is your choice, described under Data access below. Please do not push secrets, proprietary, or sensitive material to a beta platform.

Acceptable use

You may not use the Service to:

• break the law, or infringe anyone's intellectual property, privacy, or other rights;
• host child sexual abuse material or content that sexualizes minors. Zero tolerance: such content is removed and reported to the authorities, and the account is terminated permanently;
• host or distribute malware, ransomware, phishing pages, spoofed sites, credential harvesters, botnet controllers, or tools whose primary purpose is unauthorized access;
• host content that promotes terrorism or violent extremism;
• send unsolicited bulk email or messages (spam), or operate mailing infrastructure for it;
• run attacks against anyone - port scanning, denial-of-service, brute forcing, exploitation - whether the target is inside or outside Yeeted;
• attempt to escape your workload's isolation boundary, reach another customer's workloads, databases, or network, or access our internal services except through documented interfaces;
• use the Service as a media host. Yeeted runs applications, not video, audio, or bulk image libraries; video and audio uploads are refused at deploy time. Store media in an object store (such as Amazon S3) and have your application reference it by URL;
• mine cryptocurrency, or run distributed compute whose purpose is to consume resources;
• operate open proxies, VPN exit nodes, anonymizers, or traffic relays for third parties;
• circumvent plan limits, quotas, fair-use throttling, billing, or account suspensions;
• resell the Service as your own hosting product without a written agreement with us;
• store or process data whose loss or exposure would be dangerous, or that requires compliance we do not offer (see "Compliance", below).

Content moderation and enforcement

We moderate what the platform serves, and much of that moderation is automatic:

• Automated review. Automated systems, including AI systems, review deployed content, abuse reports, and platform signals. They may block content, suspend workloads, or terminate accounts without human review. Where the law requires it, you may ask us to have a human re-examine an automated decision (see Contact, below).
• Abuse reports. Anyone can report abuse. Reports are triaged and may be acted on automatically; content identified as clearly abusive may be blocked before any person looks at it.
• Blocking. A blocked project stops being served (visitors see a notice that the content is unavailable) and may be barred from redeploying.
• Termination and re-registration. If we terminate your account for abuse, you may not create a new account, and we may refuse registrations we reasonably believe are yours. Attempting to return after a termination is itself a violation of these terms.
• For active harm (abuse, attack traffic, security incidents, legal demands) we act immediately; otherwise, where practical, we will tell you before or shortly after acting.

Copyright and DMCA complaints

If you believe content hosted on the Service infringes your copyright, report it through our abuse report form using the Copyright infringement category. For us to act on a complaint it must include:

• identification of the copyrighted work you claim is infringed;
• the URL on the Service where the allegedly infringing material appears;
• your name and contact information (use the email field on the form);
• a statement that you have a good-faith belief the use is not authorized by the copyright owner, its agent, or the law, and that the information in your complaint is accurate.

We remove or block material when a complaint is valid, and we may terminate the accounts of repeat infringers. If your content was blocked on a copyright complaint you believe is mistaken, contact us (see Contact, below) and we will review the decision.

Send copyright complaints through the report form above or to [email protected].

Resource use and fair use

Plans include limits (projects, running instances, database size, and similar) shown on the pricing page and enforced by the platform. Bandwidth and builds are unmetered under a fair-use policy: sustained excessive traffic or build volume may be throttled, and we will not invoice you for overages you did not agree to. Development deployments are automatically shut down 15 minutes after each deploy or wake, whether or not they are receiving traffic; the next request to a stopped development deployment starts it again, and the Extend control in the dashboard resets the 15 minutes. Production deployments are not shut down on a timer. We may reclaim resources belonging to deleted or long-inactive accounts.

Availability, maintenance, and your data

As stated above, the Service carries no uptime commitment during beta. In addition:

• We may perform maintenance, migrations, restarts, and upgrades at any time. Workloads may be moved between machines, restarted, or briefly unavailable.
• Backups are not guaranteed. Platform snapshots, database snapshots, and version history are conveniences, not a backup service. You are responsible for your own backups and exports (the platform provides export tools - use them).
• Downgrades can delete data. If you move to a plan that does not include a resource you are using (for example a production database), that resource is scheduled for deletion after a grace period. We warn you before the purge; exporting your data during the grace period is your responsibility.
• We may change, add, or remove features, limits, and interfaces during beta, including in ways that are not backwards compatible.

Privacy and data protection

Our Privacy Policy describes what we collect and why. In short: we record the terms version you accepted and when; you can export your account data from the dashboard; and you can delete your account at any time, which triggers erasure of your personal data under GDPR Article 17, subject to the retention windows and legal-hold exceptions the Privacy Policy describes. Deleting your account also tears down your deployments and schedules your databases for deletion.

Data access

Running the Service for you is automated: building, running, storing and backing up what you deploy, and collecting logs and metrics so the product works for you. That is not staff access, and the choice below does not change it.

Whether a person at Yeeted may look at your code (source, build files, Dockerfiles, and build output that echoes them), data (database contents, schema, exports and snapshots), logs (application and build logs) or metrics (your apps' CPU, memory and request metrics) is your choice. It is off by default. You can change it at any time on Profile, under Data access, and a change takes effect immediately.

• Not at all (the default): our staff cannot see any of it.
• For support purposes only: we may look at what you allow only to diagnose and fix problems you report or that affect your service.
• For platform enhancements to better support my code: as for support, and we may also use what you allow to improve the Service for your stack, for example improving build pipelines to speed up your builds and deployments, or running test deployments of your app to verify reliability.

We may need this access to give you support help, and without it we may not be able to resolve a problem in your application. An administrator may override your choice to investigate abuse or to meet a legal obligation; every override is recorded with its reason. The Privacy Policy has the details.

Fees, billing, and refunds

• Paid plans are billed monthly in advance through Stripe, our payment processor. We never see or store your full card details.
• Prices are shown when you subscribe. We may change prices with notice, effective at your next billing period. Free and beta-discounted plans may be changed or ended at any time.
• If you cancel a paid plan mid-period, the plan change takes effect and unused time is credited or refunded through the dashboard's cancellation flow.
• Other refund requests are reviewed case by case; where we owe you one (for example a charge after your account was closed), we issue it through Stripe. Nothing here limits refund rights the law gives you.
• Failed payments may lead to suspension and, after a reasonable period, deletion of the account. You are responsible for any taxes other than taxes on our income.

Compliance

Yeeted is not offered as a HIPAA-, PCI-DSS-, FedRAMP-, or SOC 2-compliant environment, and we sign no Business Associate Agreement during beta. Do not store protected health information, full payment card data, government-classified information, or other regulated data that requires those frameworks. You are responsible for your own compliance obligations for the data you choose to process here.

Suspension and termination

You may stop using the Service and delete your account at any time from the dashboard; deletion removes your deployments and starts the retention clock described in the Privacy Policy. We may suspend or terminate your account for breach of these terms, non-payment, legal requirement, abuse or security risk, or if we discontinue the Service - and, as described under Content moderation, enforcement may be automated. Where we terminate without cause, we will make a reasonable effort to give you notice and a chance to export your data. Provisions that should survive termination (ownership, disclaimers, liability limits, indemnity) do.

Disclaimer of warranties

THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE", WITHOUT WARRANTIES OF ANY KIND, WHETHER EXPRESS, IMPLIED, OR STATUTORY, INCLUDING IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT. WE DO NOT WARRANT THAT THE SERVICE WILL BE UNINTERRUPTED, TIMELY, SECURE, ERROR-FREE, OR THAT DATA WILL NOT BE LOST. Some jurisdictions do not allow certain exclusions, so parts of this section may not apply to you.

Limitation of liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW, WE ARE NOT LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, NOR FOR LOST PROFITS, LOST REVENUE, LOST BUSINESS, OR LOST OR CORRUPTED DATA OR CODE, EVEN IF WE HAVE BEEN ADVISED OF THE POSSIBILITY. OUR TOTAL AGGREGATE LIABILITY ARISING OUT OF OR RELATING TO THE SERVICE IS LIMITED TO THE GREATER OF (A) THE FEES YOU PAID US IN THE THREE MONTHS BEFORE THE EVENT GIVING RISE TO THE CLAIM, OR (B) USD $50. For free and beta plans, this means our liability is limited to USD $50.

Indemnity

You will defend and indemnify us against third-party claims, damages, and costs (including reasonable legal fees) arising from Your Content, your use of the Service, or your breach of these terms - except to the extent caused by our own wrongdoing.

Changes to these terms

We may update these terms. When we do, we bump the version shown at the top of this page and record the version you accepted. Material changes will be announced by email or in the dashboard; continuing to use the Service after a change takes effect means you accept the updated terms. If you do not accept them, stop using the Service and delete your account.

Governing law

These terms are governed by the laws of the State of Ohio, excluding its conflict-of-laws rules. The state courts located in Summit County, Ohio, and the United States District Court for the Northern District of Ohio have exclusive jurisdiction over any dispute arising from these terms or the Service, and you and we consent to their personal jurisdiction. This does not limit either party's right to seek injunctive relief in any court where appropriate.

General

These terms are the entire agreement between us about the Service and supersede earlier discussions. If a provision is unenforceable, the rest stays in force. Our failure to enforce a provision is not a waiver of it. You may not assign this agreement without our consent; we may assign it in connection with a merger, acquisition, or sale of assets.

Contact

Questions about these terms, a legal or abuse report, or a request for human review of an automated moderation decision: [email protected]. See also our Privacy Policy.