Acceptable Use Policy

This Acceptable Use Policy ("AUP") sets out what you may and may not do with CrescoDB — the CLI, the hosted platform, and CrescoDB Cloud, which deploys and manages applications on servers and third-party providers you connect. It is part of, and incorporated into, our Terms of Service.

1. Your responsibility

You are responsible for everything you do with CrescoDB and for all code, data, and workloads you deploy through it. When you deploy to your own server or a connected provider, that infrastructure — and the acceptable-use rules of that provider — are also your responsibility. CrescoDB is an orchestration tool; you remain the operator of your apps.

2. Prohibited uses

You may not use CrescoDB, and may not deploy or operate anything through it, to:

• Break the law, or infringe anyone's intellectual-property, privacy, or other rights.
• Build, host, or distribute malware, ransomware, spyware, or other malicious code; or run phishing, credential-harvesting, or fraud operations.
• Attack or interfere with any system or network — including denial-of-service attacks, port scanning, brute-forcing, or unauthorized access — whether ours, a provider's, or a third party's.
• Send spam or unsolicited bulk messages, or operate in a way that gets your infrastructure or ours blocklisted.
• Store or transmit content that is unlawful, that sexually exploits minors, or that incites violence against people.
• Circumvent usage limits, plan entitlements, authentication, or billing; or share credentials to evade them.
• Abuse our platform's resources — for example, using automated requests to degrade the service, or using the AI features to generate abusive, deceptive, or infringing content at scale.
• Misrepresent your identity, or connect a server, repository, or provider account you are not authorized to use.
• Resell or expose CrescoDB's hosted platform as your own service without our written permission.

3. Security & testing

Do not probe, scan, or test the security of CrescoDB's platform except as permitted by our Security policy. Do not attempt to access data or accounts that are not yours. Legitimate security research is welcome — please follow the responsible-disclosure process on that page.

4. Third-party providers

Deployments you create run under your accounts with providers like your VPS host and GitHub. You must comply with each provider's own terms and acceptable-use rules. We are not responsible for actions those providers take on your account, and we may be required to act on their reports of abuse.

5. Free crescoafrica.com addresses

Every app deployed with CrescoDB can be given a free address such as yourapp.crescoafrica.com. The address points at your own server, and what it serves is yours, under everything in this policy. In addition:

• Do not choose a name that pretends to be a bank, payment service, government body, or another company or person, or that is meant to mislead people about who runs the site.
• Some names are reserved and cannot be chosen. One app holds one name, and names cannot be sold or transferred.
• We can suspend an address at any time, without notice, when it is reported for phishing, fraud, malware, or anything else this policy prohibits. A suspended name stays unavailable.
• When you change or give up a name, or delete the app, the name is held for 30 days before anyone else can take it.

Your own custom domain is always available on every plan, and is not affected by any of this.

6. Enforcement

If we reasonably believe you have violated this AUP, we may — with or without notice, depending on severity — limit, suspend, or terminate access to affected features or your account, remove offending content from our platform, and, where required, cooperate with providers or law enforcement. For urgent threats (active abuse, security risk, or legal exposure) we may act immediately. Whenever practical, we'll tell you what happened and how to resolve it.

7. Reporting abuse

To report a site on a crescoafrica.com address, write to [email protected] with the full address and what you saw. To report any other violation of this policy, contact [email protected]. Security vulnerabilities should go to [email protected] — see our Security page.

8. Changes

We may update this policy as the product and its risks evolve. We'll revise the "Last updated" date above and, for material changes, give notice through the product or by email.