Governance & ethics

We hold ourselves accountable

Ethics, security, privacy, quality, and legal compliance are not marketing lines — they are how we run projects, treat people, and stand behind our deliveries. This page summarises the standards we apply and expect from everyone who works with CodeLK (Private) Limited.

Core values

What we stand for

Nine principles that shape how we hire, deliver, and lead — from Homagama to every client engagement we undertake globally.

Integrity First

We act honestly with clients, colleagues, and regulators. We do not misrepresent capabilities, timelines, or risks to win work. Honest disclosure of scope gaps is a professional obligation, not a commercial risk.

Radical Transparency

We share material facts early — scope changes, dependencies, setbacks, and security findings. Stakeholders should know what we know, when we know it. Delayed disclosure of known risks is a governance failure.

People First

Psychological safety, fair compensation, and genuine growth paths matter. Short-term business metrics never justify harm to dignity, wellbeing, or lawful entitlements. Managers are held to a higher standard of conduct, not a lower one.

Continuous Improvement

We review incidents, retrospectives, and client feedback systematically. Governance is a living discipline — policies are versioned, owners are named, and reviews are scheduled, not deferred indefinitely.

Responsible Technology

Privacy by design, security by default, and accessibility are not optional add-ons. We perform Data Protection Impact Assessments for high-risk processing, conduct threat modelling before delivery, and test accessibility against WCAG baselines.

Community Impact

We invest in local talent, internships, and technology education. Sri Lanka is our home base and we aim to strengthen its engineering ecosystem — through hiring, mentorship, and partnerships with universities and vocational institutions.

Quality & Craft

Peer review, testing discipline, and maintainable architecture are professional obligations. We do not knowingly ship critical defects to production and we do not hide known technical debt from clients whose operations depend on the system.

Accountability

Roles, approval chains, and audit trails are explicit for regulated work. Individuals take ownership; the organisation backs them with process, tooling, and escalation paths. Accountability without authority is unfair — we ensure both exist.

Respect & Inclusion

We welcome diverse perspectives and enforce zero tolerance for harassment and discrimination. Merit and conduct define advancement. Unconscious bias in hiring and promotion is an active problem we address through structured process design, not goodwill alone.

Standards & frameworks

How we align with recognised standards

We adopt internationally recognised practices and control themes appropriate to each project and client sector. Alignment describes how we work; it does not replace formal certification unless separately published for a specific product or engagement.

Sri Lanka PDPA (No. 9 of 2022)

We align processing activities to lawfulness, purpose limitation, data minimisation, accuracy, storage limitation, and integrity/confidentiality. Record of Processing Activities (ROPA) is maintained for regulated engagements. Data Protection Impact Assessments (DPIAs) are conducted for high-risk processing.

GDPR-Style Controls for International Clients

For EU-connected clients or data subjects, we apply GDPR-equivalent safeguards: Standard Contractual Clauses (SCCs) for cross-border transfers, data subject rights workflows (access, rectification, erasure, portability), and documented lawful bases.

Information Security Practices

We do not claim certification for the company as a whole unless separately published for a specific product.

Quality Management Mindset

Requirements traceability, change control, release checklists, and client-accepted acceptance criteria are maintained alongside customer satisfaction measurement and non-conformance tracking.

OWASP Secure SDLC

Threat modelling, OWASP Top 10 mitigations, dependency vulnerability scanning (SCA), static analysis (SAST), and penetration-testing readiness are integrated into delivery. Security findings are triaged, prioritised by risk, and tracked to closure.

WCAG Accessibility Awareness

Public-facing and enterprise operator interfaces are designed and tested with WCAG 2.1 Level AA checkpoints where projects require inclusive design. Colour contrast, keyboard navigation, ARIA labels, and focus management are reviewed during QA.

Responsible & Ethical AI

Where AI/ML is used in deliverables, we apply proportionality, human oversight for high-impact outcomes, bias assessment for decision-affecting models, and clear documentation of limitations. AI-generated content and code undergoes human review before production use.

Policies

Our commitments, in full

Select a topic for the complete policy text. These statements summarise internal policy intent and are reviewed annually. Contractual obligations in your agreement with CodeLK prevail where they differ from this summary.

Every employee, contractor, and representative of CodeLK (Private) Limited is expected to uphold professional behaviour that protects people, clients, and the reputation of the firm. This policy applies in all work contexts: in the office, remotely, on client premises, at events, and in online communications.

