Terms of Service

Last Updated: June 2026

Welcome to AGI In Action. By selecting a commercial developer tier and initiating a subscription fee payment on this website, you explicitly acknowledge and agree to the following legally binding terms and conditions.

1. Nature of Transaction, Service Classification & Scope

  • Commercial Export of Services: Any payment made through this platform (including but not limited to SEPA direct transfers, international wire transfers, PayPal, or integrated credit card gateways) represents a commercial subscription fee paid by you (the “Subscriber” or “Service Recipient”) to the developer (the “Service Provider”). These transactions are explicitly classified, intended, and reported as “subscription platform fees for open source software development and maintenance“. This transaction is executed and documented exclusively as a commercial export of services from India, in strict compliance with Indian Foreign Exchange Management regulations, Reserve Bank of India (RBI) Purpose Codes (P0802 / P1008), and National Industrial Classification (NIC-2008) codes 62013, 62020, and 72100 (specifically categorised under 72100 as an experimental R&D service).
  • Defined Service Deliverables & Optional Perks: The core commercial service rendered under this agreement consists strictly of the ongoing execution, operational funding, and maintenance of the open-source architecture. As an optional, user-initiated add-on convenience perk associated with this R&D subscription, the Service Provider provisions:
    • Electronic access privileges to the Service Provider’s active, ongoing, experimental, and unpolished private open-source AI and robotics development streams (Read-Only repository access via GitHub).
    • The digital delivery of early-stage, pre-release codebase updates and technical R&D documentation.
    • Queue-based priority visibility within designated project community spaces, which scales dynamically based on tier level.
    • Absolute Exclusion of Support: This subscription strictly excludes any form of personalized one-to-one customer support, private engineering consulting, dedicated debugging, or contractually guaranteed response timelines.
  • No Consumer Goods or Custom Engineering: You explicitly acknowledge and agree that this service is an experimental R&D infrastructure subscription. It does not constitute the sale of a retail consumer product, a polished mass-market software application, a functional license key, or a contract for personalized, custom engineering consulting. You explicitly agree that you are purchasing this service in a commercial/professional capacity and waive any status as a “consumer” under the Indian Consumer Protection Act or equivalent international statutes.
  • Core Software Licensing: While this commercial subscription provides operational visibility into active development streams and early experimental updates, any functional software builds ultimately compiled, distributed, or deployed publicly remain independently governed by the open-source MIT License.

2. Scope of Service Boundaries: No Private Consulting & Passive Interaction

  • Absolute Exclusion of Private Services: The commercial fee paid covers only the generalized access privileges explicitly defined in Section 1. This transaction strictly excludes, bars, and prohibits any form of private one-to-one engineering consulting, custom software integration, personalized feature development, private debugging, code-review requests, or direct hardware/software technical support via email, private messaging, or any other medium.
  • Public Nature of Project Interactions: To preserve the Service Provider’s developmental focus, all technical queries, discussions, or communications regarding the open-source architecture must take place entirely in public view within the project’s designated public forums or GitHub repository boards.
  • No Interaction, Chasing, or Response Guarantees: The project operates on a strictly passive, asynchronous communication model. The Service Provider will not initiate outbound communication, trace missing information, or contact individual Service Recipients. While the Service Provider may, at their sole and absolute discretion, review or reply to public posts made by verified subscribers to foster community engagement, no technical responses, resolution timelines, or engineering answers are guaranteed or contractually implied.
  • Unilateral Moderation Rights: The Service Provider retains the absolute, unreviewable right to close, lock, archive, or delete any public issue, query, thread, or comment within their managed infrastructure without notice, and without incurring any liability, refund obligation, or requirement to provide alternative compensation or direct support channels.

