Back to Terms Download PDF
Terms & Conditions
v1.0.0 05 May 2026

Mobile Android Development

This document governs engagements for Codemodo's Mobile Android Development service only. Mobile Android Development covers native Android (Kotlin or Java) implementation paired with a backend (Node.js NestJS), source code, deployed backend, complete documentation, Google Play Store submission, and up to 6 months of free bug-fix maintenance after launch. Pricing is proposal-based and set after the discovery call. It does not cover iOS development, web dashboard, hosting and server costs, app store developer account fees, content creation, or data migration from legacy systems. For any engagement beyond this scope, a separate proposal and agreement apply.

Service-Specific Terms

Payment

Milestone-based across phases defined in the signed proposal. Payment schedule, milestone count, and per-milestone percentage are fixed at contract signing.

  • Payment is due within 7 business days of each milestone invoice.
  • All work is placed on hold if a milestone payment is overdue by 7 business days from the invoice date.
  • If payment remains outstanding 7 business days beyond the payment due date, the preview link, staging environment, and source code repository access are suspended until the balance is cleared.
  • After 30 business days past the due date, the engagement may be terminated under the Termination clause.

Late Payment

If a milestone payment is overdue by 7 business days from the invoice date, active development pauses. If payment remains outstanding 7 business days beyond the payment due date, the preview link, staging environment, and shared repository access are suspended until the balance is cleared. Work resumes on the next business day after settled payment is received. Termination terms in the General Terms apply if payment remains outstanding for 30 or more business days past the due date.

Deliverables

  • Source code with full ownership transfer after final payment
  • Native Android application (Kotlin preferred, Java on request)
  • Paired backend (NestJS) with API endpoints
  • API design, integration, and documentation
  • Database design and schema (PostgreSQL or MongoDB)
  • Third-party integrations as scoped (payments, push notifications, OAuth, analytics)
  • Material Design 3 component implementation
  • Internal User Acceptance Testing (UAT) before delivery
  • Google Play Store submission and approval handling

Documentation (all included)

  • User Guide: end user documentation
  • API Documentation: Swagger or equivalent, all endpoints
  • Architecture Document: system architecture diagram and decisions (mobile + backend)
  • ERD: Entity Relationship Diagram for the database
  • Build & Release Guide: Google Play submission, signing, release procedure
  • Backend Deployment Guide: production deployment procedure

Training

Training is included in every engagement. Delivered as either a live session or a recorded usage video, at the client's preference. Training scope covers end user usage and internal admin functions of the delivered application. Additional training sessions beyond the included scope are billed separately as Technical Advisory at the prevailing hourly rate.

Free Maintenance

Up to 6 months of free maintenance is included after production launch. Exact duration is confirmed per project in the service agreement and is based on project scale.

ItemCoverage
Bug fixesIncluded
Feature additionsOut of scope (separate engagement)
UI changesOut of scope (separate engagement)
New integrationsOut of scope (separate engagement)
Support availability5 working days per week
Bug acknowledgmentWithin 1 business day
Bug resolution (non-critical)Within 5 business days

User Acceptance Testing (UAT)

UAT begins when the preview link is shared with the client at the development completion milestone. Client UAT window is 10 business days from preview link share. If no acceptance response, change request, or rejection is received within this window, the deliverable is considered accepted by default.

Revisions

Revisions and scope changes during development are handled via Change Order. All scope additions, design changes, or feature modifications beyond the agreed Statement of Work are treated as out-of-scope and require a Change Order with separate proposal and pricing.

Source Material Responsibility

Mandatory client inputs before kickoff:

  • Finalized Figma design (handoff-ready)
  • Product Requirements Document (PRD) or Blueprint document
  • Content assets (copy, images, illustrations, video). If not provided, Codemodo will use free or open-source alternatives (Unsplash, Pexels, Undraw, Mixkit, etc.)
Optional inputs (can follow during the engagement)
  • Access credentials for server, domain, and third-party services. Required before production deployment.
  • Existing repository and API documentation, for continuation projects
  • Existing ERD or database schema, if available
  • Google Play Developer account credentials (provided by client, required before submission)

IP Transfer

Source code, all delivered documentation, and all repository access are transferred to the client upon final payment. Until then, code and access remain Codemodo property. The IP Transfer Document is a deliverable in every engagement and formalizes the transfer.

Hosting and Infrastructure

Hosting, server costs, domain registration, and third-party service subscriptions (databases, email, payment gateways, cloud storage, monitoring tools) are the responsibility of the client. Codemodo configures and deploys to client-owned infrastructure but does not provide infrastructure or pay third-party fees.

Out of Scope

The following items are explicitly out of scope for Mobile Android Development and require a separate engagement:

  • iOS development (separate engagement: Mobile iOS Development)
  • Web dashboard or admin panel (separate engagement)
  • Hosting, server, and Google Play Developer account fees (covered by client)
  • Content creation (copy, images, video)
  • Data migration from legacy systems
  • Scope changes beyond the agreed Statement of Work
  • Support beyond the 6-month free maintenance period
  • Branding, design, or UX changes (handled under UI Design service)

Timeline

Final timeline is confirmed in the proposal and varies by project scale, complexity, and integration count. Typical engagements run 8 to 24 weeks from kickoff, milestone-driven.

Cancellation

Cancellation is permitted after contract signing. All payments made to date are non-refundable, as development work completed up to the cancellation point is already delivered. Any deliverables completed and paid for remain the property of the client. In-progress deliverables not yet at a milestone payment trigger remain Codemodo property until the corresponding payment is received.

Validity of Proposal

Proposals are valid for 14 calendar days from date of issue. After this window, scope and pricing may be re-evaluated.

Document Outputs

