Code of Conduct

Respectful Communication

Everyone interacting with KEEN SYSTEMS PVT LTD should communicate respectfully, clearly, and professionally across live chat, email, calls, meetings, admin tools, support discussions, and project channels.

Disagreement is acceptable. Harassment, intimidation, threats, abusive language, discrimination, personal attacks, or intentionally disruptive behavior is not acceptable.

• Use clear language and provide relevant context.
• Respect time zones, response times, working hours, and agreed support channels.
• Keep project communication focused on the work, risks, decisions, and next steps.

Honesty, Accuracy, and Accountability

Clients, partners, administrators, and team members should provide accurate information and avoid knowingly misleading statements about requirements, approvals, budgets, access, timelines, incidents, or project status.

Our team aims to communicate honestly about scope, constraints, risks, trade-offs, pricing, limitations, timelines, and technical decisions.

• Share changes, blockers, incidents, and risks early.
• Confirm approvals and decisions in writing when they affect project delivery.
• Avoid unrealistic commitments, hidden dependencies, or unclear authority.

Confidentiality and Data Care

Non-public business, technical, financial, personal, system, and project information should be treated with care. Access credentials, source code, databases, private documents, and client records must be handled responsibly.

Sensitive information should be shared only when necessary, only with authorized people, and through appropriate channels.

• Do not publicly disclose confidential project information without approval.
• Do not share passwords, keys, tokens, backups, or production data in unsafe channels.
• Report suspected leaks, unauthorized access, or accidental disclosure promptly.

Responsible Technical Work

Technical work should be performed with appropriate authorization, scope, testing discipline, and respect for system stability. Changes that may affect live systems, data, users, payments, integrations, or compliance should be planned carefully.

We do not support requests intended to harm systems, bypass access controls, steal data, spread malware, impersonate others, or violate laws or third-party rights.

• Get permission before accessing, testing, migrating, scraping, automating, or modifying systems.
• Use staging or test environments where practical before production changes.
• Document important changes, assumptions, risks, and handover details.

Fair Collaboration

Healthy collaboration depends on timely decisions, reasonable feedback, clear acceptance criteria, and respect for the agreed project process.

All parties should work in good faith to resolve misunderstandings, adjust scope where needed, and protect the quality and reliability of the final system.

• Give actionable feedback during review periods.
• Avoid scope changes without discussing impact on cost, timeline, and risk.
• Respect the responsibilities of designers, developers, administrators, suppliers, and client stakeholders.

Inclusive and Safe Environment

We expect a professional environment free from discrimination, harassment, bullying, intimidation, and abusive conduct based on personal characteristics, role, seniority, language, background, nationality, gender, religion, disability, or other protected or personal attributes.

All participants should be able to ask questions, raise risks, and report concerns without fear of retaliation.

Conflicts, Escalation, and Resolution

If a concern arises, raise it early with the project contact, support contact, or company contact so it can be reviewed and resolved constructively.

For serious concerns involving safety, confidentiality, unauthorized access, harassment, fraud, or system risk, contact KEEN SYSTEMS PVT LTD directly.

• Email: info@keensystems.lk
• Phone: +94 71 249 4975

Enforcement

KEEN SYSTEMS PVT LTD may pause communication, refuse requests, remove access, close live chat, suspend support, terminate a project channel, or take other reasonable action where conduct creates risk or violates this Code of Conduct.

Enforcement decisions will consider the severity, context, legal obligations, client safety, business risk, system security, and whether the conduct is repeated or intentional.