3. Provisioning Policy, Insider GitHub Access & Unclaimed Access Protocol

  • GitHub-Centric, Non-Physical Delivery: The core service and optional perks defined in Section 1 are fulfilled strictly through digital access control within the GitHub platform. No physical goods, media drives, hardware components, or standalone source-code files will ever be compiled, packaged, or dispatched via physical mail, email, or external file-sharing services.
  • On-Demand & User-Initiated Perks: Digital access to private experimental repositories is strictly an optional, non-mandatory courtesy perk tied to the underlying software development subscription framework. This access must be explicitly claimed and initiated by the Service Recipient. The Service Provider does not monitor incoming bank metadata to match financial identities, nor will they automatically track, assign, or provision access privileges upon payment clearance.
  • Asynchronous Invitation & Performance Protocol: To claim private stream access, the Service Recipient must proactively provide a valid GitHub username through the project’s designated public communication channels or website forms. The Service Provider will issue a “Read-Only” repository invitation asynchronously at their operational convenience. No specific setup or response timeline (e.g., immediate or within 24 to 48 hours) is contractually binding or implied.
  • Unclaimed Access & Passive Satisfaction (The “Ghost Subscriber” Clause): If a Service Recipient completes a financial transaction but elects not to initiate contact or provide a valid GitHub username, the transaction remains a fully valid commercial subscription for open source software development and maintenance. The Service Provider’s service delivery obligation is legally deemed fully rendered, satisfied, and concluded through the continuous research, maintenance, and execution of the open-source project infrastructure. The Service Provider is under no legal or operational obligation to seek out, chase, or email the Service Recipient to fulfill the optional GitHub access perk.
  • Legal Definition of Full Rendering: For recipients who do choose to claim access, the optional commercial courtesy perk is legally considered fully rendered, completed, and delivered the exact millisecond the Service Provider dispatches the official invitation via the GitHub platform. The onus rests entirely on the Service Recipient to manually log into their GitHub profile and accept the pending invitation to view the repository data.
  • Continuity and Revocation of Access: Access to private experimental repositories is directly tied to an active, verified commercial software development cycle. If a recurring payment fails, is canceled, or lapses, the Service Provider reserves the absolute right to immediately and automatically revoke the Service Recipient’s access to the private repository network without prior notice, liability, or grace periods.
  • “As-Is” Experimental R&D Infrastructure: All codebase files, neural network weights, structural assets, 3D printing configurations, or technical logs hosted within private subscriber-access environments are experimental, unpolished, and provided strictly on an “AS IS” and “AS AVAILABLE” basis. The Service Provider gives no warranties of any kind, express or implied, that the experimental data will compile, function safely, or remain backward-compatible with the Service Recipient’s hardware or local software environment.

4. Fees, Cancellation, and Strict Anti-Chargeback Policy

  • Finality of Transaction Fees: The commercial fee processed through integrated payment gateways (including PayPal and Payoneer) is a flat service fee for the electronic provisioning of R&D data stream access. Because digital entry and repository access are provisioned immediately upon fee clearance, all transactions are final, strictly non-refundable, and non-reversible.
  • Explicit Waiver of Chargeback Rights: The Service Recipient explicitly acknowledges that the deliverables consist of access to experimental, unpolished research environments. By completing the transaction, the Service Recipient unconditionally waives their right to initiate a chargeback, “Item Not Received” claim, or payment dispute with their banking institution, credit card issuer, or third-party payment processors.
  • Dispute Resolution Mechanism: If the Service Recipient experiences an administrative or billing error (e.g., accidental duplicate billing), they agree to refrain from filing an official dispute with the processor and instead contact the Service Provider directly at agi-in-action@protonmail.com to resolve the matter administratively.
  • Breach and Remedies: Any unauthorised chargeback, payment reversal request, or dispute filed by a Service Recipient will be treated as a material breach of these Terms. In such an event, the Service Provider reserves the absolute right to instantly terminate all access privileges, permanently ban the user from the repository network, and present these signed Terms to the respective payment aggregator or bank as conclusive legal proof of service delivery to force an immediate dismissal of the dispute.

Here is the modified Section 5. The core structure, flow, and regulatory tracking have been strictly preserved, with surgical updates integrated to address the intermediary bank fees, invoicing alignment, and the clear definition of your R&D service parameters.

