Accesos Inteligentes · Aquiles

Software license and services acceptance agreement

This is the acceptance agreement between PUERTAS Y BARRERAS INTELIGENTES, S.A. DE C.V. (Mexican tax ID PBI130529NY0), trade name Accesos Inteligentes (product Aquiles) and the Customer. It complements the Terms and Privacy notice on aquiles-app.com. By signing it, or by paying for the package at checkout, the Customer states they have read and accept it.

Parties

Provider

PUERTAS Y BARRERAS INTELIGENTES, S.A. DE C.V. (Mexican tax ID PBI130529NY0), trade name Accesos Inteligentes, operator of https://www.aquiles-app.com. Tax address: José Trinidad Villagómez Nte. 2907, Col. Bella Vista, C.P. 64410, Monterrey, Nuevo León, México. Contact: soporte@aquiles-app.com.

Legal name: PUERTAS Y BARRERAS INTELIGENTES, S.A. DE C.V.

Tax ID: PBI130529NY0

Tax address: José Trinidad Villagómez Nte. 2907, Col. Bella Vista, C.P. 64410, Monterrey, Nuevo León, México

Customer

Recitals

I. The Provider states it is authorized to license Aquiles, a sales agent the Customer installs on their own site (WordPress plugin or Docker package).

II. The Customer states they have authority to contract, know the product (including the aquiles-app.com demo, if used), and have a WordPress site or a server that can run Docker, according to the install path they choose.

III. Both parties acknowledge that aquiles-app.com handles the account, billing, the SAAS license, and downloads, and that chat, catalog, leads, appointments, quotes, documents, and the Customer’s OpenAI API key stay on the Customer’s install, not on aquiles-app.com.

IV. The parties agree to the following terms.

Clauses

1. Purpose

The Provider grants the Customer a non-exclusive, non-transferable, revocable license to use Aquiles for one (1) site or install, unless Annex A says otherwise, and delivers the matching installer (WordPress plugin and/or Docker ZIP) plus a SAAS license key.

This does not include custom development, management of the Customer’s hosting, or any guarantee of sales, conversions, or OpenAI or hosting response times.

2. Deliverables and install paths

After payment, the Customer downloads from My account: (a) the WordPress plugin, for web hosting / cPanel; and (b) the Docker ZIP, for a VPS or their own Windows/Linux server. Shared hosting cannot run Docker.

The Customer installs on their site, using the FAQ and the license/install support in this agreement, unless they paid for the Provider’s install service at checkout. In that case the Provider schedules the install by email. Chat on the Customer’s site turns on when they install and paste the SAAS key (and the Customer’s OpenAI API key).

3. Trial

If a free trial is offered, it opens a demo panel on aquiles-app.com, with no card. It does not install chat on the Customer’s site or deliver a production SAAS license. That happens when the package is paid.

4. Fees and billing

The package includes a monthly or annual subscription, as the Customer chooses at checkout or as set in Annex A. The one-time setup fee is optional: the Customer chooses it at checkout if they want the Provider to install the software on their site. If they skip it, the Customer installs with the FAQ guide. Current amounts are those Stripe shows at payment, or those written in Annex A if the parties agree in writing.

Payment is processed by Stripe, in USD or MXN according to the chosen currency. Stripe issues the payment receipt. A Mexican tax invoice (CFDI) is not generated automatically; the Customer requests it at soporte@aquiles-app.com, with their tax details.

The subscription renews automatically for equal periods at the then-current price, unless cancelled before renewal from My account or at soporte@aquiles-app.com. The one-time install fee, if purchased, is non-refundable. There is no refund for partial periods already started, except where a mandatory rule says otherwise.

The license stays active while the subscription is paid. If the Customer cancels or a charge fails, chat stops responding once the license is marked inactive.

5. License and restrictions

The Customer does not own Aquiles code, brands, or documentation. They only receive the usage right in this agreement.

Reselling, sublicensing, copying the software for third parties, bypassing SAAS key validation, or using it on more sites than licensed is forbidden unless the Provider agrees in writing.