Shared (used across all services)
  • NDA: before any detailed discussion
  • Invoice: per milestone
  • Change Order: for any scope changes during the project
  • Meeting Notes: for every significant meeting
Mobile Android Development specific
  • Client Brief: client input before proposal
  • Proposal: scope, price, milestones, terms
  • Service Agreement: signed contract before work begins
  • Statement of Work (SOW): deliverables, milestones, acceptance criteria
  • Architecture Document: system architecture diagram (mobile + backend)
  • ERD (Entity Relationship Diagram): database structure
  • API Documentation: all endpoints (Swagger)
  • UAT Report: internal testing results before handover
  • User Guide: end user usage guide
  • Build & Release Guide: Google Play Store submission, signing, release procedure
  • Backend Deployment Guide: production deployment procedure
  • IP Transfer Document: formal transfer of source code ownership to client after full payment
  • Warranty Terms: coverage scope, duration, and void conditions
  • Handover Checklist: source code, access, documentation, training
  • Training Notes: materials from client training session
  • Maintenance Log: bug fix records during warranty period
  • Project Closure Report: summary of what was built versus original scope, lessons learned

Acceptance

By signing the Service Agreement, the client confirms acceptance of these Mobile Android Development terms in addition to the General Terms. Where this document and the General Terms conflict, this document controls for Mobile Android Development engagements only.

General Terms

These terms apply to all Codemodo service engagements. They are incorporated into every signed Service Agreement, alongside the applicable service-specific terms.

Intellectual Property

Full intellectual property rights transfer to the client upon receipt of final and complete payment. This covers source code, design files, documentation, and all project assets. No IP is transferred until all outstanding payments are settled.

During the project, all work-in-progress remains the property of Codemodo. Client access during the project is via preview link only.

Confidentiality

Both parties agree to keep all project information, business data, technical details, and commercial terms confidential. Codemodo will not disclose project details publicly without explicit written consent from the client.

Codemodo is willing to sign a Non-Disclosure Agreement (NDA) at no additional cost before any detailed project discussion. Request via info@codemodo.dev.

Asset Delivery

Source code, project assets, design files, and documentation are released to the client only after full and complete payment is received for the relevant milestone or project.

Client Responsibilities

The client is responsible for:

  • Providing accurate and complete information during discovery and briefing
  • Delivering all required assets (logo, copy, images, credentials) by the agreed date
  • Designating a single point of contact with authority to give approvals
  • Responding to review requests and sign-offs within the agreed feedback window
  • Providing access credentials (server, domain, third-party services) before production deployment

Change Orders

Any request that expands, reduces, or materially changes the agreed scope of work is handled via a Change Order. Codemodo will issue a written Change Order describing the change, its impact on timeline and cost, and the additional fee (if any). Work on the change does not begin until the Change Order is signed by the client. Change Orders are addenda to the original contract and are governed by these same terms.

Subcontracting

Codemodo does not subcontract core development, design, or planning work to third parties without explicit written agreement from the client. If subcontracting is proposed, Codemodo will disclose the scope of work to be subcontracted and the third party involved before proceeding.

Portfolio & Case Study Rights

Codemodo may reference the client's company name and a general description of the engagement (e.g., "built a fintech platform") in its portfolio, website, and marketing materials.

Detailed case studies require explicit written consent from the client before publication. This includes screenshots, metrics, client logos, and testimonials. The client may revoke portfolio permission at any time by written notice. Codemodo will remove the referenced material within 10 business days.

Termination by Codemodo

Codemodo may terminate an engagement under any of the following circumstances:

  • The client is unresponsive for 30 or more consecutive business days despite written follow-up
  • Payment remains outstanding for 30 or more business days past the due date
  • The client engages in conduct that materially obstructs project delivery

Limitation of Liability

Codemodo's total liability for any claim arising from an engagement is limited to the total fees paid by the client for that specific service. Codemodo is not liable for indirect, consequential, or incidental damages.

Governing Law

These terms are governed by the laws of the Republic of Indonesia. Any disputes shall be resolved through good-faith negotiation first. If a dispute is not resolved within 30 days of written notice, either party may pursue mediation through BANI (Badan Arbitrase Nasional Indonesia) or a mutually agreed mediator. If mediation does not resolve the dispute within 30 days, either party may escalate through the courts of Jakarta.

Force Majeure

Neither party is liable for delays or failures caused by circumstances beyond reasonable control. This includes natural disasters, internet or infrastructure outages, government actions, and public health emergencies. The affected party must notify the other in writing as soon as reasonably possible. Project timelines will be adjusted accordingly. Payment obligations for work already completed remain in effect.

Currency & Tax

All prices are quoted in Indonesian Rupiah (IDR) and are exclusive of PPN (Pajak Pertambahan Nilai / Value Added Tax) unless explicitly stated otherwise. PPN, if applicable, will be added to the invoice at the prevailing rate. Tax invoices (faktur pajak) are issued upon client request.

Survival

The following provisions survive the termination or expiration of any engagement:

  • Intellectual Property
  • Confidentiality
  • Data Protection & Privacy
  • Limitation of Liability
  • Portfolio & Case Study Rights

Data Protection & Privacy

All client data is used solely for the purpose of delivering the engaged service. This includes business information, user data, credentials, and project-related materials. Codemodo does not use client data for other engagements, training, marketing, or any purpose beyond the scope of the active project.

Work-in-progress data stored in staging and development environments is deleted within 30 business days after the project is completed or terminated. The client may request earlier deletion in writing.

Both parties agree to handle personal data in accordance with applicable Indonesian data protection regulations, including UU PDP (Undang-Undang Pelindungan Data Pribadi).

Questions? Contact info@codemodo.dev