Terms and Conditions

These terms govern the sale of licenses, instances and services of the Alias Integrator ecosystem. Our model rests on three principles: 0 subscription, 0 SaaS, lifetime license. You pay once; the software is yours and runs on your machines.

License — Alias Solo and Alias Studio ranges. One-time payment, perpetual right of use.

Instance — Alias Studio range only. One instance = one brand / one website. Configuration tailored to your business (business bridge, and AI bridge where the tier provides for it). The Alias Solo range includes neither instance nor maintenance: you install and run the application as is on your own machine.

Alias2Avatar is never sold on its own — Alias Studio range. Any Alias2Avatar Studio license is acquired together with at least one other application. Installation — performed remotely by the publisher — includes the security and audit tools (Alias2Daenerys, Alias2Salvare) and the Alias2Periphery agents.

Non-disclosure of compiled code — Alias Solo and Alias Studio ranges. The applications are delivered compiled (Nuitka): the Python code is fully closed — only Solo (the free version) is source-available. If you terminate your maintenance contract, the license remains lifetime, but you are prohibited from decompiling the Nuitka-compiled code, whether yourself or by paying a third party, in order to perform maintenance; you will need to find other solutions. Certain components are the subject of pending patent applications. The compiled code may under no circumstances be disclosed; its safekeeping and non-distribution are your responsibility.

Interoperability — Alias Studio range only. The ecosystem is designed as a single integrated whole. If you wish to connect the applications to a third-party system (for example, an ERP), this interoperability is carried out by the publisher, on request, and is always billed separately — it is not covered by the maintenance contract. When you appoint a contractor to work with the publisher on this interoperability, a strict confidentiality clause is signed between that contractor and the publisher.

Maintenance applies to the Studio range only — the Solo range has no maintenance in the strict sense: it relies on updates (previous section). Security updates, dependencies, and fixes, applied by the publisher. Payable monthly; it begins upon delivery.

Any intervention by the publisher (installation, maintenance) is performed remotely, via a secure tunnel, opened during a time slot agreed with you; outside that slot, no access is possible. In normal operation, the compute station is isolated from the Internet; for an intervention, it is temporarily opened — which is why the intervention goes through a secure tunnel. Maintenance is not carried out on a fixed schedule: it takes place according to updates and to the monitoring and audit reports (Alias2Salvare, Alias2Daenerys). The publisher also performs an audit once a month.

The publisher never has access to your data. The publisher accesses the structure of the databases, not the data; the reports mask the data and report only any format anomalies liable to cause a bug.

First year of maintenance mandatory for Studio Smart and Studio Max — no-code training, carried out by you, always requires custom adjustments. After the first year, you are free to discontinue maintenance — although it is strongly recommended — and to call on the publisher on an occasional basis, subject to billing. Its discontinuation does not affect the license: the software continues to run — you still receive standard updates free of charge, but install them yourself; the publisher no longer intervenes.

Desktop, not browser. The applications run in a desktop application, not in a browser. Alias Studio range: one desktop for your back office and one desktop for your frontend clients. Alias Solo range: a frontend only. The back office is used to populate your database, train your AI, and handle other functions related to the administration of your instance. The frontend allows your users to view content, use business extensions if you have opted for Alias2Ender, and interact in the AI stream.

Offline. The desktops work offline (except for the AI stream) and synchronize when the connection returns (travel, plane, etc.). Internet access occurs only between the NAS and the desktop. In normal operation, the compute station is isolated from the Internet: it is connected to the NAS, and it is the NAS that acts as the server.

Special cases (Alias Solo range). The frontend has neither outbound nor inbound internet access, except for: Alias2Hypatia (downloading PDFs, videos, and texts, in a secure sandbox), Alias2Trikru (sending and receiving email) and synchronization between your devices (tablet, iPhone, Mac), through occasional openings via an ngrok-type secure tunnel.

Website (Studio Web and Studio Max) in the desktop: 0 cookies, 0 trackers, 0 data collection (see Privacy). Operation. Your data physically remains on your premises; neither the publisher nor Kidogo has access to it in normal operation. You are the sole data controller for your data and that of your visitors (AI stream included). Only the data necessary for the contract (signatory's contact details, billing) is processed by Kidogo — the details are provided on the Privacy page.

Client's cloud. If you request an adaptation to a cloud that you define, you remain the sole data controller and bear alone the consequences for the sovereignty of your data; Kidogo and the publisher are not liable for it.