Acceptable Use Policy

This policy applies to everything you do with lazyai: the prompts you send the builder, the apps you create, and the apps you deploy to the managed runtime. It exists to protect the people who use your apps, the other builders who share the platform, and the platform itself.

It applies to free and paid accounts alike, and to apps running under your account regardless of who built them. Most people never need to think about any of it — if you are building an ordinary product for real users, nothing here will get in your way.

Do not use lazyai to build, host, or distribute:

• Illegal content — anything that breaks the law, or that infringes the intellectual property, privacy, or other rights of others.
• Phishing and impersonation — fake login pages, counterfeit checkouts, or any site that pretends to be another person, brand, or organization.
• Malware and attack tools — malicious code, command-and-control infrastructure, or tools designed to compromise other systems.
• Cryptocurrency mining — in any form, on any plan.
• Spam — unsolicited bulk email or messaging, whether sent from your app or organized through it.
• Scraping abuse — aggressive crawling that ignores rate limits, robots directives, or the clearly expressed wishes of the sites being scraped.
• Resource abuse — anything designed to consume compute, bandwidth, storage, or AI-build tokens beyond fair use, or to degrade the service for other builders.

These categories overlap on purpose — abuse rarely fits one neat box. If you are wondering whether something you are planning crosses a line, email hello@lazyai.dev and ask before you build it. We answer.

Outbound SMTP on port 25 is blocked platform-wide — it exists mainly to send spam from hosting like ours. If your app sends email, use a transactional email provider instead; it takes minutes to set up and your mail actually gets delivered. This block applies to every plan and is not negotiable.

Testing the security of your own app, in your own account, is fine — we would rather you find a hole than someone else. Scanning, probing, or attacking lazyai itself, other people’s apps, or anything else on the internet from our runtime is not. If you find a vulnerability in the platform, report it to hello@lazyai.dev instead of exploiting it.

When you deploy an app, you are its operator. You are responsible for its content, its behavior, its compliance with the laws that apply to it, and the personal data it collects from its own users — including publishing your own privacy policy where the law requires one. lazyai hosts your app; it is not its publisher.

If your app handles accounts, payments, or personal data, take that seriously: review what the builder generated, test it before real users depend on it, and be honest with your users about what you collect.

We prefer the lightest tool that works. Depending on severity, we may throttle a project, suspend an app or account, or — for active, ongoing abuse such as a live phishing campaign or malware distribution — use a kill switch to stop the app immediately.

Where lawful, we notify you of enforcement action and give you a chance to respond. For active abuse we act first and notify after. Repeated or serious violations can end your account under the Terms of Service.

If you believe we got an enforcement decision wrong, reply to the notice or email hello@lazyai.dev — a human will look at it.

If you find an app hosted on lazyai that violates this policy, email hello@lazyai.dev with the link and a short description of the problem. We review every report, and we do not disclose who reported an app.