Terms & Conditions
These terms govern your use of the bookuvai platform. By creating an account or placing an order, you agree to be bound by these terms.
Last updated: April 2026
Table of Contents
1. Definitions
2. Platform Laws
3. Order Lifecycle
4. Pricing & Hours
5. Payment Terms
6. Scope Freeze & Change Requests
7. Governed Communication
8. Preview System
9. Delivery & IP Transfer
10. AI Agent Rules
11. Limitation of Liability
12. Governing Law
13. Amendments
14. Contact
1. Definitions
1.1
"Platform" means the bookuvai software development platform, accessible at bookuvai.com and related domains, including all services, APIs, tools, and AI agents operated therein.
1.2
"Customer" or "You" means any individual or entity that creates an account, places an order, or otherwise uses the Platform.
1.3
"Order" means a software development project commissioned by the Customer through the Platform, governed by the order state machine.
1.4
"AI Agents" means the specialized automated software agents operated by the Platform, including but not limited to the AI PM Orchestrator, Code Agent, Test Generator, Security Scanner, and Acceptance Validator.
1.5
"Scope" means the frozen, cryptographically hashed (SHA-256) requirements document for an Order, representing the definitive specification of work to be performed.
1.6
"Milestone" means a discrete, testable, and independently deliverable unit of work within an Order.
1.7
"Preview" means a sandboxed, ephemeral deployment of work-in-progress for Customer review purposes only. A Preview is not a Delivery.
1.8
"Delivery" means the final transfer of source code, documentation, assets, and intellectual property rights to the Customer upon full payment.
1.9
"Hours Ledger" means the immutable, append-only, SHA-256 chain-verified record of hours committed, consumed, refunded, or credited for each Order.
1.10
"Platform Laws" means the non-negotiable rules enforced in code as described in Section 2 of these Terms, which cannot be overridden by any party including administrators.
2. Platform Laws
The following laws are enforced programmatically by the Platform and cannot be overridden, bypassed, or waived by any party, including Platform administrators.
L1
No Requirement, No Execution. AI agents cannot begin work without a validated, frozen scope document. No code is generated, no resources are consumed, and no hours are deducted until scope is cryptographically frozen.
L2
No Scope Freeze, No Execution. The state machine blocks execution until the scope is frozen with a SHA-256 hash. This ensures the Customer and the Platform agree on exactly what will be built.
L3
No Validation, No Milestone Completion. Every milestone requires automated test passage before it can be marked complete. AI agents cannot declare their own work as "complete."
L4
No Payment, No IP Access. Delivery artifacts, source code, and intellectual property remain locked behind a payment gate. Previews are sandboxed and do not constitute delivery.
L5
No Human Override of System Laws. Even Platform administrators cannot bypass state machine constraints. These laws are enforced in code, not policy.
L6
Preview Does Not Equal Delivery. Previews are sandboxed, time-limited (24 hours), ephemeral environments with no download capability, no source code access, and no filesystem access.
L7
Everything Is Logged. Every action, state transition, communication, payment, and agent operation is recorded in an immutable audit trail with 7-year retention.
L8
Failed Milestone, Full Refund. If the Platform fails to deliver a milestone that meets the frozen scope, the Customer receives a 100% refund for that milestone. See our Refund Policy for details.
3. Order Lifecycle
3.1
All Orders progress through the following state machine: DRAFT → REQUIREMENTS FINALIZED → SCOPE FROZEN → EXECUTING → IN VALIDATION → PREVIEW READY → AWAITING PAYMENT → DELIVERED → CLOSED. Orders may also be DECLINED at the admin review stage.
3.2
Forward-only transitions. No state may be skipped, and no backward transitions are permitted. An Order in EXECUTING state cannot return to DRAFT.
3.3
Each state transition requires specific preconditions to be met. For example, SCOPE FROZEN requires all requirements to be validated and the scope hash to be generated.
3.4
All state transitions are logged in the immutable audit trail with timestamps, the triggering actor, and the preconditions satisfied.
3.5
The Customer acknowledges that the state machine governs the entire order lifecycle and that no party may circumvent the defined sequence of states.
4. Pricing & Hours
4.1
The Platform offers three pricing plans: (a) AI PM — fully automated AI project management; (b) Live PM — live human project manager with AI agents; (c) Live PM + Developer — live human project manager, human developer, and AI agents. Current hourly rates for each plan are displayed on the Platform's pricing page and may be updated from time to time.
4.2
The minimum commitment per Order is 50 hours. Pricing is displayed in the currency configured by the Platform. For customers paying via alternative payment gateways, the equivalent local currency amount may be charged at real-time exchange rates.
4.3
All hour deductions are recorded in the immutable Hours Ledger, an append-only log secured with SHA-256 checksum chaining. Each entry records the action, the agent responsible, and the hours consumed.
4.4
AI or system failures do NOT consume Customer hours. Hours consumed due to AI agent errors, retries, or system malfunctions are automatically credited back to the Customer's Hours Ledger with a SYSTEM_CREDIT tag.
4.5
The Hours Ledger is available for export in CSV and PDF formats at any time through the Customer dashboard.
4.6
Volume discounts may apply for higher hour commitments. Applicable discounts are displayed at the time of order creation and reflected in the quotation.
5. Payment Terms
5.1
Payments are processed through Razorpay (for customers in India) and Paddle (for international customers). Both are PCI-DSS compliant payment gateways. Paddle acts as Merchant of Record for international transactions. The Platform does not store credit card numbers, CVVs, or other sensitive payment credentials.
5.2
Supported payment methods include credit cards (Visa, Mastercard, Amex, RuPay), debit cards, UPI, net banking, and digital wallets via Razorpay (India). International customers can pay via credit/debit cards, PayPal, Apple Pay, Google Pay, and wire transfer via Paddle. Availability varies by region.
5.3
Payment authorization (hold) is placed at order creation. The payment link expires after 30 minutes. After scope freeze and quotation approval, payment is captured.
5.4
Payments follow the economic finality lifecycle: PENDING → AUTHORIZED → CAPTURED → SETTLEMENT PENDING → SETTLED → FINAL. Chargebacks may be raised during the eligible dispute window, which varies by payment method.
5.5
Chargeback windows by payment method: Razorpay (India): credit cards — 120 days; debit cards — 60 days; UPI — 90 days; net banking — 60 days; wallets — 30 days; bank transfer — 3 days. Paddle (International): credit/debit cards — 120 days; PayPal — 180 days; Apple Pay/Google Pay — 120 days; wire transfer — 3 days. After the dispute window closes, the payment reaches FINAL state and no further claims are possible.
5.6
For high-value transactions, settlement holds may apply: Razorpay — 14-day hold for transactions above INR 1,00,000 (7-day standard); Paddle — settlement follows Paddle's Merchant of Record schedule (typically 1–7 business days).
5.7
Invoices are generated automatically and are accessible from the Customer dashboard. All applicable taxes (GST, VAT, etc.) are calculated and disclosed at checkout.
6. Scope Freeze & Change Requests
6.1
Once the Customer approves the requirements, the scope is frozen with a cryptographic SHA-256 hash. This hash serves as the definitive, tamper-evident record of what the Platform has agreed to build.
6.2
No modifications to the frozen scope are permitted without a formal Change Request. The Customer cannot add, remove, or alter requirements through the governed chat interface after scope freeze.
6.3
Change Requests require: (a) a detailed description of the requested change; (b) an AI-generated impact analysis showing the effect on hours, timeline, and cost; and (c) explicit Customer approval of the revised scope and cost.
6.4
Approved Change Requests generate a new scope version with a new SHA-256 hash. The original frozen scope is preserved in the audit trail for traceability.
6.5
The Platform reserves the right to decline a Change Request if it fundamentally conflicts with the architectural decisions made during scope freeze.
7. Governed Communication
7.1
All communication between the Customer and the Platform occurs through a governed chat interface, not a free-form messaging system. Input types are restricted based on the current order state.
7.2
Input types by order state: (a) Draft — short text (up to 300 characters), file uploads, and button clicks; (b) Requirements Gathering — short text, file uploads, buttons, and dropdown selections; (c) Scope Frozen — buttons and dropdowns only; (d) Execution — status view only; (e) Validation — approve or reject buttons only; (f) Payment Pending — payment action only; (g) Delivered — rating and feedback text.
7.3
AI PM messages are template-based and deterministic. The same order state produces the same message type, ensuring consistency and auditability.
7.4
All messages are logged with timestamp, order state, and template identifier in the immutable audit trail.
8. Preview System
8.1
Previews are deployed in isolated, sandboxed environments. Each preview is a temporary, self-contained deployment intended solely for Customer review.
8.2
Previews expire automatically after 24 hours. Sessions are limited to 120 minutes with a maximum of 3 concurrent users.
8.3
Previews provide NO download capability, NO source code access, and NO filesystem access. The Customer cannot extract, copy, or reverse-engineer any artifacts from a preview environment.
8.4
A Preview is not a Delivery. Accessing a preview does not constitute delivery of the work product, does not transfer any intellectual property rights, and does not satisfy payment obligations.
8.5
The Customer may approve or reject a preview. Rejection triggers a feedback loop for adjustments within the frozen scope. Approval advances the order to the payment stage.
8.6
Mobile application previews are streamed via WebRTC from server-side emulators. No APK, IPA, or installable binary is provided during the preview phase.
9. Delivery & IP Transfer
9.1
Delivery is available ONLY after full payment is confirmed and the payment has reached at minimum the CAPTURED economic finality state. No exceptions.
9.2
Delivery methods include: (a) GitHub repository transfer; (b) ZIP download (limited to 5 downloads within a 48-hour window); (c) Docker registry push; (d) VPS handover for deployment configurations.
9.3
The delivery package includes source code, database schemas and migrations, documentation, technical specifications, build configurations, CI/CD pipeline definitions, deployment scripts, and test suites.
9.4
Upon delivery, the Customer receives a perpetual, irrevocable, worldwide license to use, modify, and distribute the delivered output. Full intellectual property rights transfer to the Customer.
9.5
The Platform retains ownership of its proprietary tools, frameworks, methodologies, and AI systems. The license grant covers only the delivered output specific to the Customer's order.
9.6
All deliverables are provided AS-IS following acceptance validation. The Platform warrants that the delivered work is original and does not knowingly infringe third-party intellectual property.
9.7
Delivery requires Customer acknowledgment via digital signature. The acknowledgment document is cryptographically hashed (SHA-256) and stored immutably.
10. AI Agent Rules
10.1
AI agents never guess and never assume. All agent actions are based on the frozen scope document and validated requirements.
10.2
AI agents cannot bypass the scope hash, unlock delivery without payment, or overwrite validated artifacts.
10.3
AI agents cannot declare their own work as "complete." All work must pass automated validation before milestone completion.
10.4
All agent communication follows a hub-and-spoke model coordinated by the AI PM Orchestrator. Agents do not communicate directly with the Customer.
10.5
Retry policies for agent failures: test failures — up to 3 retries with exponential backoff; build failures — up to 2 retries with linear backoff; dependency errors — 1 retry. If all retries are exhausted, hours are credited back and the issue is escalated.
10.6
The Customer acknowledges that AI agents are automated systems and that all AI-generated output is subject to automated validation before being presented to the Customer.
11. Limitation of Liability
11.1
To the maximum extent permitted by applicable law, the Platform's total liability to the Customer for any claims arising out of or relating to these Terms or the use of the Platform shall not exceed the total amount paid by the Customer for the specific Order giving rise to the claim.
11.2
The Platform shall not be liable for any indirect, incidental, special, consequential, or punitive damages, including but not limited to loss of profits, data, business opportunities, or goodwill.
11.3
The Platform does not warrant uninterrupted or error-free operation. Scheduled maintenance windows and force majeure events are excluded from liability.
11.4
No warranty is provided for fitness of delivered software beyond the specifications defined in the frozen scope document.
12. Governing Law & Jurisdiction
12.1
These Terms are governed by and construed in accordance with the laws of India, including the Information Technology Act 2000, the Consumer Protection Act 2019, and the Digital Personal Data Protection Act 2023.
12.2
Any disputes arising under these Terms shall be subject to the exclusive jurisdiction of the courts in Bengaluru, Karnataka, India.
12.3
The Platform supports multi-jurisdiction operations. Where the Customer is located in the European Union, United Kingdom, United States, or Singapore, additional jurisdiction-specific provisions may apply as described in the Privacy Policy.
12.4
If any provision of these Terms is found to be invalid or unenforceable, the remaining provisions shall continue in full force and effect.
13. Amendments
13.1
The Platform reserves the right to update these Terms at any time. Material changes will be communicated to registered Customers via email at least 30 days before they take effect.
13.2
Continued use of the Platform after the effective date of any amendment constitutes acceptance of the revised Terms.
13.3
If the Customer does not agree to the revised Terms, the Customer may close their account before the effective date. Active Orders will continue to be governed by the Terms in effect at the time the Order was placed.
14. Contact
14.1
For questions regarding these Terms, contact us at:
General inquiries: support@bookuvai.com
Legal matters: legal@bookuvai.com
Billing & payments: billing@bookuvai.com
10x
Faster Than Agencies
$2
Starting Rate / hr
100%
Money-Back Guarantee
Free
First Quotation
Your App Could Be Live in Days, Not Just Weeks
Describe your idea in plain English. Get a free AI estimate in 10 minutes. No credit card, no commitment.
AI agents available now — average response in under 2 minutes