Founder ownership is better specified than many AI-builder promises
DoAny repeatedly says the founder keeps the company, product, customers and brand. The Terms give this claim useful legal detail. Users retain ownership of their submitted content and business data, and—as between the user and DoAny—own the websites, software, copy, workflows and other output generated specifically for them, subject to third-party rights, open-source licenses and separate agreements.2
DoAny retains ownership of its underlying platform, models, systems, templates, prompts, workflows, documentation and tooling. That is a normal distinction between generated output and the machinery used to create it.
The Terms also say DoAny does not take company equity or a revenue share unless a separate signed agreement provides otherwise.2
This is materially better than a vague marketing statement that “everything is yours.” Buyers should still inspect dependencies embedded in the generated product: third-party services can have their own fees, rate limits, policies and availability, and the generated output remains subject to third-party and open-source rights.2
The homepage’s 4.9/5 is not an admissible external rating
Third-party directories are present, but they mostly paraphrase the feature set. DokeyAI lists the free start, $25 entry price, broad function coverage and lack of coding requirements as advantages while identifying limited homepage detail as a weakness.4 MagicBox similarly describes the product as an end-to-end autonomous company-building agent and recommends keeping the founder involved in strategic decisions.5 Neither provides a robust independent user sample.
Privacy: DoAny can sit inside both founder data and customer data
DoAny’s privacy surface is more consequential than that of a simple app builder because the service may host products and operate customer-facing workflows.
The Privacy Policy says DoAny can process account and billing data, business/project information, prompts, files, code, generated output, deployment settings, databases, logs, integration tokens, messages and analytics. It can also process “Hosted Site Data” collected through products a user operates, including customer or visitor names, emails, account information, form responses, uploads, posts, support conversations, consent choices, purchase records and invoices.6
For Hosted Site Data, DoAny says the customer using DoAny is generally the controller/business and DoAny acts as service provider or processor where applicable. The customer is responsible for lawful basis, privacy notices, rights handling and consent controls.6
DoAny uses its own and third-party AI systems. Prompts, files, business data, customer data and output may be processed by those systems to provide the service. The policy warns that third-party AI provider retention and model-improvement practices can vary according to provider, account type, configuration and agreement.6
The policy says Hosted Site Data is not used for unrelated advertising. Any independent product-development or model-training use of Hosted Site Data will be described in a feature notice, setting or separate agreement. Aggregated or de-identified information may be used to improve DoAny.6
A major limitation is explicit: DoAny-hosted products must not directly process HIPAA-regulated protected health information or PCI-DSS card data in hosted forms, files, databases or logs, except that a supported PCI-compliant payment processor may collect card data in processor-controlled checkout fields.6
For founders building customer-facing products, privacy configuration is not something the agent can simply “take care of.” DoAny’s policy repeatedly places responsibility for notices, consents and appropriate collection on the business operator.
Security: public language is sensible but high level
The Privacy Policy says DoAny uses technical, organizational and administrative safeguards, but the public material reviewed here does not provide a detailed security architecture or an independent certification claim.6
The Terms require users to review authentication, data collection, integrations and published product behavior themselves, and disclaim any warranty that generated output will be secure, compliant or error-free.2
For anything beyond a low-risk experiment, a buyer should independently test authentication and authorization, secrets management, database exposure, uploaded-file handling, input validation, dependency vulnerabilities, tenant isolation, backups, data deletion and connected-account permissions before launch.
Autonomous actions require a human governance layer
The company-builder concept only works if the system can act, not merely advise. DoAny’s Terms say its agents may schedule, publish, send, respond, create and update based on instructions, connected accounts and configuration.2
The Terms simultaneously make the operator responsible for reviewing important actions. This is the correct governance model for a young agentic platform: autonomy can reduce operational workload, but it does not transfer legal or commercial responsibility away from the founder.
That is especially important for outreach, refunds, pricing changes, customer promises and public claims. A founder should decide which classes of actions can execute automatically, which require approval, and which should never be delegated without human review.
Reliability and commercial outcomes are the largest unknown
DoAny’s strongest claims concern outcomes: a product live the same day, customers found automatically, sales closed while the founder sleeps and a business that keeps operating after launch.1
The company itself correctly tempers those claims in its Terms: no search ranking, audience, customer, sale, review, revenue, retention or company viability is guaranteed.2
That means a DoAny pilot should be treated as an experiment with measurable checkpoints rather than an assumption that a $25 agent replaces a $12,800/month team. The latter comparison appears on DoAny’s own site and is marketing arithmetic, not evidence of equivalent labor output.3