5. Milestone Settlements, Dynamic Tier Scaling & Database Purge Policy

  • Permitted Split Payments & Transaction Floor: The Service Recipient is permitted to fulfil their chosen Developer Tier commercial fee via a single transaction or through multiple split payments (milestone settlements) within a single billing cycle. Because this transaction is a subscription fee for ongoing open-source software development and maintenance—and explicitly not a retail consumer good or mass-market service license—these funds directly support continuous R&D infrastructure overhead. To maintain cross-border processing efficiency, each individual transaction must strictly meet or exceed a baseline floor of $600 USD. Any individual transfer falling below this baseline floor may be subject to administrative hold or automatic reversal by the settling bank.
  • 1:1 Regulatory Matching & Internal Accounting: To satisfy automated RBI/FEMA compliance criteria via HDFC Bank (Purpose Codes P0802/P1008), the Service Provider absorbs standard intermediary banking network or routing fees. Accordingly, a separate, distinct commercial invoice will be generated internally for accounting, tax filing, and regulatory clearance purposes for every unique transaction, based strictly on the exact net settled dollar amount received in the Service Provider’s bank account. The delivery of this invoice to the Service Recipient is entirely user-initiated and contingent upon the Service Recipient proactively providing a valid contact email address through the website “SUBSCRIBER FORM” section to reach to our billing department and requesting for the invoice; otherwise, the invoice will remain strictly as an internal record to satisfy Indian financial regulations.
  • Proportional Tier Downgrading & Privileges Evaluation: Subscriber tier designation and its corresponding optional add-on privileges—specifically consisting of Read-Only private repository stream access and queue-based priority community board visibility (strictly excluding any personalized one-to-one engineering support, private debugging, or guaranteed response timelines)—are evaluated dynamically based on the cumulative net settled funds received within that active monthly cycle. If a subscriber reduces their cumulative payment compared to a prior month, their access is not immediately terminated. Instead, their status will automatically scale down gracefully to the corresponding lower tier-bracket, down to Tier 1.
  • Sub-Baseline Grace Period & Absolute Purge Clause: The structural floor required to maintain active subscriber status is the Tier 1 Base Minimum net settled amount of $600 USD per month. If the cumulative net settled funds received within a billing cycle fall entirely below $600 USD, or if a subscriber enters a state of total non-payment, an administrative grace period of one to two (1–2) consecutive billing months will be applied. If the account remains inactive or below the baseline threshold after this 1–2 month window, the subscriber will be placed on hold and may be permanently removed from the active developer database and repository network without prior notice, warning, or liability of any sort.

6. Billing, Administrative Support, and Transaction Contact

  • Restricted Communication Channel: For administrative queries strictly limited to transaction verification, payment clearance errors, or pending GitHub repository invitation access status, the Service Recipient may contact the administrative desk at: agi-in-action@protonmail.com.
  • Technical Support Exclusion: This administrative email address is strictly for billing and platform access operations. Any software-related bug reports, custom development proposals, architectural queries, or hardware troubleshooting requests dispatched to this address will be permanently ignored, archived without a response, and deleted. All technical discourse must occur within the designated public forums as defined in Section 2.

7. Governing Law, Exclusive Jurisdiction, and Severability

  • Governing Law: These Terms, the commercial relationship between the Service Recipient and the Service Provider, and any disputes arising out of or in connection with this platform shall be governed by, interpreted, and construed exclusively in accordance with the substantive laws of India, without regard to conflict of law principles or international treaties such as the UN Convention on Contracts for the International Sale of Goods (CISG).
  • Sanctioned and Prohibited Jurisdictions: The Service Provider does not offer, render, or provide services, directly or indirectly, to individuals, entities, or regions subject to comprehensive economic sanctions, trade embargoes, or restrictive measures administered by the Office of Foreign Assets Control (OFAC) of the US Department of the Treasury, the United Nations Security Council, or Indian regulatory authorities. Any transaction, subscription, or payment originating directly or indirectly from a prohibited jurisdiction or sanctioned entity will be automatically rejected or reversed to the originating banking institution or payment processor, subject to the operational timelines and procedures of the receiving financial institution.
  • Exclusive Local Jurisdiction: The Service Recipient explicitly and unconditionally agrees that any legal actions, claims, suits, or proceedings brought by either party shall be subject to the exclusive jurisdiction of the competent courts located in [Bangalore, Karnataka, India] (the local jurisdiction where the Service Provider’s primary banking institution, HDFC Bank, is maintained). The Service Recipient waives any objection to such venues on the grounds of inconvenient forum or lack of personal jurisdiction.
  • Waiver of Class Action Claims: Any dispute resolution proceedings, whether in court or via arbitration, will be conducted solely on an individual basis and not in a class, consolidated, or representative action.
  • Severability Clause: If any provision, sentence, or clause of these Terms of Service is found by a court of competent jurisdiction to be invalid, illegal, or unenforceable, that specific portion shall be limited or eliminated to the minimum extent necessary. The remaining provisions of these Terms shall remain in full force, effect, and operationally binding.

