Clear expectations make better products.
These baseline terms describe use of BuildMakr. The commercial operator should review them with counsel before accepting paid customers.
Effective July 20, 2026Using the service
You may use the platform to plan, configure, test, and operate digital products for lawful purposes. You are responsible for your account, the content and data you submit, your end-user notices and consents, and compliance with app-store, payment, privacy, employment, and industry rules that apply to your product.
Trials, free access, and paid plans
New accounts currently begin with seven days of Starter access and do not require a payment card. After the trial, the account returns to Free limits unless paid access is explicitly approved and activated. Paid configuration is retained but locked while the account is on Free. New subscription checkout remains closed unless the deployment operator deliberately enables the commercial checkout flag after validating paid-plan delivery; saving plan interest creates no charge. Existing Stripe customers retain billing-portal access.
Third-party accounts and charges
Apple and Google developer accounts, Expo/EAS usage, domains, payment processing, email delivery, hosting providers, and other connected services may require separate credentials, agreements, and fees. Unless a plan expressly says otherwise, those third-party charges are not included in the BuildMakr subscription price.
Your content and platform rights
You retain rights in the original business information, brand assets, content, and data you submit. You grant the operator the limited permission needed to host, process, back up, and transmit that material to provide the service. BuildMakr's platform code, design system, and templates remain the property of their respective owner.
Exports and third-party services
Current self-serve export is reusable project/template configuration JSON. Runtime database export and full application source export are not available. Mobile artifacts exist only after an operator-configured Expo/EAS provider accepts and completes a job. Custom domains require verification plus deployment-operator routing and TLS activation. Payments, email, OAuth, stores, domains, and integrations also depend on external credentials, terms, fees, review processes, and availability.
Acceptable use
Do not use the service to violate law or another person's rights; distribute malware; evade security controls; access accounts or data without permission; facilitate fraud, exploitation, or harassment; or overload infrastructure. The operator may restrict abusive activity to protect users and the service.
Availability and launch responsibility
Previews, generated configurations, readiness checks, plan ceilings, domain records, and product maps are aids—not artifact, deployment, legal, financial, security, accessibility, analytics, or app-store approval guarantees. Built-in authentication is for BuildMakr staff/workspace members rather than end customers. You are responsible for customer identity design, final testing, professional review where appropriate, backups, production credentials, and release approval.
Commercial completion
Refunds, service levels, liability limits, dispute terms, governing law, support commitments, and a legal contact must be completed by the commercial operator before paid public launch. Until then, this deployment should be treated as an evaluation environment.