Developer Terms & Conditions

1. Developer Registration & Eligibility

1.1 Registration Requirement

Any developer (individual or agency) working with Evanto must undergo a registration or onboarding process, which may include:

• Providing true and accurate personal or business details.
• Sharing relevant technical portfolio, experience, or sample work.
• Accepting these Developer Terms & Conditions and any project-specific agreements.

1.2 Unknown / New Developers

For developers who are previously unknown to Evanto or Banglar Katha:

• Additional verification or screening may be required.
• Trial assignments, sample tasks, or probationary periods may be used to evaluate skills and reliability.
• Access to sensitive code, data, or systems may be limited until trust is established.

1.3 Immediate Assignment After Registration

Once registration is completed and a developer is approved, suitable tasks or projects (including customization work) may be assigned immediately based on skill set and availability, subject to separate work orders or contracts.

2. Scope of Work & Project Types

2.1 Ready-Made Products

Developers may be engaged to build, enhance, or maintain ready-made digital products such as:

• Scripts, themes, templates, plugins, modules, and tools.
• Pre-configured web applications and dashboards.
• Reusable components for Evanto’s marketplace offerings.

2.2 Custom Web Apps & Client Projects

Developers may also work on custom projects for clients, including:

• Full website building and development.
• Custom functionality, integrations, and API-based solutions.
• Industry-specific solutions (e-commerce, portfolio, business, education, healthcare, etc.).

2.3 Support & Maintenance

Work may include bug fixes, performance optimization, feature updates, migration, and long-term maintenance tasks.

3. Credentials, Confidentiality & Intellectual Property

3.1 Accurate Credentials

Developers must provide accurate identity and contact information, and must not impersonate any other individual or entity.

3.2 Confidentiality Obligations

Developers agree to:

• Keep all source code, project details, client information, and internal processes strictly confidential.
• Not share, expose, or publish any proprietary information outside Evanto/Banglar Katha without written permission.
• Use access credentials (e.g., Git, server, panel) solely for assigned tasks and never share them with unauthorized parties.

3.3 Intellectual Property Ownership

Unless explicitly agreed otherwise in writing:

• All code, designs, and work products created under Evanto projects are the property of Evanto/Banglar Katha.
• Developers grant Evanto a full, irrevocable, worldwide license to use, modify, and commercialize the work created for its products and services.
• Developers must not resell or redistribute Evanto-owned work as their own or on other platforms without permission.

4. Quality, Compliance & Technical Standards

4.1 Code Quality & Best Practices

Developers are expected to follow standard coding practices, including:

• Clean, readable, and maintainable code structure.
• Proper documentation and comments where necessary.
• Use of secure, efficient, and scalable patterns.
• Avoiding unnecessary dependencies or hard-coded secrets.

4.2 Legal & Policy Compliance

Developers must ensure that their work:

• Does not include unauthorized or pirated code.
• Respects third-party licenses and open-source obligations.
• Does not include malware, backdoors, or any hidden harmful logic.
• Complies with applicable laws, especially around data protection, security, and content legality.

4.3 No Malicious Activity

Developers must not:

• Insert malicious code, spyware, or hidden tracking mechanisms without disclosure.
• Intentionally degrade, sabotage, or compromise the security of Evanto or client systems.
• Use Evanto-related access for any unauthorized or external activities.

5. Developer Liability & Responsibility

5.1 Responsibility for Work Delivered

Developers are responsible for:

• Ensuring that delivered code runs as reasonably expected in the agreed environment.
• Fixing critical bugs identified within a mutually agreed support window (where applicable).
• Not knowingly introducing security vulnerabilities or legal risks.

5.2 Liability in Case of Misconduct

If a developer’s intentional misconduct, gross negligence, or breach of these terms leads to damage (technical, financial, or reputational), Evanto/Banglar Katha may:

• Terminate the engagement immediately.
• Revoke access to systems and resources.
• Seek legal remedies or compensation as per applicable law and agreements.

6. Assignment & Variable Terms for Custom Work

6.1 Immediate Assignment After Registration

Once a developer has been registered and approved, projects and tasks (including customization work on existing products) may be assigned as per Evanto’s internal needs and scheduling.

6.2 Variation of Terms Based on Customization

For highly customized or complex projects:

• Specific terms (timelines, rates, deliverables, and responsibilities) may be defined in separate work orders, emails, or contracts.
• Additional non-disclosure or non-compete clauses may be applied where sensitive business logic or client information is involved.
• Payment and milestone structures may vary depending on the project scope.

These specific terms will supplement, and in case of conflict may override, the general conditions on this page for that particular project, as clearly communicated.

7. Payments, Invoicing & Dispute Handling

7.1 Payment Terms

Payment structures for developers may include:

• Fixed-price per project or per module.
• Hourly or time-based contracts.
• Milestone-based payments tied to deliverables.

Exact terms are communicated separately and may depend on the nature of work and developer’s engagement model.

7.2 Disputes Over Work Quality

In case of disputes:

• Evanto/Banglar Katha will review the code, deliverables, and agreed requirements.
• Developers may be asked to rectify defects or misalignments without additional cost if they arise from non-compliance with agreed scope.
• Persistent disputes may lead to reduced or withheld payments as per contractual terms.

8. Independence & No Unauthorized Representation

Developers are independent contractors or collaborators and are not authorized to:

• Represent themselves as legal agents or official signatories of Evanto or Banglar Katha.
• Enter into external contracts on behalf of Evanto without written authorization.
• Promise features, timelines, or prices to clients beyond what Evanto has approved.

9. Suspension & Termination of Developer Engagement

Evanto/Banglar Katha reserves the right to suspend or terminate a developer’s engagement if:

• There is a breach of these Developer Terms & Conditions.
• Misconduct, fraud, or malicious behavior is suspected or confirmed.
• Repeated poor-quality work, missed deadlines, or unresponsiveness occurs.

Termination may be immediate in case of serious violations, with access revoked and pending payments handled as per contract and applicable law.

10. Contact & Developer Enquiries

Developers interested in working with Evanto, or existing developers with questions about these terms, may contact:

Please include your name, skills/technology stack, and relevant portfolio or experience details for faster processing.