Treat everyone with dignity and courtesy in person, in written communications, in code review, and in virtual collaboration. Personal attacks, intimidation, passive-aggressive behaviour, and deliberate exclusion are unacceptable regardless of seniority.

Harassment, discrimination, or bullying based on gender, gender identity, ethnicity, religion, age, disability, sexual orientation, marital status, pregnancy, national origin, or any other protected characteristic is strictly prohibited and constitutes gross misconduct. Incidents may result in immediate termination and referral to the Sri Lanka Police or relevant authorities.

Substance use that impairs judgement, safety, or professionalism during work hours, on travel, or on client premises is prohibited. Prescription medication is respected; impairment is not excused by it.

Time reporting, expense claims, credentials, certifications, and test results must be accurate and complete. Falsification of any professional record constitutes fraud and grounds for termination and potential criminal referral.

Company and client systems are used only for legitimate business purposes. Personal use must be reasonable, lawful, not harmful, and consistent with applicable acceptable-use policies. Cryptocurrency mining, personal commercial activity, and circumventing security controls on company systems are prohibited.

Confidential information — whether about CodeLK, a client, a colleague, or a business partner — must not be disclosed outside authorised channels. This includes social media, personal devices used outside data handling agreements, and conversations in public spaces. Confidentiality obligations survive employment termination.

Managers and senior staff are held to a heightened standard: they must model these expectations in their own conduct and act promptly on concerns raised by their teams.

CodeLK (Private) Limited competes on merit and delivers value through engineering excellence. Winning business through improper payments, concealed inducements, or unfair competitive practices is prohibited in all jurisdictions and under all circumstances.

Bribery in any form — offering, promising, giving, requesting, or accepting — of public officials, procurement personnel, or private business counterparties is prohibited. This includes direct payments and payments through intermediaries, agents, or subcontractors.

Facilitation payments intended to expedite routine governmental actions are prohibited even where local custom might normalise them. Employees encountering such requests must report them immediately to compliance@codelk.com.

Gifts and hospitality must be modest, infrequent, transparent, and recorded in the gifts register when above nominal thresholds (currently LKR 5,000 for gifts; LKR 15,000 for hospitality per event). No gift or hospitality may be offered or accepted when a procurement decision, approval, or regulatory outcome is pending.

Conflicts of interest must be declared in writing before they deepen. This includes undisclosed financial interests in suppliers, clients, or competitors; family members employed by or owning stakes in client entities; and board or advisory roles held concurrently. Declarations are logged and reviewed annually.

We respect antitrust and fair competition norms: no price-fixing, bid-rigging, market allocation agreements, or exchange of competitively sensitive information with competitors. Employees attending industry events or trade associations must not engage in discussions that could constitute anti-competitive coordination.

Sales materials, proposals, benchmark results, and case studies must be truthful, evidence-based, and not misleading. Performance claims are substantiated. Testimonials use client-approved language. We do not disparage competitors with unverifiable claims.

CodeLK (Private) Limited is committed to respecting internationally recognised human rights and maintaining responsible labour practices across our operations and supply chain, consistent with the UN Guiding Principles on Business and Human Rights and applicable Sri Lankan labour law.

We reject child labour (any person under 16, or under 18 for hazardous work), forced labour, debt bondage, and human trafficking. New vendor relationships involve a baseline check for modern slavery risk indicators proportionate to the nature of the engagement.

Working hours, rest periods, and overtime are governed by the applicable provisions of the Shops and Office Employees Act, the Factories Ordinance, and individual employment agreements. Coerced or unpaid overtime is prohibited. Flexible working arrangements are managed transparently and fairly.

Freedom of association and the right to collective bargaining are respected within the framework of Sri Lankan law. Employees may raise workplace concerns through HR, line management, or the whistleblowing channel without fear of retaliation.

Wages are paid in full and on time, meeting or exceeding legal minimums. All deductions (EPF, ETF, loans, advances) are lawful, authorised, documented, and reflected accurately in payslips. We do not hold employee identification documents or deposits as a condition of employment.

Physical and digital working environments are safe: ergonomic workstations, appropriate access controls, emergency procedures, and a documented escalation path for health and safety concerns. Near-misses and incidents are reported, investigated, and actioned.

We publish a modern slavery and human trafficking statement annually and conduct periodic supply-chain due diligence for high-risk vendor categories. Suppliers are contractually required to meet equivalent labour and human rights standards.

