- Rogue
- Terms & Conditions
Terms & Conditions
These terms describe the conditions for using rogueon.ai and the Rogue service. The Privacy Policy explains how personal data is handled.
Last updated October 7, 2026
What Rogue is
Rogue takes a description written in plain language and produces working software from it: code, files, and the assets around them. The service runs on top of AI models, some of them operated by third parties.
Who can use it
You need to be at least 18, meet any higher age of majority where you live, and be able to enter a contract. If you are using Rogue for a company, you are confirming you can accept these terms on its behalf.
Your account
You are responsible for what happens under your account and for keeping your credentials to yourself. Tell us if you think someone else has got in.
What you own
The code and files Rogue produces for you are yours. We claim no ownership over your output and no licence to resell it. You keep whatever you put in as well: your prompts, your files, your data.
We do need permission to run the service, which means processing your input to produce your output and storing project files. Personal data is handled as described in the Privacy Policy, including account security, usage records, providers and your rights. Accepting these terms is not blanket consent to unrelated processing.
What you may not do
- Build anything illegal, or anything designed to harm people.
- Break, overload, or work around the limits of the service, including reselling capacity as your own product.
- Upload material you have no right to use.
- Use Rogue to generate malware, spam, or content that impersonates someone.
What AI output is and is not
Generated software can be wrong. It can carry bugs, security holes, or licence obligations from the ecosystem it draws on, and two identical prompts can produce different results. Review what Rogue gives you before you put it in front of users or into production. You stay responsible for what you ship.
App databases
Hosting in Rogue's Neon account is temporary. The trial lasts 14 consecutive days from the start of the trial, or from the transition date provided for an existing database. Access then pauses. After 21 days, an untransferred database, including its user accounts and saved data, is permanently deleted. App usage, edits and transfer links do not extend these deadlines. Check the dates in Database.
Complete the transfer before deletion. Creating or opening a claim link is not enough: you must finish in Neon, including for a paused database. Your Neon account, its plan, costs and Neon's terms apply after transfer. Review quotas there and change the database password. Transfer does not replenish an exhausted quota or move the app's code.
The trial has usage limits. Creating databases requires a verified email and is subject to a default limit of three managed databases per account. New databases have 100 MB of logical storage and, per Neon billing cycle, 5 CU-hours of compute, 20 active hours and 1 GB of outbound traffic. Reaching a quota can pause access earlier. Creating accounts or projects to evade limits is prohibited; abuse can lead to suspension under these terms.
Keep copies of what you need. Exporting code does not include the database or its user accounts. Arrange separate backups or data exports before the deadlines. Rogue does not offer recovery after permanent project deletion. A trial is not a commitment to permanent hosting or an uninterrupted service.
You operate the app you publish. Test its behaviour, authentication and permissions before collecting real data. If you determine why and how people's data is used, you are responsible for a lawful basis, clear privacy notices, appropriate access controls and responding to their rights requests. Use sensitive data only when the necessary legal and security requirements are met. Do not store cardholder data, as defined by the Payment Card Industry Data Security Standard (PCI DSS), in this database.
Legal duties still apply. These responsibilities do not remove Rogue's own security, data protection or service obligations, or any rights that cannot be waived under applicable law. Personal data processing, providers and legally required retention remain subject to the Privacy Policy and applicable law.
Plans and payment
Rogue is currently in beta, with no checkout for paid subscriptions. The published plan amounts are references, not subscriptions available to purchase. Confirm access and future pricing with the team through the contact page. Any separately agreed paid arrangement is governed by its own payment, renewal and cancellation conditions; this beta notice does not change those agreements.
Availability
We have not published an uptime guarantee, and there is no SLA attached to the self-serve plans. The service is provided as it is. Studio plans are negotiated separately and can carry commitments these terms do not.
Ending things
You can stop using Rogue whenever you like. We can suspend or close an account that breaks these terms, and we will tell you why unless the law stops us. Your right to your own output survives the account closing.
Liability
To the extent the law allows, Rogue is not liable for indirect or consequential loss, including lost profit or lost data, and our total liability is capped at what you paid us in the twelve months before the claim. Nothing here removes rights you have under consumer law that cannot be waived, including under the Brazilian Consumer Protection Code or applicable data protection law.
Governing law
These terms are governed by the laws of Brazil, and disputes belong to the courts of Brazil, without prejudice to any forum consumer law reserves for you.
Changes
We can update these terms. Material changes get notice before they take effect, and the date at the top always says which version you are reading.
Contact
Questions about these terms go to caio@rogueon.ai.