Developer Rules

1. Freelance Status & No Employment Relationship

1.1 Not a Full-Time Employee

Developers engaged by Evanto work as freelancers / independent contractors. They are not full-time or part-time employees of Evanto or Banglar Katha.

• No employee benefits (such as PF, insurance, paid leave, etc.) are implied or provided unless explicitly agreed in a separate written contract.
• Developers are responsible for their own taxes, compliance, and statutory obligations as per their jurisdiction.

1.2 No Ownership Rights

Developers have no right to claim ownership of:

• The Evanto brand, domain, or company (Banglar Katha).
• Any products, projects, or platforms developed under Evanto assignments.
• Any client relationships, contracts, or revenue streams belonging to Evanto or Banglar Katha.

Developers must not represent themselves in any way as founders, co-owners, partners, directors, or official legal representatives of Evanto or Banglar Katha.

2. Work Allocation, Scope & Initiative

2.1 Task-Based Allocation

Developers will be allotted tasks such as:

• Building or updating ready-made products.
• Customizing web applications or websites for clients.
• Performing bug fixes, feature enhancements, or maintenance.

2.2 No Unapproved Voluntary Changes

Developers must:

• Work only on tasks that are assigned or approved by Evanto.
• Not make voluntary changes, additions, or experiments on live products or client projects without explicit permission, even if they believe it is an improvement.
• Propose improvements through proper channels and implement them only after approval.

2.3 Custom vs Non-Custom Work

For customized projects, specific requirements, deadlines, and expectations will be shared. For non-custom or internal tasks (like ready-made products), general specifications and guidelines will be provided. In all cases, the developer must stick to agreed scope and directions.

3. Testing Responsibility & Environment Limitations

3.1 No Dedicated Testing Environment Provided

Evanto does not guarantee a dedicated testing or development environment for every developer. In many cases:

• Developers are expected to test, build, and validate their code using their own local or personal environments.
• Basic direction or configuration information may be provided, but infrastructure setup remains the developer’s responsibility unless specifically stated otherwise.

3.2 Developer’s Own Capability & Liability

Developers must:

• Create, develop, and test projects/products using their own tools, knowledge, and capabilities.
• Ensure that code delivered is functional, secure, and reasonably tested before submission.
• Take responsibility and liability for the quality and correctness of the work they submit.

Failure to meet promised quality, timelines, or basic functionality can impact future assignments and payments.

4. No Personal Watermarks, Signatures, or Hidden Marks

Developers are strictly prohibited from inserting personal branding, such as:

• Watermarks, visible or hidden signatures, or logos in code, UI, or comments that identify them personally (outside of agreed credits).
• Links to personal websites, portfolios, or social media inside client-facing parts of the product unless explicitly approved.
• Hidden messages, tags, or digital signatures that serve as self-promotion or unauthorized attribution.

Code may contain neutral technical comments where necessary, but not promotional or self-claiming content.

5. Ratings, Reviews & Developer Reputation

Evanto may maintain an internal or platform-visible system to reflect a developer’s performance, which can include:

• Ratings based on quality, reliability, and communication.
• Short reviews or remarks about completed projects.
• Indicators of experience level or skill categories.

This system helps clients and the internal team understand a developer’s track record, especially for unknown or new developers whose credentials and services are still being established.

6. Ownership, IP & Brand Autonomy

All products developed for or under Evanto, including ready-made items and custom work, are:

• Owned by Evanto/Banglar Katha unless otherwise agreed in a specific contract.
• Part of the Evanto platform and cannot be sold, published, or rebranded by the developer as their own independent product.

Evanto is an autonomously created brand and operates independently; developer contributions do not grant them any stake or equity in the brand or company.

7. Communication, Issues & Dispute Handling

Developers must communicate clearly and promptly about:

• Delays, technical challenges, or blockers.
• Scope misunderstandings or ambiguity in requirements.
• Security concerns or potential vulnerabilities noticed during work.

Disputes about code quality, deadlines, or payment will be reviewed based on documented requirements, communication history, and actual delivered work. Evanto/Banglar Katha’s decision in such cases will be guided by fairness, project documentation, and applicable agreements.

8. Contact for Developer Rules & Opportunities

For questions about these Developer Rules or to explore freelance opportunities with Evanto, developers may contact:

Include your skills, experience, and any relevant portfolio links for faster evaluation.