Speaking up early prevents harm to people, clients, and the organisation. CodeLK (Private) Limited protects individuals who report concerns in good faith — including employees, contractors, former employees, clients, and members of the public.

Reports may be submitted to: (1) direct line management; (2) HR at biz@codelk.com; (3) the compliance channel at compliance@codelk.com; or (4) escalated to designated senior leadership for serious matters. Anonymous reports are accepted where sufficient detail allows fair investigation.

Retaliation against a reporter or witness — including demotion, reduced hours, exclusion from assignments, hostile treatment, denial of benefits, negative references, or any form of pressure to withdraw a report — is prohibited and treated as a separate disciplinary offence with the same severity as the underlying conduct.

All reports are acknowledged within 48 business hours. Investigations are conducted promptly, fairly, and with appropriate confidentiality. Relevant evidence is preserved from the point of report. Outcomes are documented; reporters receive a summary response within a reasonable period.

Natural justice applies: individuals subject to an allegation are informed of the substance of the concern (unless doing so would compromise an investigation or the safety of a reporter) and given a fair opportunity to respond.

Where applicable law requires or permits disclosure to regulators (e.g. CBSL, FIU, Sri Lanka Police), we cooperate fully while taking all reasonable steps to protect reporters from unlawful exposure. Legal professional privilege is preserved in appropriate circumstances.

Malicious, knowingly false reports submitted with intent to harm an identified individual are themselves a conduct matter. The threshold for acting on good-faith reports that later prove unsubstantiated is different — good faith is assessed by what the reporter reasonably believed at the time of reporting.

Personal and organisational data is both a business asset and a protected right of the individuals it concerns. CodeLK (Private) Limited handles data with legal, technical, and organisational controls aligned to the Sri Lanka Personal Data Protection Act No. 9 of 2022 and GDPR-equivalent standards for international clients.

We maintain a Record of Processing Activities (ROPA) identifying: (a) categories of personal data processed; (b) purposes and lawful bases; (c) data subjects; (d) recipients; (e) retention periods; and (f) cross-border transfer mechanisms. The ROPA is reviewed at least annually and when material processing changes occur.

Lawful bases for processing are identified before processing commences. For consent: it must be specific, informed, freely given, and capable of withdrawal without detriment. For legitimate interests: a Legitimate Interest Assessment (LIA) is documented to demonstrate that interests are not overridden by data subject rights.

Data subject rights (access, rectification, erasure, restriction, portability, and objection) are actionable within the PDPA-prescribed timelines. Internal workflows, including identity verification, cross-system location of records, and response drafting, are documented and tested.

Data Protection Impact Assessments (DPIAs) are conducted before commencing high-risk processing: large-scale processing of sensitive data; systematic monitoring of individuals; new technologies with privacy-invasive potential; and profiling with significant legal or equivalent effects.

Encryption in transit (TLS 1.2 minimum; TLS 1.3 preferred) and encryption at rest (AES-256 or equivalent) are applied for systems processing personal data. Key management follows least privilege and documented rotation schedules.

Cross-border data transfers are assessed against PDPA Part V restrictions. For transfers to jurisdictions without an adequacy decision, appropriate safeguards (contractual clauses, binding corporate rules, or equivalent mechanisms) are documented and in place before transfer.

Personal data breaches are triaged under an Incident Response Plan. Where a breach is likely to result in a risk to the rights of data subjects, notification to the Data Protection Authority and affected individuals is prepared within the regulatory window (targeting 72 hours for high-risk breaches aligned to GDPR practice; PDPA timelines as gazetted). Breach records are retained for a minimum of five years.

Security is an engineering discipline and a business obligation — not a gate added at the end of a project. CodeLK (Private) Limited integrates security controls into how we build, deploy, monitor, and respond throughout the software lifecycle, informed by OWASP guidance, ISO 27001 control themes, and client-specific regulatory requirements.

Access to source code, production environments, CI/CD pipelines, and client data follows least privilege, role separation, and mandatory multi-factor authentication (MFA) where the system supports it. Privileged access (admin, production DB, secrets) requires documented justification and periodic review.

Secrets management: API keys, database credentials, certificates, and signing keys are never committed to source control in plaintext. We use secrets managers (AWS Secrets Manager, HashiCorp Vault, or environment-specific secure stores). Automated secrets scanning runs in CI pipelines.

Software Composition Analysis (SCA) identifies third-party dependency vulnerabilities. Critical and high CVEs are treated as release blockers; remediation SLAs are: critical ≤ 3 business days, high ≤ 10 business days, medium within the next sprint.