The software is provided as-is. Prices, discounts, copy, catalog, and commercial policies in the chat are defined by and are the responsibility of the Customer. The Provider and its licensors retain intellectual property in the Software; the Customer only receives the usage license. Customer Content remains the Customer’s.

6. Customer duties

Provide a WordPress site or a Docker server, their own OpenAI API key (BYOK), and, if they want customer email, their hosting SMTP settings.

Remain responsible for content they upload (catalog, documents, visitor data) and for the law that applies to their business, including their own privacy notice toward their customers.

Keep the plugin or install updated and not share the SAAS key or Shopify, OpenAI, or other connected secrets.

The agent uses OpenAI models with the Customer’s API key (BYOK). Replies may contain errors or “hallucinations” and are not binding offers unless the Customer validates them. The Customer will not use the agent for unlawful purposes or regulated advice without complying with those rules.

7. Provider duties

Deliver downloads and the SAAS key after payment, validate the license while the subscription is current, and handle license, payment, and install support at soporte@aquiles-app.com and in the FAQ. If the Customer paid for the install service, the Provider schedules and installs the software on the indicated site.

Support does not include custom development or management of the Customer’s hosting, WordPress, Shopify, or server.

8. Personal data

Account, payment, and license data on aquiles-app.com is handled under the Privacy notice on that site (Mexico’s LFPDPPP). ARCO requests: soporte@aquiles-app.com.

Data of visitors to the Customer’s site (leads, chats, appointments, quotes) is processed by the Customer on their WordPress or server. The Provider is not responsible for that processing.

The Customer will indemnify the Provider against third-party claims (including End users or authorities) arising from Customer Content, agent statements, breach of this agreement, or use of OpenAI.

9. Confidentiality

Each party will keep confidential the other party’s commercial, technical, and customer information obtained under this agreement, except for legal process or information that is already public.

10. Term and termination

This agreement starts on the signature date or, if there is no wet-ink signature, on the date of the first successful package payment in Stripe.

Either party may end it by cancelling the subscription in the billing portal or in writing to soporte@aquiles-app.com. On termination the production usage right ends; the Customer must stop using the software and the SAAS key.

Confidentiality, intellectual property, limitation of liability, and fees already accrued survive as applicable.

11. Liability

The Provider does not guarantee sales, OpenAI availability, or the Customer’s hosting. To the extent the law allows, the Provider’s total liability under this agreement in any twelve-month period will not exceed what the Customer paid the Provider for Aquiles in those twelve months.

Neither party is liable for lost profits, indirect damage, or data loss on the Customer’s install, except for willful misconduct or a mandatory rule to the contrary.

12. Relationship to site terms

The Terms and Privacy notice on aquiles-app.com form part of this agreement. If a signed Annex A conflicts with those texts, as between the signing parties Annex A controls amounts, term, and licensed site; otherwise these clauses control, and failing that the published Terms.

13. Governing law

This agreement is governed by the laws of Mexico. The parties submit to the competent courts of Monterrey, Nuevo León, waiving any other venue, unless a mandatory rule says otherwise. The Spanish version controls; any translation is for convenience only.

14. Acceptance

The Customer accepts this agreement by signing below and/or by completing package payment in Stripe. Either path is enough. Electronic signatures, an authenticated checkout, and the purchase confirmation email have the same effect as a handwritten signature under applicable Mexican law.

Annex A — Commercial details (fill in at signing)

If a field is left blank, the Stripe checkout and the Customer’s aquiles-app.com account control.

Signatures

Signed in duplicate on the Annex A date.

For the Provider

Name, title, signature, and date. If signing for a company, state the authority or office under which you act.

Nombre / Name

Cargo / Title

Firma / Signature

Fecha / Date

For the Customer

Name, title, signature, and date. If signing for a company, state the authority or office under which you act.

Nombre / Name

Cargo / Title

Firma / Signature

Fecha / Date

Terms and conditionsPrivacy notice