In this Agreement:

Rvzsoft: means the service provider developing digital products and services under the Rvzsoft brand;

Developer: means an individual or legal entity providing software, integration, design implementation, technical development or consultancy services directly or indirectly in a project undertaken by Rvzsoft;

Project: means any digital development work undertaken by Rvzsoft for its own product or on behalf of a customer;

Deliverable: means code, designs, documents, modules, integrations, data structures or other work outputs prepared by the Developer within the project scope and submitted to Rvzsoft;

Confidential Information: means information concerning projects, customers, infrastructure, source code, access credentials, pricing, commercial processes, user data and other non-public information.

The purpose of this Agreement is to:

• establish the working arrangements between the Developer and Rvzsoft;
• ensure the protection of project information;
• regulate delivery and quality responsibilities;
• clarify the use of source code and intellectual property rights;
• ensure the protection of customer information and Personal Data;
• prevent unauthorised use and sharing.

Rvzsoft is not obliged to enter into a developer relationship with any individual or organisation.

Rvzsoft may select developers based on criteria such as:

• technical competence;
• project experience;
• security approach;
• references;
• timing;
• project requirements.

The Developer acknowledges that the professional and contact information submitted to Rvzsoft is accurate and current.

Unless separately agreed otherwise in writing, the Developer is not an employee or representative of Rvzsoft.

This Agreement does not create:

• an employment relationship;
• a partnership;
• an agency;
• a franchise;
• an equity partnership in a company.

The Developer may not make commitments binding on Rvzsoft to third parties.

The project scope may be separately established for each engagement.

The scope may include:

• the developments to be undertaken;
• the technologies to be used;
• the components to be delivered;
• milestones, where applicable;
• delivery dates;
• fees;
• the support period.

Additional work not expressly included in the agreement is not automatically considered part of the existing scope.

The Developer must take care to ensure that the work delivered is:

• operational;
• reasonably tested;
• compatible with the project architecture;
• prepared with due attention to security;
• free from unnecessary dependencies;
• maintainable and readable.

Rvzsoft has the right to review delivered code or work and request necessary corrections.

The Developer agrees to:

• use clear naming conventions;
• write code in accordance with project standards;
• avoid unnecessary code duplication;
• handle critical operations with appropriate error handling;
• implement necessary security controls.

Where Rvzsoft has specified coding standards or a project architecture, the Developer must comply with them.

The Developer may not include any of the following in software or files delivered:

• backdoors;
• concealed administrator accounts;
• spyware;
• data collection mechanisms;
• malware;
• concealed remote access;
• unauthorised tracking systems.

The Developer may access only those systems for which they have been expressly authorised for the project.

A breach of this provision constitutes a material breach of the Agreement.

Within a project, the Developer may be granted access to:

• servers;
• hosting;
• SSH;
• FTP;
• Git;
• administration panels;
• APIs;
• databases;
• customer accounts.

This information may be used only to carry out the relevant project.

The Developer may not:

• share access credentials with third parties;
• unnecessarily store them on personal systems;
• continue to use them after the project is completed.

At Rvzsoft’s request, the relevant access credentials and local copies must be deleted.

Unless Rvzsoft expressly permits otherwise, the Developer may not establish direct commercial relationships with Rvzsoft customers.

The Developer may not:

• submit a quotation directly to a Rvzsoft customer;
• propose undertaking the project outside Rvzsoft;
• direct the customer to the Developer’s own services;
• use customer information acquired through Rvzsoft for the Developer’s own commercial activities.

If communication with the customer is technically necessary, it must take place with Rvzsoft’s knowledge.

The Developer must protect all Confidential Information accessed during the project.

This includes, in particular:

• customer information;
• quotations;
• business models;
• source code;
• databases;
• server information;
• user data;
• technical architecture;
• project plans;
• products not yet published.

The Developer may use this information only for project purposes.

The confidentiality obligation continues, by its nature, after the working relationship ends.

If the Developer accesses Personal Data within the project, they may process it only within the authority and instructions given by Rvzsoft.

The Developer may not:

• use Personal Data for their own purposes;
• copy it unnecessarily;
• transfer it to unauthorised third parties;
• retain it outside the project scope.

For the purposes of KVKK, a Developer processing Personal Data on behalf of Rvzsoft and in accordance with its instructions may act as a “Data Processor”. However, if the Developer starts processing data for their own independent purposes, they may incur responsibilities as a Data Controller. KVKK

The Data Controller also bears responsibility regarding the security measures taken by third parties processing data on its behalf; the Developer must therefore implement appropriate technical and organisational measures. KVKK

The Developer agrees to:

• use secure connection methods;
• protect passwords and access credentials;
• avoid unnecessarily downloading production data to local environments;
• avoid using real user data for testing where possible;
• report security vulnerabilities without delay.

If a data breach or security issue is identified, the Developer shall notify Rvzsoft without delay.

The Developer may not transfer project access to other developers without Rvzsoft’s prior knowledge or approval.

Where the use of a subcontracted developer is permitted, the Developer is responsible for ensuring that this person complies with obligations concerning:

• confidentiality;
• security;
• data protection;
• intellectual property rights.

The Developer must review the licence terms of the following added to the project:

• open-source software;
• paid libraries;
• plug-ins;
• fonts;
• themes or templates.

Rvzsoft must be informed in advance if a licence is unsuitable for use in a commercial project or requires disclosure of source code.

The Developer may not use unlicensed or unlawful software.

The Developer may retain rights in the following owned before the project began:

• general-purpose libraries;
• pre-existing tools;
• their own general technical infrastructure.

However, the use and ownership of deliverables developed specifically within the project are determined in the relevant project quotation or work order.

Unless otherwise agreed in writing, the Developer may not deliver custom work prepared for Rvzsoft or the customer to another customer in the same form.

The use of open-source code in a project is not prohibited.

However, the Developer must review:

• the licence type;
• suitability for commercial use;
• attribution requirements;
• source code disclosure obligations.

A licence that could restrict the commercial use of the project may not be used without Rvzsoft’s explicit approval.

Code developed within the project is transferred to:

• the designated Git repository;
• the project workspace requested by Rvzsoft; or
• the designated delivery channel.

Leaving the only copy of the project code on the Developer’s personal computer is not acceptable.

The Developer provides the reasonable technical documentation required by Rvzsoft.

Source code belonging to a Rvzsoft project may not be published in the Developer’s public GitHub or similar repositories without express permission.

If a private repository is required, access must be granted only to authorised persons.

The Developer may use artificial intelligence tools when developing code or projects.

However, the following may not be sent to third-party artificial intelligence services without the necessary security assessment:

• customer secrets;
• production data;
• passwords;
• API keys;
• access tokens;
• confidential source code.

The Developer is responsible for reviewing code generated by artificial intelligence for:

• security;
• licence compliance;
• accuracy;
• compliance with project standards.

When integrating third-party APIs or services, the Developer must comply with the relevant provider’s:

• terms of use;
• API limits;
• licence provisions;
• security requirements.

API keys must not be stored in plain text in source code.

Delivered work may be reviewed by Rvzsoft.

If incomplete or defective work is identified, the Developer may be asked to make reasonable corrections.

Acceptance of a deliverable does not automatically release the Developer from all responsibility for latent or technical defects that may subsequently emerge.

If delivered work contains an error arising from the Developer’s own code and falling within the delivery scope, correction may be expected during the support period specified in the project terms.

New features or scope changes are not error corrections.

The Developer’s remuneration may be determined as:

• a fixed project fee;
• an hourly rate;
• milestone payments;
• a periodic service fee.

The fee is separately agreed in the relevant project or work order.

Unless agreed otherwise, out-of-scope work is not considered included in the existing fee.

The Developer is responsible for obligations arising from their own legal and tax status.

Payments by Rvzsoft are made in accordance with applicable legislation and the parties’ legal status.

Without the explicit permission of Rvzsoft or the customer, the Developer may not publish the project in or on:

• their own portfolio;
• their social media account;
• their website;
• their GitHub profile.

Rvzsoft’s approval must be obtained even where a project that has become public is to be used as a reference.

The Developer may not use the Rvzsoft brand, logo or other brand elements:

• as their own brand;
• in a manner suggesting a partnership;
• for unauthorised advertising or promotional purposes.

Reference statements such as “worked as a developer on a Rvzsoft project” may also be subject to Rvzsoft’s approval.

This provision does not prevent the Developer’s general professional activities.

However, the Developer may not engage in activities aimed at directly turning customers encountered through Rvzsoft into their own customers for the purpose of bypassing Rvzsoft.

This provision applies only to customer and project information acquired through the relationship with Rvzsoft.

Rvzsoft may immediately and temporarily suspend the Developer’s system access in cases of:

• serious security breaches;
• unauthorised access;
• confidentiality breaches;
• malicious code;
• unauthorised direct commercial approaches to customers;
• unauthorised sharing of project data.

Either party may end the relationship in accordance with the project or working terms.

In cases of serious breach, Rvzsoft may terminate the working relationship immediately.

Upon termination, the Developer shall:

• deliver the project files;
• return the necessary access rights and credentials;
• delete confidential project data in their possession;
• hand over outstanding technical work.

Termination of the Agreement does not extinguish obligations that must continue by their nature, such as:

• confidentiality;
• protection of Personal Data;
• intellectual property;
• protection of customer information.

Rvzsoft may amend its standard working terms in response to legislation or changes in its service structure.

For changes significantly affecting the parties’ rights in ongoing projects, the relevant project terms and applicable law are taken into account.

Project notifications between the parties may be made through:

• email;
• the project management system;
• the support system;
• other recorded written electronic communication channels.

The parties are responsible for keeping their contact information current.

This Agreement is governed by the laws of the Republic of Türkiye.

The competent authority and jurisdiction for disputes are determined under applicable legislation, taking into account the parties’ legal status and the nature of the dispute.

I have deliberately not included a fixed provision stating that “Ankara Courts shall have jurisdiction” here; specifying a particular court would not be appropriate before Rvzsoft’s legal status and the parties with whom the agreement will be concluded are clarified.

The invalidity or unenforceability of any provision of this Agreement does not affect the validity of the remaining provisions.

The invalid provision is applied, to the extent possible, in a lawful manner closest to the purpose of the Agreement.