SEC-01 · Version 1.0.0
SMARTEDTECH SL (स्वामी) द्वारा अनुमोदित · प्रभावी: 1 नवंबर 2026
You accept this document with the checkbox on the project enquiry. No electronic signature is collected on this page.
SET Labs Service-Specific Terms (Custom Development, Turnkey Delivery and Managed Operations)
1. Scope
1.1 These terms supplement CUS-03 for the three service lines offered on imeset.com: (a) custom AI and software development; (b) turnkey platform delivery; (c) managed platform operations. The Order states which service lines apply.
1.2 In case of conflict, the precedence in CUS-03 clause 1.4 applies; these terms rank above CUS-03 and below the Order and DAT-01.
2. Discovery and quotation
2.1 Discovery work (workshops, audits, architecture assessment) is delivered under its own Order line and produces a written discovery report. The report is the basis of the SOW; it does not authorise development.
2.2 A quotation states the assumptions on which the price is based. If an assumption proves wrong, the Operator proposes a change order before continuing the affected work.
3. Custom development
3.1 The SOW identifies business objectives, named deliverables, supported environments, Customer dependencies, acceptance evidence and milestones.
3.2 The Operator delivers in reviewable increments. Each increment is accompanied by the acceptance evidence stated in the SOW (test results, demonstration record, documentation). A demonstration environment is labelled as such and is not production proof.
3.3 New features built on the SET Core consume the existing SDK and rails. The Operator does not deliver a parallel identity, consent, audit or ledger engine, and does not assign, clone or share the SET Core source. The Customer receives the deliverable licence stated in CUS-03 clause 8.5.
3.4 Third-party components, open-source licences and external model or hosting providers used in a deliverable are listed in the SOW with their licence and cost; the Customer approves each addition that carries a cost or a licence obligation.
4. Turnkey delivery
4.1 Turnkey delivery includes the deployment of the deliverable into the target environment stated in the SOW, the handover documentation, and the handover training sessions stated in the Order.
4.2 Launch readiness is decided by the Customer's named approver on the Operator's readiness report. The Order names the approver, the rollback plan and the post-launch support period.
4.3 Handover assets are: source and configuration of the deliverable (excluding the SET Core source and the Operator's reusable tooling), deployment scripts, documentation, and credentials transferred through a secure channel. Repository access scope is stated in the SOW.
5. Managed operations
5.1 Managed operations covers monitoring, maintenance, security patching, backup and restore, incident response and the service levels in CUS-03 clause 7, for the systems listed in the Order.
5.2 The Operator operates within the authority the Customer grants in the Order. Managed operations do not transfer to the Operator any statutory, regulatory or professional decision authority of the Customer; actions with legal, financial or employment effect are executed only on the Customer's recorded instruction.
5.3 Monthly service reports state uptime, incidents, changes applied and open risks. Figures are taken from the monitoring source named in the report.
6. Data, secure channel and processing
6.1 The Customer does not place patient, child, case-file, credential or other sensitive data in a public enquiry form or in a general project channel. Where a project involves such data, the Operator opens the secure channel stated in the SOW and DAT-01 is signed before any such data is processed.
6.2 External hosting and model providers used for the Customer's workload are contracted as stated in the Order: either by the Customer directly (the Customer holds the keys and the contract) or by the Operator as a subprocessor listed in DAT-01 Annex C. Regions and data locations are stated in DAT-02.
7. Change and publication
7.1 Scope changes, new third-party costs, external communications and publication of any part of the work require the change authority named in the Order.
7.2 Neither party publishes the existence or results of the engagement without the other's written permission (CUS-03 clause 8.6).
8. Exit
8.1 The Order states the handover assets, export format, migration assistance, support term and deletion schedule. Data export is available for 30 days after termination (CUS-03 clause 6.3).
8.2 Procurement rules, sector licences and professional registrations applicable to the Customer's business remain the Customer's responsibility.
9. Governing terms
CUS-03 clauses 10 (confidentiality and retention), 11 (changes), 12 (liability), 13 (notices) and 14 (governing law and forum, Spanish law, courts of Barcelona) apply to these terms.
