Effective Term Date: June 9, 2026

Terms of Service

Review the structural parameters, SLA guidelines, intellectual parameters, and compliance conditions governing your development journey on AndroidBuilder.

Search Agreement Clauses

SLA Compliance Toggler

Simulate checking whether your development assets comply with the terms defined under our developer checklist.

Target SDK 34 Compliance
Legal Key-Signature

1. Acceptance of Terms

These Terms of Service ("Terms") dictate the structural parameters and legally binding rules governing your acquisition, lease, deployment, or visual usage of the AndroidBuilder.in platform, its compilers, and APIs.

By interacting with our block-interface, generating keystores, hosting custom extensions on our Extensions IDE, or compiling your visual drafts, you explicitly declare your legal competency and structured agreement to be bounded by these terms.

2. Account Registration & Safety

Accessing compiled services requires an active development profile. You agree to submit true, structurally sound, and accurate identifiers during sign-up.

You retain sovereign accountability for maintaining absolute protection over your active login parameters. AndroidBuilder will not be legally liable for any security compromises, code modifications, or Keystore thefts resulting from developer negligence. Sharing developer credentials across individual commercial entities is strictly prohibited.

3. Compiler & Service Usage

Our cloud system compiles visual block projects into production-ready Android App Bundles (.AAB) or Package binaries (.APK). Due to server infrastructure overhead, usage limits apply:

Queue & Compilation SLA Free tier compiles are subject to execution delays depending on active cluster workload. Upgraded accounts gain access to prioritized compilation lanes.
Auto-purge Thresholds Compiled binaries (.APK/.AAB) hosted within compile queues are automatically purged from system storage 60 minutes post-successful compile.

4. Code & Intellectual Property

Your Code: You preserve absolute, unilateral ownership of all custom visual block arrangements, code logics, assets (.AIA), drawings, and database secrets designed inside your project files. AndroidBuilder claims no copyright over assets you assemble.

Platform IP: All system frameworks, visual icons, graphical compiler block modules, backend compilers, and Extensions IDE tools remain the exclusive property of AndroidBuilder.in and its design partners.

5. Extensions Portal & AIX Files

AndroidBuilder supports the importation and deployment of community extensions (.AIX files). By importing or creating custom .AIX files using our Extensions IDE, you confirm that:

  • You possess direct licensing authorities over the imported Java components.
  • The extensions contain no spyware, adware modules, or target code exploits.
  • Your extensions do not bypass Google Play Core security frameworks.

6. Monetization Policies

When utilizing integrated components for monetization (AdMob, Meta Ads, AppLovin, or Start.io), you assume sovereign accountability for complying with those services' separate developer policies.

Any account closures, revenue suspensions, policy enforcement actions, or device banning by Google AdMob or corresponding networks are independent of our platforms. AndroidBuilder offers no refunds, coverage, or legal liability for any lost ad profits.

7. Abuse & Reverse-Engineering

To protect our cloud service, the following structural activities are strictly prohibited and will trigger immediate account suspension:

  • Decompiling, reverse-engineering, or ripping out backend compiler scripts or visual nodes.
  • Flooding compilation servers with simulated automated request streams.
  • Packaging applications designed to execute banking phishing schemes, malware installation, or system evasion.

8. Warranty & Liabilities

AndroidBuilder.in is provided "AS IS" and "AS AVAILABLE", devoid of any explicit, structural, or implied warranties regarding runtime uptime, design reliability, or absolute error-free compiler states.

Under no legal system will AndroidBuilder, its creators, or server partners be accountable for any direct, indirect, random, or punitive liabilities, including but not limited to compiler errors, project data loss, keystore corruptions, or commercial revenue drops.

9. Jurisdiction & Disputes

These terms shall be governed and interpreted according to the laws of the Republic of India, without reference to conflict of laws doctrines.

Any structural dispute, legal claim, or administrative proceeding arising from the use of our services shall be filed exclusively inside tribunals holding jurisdiction within Gwalior, Madhya Pradesh, India.