Refund Policy

KEO AI Architecture specializes in custom software engineering, API integrations, and digital intellectual property. Due to the non-returnable nature of custom source code and digital goods, all sales are final once the code has been transferred, deployed, or delivered to the client.

1. User Acceptance Testing (UAT)

Before final delivery, clients are required to review and test the software on a secure staging environment. Approval of the software on the staging environment constitutes final acceptance of the deliverable. Once accepted and deployed to the client's live environment or repository, no refunds will be provided.

2. Eligibility for Refunds

Refunds are only issued in the rare event that KEO AI Architecture fails to deliver the agreed-upon Statement of Work (SOW) within the contracted timeframe, and the failure is entirely on the part of our development team. Delays caused by the client failing to provide necessary credentials, APIs, or feedback do not qualify for a refund.

3. Chargebacks and Friendly Fraud

If a client initiates a chargeback or payment dispute through their bank or payment processor after receiving functional source code, their license to use the software is immediately and permanently revoked.

• All associated API access and integrated developer credentials will be terminated.
• The client will be subject to immediate legal action for copyright infringement, breach of contract, and theft of services.
• We will issue a formal DMCA Takedown Notice to the client's hosting providers or repositories.

4. Maintenance Retainers & Support

Ongoing technical support and maintenance subscriptions can be canceled at any time with a 14-day written notice. However, past billing periods where the developer was retained and available on standby are strictly non-refundable.

5. Client Environments & Third-Party Limitations

We guarantee our software functions within standard, agreed-upon production parameters. We do not issue refunds for issues arising from local IT limitations, third-party firewall restrictions, operating system security blocks (such as Apple macOS Gatekeeper), or unannounced changes to third-party APIs beyond our control.