Static Application Security Testing (SAST) and, for applicable projects, Dynamic Application Security Testing (DAST) are integrated into pipelines. OWASP Top 10 categories — including injection, broken access control, cryptographic failures, and security misconfiguration — are addressed in secure coding training and code review.

Threat modelling or abuse-case analysis is conducted for new features handling financial data, health information, authentication flows, and personal data. The output informs architecture decisions, not just test cases.

Penetration testing or independent security assessments are commissioned for products and client engagements where risk, regulatory requirements, or contract terms require them. Findings are tracked in a remediation register; critical findings are not closed by risk acceptance without explicit client sign-off.

Security incident response: a documented IR plan covers detection, containment, eradication, recovery, and post-incident review. Incident owners, communication trees, and regulatory notification procedures are defined. Exercises (tabletop or simulated) are conducted at least annually.

Logging and monitoring are designed to support detection and forensic investigation without excessive personal data collection. Logs are retained for a period consistent with operational need, contractual requirements, and privacy obligations.

CodeLK (Private) Limited applies a structured risk management approach to delivery, operational, and strategic risks. Risk management is not a compliance exercise — it is how we protect client outcomes, business continuity, and the people who depend on the systems we deliver.

Risk identification is conducted at project inception (risk register populated during kick-off), during key phase transitions, and whenever material scope, technology, or dependency changes occur. Risks are documented with description, likelihood, impact, risk owner, and mitigation/contingency actions.

Risk categories: delivery (scope creep, dependency failures, resource gaps), technical (architectural risk, technology limitations, security vulnerabilities), regulatory (applicable law changes, compliance gaps at go-live), operational (business continuity, third-party reliability), and reputational.

Risk scoring uses a 5×5 likelihood/impact matrix. Risks rated high or critical require escalation to project sponsors within one business day, documented treatment decisions, and progress review at each project checkpoint.

Residual risk acceptance: risks that cannot be fully mitigated are formally accepted in writing by an authorised client representative. Acceptance does not mean the risk is ignored — it means the risk owner has made an informed decision with documented justification.

Business Continuity and Disaster Recovery planning is conducted for systems handling critical financial, health, or public-service workloads. RTO and RPO targets are agreed with clients, architecturally supported, and periodically tested. Test results and gaps are reported honestly.

Third-party and supply chain risk: key sub-processors, cloud providers, and tool vendors are assessed for security posture, financial stability, regulatory compliance, and geographic concentration risk. Concentration risk — heavy reliance on a single cloud region or vendor — is explicitly flagged in delivery documentation.

Predictable delivery and verifiable quality reduce risk for clients and teams. Our QA standards define minimum expectations — projects may apply additional controls based on regulatory requirements, client contracts, or risk classification.

Requirements and acceptance criteria are documented, agreed, and baselined before large build phases begin. Change requests are subject to formal impact analysis covering scope, schedule, cost, and risk. Scope creep without impact assessment is a delivery risk that CodeLK will surface proactively.

Version control (Git) with a documented branching strategy (feature branches, protected main/release branches, mandatory pull request review) is mandatory for all production-bound code. Direct commits to main without review are prohibited.

Automated testing (unit, integration, and where appropriate end-to-end) is required for critical paths. Test coverage is not a vanity metric — it is calibrated to risk: financial calculations, authentication logic, and compliance-relevant workflows receive priority coverage.

Definition of Done includes: passing automated tests, peer code review, security check completion, documentation updated, rollback plan documented for risky releases, and client-agreed acceptance criteria verified.

Technical debt is visible in the backlog and addressed incrementally on an agreed schedule. We do not hide known defects, performance bottlenecks, or architecture constraints from clients who would be materially affected. A known-defects register is maintained for all active products.

Environment separation (development, staging/UAT, production) is enforced. Production data is not used in non-production environments without explicit client consent, documented legal basis, and data minimisation/anonymisation. Exception requests require written approval from the designated client data owner.

Release management: all production deployments require a documented deployment checklist, rollback procedure, post-deployment verification, and monitoring window. Zero-downtime deployment patterns (blue-green, canary) are used where client SLAs require uninterrupted service.

Clear terms on ownership, licensing, and reuse protect both CodeLK and our clients. Ambiguity in IP terms is a frequent source of post-delivery disputes — we address it in the Statement of Work, not after.

