Enterprise privacy policy
& data sovereignty.

Section 01 // Data sovereignty

Zero-surveillance thesis

1.1 Sovereign engineering philosophy

Under statutory legal definitions established by the Digital Personal Data Protection (DPDP) Act 2023, Lekuko acts as a Data Fiduciary solely for inbound corporate consultation data collected via lekuko.com/contact. For client operational infrastructure, including deployed Edge AI vision systems, computer vision models and enterprise software nodes, Lekuko operates as a Data Processor under non-custodial telemetry terms.

Operational processing is described as occurring locally within the physical perimeter of the client's deployment hardware or localized server infrastructure. Raw video streams, optical frames, sensor data and internal corporate records are processed within localized edge hardware nodes and do not cross foreign or public network pipelines. Lekuko states that it maintains no central cloud repositories of client operational data.

1.2 Zero-resale & anti-monetization commitment

Lekuko prohibits commercialization of client telemetry and institutional data assets. The stated guarantees are:

• Zero metadata monetization: client technical parameters, system constraints, physical architecture designs and operational telemetry are not to be sold, leased, rented or exchanged for commercial gain.
• Zero third-party broker integration: inbound intake submissions and system briefs are to be isolated from ad-tech networks, external tracking pixels, data brokers and third-party commercial analytics engines.
• Role-based internal isolation: access is governed by zero-trust Role-Based Access Control (RBAC); submissions are accessible only to assigned architectural leads evaluating system viability.
• Absolute asset confidentiality: industrial workflows, mechanical CAD schematics, clinical ERP schemas and proprietary custom algorithms remain the exclusive intellectual property of the client entity.

Section 02 // Technical telemetry

Intake data & operational telemetry

2.1 Inbound B2B consultation data

When a client entity initiates a B2B technical briefing through lekuko.com/contact or transfers encrypted structural assets through AES-256 secure transfer channels, Lekuko acts as a Data Fiduciary collecting data restricted to project evaluation requirements:

• Corporate identity data: enterprise legal name, operating jurisdiction, corporate email address and authorized point-of-contact details.
• Systemic scope & parameters: technical requirements, spatial and physical constraints, industrial floor parameters and deployment timelines.
• Domain-specific operational parameters: high-level parameters such as serial-level inventory structures, clinical EMR/audiology practice workflows or high-speed manufacturing conveyor constraints supplied for evaluation.

2.2 Edge & IoT operational telemetry

For deployed client hardware, including Edge ANPR units, optical defect detection systems and physical mechatronic controllers, Lekuko describes its role as Data Processor operating under non-custodial parameters:

• Volatile memory register isolation: optical frame buffers, sensor feeds and inference evaluations execute in volatile SRAM/DRAM registers and are not swapped or written to non-volatile flash storage or disk during the execution cycle.
• Sub-12ms payload transmission: processing executes locally on edge hardware such as Nvidia Jetson modules, System-on-Modules or custom SOM PCBs. Following local evaluation, an encrypted minimal payload (<2KB JSON) is sent to localized servers within an execution/transmission window under 12 milliseconds.
• Zero persistent cloud video storage: optical feeds are flushed from volatile registers after inference. Raw visual telemetry is not transmitted to external cloud infrastructure or persistent remote storage.
• Ephemeral debug logs: system-health telemetry such as core temperatures, thermal dissipation metrics and voltage stability logs is stored locally in volatile memory for rolling diagnostics before deletion.

2.3 Data stream comparison

Section 03 // Confidentiality

Anonymization & NDA protection

3.1 MNDA superseding authority

Upon formal engagement or execution of a Mutual Non-Disclosure Agreement (MNDA) between Lekuko and a client entity, the explicit contractual terms of that MNDA take precedence over the dynamic policies stated on lekuko.com. Structural briefs, hardware parameters, source code and deployment telemetry remain protected under binding contractual NDA terms.

3.2 Case study anonymization protocol

To demonstrate execution capabilities without violating client NDAs or compromising proprietary competitive advantages, technical case studies published on lekuko.com are described as subject to descriptive and algorithmic sanitization. Published deployment IDs map to the following domains:

• ANPR-SYS-01: Edge AI / vehicle surveillance; edge OCR, localized tensor processing and encrypted payload transmission.
• IND-DEFECT-02: computer vision / industrial manufacturing; micro-defect recognition on high-speed conveyor belts with pneumatic rejection under variable lighting.
• HEALTH-ERP-03: enterprise software / healthcare EMR; multi-branch clinical audiology workflows, patient CRM routing and serial-level device inventory tracking.
• MECH-ENV-05: mechanical engineering / physical hardware; passive thermal dissipation, CFD modeling and IP67 weather-proof outdoor edge-AI enclosures.

3.3 Data masking requirements

Prior to public release of any deployment briefing or technical case study, the policy specifies this four-step sanitization sequence:

1. Corporate identity stripping: remove corporate names, subsidiary brand identities, trademarked terms and organizational nomenclature.
2. Geographic & network isolation: redact installation coordinates, IP addresses, server topology naming and internal network identifiers.
3. Parameter generalization: convert proprietary throughput, financial metrics and operational yield numbers into abstract ratios and standardized benchmarks.
4. Visual & schematic abstraction: remove raw optical imagery, hardware serial markings and live client UI layouts in favor of generic topology diagrams, unbranded wireframes and abstracted CAD vectors.

Section 04 // Security framework

Cryptography & compliance

4.1 Cryptographic architecture

The policy specifies these cryptographic standards across software modules, embedded hardware and network interfaces:

• Data at rest: centralized database nodes, localized intake repositories and encrypted administrative stores use AES-256.
• Data in transit: external communications, intake submissions and API interactions require TLS 1.3 transport security with HTTP Strict Transport Security (HSTS).
• Payload isolation: edge-to-local-server telemetry uses localized AES-256 payload encryption in minimal JSON structures.

4.2 Data localization & DPDP Act alignment

Lekuko states that it operates in compliance with the Digital Personal Data Protection (DPDP) Act 2023 of the Republic of India. The policy describes primary database hosting, intake servers and localized storage facilities as located exclusively within Surat, Gujarat, Republic of India.

• Data Principal rights: access, update or erasure requests are stated to be processed within a statutory window of 30 days.
• Withdrawal of consent: a Data Principal may withdraw consent for B2B intake processing; the policy says processing ceases and intake records are purged from active repositories within 7 business days.
• Breach notification: for a verified personal-data incident under fiduciary care, Lekuko says it will notify the Data Protection Board of India and affected Data Principals within statutory timelines.

4.3 International regulatory harmonization

For international clients, cross-border corporate acquisitions or multi-jurisdictional B2B software integrations, Lekuko states that it harmonizes its framework with European Union General Data Protection Regulation (GDPR) principles, including:

• Operational isolation of EU-adjacent data subjects within isolated infrastructure partitions.
• Support for cross-border Right-to-be-Forgotten erasure pipelines across non-contractual intake systems.
• No cross-border transfer of sensitive technical telemetry without explicit contractual consent and legal mechanisms.

Section 05 // Client rights & escalation

Formal data-rights requests

5.1 Formal rights executions

Client entities and authorized corporate Data Principals may initiate formal legal-technical requests regarding data held within Lekuko systems:

• Data erasure: request permanent purging of corporate intake records, consultation briefs and technical scope parameters from active intake databases.
• Telemetry audit: request architectural verification of localization, non-custodial status and cryptographic posture of deployed edge telemetry infrastructure.
• Access & rectification: request inspection, review or correction of corporate identity records and system briefs maintained by Lekuko.

5.2 Direct founder escalation endpoints

To execute formal legal rights, request technical compliance verification or submit contractual inquiries, the source policy directs communications to:

• Architectural & data inquiries: support@lekuko.com
• Acquisitions & legal operations: support@lekuko.com
• Physical operational floor: Surat, Gujarat, India.

================================================================================
[ SECURITY PROTOCOL STATUS : ACTIVE / VERIFIED ]
[ DATA RESIDENCY : SURAT, GUJARAT, REPUBLIC OF INDIA ]
[ CRYPTOGRAPHIC STANDARD : TLS 1.3 (TRANSIT) / AES-256 (REST/PAYLOAD) ]
[ NDA ENFORCEMENT : AUTOMATED UPON TECHNICAL BRIEFING SUBMISSION ]
[ STATUTORY WARNING : UNAUTHORIZED SCRAPING, DATA MINING, OR NETWORK
  TELEMETRY INTERCEPTION IS STRICTLY PROHIBITED
  UNDER THE IT ACT 2000 & DPDP ACT 2023. ]
================================================================================