These Enterprise Terms & Conditions and Service Governance Document (“Terms”) govern B2B interactions on lekuko.com/terms (the “Terminal”), as well as formal technical evaluations, engineering engagements and project executions entered into with Lekuko.
Section 01 // B2B engagement threshold
Scope, qualification & evaluation
1. Scope of terms & entity definitions
Lekuko operates as a specialized enterprise engineering conglomerate structured through four distinct, domain-focused divisions:
- Lekuko Solutions: enterprise software, clinical systems, multi-branch healthcare CRM/ERP/EMR platforms and complex operational software architecture.
- Lekuko IoT: true-edge computer vision, localized tensor processing, hardware-adjacent edge artificial intelligence and predictive telemetry logic.
- Lekuko Mechatronics: custom hardware-software bridging, micro-controller/PLC logic, real-time actuation, dynamic feedback loops and kinetic robotic systems.
- Lekuko Mechanics: physical mechanical engineering, SolidWorks CAD assembly design, FEA, CFD thermal modeling, 3D structural prototyping and industrial fabrication.
2. Non-consumer qualification clause
Lekuko's service offerings, engineering capabilities, terminal intakes and architectural consultations are structured strictly for corporate entities, technical directors, CTOs, enterprise clients and authorized B2B representatives. Lekuko explicitly denies access, service applicability and contractual obligations to individual consumer inquiries, generalist retail IT services or personal home-automation requests. Interactions on this Terminal constitute an express legal representation that the interacting party acts on behalf of a registered corporate entity with legitimate B2B operational scope.
3. Mandate evaluation & intake rights
Submissions made via the /contact intake terminal represent non-binding requests for technical evaluation. Lekuko evaluates incoming engineering mandates based on internal benchmarks, including:
- Algorithmic complexity, state-machine dynamics and systemic logic requirements.
- Real-time processing parameters, throughput targets and latency/bandwidth constraints.
- Physical, material, thermal and hardware environmental parameters.
- Current divisional capacity and engineering-floor allocation.
Lekuko reserves the right to accept, decline, defer or ignore any incoming mandate submission without obligation to provide technical justification, administrative explanation or legal recourse.
Section 02 // Intellectual property
Deliverable sovereignty
1. Client ownership & deliverable transfer
Contingent upon full, final and unconditional receipt of cleared funds for all contractual milestones, accompanied by a formal written Deliverable Acceptance Certificate signed by Lekuko, Lekuko transfers full ownership rights to the client for unique, custom-engineered deliverables created explicitly for that client. Transferred intellectual property includes:
- Custom software codebases: application-layer source code, bespoke API integrations, custom user interfaces and client-specific operational workflows.
- Custom electronics & schematics: bespoke PCB layout files, wiring harness blueprints, component BOMs and custom electronic circuit schematics.
- Mechanical CAD assemblies: SolidWorks 3D CAD assemblies, detailed component manufacturing drawings and bespoke physical enclosure housings engineered specifically for the client's environment.
2. Pre-existing IP & core framework sovereignty
Lekuko retains sole ownership of and proprietary rights to its pre-existing intellectual property, core engines, modular libraries, mathematical models, algorithms and fundamental hardware/software frameworks (“Lekuko Core IP”). Reserved proprietary assets include:
- Computer vision processing engines: core optical recognition algorithms, high-speed line-scanning routines and custom license-plate recognition logic.
- Optimization pipelines: proprietary TensorRT execution strategies, hardware acceleration bindings and edge-inference optimization pipelines.
- Edge AI frameworks: custom-trained baseline neural network models, weight distribution matrices and real-time vision processing routines.
- Firmware & embedded architectures: generalized C/C++ micro-controller frameworks, low-level register access routines and RTOS task-scheduling bridges.
- Predictive mathematics & telemetry engines: failure-prediction models, wear-and-tear algorithms, sensor-fusion analytics and cycle-count logic.
- Enterprise software modules: core ERP structural frameworks, serialized inventory tracking logic, RBAC modules and automated audit logging engines.
Embedded license grant
When Lekuko Core IP is integrated into a client deliverable, Lekuko grants the client a non-exclusive, perpetual, enterprise-wide, royalty-free license to execute and utilize the embedded Core IP solely as integrated within the delivered custom physical or digital system. The client shall not reverse engineer, decompile, extract, disassemble or license Lekuko Core IP independently of the unified deliverable.
Section 03 // Confidentiality governance
MNDA priority & anonymization
1. Binding confidentiality obligations, MNDA priority & data localization
Technical briefings, architectural diagrams, network topological flows, CAD parameters, operational bottlenecks and corporate metrics transmitted via lekuko.com or direct operational communications are governed by enterprise confidentiality standards. Neither party shall disclose, publish or distribute non-public technical data received during mandate evaluation or contract execution.
In the event of a conflict between these web-based confidentiality terms and a fully executed formal bilateral Master Non-Disclosure Agreement (MNDA) or specific project contract, the executed MNDA or project contract takes precedence.
Lekuko states that it complies with Indian data-localization standards, including the DPDP Act. As a baseline operational commitment, it utilizes localized server infrastructure within the Republic of India and in-country payload routing as its primary default for telemetry and data transfers, unless explicitly mandated otherwise by an international client's operational specifications.
2. Anonymized case study & technical briefing protection
Lekuko displays production briefings and deployment case studies, including ANPR-SYS-01, IND-DEFECT-02, HEALTH-ERP-03 and MECH-ENV-05. Published technical metrics, physical speed claims and architectural topology diagrams represent anonymized execution data. Client identities, deployment locations and proprietary brand names are stated to be scrubbed to protect confidentiality while demonstrating engineering capabilities.
Section 04 // SLAs, testing & limits
Verification protocols & liability boundaries
1. Testing protocols & execution standards
| Department division | Testing & validation protocol |
|---|---|
| Lekuko Solutions | Localized staging database isolation, RBAC security auditing, automated SLA escalation logging, dynamic load and high-concurrency stress testing. |
| Lekuko IoT | Localized laboratory inference-speed verification, edge-tensor hardware performance tuning, hardware-level AES-256 payload-encryption checks and variable ambient-lighting simulation. |
| Lekuko Mechatronics | Sub-millisecond signal-timing validation, closed-loop kinetic feedback testing, real-time controller-latency verification, dynamic torque and load-balancing checks under RTOS constraints. |
| Lekuko Mechanics | SolidWorks FEA structural-load testing, CFD thermal-dissipation modeling, physical vibration-dampening checks and environmental weather-seal validation (e.g., IP67 specifications, HP MJF PA12 Nylon thermal-tolerance testing). |
2. Liability boundaries & operational limits
To the maximum extent permitted by applicable law, Lekuko disclaims liability for system disruptions, physical hardware damage, kinetic failures or computational errors resulting from:
- Deployments of edge AI hardware or mechatronic units in unverified, uncalibrated or unauthorized external environments exceeding agreed thermal, kinetic, environmental or voltage specifications.
- Unauthorized client or third-party intervention, including overflashing custom bootloaders or modifying low-level register maps; altering PWM timing, torque limits, feedback values or control loops; or bypassing, blocking or altering thermal dissipation mechanisms in environments exceeding 50°C ambient temperature.
- External network interference, local ISP outages or third-party cloud compute infrastructure failures.
- Physical power-delivery fluctuations, electrical surges, phase failures or inadequate facility grounding on the client's premises.
- Unauthorized client or third-party modifications, decompilations or source-code alterations to deployed C/C++ firmware, PCB traces, cloud container topologies or system databases without Lekuko's express written consent.
Lekuko states its operational commitment to localized server deployment within India as its baseline system standard. In no event shall Lekuko's total cumulative financial liability for a claim arising out of or relating to an engagement exceed the total fees paid by the client to Lekuko for the specific deliverable causing the claim.
Section 05 // Legal forum
Governing law & technical dispute resolution
1. Jurisdiction & legal forum
These Terms, project engagements, service-level agreements and legal relations between Lekuko and clients are governed by and construed and enforced in accordance with the laws of the Republic of India, without regard to conflict-of-law principles. Any legal suit, action or proceeding arising out of or relating to these Terms, project mandates or Lekuko's services shall be instituted exclusively in the competent courts situated in Surat, Gujarat, India.
2. Formal technical audit protocol for dispute resolution
For a technical dispute regarding deliverable performance, code architecture, hardware reliability or milestone compliance, the parties must execute the following two-step mechanism before formal litigation or third-party arbitration.
Step 1 // Joint technical audit
Before a formal legal demand or arbitration notice is filed, senior system architects from both Lekuko and the client must convene for a mandatory Joint Technical Audit. The audit must be convened within fourteen (14) calendar days of written notice from either party and concluded within thirty (30) business days. Its scope includes:
- Joint inspection of raw, immutable system logs and automated audit trails.
- Audit of Git repository code commits, branch merges and firmware build histories.
- Analysis of hardware telemetry, power logs and local laboratory benchmark data.
- Evaluation of executed milestone specifications against agreed physical parameters and laboratory test logs.
Step 2 // Binding arbitration
If the Joint Technical Audit does not resolve the dispute within thirty (30) business days of initiation, either party may issue a formal Notice of Binding Arbitration. The matter shall be referred to and finally resolved by binding arbitration in Surat, Gujarat, India, in accordance with the Arbitration and Conciliation Act, 1996, including statutory amendments. The panel shall consist of a sole arbitrator jointly selected by both parties who is professionally conversant with deep-tech, embedded firmware, micro-controller logic and enterprise software engineering protocols.
3. Corporate legal routing details
For formal legal communications, architectural dispute escalations, MNDA submissions or official procurement notices, the source document directs inquiries to:
- Legal & architectural escalations: support@lekuko.com
- Operational execution floor: Surat, Gujarat, India.
- Intake & discovery terminal: lekuko.com/contact