Answers
The questions that decide it — the ones a security review asks, and the ones you ask yourself before you describe years of know-how to a platform. Including the ones where the answer is a limit.
Who owns the code if an AI builds it?
You do — ownership of the output, written into the Terms §11. Every product built here is a real git repository, and it exports into your own GitHub or GitLab account whenever you ask (§12.1). The code was already yours; export only changes where it lives.
If I leave, do I take my product with me?
Yes, and test that early rather than when you are angry. Export pushes the product's current code into a repository under your own account (Terms §12.1), as a fresh single-commit history: the internal build log stays with us as the record we build and serve previews from. What you take is the source; hosting and the database are yours to stand up wherever you take it.
Do you train models on my work?
RunMyB does not. Terms §10: you own your content, and we do not train models on it — not the conversation in which you describe the product, not what is built from it, not the files you bring. Nor do we permit the AI providers that process it for the platform to do so on our behalf: the Data Processing Addendum §7 says so, and how every request we route through OpenRouter is told to avoid providers that would. Until 18 October 2026 the build roles were an exception; §7 records it too. If your product's own AI features run on your own provider key, that provider works under your agreement with it.
Could you build a competing product out of my idea?
No. Terms §10.1: we will not use what you describe to build a product that competes with yours. Read §11.5 in the same sitting, because it is what §10.1 does not do: your idea is not made exclusive, and someone who independently describes something similar may get something similar. If you bring clients here, we will not market to them or approach them with an offer that goes around you (§10.2).
What if I do not like what it builds?
You find out privately, before anyone else does. What comes back runs on a private preview only you and the people you send the link to can reach. Say what is wrong and it is changed and re-checked. Accepting a build and publishing it are two separate acts, and both are yours.
Who decides what gets published?
You do. Publishing a product, changing it or taking it down is always your explicit decision — nothing goes public because a build finished.
Who is answerable when the software gets something wrong?
The two halves have different owners. Whether the software works is ours to check: every build must serve, load and run without crashing; a build that stores data must prove its data survives a restart; a build with user accounts must pass an authentication floor before you see it. Whether it is right for your business is yours to judge — on the preview, before anything is published. A floor cannot know your domain.
Do I need to know anything technical?
No, and there is no document to write first. You describe what the product should do in plain language. You never configure a server, because you never get one. What is asked of you is judgement, not syntax: what gets built, what is right on the preview, what ships.
Can another business on this platform read my data?
Every hosted product gets its own isolated database and its own sandboxed runtime — not a shared table with a customer column in it. One thing is true by design: the platform's own admin overview reads across products, because somebody has to be able to see that the platform itself is healthy, and that access is limited to named administrators.
Inside my own product, can one customer see another's data?
Applications built here with user accounts get real sign-in — email and password, passkeys, two-factor codes — built in rather than bolted on. Every such build must pass an authentication floor, and one of its checks is that one user cannot reach another's records. A build that cannot pass it does not reach you.
If someone asks me to delete their data, can I prove it is gone?
When you erase a product, the platform tells you what it actually reached. A hosted database that survives the erasure is never counted as deleted: it stays a recorded obligation naming the exact resource until a person confirms, with the hosting provider's own answer, that it is gone.
What does RunMyB do with my Google Drive, Gmail and Calendar?
Nothing unless you connect them, one at a time, on the Connections card in the console. Drive: RunMyB imports only the files you pick in Google's file chooser into your venture's library. Gmail: RunMyB sends an email only after you have seen and confirmed the exact message; it never reads your mail. Calendar: RunMyB reads the events of your own primary calendar, read-only, so its assistant can tell you about changes and answer your questions. When you ask RunMyB's assistant, a build or the brand import to work with this data — and when the platform's automated safety checks and its activity narrator (which you can switch off for a venture) see it — it goes to the AI providers named or described in our Privacy Policy, under terms, routing instructions or account settings that exclude training on it, and it is never used for advertising. You can disconnect any of them on the Connections card at any time; disconnecting deletes that service's stored token at once, and RunMyB asks Google to end its access when you disconnect the last Google service connected with that Google account — you can also end it yourself in your Google account at any time. How long imported files and other records are kept, and how to have them deleted, is set out in our Privacy Policy.
What happens to my product if RunMyB disappears?
No company at this stage can honestly promise you a decade, and we will not answer that with a growth number. What we can do is make sure your product does not live only here: the code exports to a repository under your own account whenever you ask.
What do you not have?
We hold no third-party security audit: SOC 2 and ISO 27001 both require an external auditor, and we do not have one. There is no published uptime or support commitment. There is no published price — what a try costs is on What a try costs. RunMyB is opening in stages, and access is by invitation for now.
Where can I read the actual clauses?
In the Terms of Service, published in full, in force and versioned, alongside the Privacy Policy and the content rules. If your question is not answered here, ask it: hello@runmyb.com.
This form needs JavaScript, which your browser has switched off. Write to hello@runmyb.com with the word waitlist and we'll add you by hand.
You're on the list. What we recorded: your address, the consent wording you agreed to, the time, and a one-word note that you came from this page. Nothing else is in that record — no name, no IP address, no tracking.
You won't get a confirmation email. If you want it confirmed, write to hello@runmyb.com and we'll check. If we write, it will be about getting you in — the first thing we ask is what you would build and who it is for, because we let people in one at a time and decide by hand. We can't tell you when, and we won't send anything else in the meantime.
Changed your mind? Write to privacy@runmyb.com and we'll take you off the list.
That didn't go through and it's safe to try again — a repeat submission can't create a duplicate. If it keeps failing, email hello@runmyb.com.
RunMyB is opening in stages, and access is by invitation for now.