Statements of Work define: deliverables and acceptance criteria; warranties and defect liability periods; IP ownership (work-for-hire assignment vs. licence grant vs. retained background IP); liability caps; data handling obligations; and confidentiality terms. Material deviations from these terms require written amendment.

Background IP: tools, frameworks, libraries, and methodologies CodeLK developed independently and brings to an engagement are retained by CodeLK. Where client use of these is commercially material, licence terms are documented in the engagement agreement.

Client pre-existing IP and confidential data are used only within the scope of the engagement. At contract end, client IP is returned or securely destroyed per agreed procedures, within the timeframe specified in the contract (default: 30 days after final delivery).

Open-source licence compliance: all open-source components are used in compliance with their licence terms. Copyleft licences (GPL, AGPL) are flagged during architecture review for deliverables where licence propagation affects client distribution rights. Licence notices and attribution requirements are preserved.

We do not incorporate code of unclear provenance, AI-generated code without review, or material from previous client engagements into new deliverables without ensuring no confidentiality or ownership conflicts exist.

Commercial agreements: we will not accept engagement terms that require us to act unlawfully, suppress regulatory reporting, or misrepresent the nature of work product to third parties. Pressure to do so is treated as a client escalation matter.

CodeLK remains accountable for work performed on our behalf. Third parties engaged in delivery or data processing must meet our minimum standards, and we contract for compliance rather than assuming it.

Subcontractors and delivery partners are subject to non-disclosure, information security, data protection, and conduct obligations that are back-to-back with client agreements where client approval is given. We do not pass off subcontracted work as entirely in-house without client knowledge.

Vendor due diligence covers: technical capability assessment, relevant certifications or security questionnaire completion, financial stability check for long-term engagements, and modern slavery / labour rights attestation for staffing-category suppliers.

Data processors (cloud providers, SaaS tools, analytics platforms) that handle personal data on CodeLK or client behalf are assessed against applicable PDPA data processor obligations. Data Processing Agreements (DPAs) are in place before processing begins.

Material subcontracting: client approval is required before subcontracting material delivery components where the engagement agreement or client policy requires it. "Material" is defined as work representing ≥20% of effort or any work involving client production data or regulated system access.

Offshore and cross-border delivery: geographic location of delivery personnel is disclosed to clients when it affects data residency, regulatory expectations, or support hours. We do not route client data through jurisdictions prohibited under client agreements or applicable law without explicit written consent.

Vendor exit planning: for engagements with strategic or critical vendors, CodeLK maintains documented exit plans and data portability provisions to prevent unhealthy dependency. This is reviewed annually for tier-1 suppliers.

When things go wrong, how an organisation responds determines the outcome for affected people and business continuity. CodeLK maintains documented incident response procedures for security events, service disruptions, and data breaches — tested and ready to activate.

Incident classification: P1 (critical — service unavailable, active security breach, data loss); P2 (high — significant performance degradation, suspected breach, compliance violation); P3 (medium — degraded functionality, potential security misconfig); P4 (low — minor service impact, informational). P1 and P2 trigger immediate escalation to the incident response team and relevant client contacts.

Incident response phases: Detection (automated monitoring, user report, or third-party notification); Triage (severity classification, initial containment); Containment (isolate affected systems, revoke compromised credentials, preserve evidence); Eradication (root cause remediation); Recovery (staged restoration with post-restoration verification); Post-Incident Review (root cause analysis, control improvements, lessons learned documented within 5 business days).

Data breach response: breaches or suspected breaches involving personal data trigger a parallel PDPA/regulatory notification assessment from the first notification. Breach notification decisions are not deferred pending full root cause analysis — risk is assessed on available information at each 24-hour interval.

Incident evidence: system logs, access records, configuration snapshots, and communications relevant to an incident are preserved in tamper-evident storage immediately on classification as P1 or P2. Evidence preservation takes precedence over system restoration where legally relevant.

Client incident communication: clients are notified of P1 and P2 incidents affecting their systems within the SLA timeframes documented in their engagement agreement (default: P1 within 1 hour; P2 within 4 hours). Communication is factual, acknowledges uncertainty clearly, and provides estimated resolution timelines based on current information.

Business Continuity Plan (BCP) and Disaster Recovery (DR) documentation is maintained for CodeLK internal systems and, where contracted, for client-hosted solutions. BCP/DR exercises are conducted annually; results, gaps, and remediation actions are documented.

