Platform Rules

These Platform Rules explain what is and isn't allowed for applications, sites, and content you build, host, or deploy on Builder's infrastructure. They keep Builder safe and trustworthy while giving you room to build. If we determine that a Customer Application breaks these rules, we may remove or block it, suspend access, or take other action as described in the Acceptable Use Policy and SaaS Services Agreement.

These rules are the plain-English version of Builder's Acceptable Use Policy. Where the AUP is the formal contractual document, these rules describe the same expectations in accessible language for anyone building, hosting, or deploying on Builder's infrastructure. In the event of any conflict between these Platform Rules and the Acceptable Use Policy, the Acceptable Use Policy governs.

1. No Attacks or Malicious Code

Don't use Builder to attack, deceive, or compromise people or systems. No malware, ransomware, spyware, or other malicious code. No phishing, fake login pages, or credential-harvesting sites. No attempts to hack, break into, or bypass the security of any system. No bots that spam or abuse resources. No cryptocurrency mining.

2. No Impersonation or Deception

Don't impersonate people, brands, or organizations to deceive others. Don't publish one-to-one copies of existing commercial or well-known sites using their names and logos — we treat these as malicious and will remove them. Don't publish fake news, fabricated media, or deceptive deepfakes.

3. Illegal and Regulated Content

No content that promotes or facilitates illegal activity. No illicit marketplaces for buying, selling, or trading illegal goods, services, stolen data, or stolen credentials. No criminal infrastructure — command-and-control servers, services built to evade law enforcement, or money-laundering services. No fake or fraudulent financial services (fake crypto-wallets, fake payment services, fake banking or investment offerings) — this is never allowed.

Regulated and age-restricted goods and services — trust, but verify. You may build apps that offer regulated or age-restricted goods or services (gambling, financial services, alcohol, tobacco, weapons, controlled substances) only if you hold all required licenses and approvals. We take you at your word, but we verify: we may ask for proof at any time, and we'll suspend or take down apps we believe are operating without proper licenses until you show us valid proof.

4. No Adult Content

Builder does not allow adult, sexual, or sexually suggestive content of any kind — including pornography, nudity, erotic content, and escort or adult-companion services. This rule applies even to content that involves only consenting adults and is legal in your jurisdiction. There is no '18+' or 'mature content' exception on Builder.

5. Protecting People

Zero tolerance for content that sexually exploits or endangers minors (CSAM). We will terminate the account and report to authorities. No content that harasses, bullies, threatens, or incites violence. No hate speech or content that promotes discrimination or prejudice. No intimate imagery. No doxxing (sharing others' private information without consent).

6. Copyright and IP

Respect copyright and intellectual property. Don't host content that infringes someone's copyright or trademark, including one-to-one copies of existing commercial sites. If you receive a DMCA takedown notice relating to your app, we'll follow the process at builder.io/legal/dmca.

7. Privacy and Data

Don't collect, store, or process your users' personal data without a lawful basis, a privacy notice, and (where required) their consent. Don't collect data you don't need. If you use Builder's hosting or database features to process personal data, you're the controller — you're responsible for complying with privacy law.

8. Reporting and Appeals

To report a violation, email abuse@builder.io with the affected URL or project ID and a description of the issue. If you believe an action against your app was taken in error, email abuse@builder.io with the subject 'Appeal' and include supporting context (such as evidence of licensing).

9. Enforcement

We aim to use the least disruptive effective measure — removing specific content before suspending an entire app, and suspending an app before closing an account. For urgent threats (malware, phishing, CSAM, legal emergencies) we act immediately. The full process is described in the Suspension, Takedown and Data-Handling Policy at builder.io/legal/takedown.