BuildMyApp Terms & Conditions
Version 2.7 -- Effective October 8, 2026
1. Platform Overview
BuildMyApp is a software development service operated by Maia AI, LLC. You describe the software you need in a request. BuildMyApp's own team, the BuildMyApp Dev Team (see Section 11), reviews each request and either sends you a proposal or passes on it. If you accept a proposal, BuildMyApp builds the software under a monitored build with the warranty protections in these Terms. BuildMyApp also offers software it has built through listings. Builds may be delivered as a single deliverable or as a sequence of milestones, each with its own delivery, review, and payment cycle.
2. Posting Requests
By posting a request, you agree not to include confidential, proprietary, or other private information in it. Posting a request does not create a confidential relationship, and BuildMyApp owes you no obligation of confidentiality or compensation for its contents. BuildMyApp may already be developing, or may later develop, software similar to what a request describes, and it remains free to do so. This does not change your rights in software BuildMyApp builds for you under a proposal you accept, which Section 10 governs. BuildMyApp does not take responsibility for the consequences of information you choose to put in a request.
Pricing. When you post a request, you set the price you are willing to pay. BuildMyApp either proposes to build it at that price or passes; it does not negotiate. You may change the price while the request is open, unless a proposal is awaiting your decision or has been accepted. When you accept a proposal, you pay the price it shows.
3. Platform Fees
Custom builds. BuildMyApp builds the software, so the price of a custom build is paid to BuildMyApp. Where a build page, receipt or statement shows the price divided into a platform fee and a developer's share, both are BuildMyApp's.
Platform-commercialized software. For Platform-commercialized software (see Section 10), BuildMyApp alone commercializes it, and buyers receive rights to use it rather than rights to resell it. Where BuildMyApp commercializes such software, it shares what it receives: 30% to the original buyer and 70% to BuildMyApp, calculated on what BuildMyApp actually receives after any app store, payment processor, or other third-party fees. BuildMyApp collects and distributes the original buyer's share.
Hosting Service Fee (Run Fee): Buyers who use BuildMyApp's hosted delivery form pay a monthly Run Fee covering the cost of running the software on BuildMyApp's infrastructure. The Run Fee is a hosting service fee paid to BuildMyApp; it is not a license fee, and it is separate from the listing or build purchase price. The buyer's license to use the software is paid for via the listing or build purchase price. The Run Fee is separate from any subscription price. On a subscription plan your recurring charge covers both: the Run Fee for hosting, and the subscription price for the license. The listing shows you both amounts before you buy.
Post-warranty spin-up fees: Buyers who request a new delivery form after their 30-day warranty period (for example, downloading a desktop installer for the first time on day 60, or requesting a source repository transfer for the first time on day 45) pay a per-request spin-up fee to BuildMyApp. The fee is disclosed at the time of request. Software, installers, and repository invites already received during the warranty period remain available without additional charge.
4. Payment Flow
Payments are processed through Stripe. When you accept BuildMyApp's proposal, the funds you pay are held during the build period and the subsequent 30-day warranty period, and BuildMyApp retains them only after the warranty period concludes without a valid claim.
Milestone Builds: For builds delivered in milestones, you pay a deposit when you accept the proposal (credited toward the first milestone), and each milestone is then charged to your saved payment method when that milestone is accepted, rather than the full price being collected up front. When a non-final milestone is accepted, that milestone’s payment is released to BuildMyApp immediately. When the final milestone is accepted, its payment is held through the 30-day warranty period before release.
Where a buyer is refunded -- in full or in part -- BuildMyApp does not retain any part of the refunded portion.
See the Refund Policy for the full breakdown.
Deposits and balance payments for custom builds
For lump-sum custom builds, you pay the deposit stated in the proposal
when you accept it. You authorize BuildMyApp to charge the remaining balance to your
saved payment method automatically when you accept the delivered build, or
when the review window ends and the build is accepted automatically. If a
balance charge fails, we will retry it and you can pay it directly from
your build page. If a build ends before delivery, the deposit is refunded
to the buyer when BuildMyApp withdraws from the build (see "BuildMyApp
Withdrawal Before Delivery" below) or the build is terminated for cause;
other dispositions may apply per a mediation resolution's terms.
For milestone custom builds, the deposit is credited toward the first
milestone. Each milestone is then charged automatically to your saved
payment method when that milestone is accepted (or when its review window
ends and it is accepted automatically). You pay only for milestones you
accept. If a milestone charge fails, we retry it and you can pay it from
your build page; work on later milestones may continue.
5. Acceptance & Auto-Accept Policy
When BuildMyApp submits a delivery, the buyer has a review window to accept or reject it. If no action is taken within the review window, the delivery is automatically accepted.
| Price Range | Review Window |
|---|
| Under $1,000 | 3 days |
| $1,001 – $10,000 | 7 days |
| $10,001 – $50,000 | 10 days |
| Over $50,000 | 14 days |
Milestone Builds: For builds delivered in milestones, the acceptance process applies independently to each milestone. When BuildMyApp submits a milestone delivery, the buyer has a review window to accept or reject that specific milestone. The review window duration is determined by the milestone’s payment amount (not the total contract price), using the same price-range table above. If no action is taken within the review window, the milestone is automatically accepted.
A build delivered in milestones is considered fully accepted only when the final milestone has been accepted. Acceptance of individual milestones is binding -- once a milestone is accepted, it cannot be reversed through subsequent milestone rejections or build cancellation.
6. Warranty Terms
After acceptance, a 30-day warranty period begins. During this period, the buyer may file a warranty claim if the delivered software fails to meet the acceptance criteria specified in the original request.
Milestone Builds: For builds delivered in milestones, the 30-day warranty period begins only when the final milestone is accepted (i.e., when the build as a whole is complete). Intermediate milestone acceptances do not start the warranty clock. The warranty covers the entire delivered build, not individual milestones in isolation.
Covered: Features and functionality listed in acceptance criteria that stop working and are not fixed by BuildMyApp within 10 days of notification of a warranty claim submitted through BuildMyApp, provided there have been no changes to the code files that may have caused or contributed to the failure.
Warranty Process: (1) Buyer files a warranty claim identifying the specific acceptance criteria violated. (2) AI review determines whether buyer-side code changes may have caused or contributed to the issue. (3) If the issue is valid, BuildMyApp has 10 days to fix it. (4) If BuildMyApp does not fix the issue within 10 days, a full refund is issued to the Buyer.
Not covered: New feature requests, compatibility with environments not specified in the original request, performance expectations not defined in acceptance criteria, issues caused by the buyer's modifications to the delivered code (as determined by AI review).
AI Review: Acceptance criteria are reviewed by AI before posting to ensure they are objectively verifiable and reasonable within the scope of warranty coverage. Criteria may be modified to meet these standards. AI review also compares the code at delivery time versus current state to determine if buyer modifications contributed to a warranty claim.
Final-Delivery Scope: "Delivered Forms" are the channels through which you receive a build: a hosted instance, a downloaded installation, or the transfer of a private Git repository. Warranty covers each Delivered Form for 30 days from purchase (listings) or sign-off (commissioned builds). Warranty fixes for Delivered Forms you have already received propagate to all of them: a fix may arrive as a redeployed hosted instance, a new signed installer at your stable download URL, or a new commit on your private repository, whichever Delivered Forms you have. Delivered Forms you request after your 30-day warranty window has ended incur a spin-up fee per Delivered Form (currently $19). Note: additional deployments do not alter original warranty periods. The acceptance environment provisioned for commissioned builds is not under warranty after sign-off; if you opted not to keep hosted as one of your Delivered Forms, that environment is paused for 30 days and then permanently removed.
Dispute Resolution: Any disputes regarding warranty claims will be resolved through LLM Arbitration provided by Vilora.ai.
Vilora is affiliated with BuildMyApp. Vilora is operated by Maia AI, LLC, which also operates BuildMyApp. Because BuildMyApp is the builder in every custom build, it is a party to every warranty dispute and mediation that Vilora handles. Vilora is designed to be neutral and is not instructed to favour BuildMyApp: it applies the acceptance criteria as written and the evidence both sides provide.
7. Rejection Policy
Buyers may reject a delivery during the review window. Rejections open mediation automatically, facilitated by Vilora.ai, to help the parties resolve the issue. BuildMyApp may revise and resubmit the delivery. Rejection history is tracked on the buyer’s record.
Milestone Builds: When a buyer rejects a milestone delivery, no funds are moved. The rejection opens mediation automatically, and BuildMyApp may revise and resubmit the milestone. Previously accepted milestones and their released payments are not affected by a subsequent milestone rejection. If the build is cancelled after repeated rejections, only payments for unaccepted milestones are refunded to the buyer; payments already released for accepted milestones are kept by BuildMyApp.
Build Cancellation: If a delivery or milestone accumulates repeated rejections without resolution, either party may request cancellation. Upon cancellation, held funds for unaccepted work are refunded to the buyer. Funds already released for accepted milestones are not recoverable through cancellation.
Mediation Deadline: Mediation is time-bounded. If a resolution is not agreed within 10 days of mediation opening, or if either party ends mediation before that window closes, the build will be automatically cancelled. Held funds will be refunded to the buyer in full, funds already released for accepted work remain with BuildMyApp, and the unresolved mediation is recorded on the build.
Buyer Termination for Missed Deadline
If BuildMyApp has not delivered by the proposal’s estimated completion date plus a 20% grace
window, the buyer may terminate the build. Held funds are refunded to the buyer in full and the
request may be reopened.
See the Refund Policy for refund mechanics.
BuildMyApp Withdrawal Before Delivery
Before delivering, BuildMyApp may withdraw from a build for any reason. On withdrawal, all funds held for the build are refunded to the buyer in full, any deposit is returned, and the request may be reopened. Funds already released to BuildMyApp for accepted milestones are not affected.
8. Commit Monitoring
During active builds, BuildMyApp monitors the build’s repository for commit activity and tells you when no substantive work has been detected for an extended period. Your right to terminate a build that is not delivered on time is under "Buyer Termination for Missed Deadline" in Section 7.
9. Buyer Activity Record
BuildMyApp keeps computed records of buyer activity on the platform, such as acceptance and rejection history. They are calculated from actual platform activity, cannot be edited by users, and are shown on your public profile.
10. License Types and IP Rights
Every build delivered through BuildMyApp, and all software sold or licensed from a listing (including buy-out, one-time Non-Exclusive and subscription purchases), follows the IP framework set out below, regardless of the licensing preference selected at request time. The choice between Exclusive and Non-Exclusive controls only the rights granted in Foreground IP; the remaining categories apply identically to both license types.
In this Section, “the Developer” means BuildMyApp, which builds the software through the BuildMyApp Dev Team (see Section 11).
Foreground IP (Buyer-owned under Exclusive; licensed under Non-Exclusive). “Foreground IP” means the business logic, data models, user interfaces, branding, and buyer-specific integrations created by the Developer for the Buyer in connection with a request. Under an Exclusive license, no other buyer ever receives the Foreground IP; the Developer assigns the Foreground IP to the Buyer on acceptance. Under a Non-Exclusive license, the Buyer receives a worldwide right to USE the Foreground IP for the Buyer's own purposes, and nothing more: the Buyer does not receive the right to resell, sublicense, transfer, publish or otherwise distribute it, whatever the software's origin. The Developer retains ownership of the Foreground IP. Where the software is Platform-commercialized, as defined under "Platform-commercialized software" below, BuildMyApp alone commercializes it, subject to the revenue-sharing terms in Section 3.
What your Non-Exclusive license lets you do, and what it does not. This is the same whatever the software's origin. You may use the software for your own purposes, including in your business, and you may let your own employees and contractors use it on your behalf. You may not sell it, license or sublicense it to anyone else, transfer your license, publish it, list it on any marketplace or app store, or otherwise distribute it, whether for payment or free of charge. If you want rights beyond use, that is an Exclusive license, and it is priced differently.
How long a Non-Exclusive license lasts. There are two kinds, and the listing or proposal tells you which one you are buying before you pay.
Perpetual. If you paid a one-time price, whether for a commissioned build or for a listing bought on a one-time plan, your right to use the Foreground IP is perpetual. It does not expire and it does not depend on continuing to pay anything. If that software is hosted by BuildMyApp, the monthly Run Fee keeps it running for you; stopping the Run Fee stops the hosting, not your license. See Section 3.
For as long as you subscribe. If you bought on a subscription plan, a recurring monthly or yearly price set by BuildMyApp, your right to use the Foreground IP runs for the subscription term you have paid for and ends when that term ends. It renews automatically with each renewal payment. If you cancel, or if a renewal payment is not collected, your license runs to the end of the period you have already paid for and then ends. We do not prorate a cancellation, and we do not cut your license short inside a period you have paid for. A subscription plan is a use-license subscription, not a maintenance or support contract. If BuildMyApp withdraws the plan you subscribed to, you keep your license and may keep renewing on that plan until you choose to cancel, and BuildMyApp stops accepting new subscribers to that plan.
Price changes on a subscription plan. BuildMyApp may change the price of a subscription plan. A new price reaches you only at a renewal, never during a period you have already paid for. If the price goes up, we email you first, and the higher price applies only at a renewal at least 30 days after that email; until then you keep renewing at your current price. You can cancel before the higher price applies, and your license runs to the end of the period you have paid for. If the price goes down, the lower price applies from your next renewal.
If a payment is reversed. If you are refunded in full for a subscription period, or you charge that payment back, your license for that period ends. If a chargeback is later resolved in BuildMyApp's favour and the payment stands, your license for that period is restored. Other periods you have paid for are not affected, including periods after the one reversed. A partial refund does not shorten the period it relates to.
What it means when a subscription license ends. Your right to use that software ends with it. Your hosted environment stops running, and if you hold any other copy of the software, for example a desktop installer, you must stop using it and remove your copies. Your own data is yours and is not affected: for 30 days after the subscription ends we keep your data available so that you can export it, and we delete it after that. Resubscribing restores your license, and if you resubscribe inside that 30-day window it restores your data too.
Which version of these Terms applies to a purchase. When you buy a license, BuildMyApp records the version of these Terms in effect at that moment against that transaction. That recorded version governs, for the whole life of that purchase: the license granted, how long it lasts, who owns what, and how any resale revenue is shared. A perpetual right you already hold stays perpetual, and a later version of these Terms does not shorten, convert, or add conditions to it. Everything else in these Terms, including your use of the platform generally, dispute resolution, governing law and limitation of liability, is governed by the current version as provided in Section 14.
What BuildMyApp will not do. Once a subscription license has ended, BuildMyApp will not issue you a new copy of that software or a new delivery form for it, and will not accept a spin-up fee for one. Resubscribing is the way back.
Apps distributed through an app store. Some software reaches its users only through the Apple App Store, the Google Play Store, or a similar consumer app store, which requires a developer account with that store and acceptance of that store's own terms. Where software you receive through BuildMyApp is that kind of app, whether it was built for you or bought from a listing, the following applies in addition to everything above.
Under an Exclusive license, you publish it. Your rights in the Foreground IP include the right to publish, distribute, and update that app through an app store under your own developer account, and to keep doing so. You publish under your own account, your relationship with Apple, Google, or any other store is between you and them, and BuildMyApp is not a party to it, does not publish on your behalf, and is not responsible for app review outcomes, store policy changes, or a store's decision to reject or remove an app.
Under a Non-Exclusive license of Platform-commercialized software, BuildMyApp publishes it. Publication is commercialization, and for that software it belongs to BuildMyApp alone. BuildMyApp publishes under its own developer account and shares what it receives as set out in Section 3. BuildMyApp will publish the app so that you can install and use it. It may do so as a public store listing or through a private or unlisted channel the store offers, and which channel it uses is BuildMyApp's decision. BuildMyApp is not responsible for app review outcomes, store policy changes, or a store's decision to reject or remove an app; if a store rejects or removes it, BuildMyApp will make reasonable efforts to publish it again or to give you another way to install it.
The Buyer does not publish it under a Non-Exclusive license. A Non-Exclusive license is a right to use the software, not to distribute it, so publication to an app store is not something the Buyer may do.
If a subscription license ends. Your right to USE the app ends, so stop using it and remove your copies, as set out under "What it means when a subscription license ends" above. Nothing here asks you to withdraw an app from a store, because a Non-Exclusive buyer never published one.
Platform-commercialized software. "Platform-commercialized software" means software created through a BuildMyApp build that the buyer commissioned under a Non-Exclusive license, including later versions and derivatives of it. BuildMyApp's records of the build and its license decide whether software is Platform-commercialized. It does not include software acquired through BuildMyApp under an Exclusive license, whether by commissioning it or by a buy-out. Software BuildMyApp offers through a listing that is not Platform-commercialized is BuildMyApp's own, and BuildMyApp keeps what it receives for it.
Exclusive software is never Platform-commercialized. BuildMyApp's commercialization rights do not apply to software delivered under an Exclusive license, and nothing in them permits BuildMyApp to distribute Foreground IP that has been assigned to a Buyer under an Exclusive license.
Converting to a perpetual license. BuildMyApp may, but is not required to, offer subscribers the option to convert a subscription license into a perpetual one by paying a one-time price it sets at the time, with or without credit for subscription payments already made. No such option exists unless and until BuildMyApp offers it.
Background IP (Developer-retained, embedded license to Buyer). “Background IP” means generic scaffolding, utilities, framework adapters, build tooling, libraries, and similar non-buyer-specific materials that the Developer brings to, or develops independently of, a particular engagement. The Developer retains all right, title, and interest in Background IP. The Buyer receives a perpetual, royalty-free, non-exclusive, worldwide license to use, reproduce, modify, and distribute Background IP solely as embedded in the delivered software. The Developer may reuse Background IP without restriction in other engagements. Where the Buyer's Foreground IP license is a subscription license, this embedded Background IP license runs for the same term and ends with it. The Developer's ownership of Background IP is unaffected either way.
Residuals (Developer-retained). “Residuals” means general methods, techniques, design patterns, and know-how retained in the unaided memory of natural persons performing work on the engagement or in the working memory of AI tools used by the Developer in the ordinary course. The Developer may use Residuals freely in future engagements. This carve-out does not authorize disclosure of Confidential Information that the Buyer has identified in writing as confidential, or that a reasonable person would understand to be confidential under the circumstances.
Anonymized Learnings (Developer-retained). The Developer may retain build retrospectives, lessons learned, and similar reflective materials for the purpose of improving the Developer’s practice, provided that all Buyer-identifying details, Confidential Information, and Foreground IP have been removed.
Relationship to other sections. The Non-Exclusive revenue-sharing terms in Section 3 apply to Foreground IP only, and apply to subscription payments in the same way as to one-time purchase fees.
11. The BuildMyApp Dev Team
BuildMyApp builds custom software through the BuildMyApp Dev Team, made up of employees and contractors of Maia AI, LLC.
Moderation Discretion
BuildMyApp may, at its sole discretion, hide, redact, or remove content posted to any collaboration session, listing Q&A thread, or other user-facing surface on the platform if such content is determined to violate these Terms, infringe on third-party rights, or otherwise harm the platform or its community. Hidden messages remain in place with a moderated notice; their original content is suppressed for non-moderator viewers.
12. Limitation of Liability
Except for the warranty in Section 6, BuildMyApp provides the software it builds or offers, and the platform, "as is" and "as available", and disclaims all other warranties, express or implied, including merchantability, fitness for a particular purpose and non-infringement, to the maximum extent permitted by law.
To the maximum extent permitted by law, the total aggregate liability of BuildMyApp arising out of or related to these terms or the use of the platform shall not exceed the total fees paid by a Buyer to BuildMyApp for a specific transaction giving rise to the claim.
To the maximum extent permitted by applicable law, Maia AI, LLC, its affiliates, and their respective officers, directors, employees, and agents shall not be liable for any indirect, incidental, special, consequential, or punitive damages, or any loss of profits, revenue, data, or business opportunities, arising out of or related to the use of, or inability to use, the platform or services, even if advised of the possibility of such damages.
Some jurisdictions do not allow the exclusion or limitation of certain damages, so the above limitations may not apply to the extent prohibited by law.
13. Governing Law & Forum
These Terms & Conditions shall be governed by and construed in accordance with the laws of the State of Texas, without regard to its conflict of law provisions. Any legal action or proceeding arising out of or related to these terms or the use of the platform shall be brought exclusively in the state or federal courts located in Travis County, Austin, Texas, and you consent to the personal jurisdiction of such courts.
14. Agreement
By using BuildMyApp, you agree to these Terms and Conditions. Continued use of the platform after changes to these terms constitutes acceptance of the revised terms for your use of the platform.
This does not reach a license you have already bought. The purchase-specific rights identified in Section 10 under "Which version of these Terms applies to a purchase" -- the license granted, its duration, the ownership allocation, and the resale revenue split -- continue to be governed by the version recorded against that transaction, whatever version you later accept.