Digital services carry a carbon and material footprint. CodeLK (Private) Limited pursues practical environmental responsibility across our operations, procurement, and the architectural advice we give clients.

Remote-first and cloud-based collaboration reduces commute emissions and office footprint where operationally appropriate. Remote working policy includes guidance on energy-efficient home working and discourages unnecessary travel.

Cloud workload efficiency: right-sizing, autoscaling policies, scheduled non-production environment shutdowns, and use of cloud provider sustainability features (AWS Graviton instances, renewable energy region selection) are encouraged in delivery and operations.

Hardware procurement: energy-efficient ratings (ENERGY STAR or equivalent), repairability, and expected lifecycle are factors in procurement decisions. Premature replacement of functional equipment is avoided. Manufacturer sustainability commitments are a weighted factor.

End-of-life electronics are disposed of through ICTA-recognised or equivalent certified e-waste channels. No electronic equipment is discarded in general waste. Data destruction (DoD-standard wipe or physical destruction for sensitive media) precedes disposal.

Paper reduction target: 80% reduction in paper use for internal operations by end of 2025 through digital workflows, e-signatures, electronic document stores, and electronic meeting practices. Progress is reported in the annual CSR summary.

We encourage clients to consider the environmental impact of architectural choices: database right-sizing, efficient query optimisation, image and asset compression, and CDN use reduce both operational costs and compute energy consumption.

We aim to be a positive employer and digital citizen in Sri Lanka and in the communities where our people live. CSR at CodeLK is operationalised in hiring, community investment, and how we structure our workplace — not limited to annual charity donations.

Equal opportunity: hiring, promotion, compensation, and development decisions are made on role-relevant criteria — skills, demonstrated performance, and conduct. We maintain salary bands, review pay equity annually, and address unexplained variance.

Diversity in pipeline: we actively seek applications from underrepresented groups, design job descriptions to reduce unnecessary experience inflation, and use structured interview criteria to reduce evaluator bias. We publish our hiring statistics in the annual CSR summary.

Technology education investment: a portion of net revenue supports internship programmes, technical mentorship, guest lectures at universities, and co-creation of curriculum with educational partners aligned to ICT and SLQF standards.

Pro-bono capacity: engineering capacity may be allocated to registered non-profits, NGOs, or community-benefit initiatives on a case-by-case basis subject to a brief governance review. Applications are welcomed at biz@codelk.com.

Mental health and wellbeing: we provide access to mental health resources, maintain reasonable workload norms, and review project staffing when sustained overtime indicators are detected. Manager training includes psychological safety and wellbeing identification.

Annual CSR summary: we publish highlights covering community investment, workforce diversity, environmental progress, and governance updates annually. The summary is made available on request and on this site when published.

CodeLK (Private) Limited operates within Sri Lankan law and within the client-specific regulatory frameworks relevant to each engagement. This section summarises our legal and regulatory standing.

Company registration: CodeLK (Private) Limited, PV 00234171, registered under the Companies Act No. 7 of 2007 (Sri Lanka). Statutory records, annual returns, and filings are maintained accurately and submitted to the Registrar of Companies within prescribed periods.

Tax compliance: income tax, VAT, and withholding tax obligations are maintained with the Inland Revenue Department (IRD). Employment tax (PAYE, EPF, ETF) is calculated, deducted, and remitted accurately and on time.

ICTA alignment: software development and ICT service delivery practices align with the Information and Communication Technology Agency of Sri Lanka (ICTA) guidance and Sri Lanka ICT sector norms where applicable to our service categories.

Sector-specific regulatory mapping: for each client engagement in a regulated sector (banking, insurance, healthcare, education), applicable regulatory requirements are mapped at project inception. Control gaps identified against go-live readiness are escalated to the client sponsor in writing before launch.

Independent assurance: security assessments, code reviews, or compliance audits by qualified third parties are commissioned for products and engagements where risk, contract terms, or regulatory requirements warrant them. Findings are disclosed to the contracting client.

Records retention and legal hold: retention schedules balance operational need, contractual obligation, litigation hold requirements, and PDPA minimisation. When a legal hold is active, automated deletion routines affecting relevant records are suspended until the hold is lifted.

Contact for legal, compliance, and governance enquiries: compliance@codelk.com. General business enquiries: biz@codelk.com. Due diligence questionnaires, DPIAs, and assurance requests: compliance@codelk.com.

Get in touch

Let's build your next system together.

Tell us about the system you need — we'll reply within one business day. Or write to biz@codelk.com.

Contact us