8. Institutional Clearance Reliance & True-Fraud Remittance Safe Harbor

  • Multi-Party Clearance as Definitive Verification: The Service Recipient acknowledges that cross-border commercial service transactions are cleared through a dual-gated institutional architecture (the sender’s originating financial ecosystem and the receiver’s settling platforms, including PayPal, Payoneer, and HDFC Bank). Once a payment successfully passes the automated fraud filters of both independent ecosystems and settles into the Service Provider’s account, it is legally certified as a valid, authorized commercial remittance.
  • Fully Earned Income upon Settlement: Because the project streams are continuously maintained on an “AS IS” and “AS AVAILABLE” basis, all institutional-cleared funds are considered fully earned by the Service Provider at the exact moment of settlement. If a sender chooses to remit funds but fails to initiate communication or claim their optional GitHub access perk, the transaction remains legally complete and closed. The Service Provider has no administrative duty to investigate, trace, or chase uncommunicative senders.
  • True-Fraud Rectification & Return-to-Source Protocol: This section applies strictly to verified criminal fraud (such as documented identity theft or compromised bank networks) and is entirely distinct from standard user-initiated consumer chargebacks. In the event that a clearing bank or regulatory authority provides definitive, conclusive proof that a settled transaction was the result of a true systemic exploit or compromised instrument, the Service Provider will cooperate in good faith to allow the processing network to reverse and return those specific funds directly to their legitimate source.
  • Merchant Exoneration Clause: Because any such return-to-source action is the direct result of a false-positive clearance by the institutional financial gatekeepers, the Service Provider shall be held entirely free from any administrative liability, banking penalties, blacklisting, or complicity. The financial system bears the ultimate responsibility for its own processing oversights.

9. Absolute Right of Modification, Operational Evolution & Liability Shield

  • Unrestricted Right to Amend: The Service Provider retains the sole, absolute, and unreviewable right to modify, rewrite, or completely replace these Terms of Service, as well as alter the project’s operational, technical, or delivery frameworks at any time. This right may be exercised at the Service Provider’s sole discretion to adapt to the rapidly changing landscape of Artificial Intelligence, robotics development, platform constraints, or personal operational realities.
  • Universal, Immediate Retroactivity: Any amendments, structural updates, or total rewrites of these Terms become legally binding on all parties the exact millisecond they are published on the project’s public repository or web interface. These updated terms apply universally to all future transactions and all active, ongoing, or existing Service Recipients/Subscribers. Continued status as a subscriber is strictly contingent on accepting the most current version of these Terms; no prior rules or privileges will be grandfathered.
  • Platform Failures, Security Breaches & Force Majeure: In the event of an operational crisis—including but not limited to GitHub service termination, repository bans, malicious hacking or account breaches, data destruction, catastrophic hardware failure, or sudden local/international regulatory shifts regarding AI deployment—the Service Provider reserves the right to immediately suspend, modify, or permanently terminate all access streams and delivery mechanisms.
  • Ironclad Chargeback & Refund Shield: If the operational model changes, if access is modified, or if the project’s delivery mechanisms are permanently disabled due to legal impossibility, third-party platform action, or security breaches (such as account hacking), the Service Recipient explicitly waives all rights to demand refunds, launch financial disputes, or initiate payment chargebacks. All historical and active transactions remain fully finalized, non-refundable commercial service export payments for past or ongoing R&D execution. The Service Provider is permanently shielded from any financial liability, compensation claims, or restitution demands under any circumstances.